doc: uppercase RPC

runtime/doc/develop.txt

@@ -171,8 +171,8 @@ functions in eval.c:
   (vimscript) to check if features are available.
 
 The provider#(name)#Call function implements integration with an external
-system, because calling shell commands and |rpc| clients are easier to work
-with in vimscript.
+system, because shell commands and |RPC| clients are easier to work with in
+vimscript.
 
 For example, the Python provider is implemented by the
 autoload/provider/python.vim script; the provider#python#Call function is only

runtime/doc/eval.txt

@@ -2030,11 +2030,11 @@ resolve({filename})		String	get filename a shortcut points to
 reverse({list})		List	reverse {list} in-place
 round({expr})			Float	round off {expr}
 rpcnotify({channel}, {event}[, {args}...])
-				Sends a |rpc| notification to {channel}
+				Sends an |RPC| notification to {channel}
 rpcrequest({channel}, {method}[, {args}...])
-				Sends a |rpc| request to {channel}
-rpcstart({prog}[, {argv}])	Spawns {prog} and opens a |rpc| channel
-rpcstop({channel})		Closes a |rpc| {channel}
+				Sends an |RPC| request to {channel}
+rpcstart({prog}[, {argv}])	Spawns {prog} and opens an |RPC| channel
+rpcstop({channel})		Closes an |RPC| {channel}
 screenattr({row}, {col})	Number	attribute at screen position
 screenchar({row}, {col})	Number	character at screen position
 screencol()			Number	current cursor column
@@ -5525,20 +5525,20 @@ round({expr})							*round()*
 <			-5.0
 
 rpcnotify({channel}, {event}[, {args}...])		  {Nvim} *rpcnotify()*
-		Sends {event} to {channel} via |rpc| and returns immediately.
+		Sends {event} to {channel} via |RPC| and returns immediately.
 		If {channel} is 0, the event is broadcast to all channels.
 		Example: >
 			:au VimLeave call rpcnotify(0, "leaving")
 
 rpcrequest({channel}, {method}[, {args}...])		 {Nvim} *rpcrequest()*
 		Sends a request to {channel} to invoke {method} via
-		|rpc| and blocks until a response is received.
+		|RPC| and blocks until a response is received.
 		Example: >
 			:let result = rpcrequest(rpc_chan, "func", 1, 2, 3)
 
 rpcstart({prog}[, {argv}])				   {Nvim} *rpcstart()*
 		Spawns {prog} as a job (optionally passing the list {argv}),
-		and opens an |rpc| channel with the spawned process's
+		and opens an |RPC| channel with the spawned process's
 		stdin/stdout. Returns:
 		  - channel id on success, which is used by |rpcrequest()|,
 		    |rpcnotify()| and |rpcstop()|
@@ -5547,7 +5547,7 @@ rpcstart({prog}[, {argv}])				   {Nvim} *rpcstart()*
 			:let rpc_chan = rpcstart('prog', ['arg1', 'arg2'])
 
 rpcstop({channel})					    {Nvim} *rpcstop()*
-		Closes an |rpc| {channel}, possibly created via
+		Closes an |RPC| {channel}, possibly created via
 		|rpcstart()|. Also closes channels created by connections to
 		|v:servername|.
 

runtime/doc/msgpack_rpc.txt

@@ -4,7 +4,7 @@
 		 NVIM REFERENCE MANUAL    by Thiago de Arruda
 
 
-RPC API for Nvim					  *rpc*  *msgpack-rpc*
+RPC API for Nvim				     *RPC* *rpc* *msgpack-rpc*
 
 1. Introduction			|rpc-intro|
 2. API mapping			|rpc-api|

runtime/doc/provider.txt

@@ -12,7 +12,7 @@ Nvim delegates some features to dynamic "providers".
 Python integration		    	      *provider-python*
 
 Nvim supports the Vim legacy |python-vim| and |python3| interfaces via
-external Python interpreters connected via |rpc|,
+external Python interpreters connected via |RPC|,
 
 Note: Only the Vim 7.3 API is supported; bindeval (Vim 7.4) is not.
 

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.