Fixed the Acrolinx score

Author: Padmalathas

articles/cyclecloud/slurm-3.md

@@ -11,15 +11,15 @@ ms.author: anhoward
 Slurm scheduler support was rewritten as part of the CycleCloud 8.4.0 release. Key features include:
 
 * Support for dynamic nodes, and dynamic partitions via dynamic nodearays, supporting both single and multiple virtual machine (VM) sizes
-* New slurm versions 23.02 and 22.05.8
+* New Slurm versions 23.02 and 22.05.8
 * Cost reporting via `azslurm` CLI
 * `azslurm` cli based autoscaler
 * Ubuntu 20 support
 * Removed need for topology plugin, and therefore also any submit plugin
 
 ## Slurm Clusters in CycleCloud versions < 8.4.0
 
-See [Transitioning from 2.7 to 3.0](#transitioning-from-27-to-30) for more information.
+For more information, see [Transitioning from 2.7 to 3.0](#transitioning-from-27-to-30).
 
 ### Making Cluster Changes
 
@@ -30,13 +30,13 @@ The Slurm cluster deployed in CycleCloud contains a cli called `azslurm` to faci
       # azslurm scale
 ```
 
-This creates the partitions with the correct number of nodes, the proper `gres.conf` and restart the `slurmctld`.
+The command creates the partitions with the correct number of nodes, the proper `gres.conf` and restart the `slurmctld`.
 
-### No longer pre-creating execute nodes
+### No longer precreating execute nodes
 
-Starting CycleCloud version 3.0.0 Slurm project, the nodes aren't pre-creating. Nodes are created when `azslurm resume` is invoked, or by manually creating them in CycleCloud using CLI.
+Starting CycleCloud version 3.0.0 Slurm project, the nodes aren't precreating. Nodes are created when `azslurm resume` is invoked, or by manually creating them in CycleCloud using CLI.
 
-### Creating additional partitions
+### Creating extra partitions
 
 The default template that ships with Azure CycleCloud has three partitions (`hpc`, `htc` and `dynamic`), and you can define custom nodearrays that map directly to Slurm partitions. For example, to create a GPU partition, add the following section to your cluster template:
 
@@ -60,8 +60,7 @@ The default template that ships with Azure CycleCloud has three partitions (`hpc
 
 ### Dynamic Partitions
 
-Starting CycleCloud version 3.0.1, we support dynamic partitions. You can make a `nodearray` map to a dynamic partition by adding the following.
-Note that `myfeature` could be any desired feature description or more than one feature, separated by a comma.
+Starting CycleCloud version 3.0.1, we support dynamic partitions. You can make a `nodearray` map to a dynamic partition by adding the following. The `myfeature` could be any desired feature description or more than one feature, separated by a comma.
 
 ```ini
       [[[configuration]]]
@@ -72,7 +71,7 @@ Note that `myfeature` could be any desired feature description or more than one
       slurm.dynamic_config := "-Z --conf \"Feature=myfeature\""
 ```
 
-This generates a dynamic partition like the following
+The shared code snip generates a dynamic partition like the following
 
 ```ini
 # Creating dynamic nodeset and partition using slurm.dynamic_config=-Z --conf "Feature=myfeature"
@@ -82,9 +81,9 @@ PartitionName=mydynamicpart Nodes=mydynamicns
 
 ### Using Dynamic Partitions to Autoscale
 
-By default, dynamic partition deosn't inclue any nodes. You can start nodes through CycleCloud or by running `azslurm resume` manually, they'll join the cluster using the name you choose. However, since Slurm isn't aware of these nodes ahead of time, it can't autoscale them up.
+By default, dynamic partition doesn't include any nodes. You can start nodes through CycleCloud or by running `azslurm resume` manually, they join the cluster using the name you choose. However, since Slurm isn't aware of these nodes ahead of time, it can't autoscale them up.
 
-Instead, you can also pre-create node records like so, which allows Slurm to autoscale them up.
+Instead, you can also precreate node records like so, which allows Slurm to autoscale them up.
 
 ```bash
 scontrol create nodename=f4-[1-10] Feature=myfeature State=CLOUD
@@ -100,7 +99,7 @@ scontrol create nodename=f4-[1-10] Feature=myfeature,Standard_F4 State=CLOUD
 scontrol create nodename=f8-[1-10] Feature=myfeature,Standard_F8 State=CLOUD
 ```
 
-Either way, once you have created these nodes in a `State=Cloud` they're now available to autoscale like other nodes.
+Either way, once you create these nodes in a `State=Cloud` they become available for autoscaling like other nodes.
 
 To support **multiple VM sizes in a CycleCloud nodearray**, you can alter the template to allow multiple VM sizes by adding `Config.Mutiselect = true`.
 
@@ -113,19 +112,19 @@ To support **multiple VM sizes in a CycleCloud nodearray**, you can alter the te
         Config.Multiselect = true
 ```
 
-### Dynamic Scaledown
+### Dynamic Scale down
 
-By default, all nodes in the dynamic partition scales down just like the other partitions. To disable this, see [SuspendExcParts](https://slurm.schedmd.com/slurm.conf.html).
+By default, all nodes in the dynamic partition scales down just like the other partitions. To disable dynamic partition, see [SuspendExcParts](https://slurm.schedmd.com/slurm.conf.html).
 
 ### Manual scaling
 
-If cyclecloud_slurm detects that autoscale is disabled (SuspendTime=-1), it uses the FUTURE state to denote nodes that're powered down instead of relying on the power state in Slurm. That is, when autoscale is enabled, off nodes are denoted as `idle~` in sinfo. When autoscale is disabled, the off nodes will not appear in sinfo at all. You can still see their definition with `scontrol show nodes --future`.
+If cyclecloud_slurm detects that autoscale is disabled (SuspendTime=-1), it uses the FUTURE state to denote nodes that're powered down instead of relying on the power state in Slurm. That is, when autoscale is enabled, off nodes are denoted as `idle~` in sinfo. When autoscaling is off, the inactive nodes don’t show up in sinfo. You can still see their definition with `scontrol show nodes --future`.
 
-To start new nodes, run `/opt/azurehpc/slurm/resume_program.sh node_list` (e.g. htc-[1-10]).
+To start new nodes, run `/opt/azurehpc/slurm/resume_program.sh node_list` (for example, htc-[1-10]).
 
-To shutdown nodes, run `/opt/azurehpc/slurm/suspend_program.sh node_list` (e.g. htc-[1-10]).
+To shutdown nodes, run `/opt/azurehpc/slurm/suspend_program.sh node_list` (for example, htc-[1-10]).
 
-To start a cluster in this mode, simply add `SuspendTime=-1` to the additional slurm config in the template.
+To start a cluster in this mode, simply add `SuspendTime=-1` to the supplemental Slurm config in the template.
 
 To switch a cluster to this mode, add `SuspendTime=-1` to the slurm.conf and run `scontrol reconfigure`. Then run `azslurm remove_nodes && azslurm scale`. 
 
@@ -138,9 +137,9 @@ To switch a cluster to this mode, add `SuspendTime=-1` to the slurm.conf and run
       ->
       `/opt/azurehpc/slurm`
 
-2. Autoscale logs are now in `/opt/azurehpc/slurm/logs` instead of `/var/log/slurmctld`. Note, that `slurmctld.log` will be in this folder.
+2. Autoscale logs are now in `/opt/azurehpc/slurm/logs` instead of `/var/log/slurmctld`. Note, that `slurmctld.log` is in this folder.
 
-3. The `cyclecloud_slurm.sh` script no longer available. It's been replaced by a new CLI tool called `azslurm`, which you can be run as root. `azslurm` also supports autocomplete.
+3. The `cyclecloud_slurm.sh` script no longer available. A new CLI tool called `azslurm` replaced `cyclecloud_slurm.sh`, and you can be run as root. `azslurm` also supports autocomplete.
 
       ```bash
       [root@scheduler ~]# azslurm
@@ -170,7 +169,7 @@ To switch a cluster to this mode, add `SuspendTime=-1` to the slurm.conf and run
 
 5. CycleCloud no longer creates nodes ahead of time. It only creates them when they're needed.
 
-6. All slurm binaries are inside the `azure-slurm-install-pkg*.tar.gz` file, under `slurm-pkgs`. They're pulled from a specific binary release. The current binary release is [4.0.0](https://github.com/Azure/cyclecloud-slurm/releases/tag/4.0.0)
+6. All Slurm binaries are inside the `azure-slurm-install-pkg*.tar.gz` file, under `slurm-pkgs`. They're pulled from a specific binary release. The current binary release is [4.0.0](https://github.com/Azure/cyclecloud-slurm/releases/tag/4.0.0)
 
 7. For MPI jobs, the only default network boundary is the partition. Unlike version 2.x, each pertition doesn't include multiple "placement groups". So you only have one colocated VMSS per partition. There's no need for the topology plugin anymore, so the job submission plugin isn't needed either. Instead, submitting to multiple partitions is the recommended option for use cases that require jobs submission to multiple placement groups.