Merge pull request #1889 from herlo/master

fixed 'recurse' typo in several locations

doc/man/salt.7

@@ -16793,7 +16793,7 @@ Return data to a redis data store
 .SH STATE FILE BACKUPS
 .sp
 In 0.10.2 a new feature was added for backing up files that are replaced by
-the file.managed and file.recuse states. The new feature is called the backup
+the file.managed and file.recurse states. The new feature is called the backup
 mode. Setting the backup mode is easy, but is can be set in a number of
 places.
 .sp
@@ -18733,7 +18733,7 @@ takes a few arguments:
 Recursive directory management can also be set via the \fBrecurse\fP
 function. Recursive directory management allows for a directory on the salt
 master to be recursively copied down to the minion. This is a great tool for
-deploying large code and configuration systems. A recuse state would look
+deploying large code and configuration systems. A recurse state would look
 something like this:
 .sp
 .nf
@@ -23760,7 +23760,7 @@ but when enabled the cache is used to make grain matching from the salt command
 more powerful, since the minions that will match can be pre determined.
 .SS Backup Files
 .sp
-By default all files replaced by the file.managed and file.recuse states we
+By default all files replaced by the file.managed and file.recurse states we
 simply deleted. 0.10.2 adds a new option. By setting the backup option to
 \fBminion\fP the files are backed up before they are replaced.
 .sp
@@ -24746,7 +24746,7 @@ Make a symlink.
 .B file.recurse
 The recurse state function will recursively download a directory on the
 master file server and place it on the minion. Any change in the files on
-the master will be pushed to the minion. The recuse function is very
+the master will be pushed to the minion. The recurse function is very
 powerful and has been tested by pushing out the full Linux kernel source.
 .sp
 .nf

doc/ref/states/backup_mode.rst

@@ -3,7 +3,7 @@ State File Backups
 ==================
 
 In 0.10.2 a new feature was added for backing up files that are replaced by
-the file.managed and file.recuse states. The new feature is called the backup
+the file.managed and file.recurse states. The new feature is called the backup
 mode. Setting the backup mode is easy, but is can be set in a number of
 places.
 

doc/topics/releases/0.10.2.rst

@@ -49,7 +49,7 @@ more powerful, since the minions that will match can be pre determined.
 Backup Files
 ------------
 
-By default all files replaced by the file.managed and file.recuse states we
+By default all files replaced by the file.managed and file.recurse states we
 simply deleted. 0.10.2 adds a new option. By setting the backup option to
 ``minion`` the files are backed up before they are replaced.
 

doc/topics/releases/0.9.3.rst

@@ -196,7 +196,7 @@ file.symlink
 file.recurse
     The recurse state function will recursively download a directory on the
     master file server and place it on the minion. Any change in the files on
-    the master will be pushed to the minion. The recuse function is very
+    the master will be pushed to the minion. The recurse function is very
     powerful and has been tested by pushing out the full Linux kernel source.
 
     .. code-block:: yaml

salt/state.py

@@ -246,7 +246,7 @@ class State(object):
         Check to see if the modules for this state instance need to be
         updated, only update if the state is a file. If the function is
         managed check to see if the file is a possible module type, e.g. a
-        python, pyx, or .so. Always refresh if the function is recuse,
+        python, pyx, or .so. Always refresh if the function is recurse,
         since that can lay down anything.
         '''
         def _refresh():

salt/states/file.py

@@ -66,7 +66,7 @@ takes a few arguments:
 Recursive directory management can also be set via the ``recurse``
 function. Recursive directory management allows for a directory on the salt
 master to be recursively copied down to the minion. This is a great tool for
-deploying large code and configuration systems. A recuse state would look
+deploying large code and configuration systems. A recurse state would look
 something like this:
 
 .. code-block:: yaml