Address spelling errors while running CI checks.

docs/inventories.rst

@@ -226,7 +226,7 @@ To create an inventory with Ansible facts, you need to run a playbook against th
 Filter on environment variables
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-An example problem is demonstrated here that involves filtering on env vars using the yaml format:
+An example problem is demonstrated here that involves filtering on environment variables using the yaml format:
 
 ``source_vars``:
 
@@ -280,7 +280,7 @@ The ``host_filter`` parameter allows for:
 - use of the boolean and operator:
 
   - ``__`` to reference related fields in relational fields
-  - ``__`` is used on ansible_facts to separate keys in a JSON key path
+  - ``__`` is used on ``ansible_facts`` to separate keys in a JSON key path
   - ``[]`` is used to denote a json array in the path specification
   - ``""`` can be used in the value when spaces are wanted in the value
 
@@ -328,8 +328,8 @@ If a search term in ``host_filter`` is of string type, to make the value a numbe
 
 .. _ug_host_filter_facts:
 
-Define host filter with ansible_facts
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Define host filter with ``ansible_facts``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To use ``ansible_facts`` to define the host filter, perform the following steps:
 
@@ -592,7 +592,7 @@ This opens the Create Source window.
 
 6. Use the **Host Filter** field to specify only matching host names to be imported into AWX.
 
-7. In the **Enabled Variable**, specify AWX to retrieve the enabled state from the given dictionary of host variables. The enabled variable may be specified using dot notation as 'foo.bar', in which case the lookup will traverse into nested dicts, equivalent to: ``from_dict.get('foo', {}).get('bar', default)``.
+7. In the **Enabled Variable**, specify AWX to retrieve the enabled state from the given dictionary of host variables. The enabled variable may be specified using dot notation as 'foo.bar', in which case the lookup will traverse into nested dictionaries, equivalent to: ``from_dict.get('foo', {}).get('bar', default)``.
 
 8. If you specified a dictionary of host variables in the **Enabled Variable** field, you can provide a value to enable on import. For example, if ``enabled_var='status.power_state'`` and ``enabled_value='powered_on'`` with the following host variables, the host would be marked enabled:
 
@@ -758,7 +758,7 @@ The Run command window opens.
 
 - **Arguments**: Provide arguments to be used with the module you selected.
 - **Limit**: Enter the limit used to target hosts in the inventory. To target all hosts in the inventory enter ``all`` or ``*``, or leave the field blank. This is automatically populated with whatever was selected in the previous view prior to clicking the launch button.
-- **Machine Credential**: Select the credential to use when accessing the remote hosts to run the command. Choose the credential containing the username and SSH key or password that Ansbile needs to log into the remote hosts.
+- **Machine Credential**: Select the credential to use when accessing the remote hosts to run the command. Choose the credential containing the username and SSH key or password that Ansible needs to log into the remote hosts.
 - **Verbosity**: Select a verbosity level for the standard output.
 - **Forks**: If needed, select the number of parallel or simultaneous processes to use while executing the command.
 - **Show Changes**: Select to enable the display of Ansible changes in the standard output. The default is OFF.

docs/inventory-plugins.rst

@@ -96,7 +96,7 @@ An inventory that is sourced from a project means that is uses the SCM type from
 
 2. The Create Source window expands with additional fields. Enter the following details:
 
-  - **Source Control Branch/Tag/Commit**: Optionally enter the SCM branch, tags, commit hashes, arbitrary refs, or revision number (if applicable) from the source control (Git or Subversion) to checkout. Some commit hashes and refs may not be available unless you also provide a custom refspec in the next field. If left blank, the default is HEAD which is the last checked out Branch/Tag/Commit for this project.
+  - **Source Control Branch/Tag/Commit**: Optionally enter the SCM branch, tags, commit hashes, arbitrary refs, or revision number (if applicable) from the source control (Git or Subversion) to checkout. Some commit hashes and refs may not be available unless you also provide a custom ref spec in the next field. If left blank, the default is HEAD which is the last checked out Branch/Tag/Commit for this project.
 
     This field only displays if the sourced project has the **Allow Branch Override** option checked.
 

docs/spelling_wordlist.txt

@@ -13,19 +13,23 @@ ec2
 edu
 Hashi
 hasn
+hostvars
 https
+ini
 Kerberos
 keylogging
 Kubernetes
 lookups
 namespace
+natively
 OAuth
 OpenShift
 Ovirt
 ovirt
 PEM
 Pre
 pre
+selinux
 Submodules
 Subpackages
 sudo