Update for Acrolinx feedback

Author: Doug Clayton

articles/cyclecloud/cluster-references/chef-reference.md

@@ -7,13 +7,13 @@ ms.date: 09/23/2025
 ms.custom: compute-evergreen
 ---
 
-# Chef Orchestration
+# Chef orchestration
 
-[Chef](https://www.chef.io) is a configuration management tool that automates the deployment and management of applications and infrastructure. It uses a domain-specific language (DSL) for writing system configuration "recipes". These recipes are stored in "cookbooks" that can be shared and reused across different systems.
+[Chef](https://www.chef.io) is a configuration management tool that automates the deployment and management of applications and infrastructure. It uses a domain-specific language (DSL) for writing system configuration "recipes." These recipes are stored in "cookbooks" that can be shared and reused across different systems.
 
 Each cluster-init spec can reference one or more [Chef roles](https://docs.chef.io/roles.html) and/or [cookbook recipes](https://docs.chef.io/recipes.html) that need to be executed on the booting VM. 
 
-[!NOTE]
+> [!NOTE]
 > CycleCloud uses Chef in a stand-alone mode that doesn't rely on a centralized Chef server. The set of Chef cookbooks needed to prepare each VM are downloaded from the Azure Storage Account along with the rest of the files in the project.
 
 ## Project Structure
@@ -66,7 +66,7 @@ The node downloads the zipped Chef files during the bootstrapping phase of node
 > To run custom cookbooks, you must add them to the run_list for the node.
 
 
-## jetpack download
+## Jetpack download resource provider
 
 The following example shows how to create a `jetpack_download` lightweight resource provider for Chef users:
 

articles/cyclecloud/cluster-references/cluster-init-reference.md

@@ -18,13 +18,13 @@ The section uses a shorthand notation to reference the fully qualified spec:
 [[[cluster-init PROJECT:SPEC:VERSION]]]
 ```
 
-By default, projects are assumed to stored in the [locker](../how-to/projects.md#lockers) already. However, if you are using a project defined in GitHub, you can indicate that with the `cyclecloud/` prefix:
+By default, projects are assumed to be stored in the [locker](../how-to/projects.md#lockers) already. However, if you're using a project defined in GitHub, you can indicate that with the `cyclecloud/` prefix:
 
 ```ini
 [[[cluster-init cyclecloud/PROJECT:SPEC:VERSION]]]
 ```
 
-This tells CycleCloud to download the project files from GitHub and upload them to your locker in a special cache area. Without `cyclecloud/` in the cluster-init reference, CycleCloud will expect the project to be uploaded by you.
+This section tells CycleCloud to download the project files from GitHub and upload them to your locker in a special cache area. Without `cyclecloud/` in the cluster-init reference, CycleCloud expects you to upload the project manually.
 
 As an example, this cluster template defines one node that uses three specs:
 
@@ -49,17 +49,17 @@ Attribute values that start with `$` reference parameters.
 
 The CycleCloud project specs run in the order you list them in the Cluster Template File. In this example, `my-proj:default` runs first because it comes from the node defaults. Next, `myproject:my-spec` runs, which comes from the locker named `test-locker`. Finally, `my-proj:my-spec` runs.
 
-The `[[[cluster-init PROJECT:SPEC:VERSION]]]` form is a shorthand for the following:
+The `[[[cluster-init PROJECT:SPEC:VERSION]]]` form is a shorthand for the following section:
 ```ini
     [[[cluster-init]]]
       Project = PROJECT
       Version = VERSION
       Spec = SPEC
 ```
 
-You can also use `[[[cluster-init SOURCE_LOCKER/PROJECT:SPEC:VERSION]]]` to specify a `SourceLocker` for the cluster-init spec. The source locker is optional. Without it, CycleCloud assumes the locker already has the files staged. If set to the special name `cyclecloud`, it uses a built-in project defined in CycleCloud whose contents are stored in GitHub. Otherwise, if set to a different locker, it stages the files from that locker to the target locker before starting the node. This is useful for custom cluster-init projects and multi-region deployments, because you only have to manually stage the files to a single locker, which you can use as a source locker for nodes in a different region.
+You can also use `[[[cluster-init SOURCE_LOCKER/PROJECT:SPEC:VERSION]]]` to specify a `SourceLocker` for the cluster-init spec. The source locker is optional. Without it, CycleCloud assumes the locker already has the files staged. If set to the special name `cyclecloud`, it uses a built-in project defined in CycleCloud whose contents are stored in GitHub. Otherwise, if set to a different locker, it stages the files from that locker to the target locker before starting the node. This feature is useful for custom cluster-init projects and multi-region deployments. You manually stage the files to a single locker, and CycleCloud uses that locker as a source locker for nodes in other regions.
 
-[!NOTE]
+> [!NOTE]
 > Projects that are staged automatically are put in a special cache directory of the target locker so that they don't conflict with projects you stage manually.
 
 ## Attribute reference

articles/cyclecloud/concepts/clusters.md

@@ -38,12 +38,12 @@ CycleCloud provisions VMs from base VM images defined in the cluster template. T
 
 ![Node Preparation Diagram](../images/concept-node-prep-diagram.png)
 
-You can control how nodes are customized on boot by creating a custom *cluster-init project*. A project contains the scripts and other files needed to customize a node, separated into *specs* for the different kinds of roles in a cluster. For example, a project for a batch scheduler such as Slurm comprises a minimum of three specs: one for the scheduler head nodes, one for the the compute nodes, and another for the login nodes. [Read more about the CycleCloud projects](~/articles/cyclecloud/how-to/projects.md).
+You can control how nodes are customized on boot by creating a custom *cluster-init project*. A project contains the scripts and other files needed to customize a node, separated into *specs* for the different kinds of roles in a cluster. For example, a project for a batch scheduler such as Slurm comprises a minimum of three specs: one for the scheduler head nodes, one for the compute nodes, and another for the login nodes. [Read more about the CycleCloud projects](~/articles/cyclecloud/how-to/projects.md).
 
 In the node definition, you reference the specs that should run on that node. Jetpack uses these specs on boot to prepare a node for its role in the cluster. The spec files come from the user's Blob Storage Account, and are staged from the CycleCloud application server into the storage account before nodes are started.
 
 > [!NOTE]
-> The specs for built-in templates (such as the Slurm cluster type) are stored in GitHub, and are automatically downoaded to the user's storage account when the node starts.
+> The specs for built-in templates (such as the Slurm cluster type) are stored in GitHub. CycleCloud automatically downloads them to the user's storage account when the node starts.
 
 When a node boots, Jetpack downloads the specs defined on the node with the `[[[cluster-init]]]` section and processes them in order to *converge* the node to a working state (for instance, to be a compute node).
 

articles/cyclecloud/how-to/projects.md

@@ -92,7 +92,7 @@ Project contents are stored within a **locker**. You can upload the contents of
 If you add more than one locker, you can set your default locker with `cyclecloud project default_target (locker)`, and then run `cyclecloud project upload`. You can also set a global default locker for projects to share by running the command `cyclecloud project default locker (locker) -global`.
 
 > [!NOTE]
-> Default lockers are stored in the CycleCloud config file, usually located in _~/.cycle/config.ini_ and not the _project.ini_ file. This setup allows version control for _project.ini_.
+> Default lockers are stored in the CycleCloud config file, located in _~/.cycle/config.ini_ and not the _project.ini_ file. This setup allows version control for _project.ini_.
 
 When you upload your project contents, CycleCloud syncs the cluster-init contents to your target locker, at `projects/(project)/(version)/(spec_name)/cluster-init`.
 
@@ -160,7 +160,7 @@ Specs are defined in your cluster template, using the `[[[cluster-init]]]` [sect
 ```
 
 This example takes advantage of the `defaults` node definition that all nodes inherit from. 
-The scheduler node will get both the `common` and `scheduler` specs, and nodes in the execute node array will get both the `common` and `execute` specs.
+The scheduler node gets both the `common` and `scheduler` specs, and nodes in the execute node array get both the `common` and `execute` specs.
 
 ## File locations
 
@@ -236,4 +236,4 @@ The command sends its output to STDOUT and to _jetpack.log_. Each script's outpu
 
 ## jetpack download
 
-To download a blob within a cluster-init script, use the command `jetpack download (filename)` to pull it from the `blobs` directory. Running this command from a cluster-init script lets it determine the project and base URL for you. To use it in a non-cluster-init context, you need to specify the project (see --help for more information).
+To download a blob within a cluster-init script, use the command `jetpack download (filename)` to pull it from the `blobs` directory. Running this command from a cluster-init script lets it determine the project and base URL for you. To use it in a non-cluster-init context, you need to specify the project. For more information, use the `--help` option.

articles/cyclecloud/how-to/storage-blobs.md

@@ -47,4 +47,4 @@ CycleCloud stores project contents in a **locker**, which is an Azure Storage co
 You can also set a default project locker from the command line. To set the default locker, run `cyclecloud project default_locker [locker]` from your project's directory. Once set, you can run `cyclecloud project upload` without specifying a locker. To set a global default locker for all your projects, run `cyclecloud project default_locker --global [locker]`.
 
 > [!NOTE]
-> You configure default lockers in the CycleCloud CLI configuration file (usually located in _~/.cycle/config.ini_), not in the _project.ini_. Keeping this configuration out of the _project.ini_ allows you to version control the _project.ini_.
+> You configure default lockers in the CycleCloud CLI configuration file (located in _~/.cycle/config.ini_), not in the _project.ini_. Keeping this configuration out of the _project.ini_ allows you to version control the _project.ini_.

articles/cyclecloud/jetpack.md

@@ -40,7 +40,7 @@ The Jetpack installer:
 | --------- | ------------ |
 | `bin`     | Useful binaries and scripts. |
 | `config`  | User-defined and cluster-defined configuration files and scripts. |
-| `logs`    | Logs generated by joining a cluster and converging the node. Of particular interest is *jetpack.log*, which contains the results of the converge. |
+| `logs`    | Logs generated by joining a cluster and converging the node. Of particular interest is *jetpack.log*, which contains the results of the converge process. |
 | `run`     | Runtime files generated by the system. We don't recommend directly accessing these files. |
 | `system`  | Internal files. We don't recommend directly using any files in this directory as they can significantly change from release to release.  |
 
@@ -56,7 +56,7 @@ The **Jetpack** command-line tool provides a useful set of subcommands for manip
 | ------------------- | -------------------------------------------------------- |
 | `jetpack autoscale` | Autoscale the cluster this node belongs to.              |
 | `jetpack config`    | Retrieve a configuration value.                          |
-| `jetpack converge`  | Execute a "converge", to update the node configuration.  |
+| `jetpack converge`  | Execute a "converge" to update the node configuration.  |
 | `jetpack download`  | Download a blob resource from a project in Azure Storage.|
 | `jetpack keepalive` | Delay system termination by the HealthCheck Service.     |
 | `jetpack log`       | Log a message to CycleCloud cluster UI.                  |