grammar and spelling sanity check (#434)

docs/HOWTO/00_Accounts_and_Access/Redundant_LDAP.rst

@@ -96,7 +96,7 @@ Leave any other classes that are there if they are needed. Run the Puppet
 agent on the LDAP server until it runs cleanly. Run the agent on the Puppet
 server. Once all the other clients update against the Puppet server, they will
 be able to authenticate against the LDAP server. Adding users and groups is
-described in the :ref:`User_Management`.
+described in the :ref:`User_Management` section.
 
 .. NOTE::
 

docs/HOWTO/20_Puppet/Block_or_Cache_Facts.rst

@@ -5,7 +5,7 @@ As described in `Configuring Facter with facter.conf`_, you can block or cache
 groups of facts on a node using settings in :file:`facter.conf` on that node.  SIMP
 has made this easier by adding management of :file:`facter.conf` to :pupmod:`simp/pupmod`
 (version >= '8.0.0'). Using this module, you can 
-managel :file:`facter.conf` and specify its configuration in :term:`Hiera`.
+manage :file:`facter.conf` and specify its configuration in :term:`Hiera`.
 
 Here is example Hiera that blocks and caches select groups of facts:
 

docs/HOWTO/20_Puppet/Hiera_eyaml.rst

@@ -204,7 +204,7 @@ Using :command:`eyaml edit`
 
 If a user editing the :file:`.eyaml` file has access to both the private and
 public keys, they can use :command:`eyaml edit file.eyaml` as a convenient
-alternative to the :command:`eyaml encrypt` example in th previous section.
+alternative to the :command:`eyaml encrypt` example in the previous section.
 
 :command:`eyaml edit` will automatically decrypt the file and bring up an editor
 to edit the values in plaintext.  After exiting the editor, any edited values

docs/HOWTO/90_Misc/Unpack_dvd.rst

@@ -72,7 +72,7 @@ When PXE file extraction is enabled with the :code:`-X` option,
     * The default rsync directory is :file:`/var/simp/environments/production/rsync/<os-family>/Global/tftpboot/linux-install/`.
   * extract the files to the created OS directory.
   * create a link <os-family>-<major-version>-<arch> to the above directory.
-  * if run as root, change the permisions recursivley on created directoy and its contents to those of the rsync directory.
+  * if run as root, change the permissions recursively on created directory and its contents to those of the rsync directory.
 
 Use :code:`unpack_dvd --help` for options to change some of the defaults.
 

docs/changelogs/6.5.0_Changelog.rst

@@ -1216,7 +1216,7 @@ pupmod-simp-iptables
     undefined behavior and is not advised.
   * To enable 'firewalld' mode on supported operating systems, simply set
     :code:`iptables::use_firewalld` to :code:`true` via Hiera.
-  * EL 8 systems will enable 'firewalld' mode by default.
+  * EL8 systems will enable 'firewalld' mode by default.
 
 * Improved the internal rule matching to handle most netmask and port updates.
 * Added a :code:`exact_match` Boolean to the :code:`iptables_optimize` and
@@ -1344,7 +1344,7 @@ understand the current usage.  Notable feature/API changes:
 
   * Exposed server :program:`stunnel` configuration that was scattered
     throughout the module to this API.  User can now specify
-    :code:`stunnel_accept_address`, :code:`stunnel_nfsd_acccept_port`,
+    :code:`stunnel_accept_address`, :code:`stunnel_nfsd_accept_port`,
     :code:`stunnel_socket_options`, :code:`stunnel_verify`, and
     :code:`stunnel_wantedby` in this class. When unspecified, the defaults for
     all but :code:`stunnel_accept_address` and
@@ -1816,7 +1816,7 @@ pupmod-simp-simp_snmpd
     * :code:`simp_snmpd::service_config_perms`
 
   * Added configuration of :program:`snmpd` user and group IDs, as well
-    as optional managment of the user and group:
+    as optional management of the user and group:
 
     * :code:`simp_snmpd::snmpd_uid`
     * :code:`simp_snmpd::snmpd_gid`
@@ -1981,7 +1981,7 @@ Updated the following functions:
       the same characteristics.
     * Regenerates the password if the requested 'complexity' or 'complex_only'
       setting differs from the setting used for the latest persisted password.
-    * Stores up to the lastest 10 <password,salt> pairs in the password's
+    * Stores up to the latest 10 <password,salt> pairs in the password's
       simpkv metadata.
 
   * Added a :code:`gen_timeout_seconds` password option.  Previously this was
@@ -2117,7 +2117,7 @@ rubygem-simp-cli
   * Removed deprecated :code:`--non-interactive` option.  Use
     :code:`--force-defaults` instead.
 
-* Added :command:`simp kv` command family to allow users to manage and inspect
+* Added :command:`simpkv` command family to allow users to manage and inspect
   entries in a simpkv key/value store
 * :command:`simp passgen` changes
 
@@ -2254,7 +2254,7 @@ SIMP ISO
 * Fixed a bug in the instructions about enabling encryption in non-FIPS
   mode in the sample client kickstart files.
 
-  * Following the erronous instructions prevented automatic decryption from
+  * Following the erroneous instructions prevented automatic decryption from
     happening at client boot, because the encrypted disk credentials were not
     added to the :program:`dracut` configuration.
 

docs/getting_started_guide/Installation_Options/ISO/ISO_Build/Building_SIMP_From_Tarball.rst

@@ -34,7 +34,7 @@ version you need, check the :ref:`faq-simp_version_guide`.
 
 .. NOTE::
 
-   Even though the tar files are labelled as ``CentOS``, they will work
+   Even though the tar files are labeled as ``CentOS``, they will work
    properly for ``RHEL`` systems as well.
 
 Generating The ISO

docs/user_guide/Initial_Server_Configuration.rst

@@ -25,7 +25,7 @@ For a list of the commands ``simp`` provides, type ``simp help``. Type
     to apply the changes.
 
   * ``simp config`` uses the ``production`` :term:`Puppet Environment` by
-    default. If you want to use a different intial environment, see
+    default. If you want to use a different initial environment, see
     :ref:`howto-use-an-alternate-simp-config-environment`.
 
 * ``simp bootstrap`` uses several targeted Puppet runs to configure the rest

docs/user_guide/Initial_Server_Configuration/Prevent_Lockout_on_Puppetserver.inc

@@ -140,7 +140,7 @@ Resume Bootstrap Operation and Verify User Access
 
        * See :ref:`Services_dying`.
 
-#. Verify user accesss
+#. Verify user access
 
    * Using a **NEW SSH SESSION OR TERMINAL** (do NOT close your working
      session)
@@ -153,7 +153,7 @@ Resume Bootstrap Operation and Verify User Access
      If your new user cannot ssh into the server and sudo to ``root``
 
      * DO NOT reboot the server until you resolve the problem!
-     * DO NOT log out of your primary work terminal unti you resolve the
+     * DO NOT log out of your primary work terminal until you resolve the
        problem!
 
 Finalization

docs/user_guide/SIMP_Administration/Classification_and_Data/SIMP_Scenarios.inc

@@ -22,7 +22,7 @@ turned off. This scenario was designed to make it easier to implement SIMP in an
 existing environment, because it might not be trivial to flip SELinux to
 Enforcing on all nodes.
 
-The *poss* option is the barebones option. It only includes the ``pupmod``
+The *poss* option is the bare-bones option. It only includes the ``pupmod``
 class, to configure Puppet agent on clients. All of the simp_options default to
 false, so SIMP will not do a lot of modification to clients through Puppet when
 using this scenario.

docs/user_guide/SIMP_Administration/Environments/Environments_Examples.inc

@@ -229,7 +229,7 @@ Before proceeding with this section, you should
    All of these packages will already be installed if you have installed the SIMP
    server from ISO or from RPMs.
 
-   These RPMS can be obtained from an ISO or if the system has access to the internet
+   These RPMs can be obtained from an ISO or if the system has access to the internet
    the SIMP repositories can configured as described in :ref:`gsg-installing_simp_from_a_repository`.
 
    .. code-block:: bash
@@ -319,7 +319,7 @@ By default, this environment will be using a different Certificate
 Authority for  :ref:`Infrastructure Certificates<ug-sa-ga-infrastructure-certificates>`. It
 therefore may not be able to communicate to a server in another environment when
 certificate authentication is required,  for example LDAP.  You will have to create a new LDAP server
-or add the new CA to the list of trusted CA's in the other environment.
+or add the new CA to the list of trusted CAs in the other environment.
 
 This environment will also generate a new set of passwords when ``simplib::passgen`` function is
 used in a Puppet module.  It therefore may not be able to talk to a server in another environment

docs/user_guide/Upgrade_SIMP/Version_Maps/6.3.3_6.4.0.inc

@@ -96,7 +96,7 @@ Upgrade Steps
 These steps for upgrading are for use in SIMP systems that are not currently using
 :term:`r10k` or :term:`Code Manager`.
 
-Update OS and SIMP RPMS
+Update OS and SIMP RPMs
 """""""""""""""""""""""
 
 Update the repos for the :term:`OS` and SIMP and run :command:`yum update`.

docs/user_guide/User_Management/LDAP/389_DS/manage_groups.rst

@@ -1,7 +1,7 @@
 .. _ug-user_management-ldap-389_ds-manage_groups:
 
 Group Management in 389-DS
-=========================
+==========================
 
 List 389-DS Groups
 ------------------