Minor spelling fixes

4 files changed, 5 insertions, 5 deletions

diff --git a/docsite/rst/examples.rst b/docsite/rst/examples.rst
index 43ebbd70bd..6c25b56bc9 100644
--- a/docsite/rst/examples.rst
+++ b/docsite/rst/examples.rst
@@ -226,7 +226,7 @@ also works with ``ansible-playbook``::
 
     $ ansible webservers:dbservers -m command -a "/bin/foo xyz" --limit region
 
-Assuming version 0.9 or later, as with other host patterns, values to limit can be seperated with ";", ":", or ",".
+Assuming version 0.9 or later, as with other host patterns, values to limit can be separated with ";", ":", or ",".
 
 Now let's talk about range selection.   Suppose you have 1000 servers in group 'datacenter', but only want to target one at a time.  This is also easy::
 
diff --git a/docsite/rst/patterns.rst b/docsite/rst/patterns.rst
index c5fc8be0fe..475484e9ff 100644
--- a/docsite/rst/patterns.rst
+++ b/docsite/rst/patterns.rst
@@ -185,7 +185,7 @@ variables to groups.  These variables can be used by /usr/bin/ansible-playbook,
    southeast
 
 If you need to store lists or hash data, or prefer to keep host and group specific variables
-seperate from the inventory file, see the next section.
+separate from the inventory file, see the next section.
 
 Splitting Out Host and Group Specific Data
 ++++++++++++++++++++++++++++++++++++++++++
diff --git a/docsite/rst/playbooks.rst b/docsite/rst/playbooks.rst
index 195715ca78..64db86a08d 100644
--- a/docsite/rst/playbooks.rst
+++ b/docsite/rst/playbooks.rst
@@ -414,7 +414,7 @@ Tips and Tricks
 
 Look at the bottom of the playbook execution for a summary of the nodes that were executed
 and how they performed.   General failures and fatal "unreachable" communication attempts are
-kept seperate in the counts.
+kept separate in the counts.
 
 If you ever want to see detailed output from successful modules as well as unsuccessful ones,
 use the '--verbose' flag.  This is available in Ansible 0.5 and later.
diff --git a/docsite/rst/playbooks2.rst b/docsite/rst/playbooks2.rst
index ae90f011b9..0aa8e52fec 100644
--- a/docsite/rst/playbooks2.rst
+++ b/docsite/rst/playbooks2.rst
@@ -324,7 +324,7 @@ In Ansible 0.8, a few shortcuts are available for testing whether a variable is
 
 There is a matching 'is_unset' that works the same way.  Quoting the variable inside the function is mandatory.
 
-When combining `only_if` with `with_items`, be aware that the `only_if` statement is processed seperately for each item.
+When combining `only_if` with `with_items`, be aware that the `only_if` statement is processed separately for each item.
 This is by design::
 
     tasks:
@@ -343,7 +343,7 @@ Conditional Execution (Simplified)
 
 In Ansible 0.9, we realized that only_if was a bit syntactically complicated, and exposed too much Python
 to the user.  As a result, the 'when' set of keywords was added.  The 'when' statements do not have
-to be quoted or casted to specify types, but you should seperate any variables used with whitespace.  In
+to be quoted or casted to specify types, but you should separate any variables used with whitespace.  In
 most cases users will be able to use 'when', but for more complex cases, only_if may still be required.
 
 Here are various examples of 'when' in use.  'when' is incompatible with 'only_if' in the same task::