Fix spelling error: recieve -> receive

doc/man/salt-minion.1

@@ -31,13 +31,13 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" Man page generated from reStructeredText.
 .
 .sp
-The salt minion daemon, recieves commands from a remote salt master.
+The salt minion daemon, receives commands from a remote salt master.
 .SH SYNOPSIS
 .sp
 salt\-minion [ options ]
 .SH DESCRIPTION
 .sp
-The salt minion recieves commands from the central salt master and replies with
+The salt minion receives commands from the central salt master and replies with
 the results of said commands.
 .SH OPTIONS
 .INDENT 0.0

doc/man/salt.7

@@ -794,7 +794,7 @@ Default: \fBFalse\fP
 Open mode is a dangerous security feature. One problem encountered with pki
 authentication systems is that keys can become "mixed up" and authentication
 begins to fail. Open mode turns off authentication and tells the master to
-accept all authentication. This will clean up the pki keys recieved from the
+accept all authentication. This will clean up the pki keys received from the
 minions. Open mode should not be turned on for general use, open mode should
 only be used for a short period of time to clean up pki keys. To turn on open
 mode the value passed must be \fBTrue\fP.
@@ -1022,7 +1022,7 @@ disable_modules: [cmd,virt,test]
 .sp
 Default: \fBFalse\fP
 .sp
-Open mode can be used to clean out the pki key recieved from the salt master,
+Open mode can be used to clean out the pki key received from the salt master,
 turn on open mode, restart the minion, then turn off open mode and restart the
 minion to clean the keys.
 .sp
@@ -1136,13 +1136,13 @@ The master configuration file to use, the default is /etc/salt/master
 .UNINDENT
 .SS \fBsalt\-minion\fP
 .sp
-The salt minion daemon, recieves commands from a remote salt master.
+The salt minion daemon, receives commands from a remote salt master.
 .SS Synopsis
 .sp
 salt\-minion [ options ]
 .SS Description
 .sp
-The salt minion recieves commands from the central salt master and replies with
+The salt minion receives commands from the central salt master and replies with
 the results of said commands.
 .SS Options
 .INDENT 0.0
@@ -2859,7 +2859,7 @@ This is where the returner interface comes in. Returners are modules called
 in place of returning the data to the salt master.
 .sp
 The returner interface allows the return data to be sent to any system that
-can recieve data. This means that return data can be sent to a Redis server,
+can receive data. This means that return data can be sent to a Redis server,
 a MongoDB server, a MySQL server, or any system!
 .IP "See also"
 .sp

doc/ref/cli/salt-minion.rst

@@ -2,7 +2,7 @@
 ``salt-minion``
 ===============
 
-The salt minion daemon, recieves commands from a remote salt master.
+The salt minion daemon, receives commands from a remote salt master.
 
 Synopsis
 ========
@@ -12,7 +12,7 @@ salt-minion [ options ]
 Description
 ===========
 
-The salt minion recieves commands from the central salt master and replies with
+The salt minion receives commands from the central salt master and replies with
 the results of said commands.
 
 Options

doc/ref/configuration/index.rst

@@ -156,7 +156,7 @@ Default: ``False``
 Open mode is a dangerous security feature. One problem encountered with pki
 authentication systems is that keys can become "mixed up" and authentication
 begins to fail. Open mode turns off authentication and tells the master to
-accept all authentication. This will clean up the pki keys recieved from the
+accept all authentication. This will clean up the pki keys received from the
 minions. Open mode should not be turned on for general use, open mode should
 only be used for a short period of time to clean up pki keys. To turn on open
 mode the value passed must be ``True``.
@@ -427,7 +427,7 @@ and cannot be disabled.
 
 Default: ``False``
 
-Open mode can be used to clean out the pki key recieved from the salt master,
+Open mode can be used to clean out the pki key received from the salt master,
 turn on open mode, restart the minion, then turn off open mode and restart the
 minion to clean the keys.
 

doc/ref/returners/index.rst

@@ -17,7 +17,7 @@ This is where the returner interface comes in. Returners are modules called
 in place of returning the data to the salt master.
 
 The returner interface allows the return data to be sent to any system that
-can recieve data. This means that return data can be sent to a Redis server,
+can receive data. This means that return data can be sent to a Redis server,
 a MongoDB server, a MySQL server, or any system!
 
 .. seealso:: :doc:`Full list of builtin returners <returners>`

doc/topics/specs/salt_auth_proto_abs.rst

@@ -23,7 +23,7 @@ The message itself is abstracted as a python dict in this fashion:
     {'enc': 'aes',
      'load': <encrypted python pickle>}
 
-When this message is recieved the load can be decrypted using the shared AES
+When this message is received the load can be decrypted using the shared AES
 key. The 'enc' dict ket can also be "pub" for pubkey encryption, or "clear"
 for passing messages in the clear.
 
@@ -60,7 +60,7 @@ the minion subscriber to the master publisher.
 All messages sent from the publisher are encypted using the revolving AES key,
 in the event that the master restarts the minions will all have an invalid
 AES key because it has been regenerated on the master. The master will then
-send out a publication that the minions cannot decrypt. If the minion recieves
+send out a publication that the minions cannot decrypt. If the minion receives
 a publication that cannot be decrypted then the minion will re-authenticate,
 obtain the correct AES key, and decrypt the message. This means that the
 AES key on the salt master can safely revolve without inturupting the minion