aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc/remote_plugin.txt
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc/remote_plugin.txt')
-rw-r--r--runtime/doc/remote_plugin.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/doc/remote_plugin.txt b/runtime/doc/remote_plugin.txt
index 3a2215f11c..d906096a86 100644
--- a/runtime/doc/remote_plugin.txt
+++ b/runtime/doc/remote_plugin.txt
@@ -16,7 +16,7 @@ Nvim support for remote plugins *remote-plugin*
Extensibility is a primary goal of Nvim. Any programming language may be used
to extend Nvim without changes to Nvim itself. This is achieved with remote
-plugins, coprocesses that have a direct communication channel (via |rpc|) with
+plugins, coprocesses that have a direct communication channel (via |RPC|) with
the Nvim process.
Even though these plugins run in separate processes they can call, be called,
@@ -33,7 +33,7 @@ check whether a plugin host is available for their chosen programming language.
Plugin hosts are programs that provide a high-level environment for plugins,
taking care of most boilerplate involved in defining commands, autocmds, and
-functions that are implemented over |rpc| connections. Hosts are loaded only
+functions that are implemented over |RPC| connections. Hosts are loaded only
when one of their registered plugins require it, keeping Nvim's startup as
fast as possible, even if many plugins/hosts are installed.