diff --git a/doc/source/deploy_install_guides/release/modify-the-kernel-in-the-cli-39f25220ec1b.rst b/doc/source/deploy_install_guides/release/modify-the-kernel-in-the-cli-39f25220ec1b.rst index 2614f8605..c2eca717c 100644 --- a/doc/source/deploy_install_guides/release/modify-the-kernel-in-the-cli-39f25220ec1b.rst +++ b/doc/source/deploy_install_guides/release/modify-the-kernel-in-the-cli-39f25220ec1b.rst @@ -66,7 +66,7 @@ The Kernel can be configured during runtime as [ standard <-> lowlatency ]. +--------------------+--------------+ -Modify Kernel using the Ansible Bootstarp yaml +Modify Kernel using the Ansible Bootstrap yaml ---------------------------------------------- Add the following line to you ``localhost.yaml`` file that is used to bootstrap diff --git a/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst b/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst index b73c4411e..c97117151 100644 --- a/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst +++ b/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst @@ -16,7 +16,7 @@ User Types - **'sysadmin' Linux User** - The 'sysadmin' linux user is a special-case user for intial install only. + The 'sysadmin' linux user is a special-case user for initial install only. - **System Administrators** diff --git a/doc/source/security/kubernetes/linux-accounts-password-3dcad436dce4.rst b/doc/source/security/kubernetes/linux-accounts-password-3dcad436dce4.rst index e77d8baa2..fa49e3ce6 100644 --- a/doc/source/security/kubernetes/linux-accounts-password-3dcad436dce4.rst +++ b/doc/source/security/kubernetes/linux-accounts-password-3dcad436dce4.rst @@ -17,8 +17,8 @@ password expiry settings you want to view. .. rubric:: Change Password Expiry Settings -To change the password expiry period of Linux accounts, run the :command:`chage` -command, as bellow: +To change the password expiry period of Linux accounts, run the +:command:`chage` command, as below: .. code-block:: none diff --git a/doc/source/storage/kubernetes/install-rook-ceph-a7926a1f9b70.rst b/doc/source/storage/kubernetes/install-rook-ceph-a7926a1f9b70.rst index 1f840adbc..bdea3abf2 100644 --- a/doc/source/storage/kubernetes/install-rook-ceph-a7926a1f9b70.rst +++ b/doc/source/storage/kubernetes/install-rook-ceph-a7926a1f9b70.rst @@ -193,8 +193,8 @@ You can check the pods of the storage cluster running the following command: kubectl get pod -n rook-ceph -Instalation on Simplex with controller model, 1 monitor, installing manually, services: block and cephfs --------------------------------------------------------------------------------------------------------- +Installation on Simplex with controller model, 1 monitor, installing manually, services: block and cephfs +--------------------------------------------------------------------------------------------------------- In this configuration, you can add monitors and |OSDs| on the Simplex node. diff --git a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst index 6eb85b893..0bab17de3 100644 --- a/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst +++ b/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-the-cli.rst @@ -104,7 +104,7 @@ Modify the pool, in this example ``oam-ipv6``, using the following parameters: .. note:: If the system is dual-stack open a ssh session via the other |OAM| network - configured before proceding, to not loose the connection. + configured before proceeding, to not loose the connection. .. code-block:: none diff --git a/doc/source/system_configuration/kubernetes/redundant-system-clock-synchronization-89ee23f54fbb.rst b/doc/source/system_configuration/kubernetes/redundant-system-clock-synchronization-89ee23f54fbb.rst index 2b2e42097..3af93e09e 100644 --- a/doc/source/system_configuration/kubernetes/redundant-system-clock-synchronization-89ee23f54fbb.rst +++ b/doc/source/system_configuration/kubernetes/redundant-system-clock-synchronization-89ee23f54fbb.rst @@ -84,7 +84,7 @@ sources, and manage and monitor the ``phc2sys`` application. cmdline_opts='-w' #. Assign required interface parameters. The ``ha_domainNumber`` parameter can - be ommitted if a shared domain number is used and is configured under the + be omitted if a shared domain number is used and is configured under the global instance parameters. .. code-block:: none diff --git a/doc/source/updates/kubernetes/patch-release-deployment-before-bootstrap-and-commissioning-of-7d0a97144db8.rst b/doc/source/updates/kubernetes/patch-release-deployment-before-bootstrap-and-commissioning-of-7d0a97144db8.rst index 714f05a84..788ebcab9 100644 --- a/doc/source/updates/kubernetes/patch-release-deployment-before-bootstrap-and-commissioning-of-7d0a97144db8.rst +++ b/doc/source/updates/kubernetes/patch-release-deployment-before-bootstrap-and-commissioning-of-7d0a97144db8.rst @@ -9,13 +9,13 @@ Deployment of Patch Releases before Bootstrap and Commissioning of initial Insta .. rubric:: |context| -When initially installing a |prod-long| system, occassionally it is required +When initially installing a |prod-long| system, occasionally it is required to deploy the latest available patch release for the major release being deployed. The patch releases should be deployed using the procedure below. -- *AFTER* the intial install of software on the first host +- *AFTER* the initial install of software on the first host (controller-0), and - *BEFORE* running the Ansible Bootstrap Playbook and configuring and