From a681e35c0ef1c94bf909e5988a1342bcc5a411e4 Mon Sep 17 00:00:00 2001 From: besawn <38794505+besawn@users.noreply.github.com> Date: Fri, 11 Feb 2022 07:54:30 -0500 Subject: [PATCH] Spelling fixes in admin-guides/manage_clusters/common docs --- .../common/deployment/additionalpkg/nonubuntu_os_pkg.rst | 2 +- .../manage_clusters/common/deployment/create_img.rst | 2 +- .../manage_clusters/common/deployment/driver_update_disk.rst | 2 +- .../common/deployment/network/cfg_network_bridge.rst | 2 +- .../common/deployment/network/cfg_network_vlan.rst | 2 +- .../common/deployment/prepostscripts/postinstall_script.rst | 2 +- .../common/deployment/syncfile/syncfile_synclist_file.rst | 2 +- .../common/deployment/syncfile/syncfile_xdcp.rst | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/additionalpkg/nonubuntu_os_pkg.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/additionalpkg/nonubuntu_os_pkg.rst index 09003fc57..7380332a9 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/additionalpkg/nonubuntu_os_pkg.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/additionalpkg/nonubuntu_os_pkg.rst @@ -82,7 +82,7 @@ Group/Pattern Names It is only supported for stateful deployment. -In Linux, a groups of rpms can be packaged together into one package. It is called a group on RedHat, CentOS, Fedora and Scientific Linux. To get the a list of available groups, run +In Linux, a groups of rpms can be packaged together into one package. It is called a group on RedHat, CentOS, Fedora and Scientific Linux. To get the list of available groups, run * **[RHEL]** :: diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/create_img.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/create_img.rst index fcf2cafb4..f27c2e7bf 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/create_img.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/create_img.rst @@ -79,7 +79,7 @@ If this is the same distro version as what your management node uses, create a ` enabled=1 gpgcheck=0 -This way, if you need to install some additional RPMs into your MN later, you can simply install them with ``yum``. Or if you are installing a software on your MN that depends some RPMs from this disto, those RPMs will be found and installed automatically. +This way, if you need to install some additional RPMs into your MN later, you can simply install them with ``yum``. Or if you are installing a software on your MN that depends some RPMs from this distro, those RPMs will be found and installed automatically. **[Tips 2]** diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/driver_update_disk.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/driver_update_disk.rst index 2a31a51cc..834afb0c9 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/driver_update_disk.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/driver_update_disk.rst @@ -79,7 +79,7 @@ If 'osupdatename' is specified, the kernel shipped with the 'osupdatename' will - If putting the driver disk in /driverdisk//: -Running 'nodeset ' in anyway will load the driver disk +Running 'nodeset ' in anyway will load the driver disk .. END_inject_into_initrd__for_diskful_for_DUD diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_bridge.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_bridge.rst index 816e8fc08..bd3c36fd9 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_bridge.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_bridge.rst @@ -4,7 +4,7 @@ Configure Bridge Based On Ethernet NIC The following example set the xCAT properties for compute node ``cn1`` to create: * Compute node ``cn1`` has one physical NIC: eth1 - * User wants to confgure 1 bridge br1 based on eth1 + * User wants to configure 1 bridge br1 based on eth1 * Assign ip ``30.5.106.9`` to br0 Add network object into the networks table diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_vlan.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_vlan.rst index 65ee1de30..7263956d0 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_vlan.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_vlan.rst @@ -4,7 +4,7 @@ Configure VLAN Based on Ethernet Adapter The following example set the xCAT properties for compute node ``cn1`` to create: * Compute node ``cn1`` has one physical NIC: eth0 - * Confgure 2 vlans: eth0.6 and eth0.7 based on eth0 + * Configure 2 vlans: eth0.6 and eth0.7 based on eth0 * Assign ip ``60.5.106.9`` to eth0.6 and ``70.5.106.9`` to eth0.7 Define the additional networks to xCAT diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/prepostscripts/postinstall_script.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/prepostscripts/postinstall_script.rst index d3066b65c..15f9fe40c 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/prepostscripts/postinstall_script.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/prepostscripts/postinstall_script.rst @@ -32,7 +32,7 @@ When do ``postinstall`` scripts run? High level flow of ``genimage`` process: a) install the packages specified by ``pkglist`` into ``rootimgdir`` directory -b) cumstomize the ``rootimgdir`` directory +b) customize the ``rootimgdir`` directory c) generate the initrd based on the ``rootimgdir`` directory The ``postinstall`` scripts are executed in step b). diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_synclist_file.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_synclist_file.rst index 77b42e398..766dcdd5b 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_synclist_file.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_synclist_file.rst @@ -115,7 +115,7 @@ The **EXECUTE** clause is used to list all the postsync scripts (.post **EXECUTEALWAYS** -The **EXECUTEALWAYS** clause is used to list all the postsync scripts you would like to run after the files are synced, whether or not any file is actually updated. The files in this list must be added to the list of files to sync. If noderange is used in the synclist for the file listed in the **EXECUTEALWAYS** clause, the script will only be exectuted on the nodes in that noderange. +The **EXECUTEALWAYS** clause is used to list all the postsync scripts you would like to run after the files are synced, whether or not any file is actually updated. The files in this list must be added to the list of files to sync. If noderange is used in the synclist for the file listed in the **EXECUTEALWAYS** clause, the script will only be executed on the nodes in that noderange. .. note:: The path to the file to EXECUTE or EXECUTEALWAYS, is the location of the file on the MN. diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_xdcp.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_xdcp.rst index 41cc01990..3056741b0 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_xdcp.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/syncfile/syncfile_xdcp.rst @@ -25,7 +25,7 @@ For Linux nodes, you can use ``xdcp`` command **-i** option with **-F** to sync xdcp -i /install/////rootimg -F /install/custom///.synclist -You can use the ``xdcp`` **-s** option to sync the files only to the service nodes for the node group named **compute**. The files will be placed in the default **/var/xcat/syncfiles** directory or in the directory as indicated in the **site.SNsyncfiledir** attribute. If you want the files synched to the same directory on the service node that they come from on the Management Node, set **site.SNsyncfiledir=/** attribute. This can be setup before a node install, to have the files available to be synced during the install: :: +You can use the ``xdcp`` **-s** option to sync the files only to the service nodes for the node group named **compute**. The files will be placed in the default **/var/xcat/syncfiles** directory or in the directory as indicated in the **site.SNsyncfiledir** attribute. If you want the files synced to the same directory on the service node that they come from on the Management Node, set **site.SNsyncfiledir=/** attribute. This can be setup before a node install, to have the files available to be synced during the install: :: xdcp compute -s -F /install/custom///.synclist