Merge pull request #302005 from tfitzmac/0629edit1

copy edit

Author: denrea

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

@@ -2,16 +2,16 @@
 title: Azure CycleCloud Cluster-Init Parameter Reference
 description: See a reference for cluster-init objects to be used with Azure CycleCloud. A cluster-init object defines the CycleCloud project specifications to run on a node.
 author: adriankjohnson
-ms.date: 05/31/2024
+ms.date: 06/29/2025
 ms.author: adjohnso
 ms.custom: compute-evergreen
 ---
 
 # Cluster-Init
 
-Cluster-init objects are subordinate in rank to `node` and `nodearray`. The cluster-init object defines the [CycleCloud project](~/articles/cyclecloud/how-to/projects.md) specs to run on a node.
+Cluster-init objects are subordinate to `node` and `nodearray` objects. The cluster-init object defines the [CycleCloud project](~/articles/cyclecloud/how-to/projects.md) specs to run on a node.
 
-Adding a `[[[cluster-init]]]` section to a node will include a project spec. Cluster-init definition can also be written in short-hand notation:
+When you add a `[[[cluster-init]]]` section to a node, you include a project spec. You can also use shorthand notation to define cluster-init:
 
 ``` ini
 [cluster my-cluster]
@@ -35,18 +35,17 @@ Adding a `[[[cluster-init]]]` section to a node will include a project spec. Clu
 
 ```
 
-Attribute values that begin with `$` are referencing parameters.
+Attribute values that start with `$` reference parameters.
 
-The order of the Project specs is respected as provided in the Cluster Template File. In this case `my-proj:default` will run first as it
-comes from the node defaults, followed by `myproject:x.y.x`, and finally `my-proj:my-spec`.
+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:x.y.x` runs, and finally, `my-proj:my-spec` runs.
 
-## Attribute Reference
+## Attribute reference
 
 Attribute | Type | Definition
 ------ | ----- | ----------
-Project | String | Name of CycleCloud project.
-Version | String | Version of CycleCloud project spec.
-Spec | String | Name of CycleCloud project spec.
-Locker | String | Name of locker from which to download project spec.
+Project | String | Name of the CycleCloud project.
+Version | String | Version of the CycleCloud project specification.
+Spec | String | Name of the CycleCloud project specification.
+Locker | String | Name of the locker to download the project specification from.
 
-For projects contained in the CycleCloud project, Locker should be set to `cyclecloud`.
+For projects in the CycleCloud project, set the `Locker` attribute to `cyclecloud`.

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

@@ -2,18 +2,18 @@
 title: Cluster Reference Docs
 description: CycleCloud template reference for the Cluster section
 author: adriankjohnson
-ms.date: 05/31/2024
+ms.date: 06/29/2025
 ms.author: adjohnso
 ms.custom: compute-evergreen
 ---
 
-# Cluster Section
+# Cluster section
 
-A cluster template file must have at least one `[cluster]` section with an inline name attribute.  This is the only required section of the file.
+A cluster template file must have at least one `[cluster]` section with an inline name attribute. This section is the only required section of the file.
 
 ## Examples
 
-Conventional cluster template files have a single cluster declaration.  
+Conventional cluster template files have a single cluster declaration.
 
 ``` ini
 [cluster my-cluster]
@@ -27,23 +27,23 @@ Conventional cluster template files have a single cluster declaration.
         Credentials = $Credentials
 ```
 
-## Attribute Reference
+## Attribute reference
 
 Attribute | Type | Definition
 ------ | ----- | ----------
-Abstract | Boolean | Whether cluster definition is purely for child reference.
-Autoscale | Boolean | Enable auto-start and stop on nodearrays
-Category | String | Which category to display the cluster icon
-CategoryOrder | Integer | Install to a directory other than /opt/cycle_server
-FormLayout    | String  | "SelectionPanel" for a multi-panel display or "List" for a flat list of parameters. Defaults to "List" if not set.
-IconUrl  | URL | link to representative icon for cluster displayed in UI
-MaxCount | Integer | To ensure that the cluster never exceeds 10 nodes you would specify a value of 10. Note that MaxCount and MaxCoreCount can be used together, in which case the lower effective constraint will take effect.
-MaxCoreCount | Integer | To ensure that the cluster never exceeds 100 cores you would specify a value of 100. Note that MaxCount and MaxCoreCount can be used together, in which case the lower effective constraint will take effect.
+Abstract | Boolean | Whether the cluster definition is purely for child reference.
+Autoscale | Boolean | Enable auto-start and stop on node arrays.
+Category | String | Which category to display the cluster icon.
+CategoryOrder | Integer | Install to a directory other than `/opt/cycle_server`.
+FormLayout | String | `"SelectionPanel"` for a multi-panel display or `"List"` for a flat list of parameters. Defaults to `"List"` if not set.
+IconUrl | URL | Link to representative icon for cluster displayed in UI.
+MaxCount | Integer | To ensure that the cluster never exceeds 10 nodes, specify a value of 10. You can use `MaxCount` and `MaxCoreCount` together. The lower effective constraint takes effect.
+MaxCoreCount | Integer | To ensure that the cluster never exceeds 100 cores, enter 100. You can use MaxCount and MaxCoreCount together. The lower effective constraint takes effect.
 ParentName | String | Assume properties of abstract parent cluster in the same cluster template file unless local override.
 
 > [!NOTE]
 > None of the cluster attributes are required.
 
-## Subordinate Objects
+## Subordinate objects
 
 The cluster object has either `[[node]]` or `[[nodearray]]` as subordinate objects.

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

@@ -2,23 +2,23 @@
 title: Cluster Template Reference Overview
 description: View reference information on cluster templates in Azure CycleCloud. See cluster template file hierarchy, object attributes, parameters, and template objects.
 author: mvrequa
-ms.date: 06/03/2024
+ms.date: 06/29/2025
 ms.author: mirequa
 ms.topic: conceptual
 ms.service: azure-cyclecloud
 ms.custom: compute-evergreen
 ---
 
-# CycleCloud Cluster Template File
+# CycleCloud cluster template file
 
-CycleCloud clusters are defined in declarative and hierarchical text files called templates. A number of example CycleCloud cluster templates are available for [download](~/articles/cyclecloud/download-cluster-templates.md)
+You define CycleCloud clusters in declarative and hierarchical text files called templates. You can [download](~/articles/cyclecloud/download-cluster-templates.md) several example CycleCloud cluster templates.
 
 > [!NOTE]
-> The CycleCloud cluster template file is case insensitive throughout.
+> The CycleCloud cluster template file is case insensitive.
 
-## CycleCloud Cluster Template File Hierarchy
+## CycleCloud cluster template file hierarchy
 
-The cluster template file is organized into a hierarchical structure. Each section defines a primary object and the object's name appears in the section header (eg. `[cluster my-cluster]`). The number of square brackets represents the rank, with fewer brackets indicating higher rank. The top of the hierarchy, and the only required object in the Cluster Template file is the `[cluster]` object. The specific order of the sections is not important.
+The cluster template file uses a hierarchical structure. Each section defines a primary object and includes the object's name in the section header (for example, `[cluster my-cluster]`). The number of square brackets shows the rank, with fewer brackets indicating higher rank. The top of the hierarchy, and the only required object in the cluster template file, is the `[cluster]` object. The specific order of the sections doesn't matter.
 
 ``` template
 [cluster]
@@ -35,15 +35,15 @@ The cluster template file is organized into a hierarchical structure. Each secti
     [[[parameter]]]
 ```
 
-A `[cluster]` may contain a `[[node]]`, which may contain a `[[[volume]]]`.
+A `[cluster]` can contain a `[[node]]`, which can contain a `[[[volume]]]`.
 
 A `[[[volume]]]` must be within a `[[node]]`, which must be within a `[cluster]`.
 
 Many objects correspond to Azure resources. For example, `[[node]]` corresponds to Azure VM, `[[[volume]]]` corresponds to Azure Disk, and `[[[network-interface]]]` corresponds to Network Interface.
 
 ## Object Attributes
 
-Each object may possess attributes which govern the object's behavior:
+Each object can have attributes that control its behavior:
 
 ``` ini
 [[node my-node]]
@@ -53,7 +53,7 @@ Attribute2 = Value2
 
 ## Parameters
 
-[Cluster Parameters](./parameter-reference.md) are variables set at cluster creation time. They can be used in the definition of any attribute.
+[Cluster Parameters](./parameter-reference.md) are variables you set when you create a cluster. Use these parameters in the definition of any attribute.
 
 ``` ini
 [cluster MyCluster]
@@ -63,24 +63,23 @@ Attribute2 = Value2
   DefaultValue = 200
 ```
 
-The `$` is a special character to denote a parameter value by name.  
+The `$` character lets you specify a parameter value by name.
 
-Parameters have properties both to define the type and to control how they are represented in the cluster UI selectors. Parameters are defined
-at the time of cluster creation so they can either be set via command line parameter flag `-p parameter-file.json`, or by using the cluster UI.
+Parameters have properties that define their type and control how the cluster UI selectors represent them. You define parameters when you create the cluster. You can set them by using the command line parameter flag `-p parameter-file.json` or the cluster UI.
 
 ### Special Parsing
 
-The [template parser](./special-parsing.md) is capable of handling certain logic and special definitions and process functions of parameter values:
+The [template parser](./special-parsing.md) can handle certain logic, special definitions, and process functions of parameter values:
 
 ``` ini
 Attribute1 = ${ifThenElse(AccessSubnet !== undefined, AccessSubnet, ComputeSubnet)}
 ```
 
-The special parser is activated with the `${}` syntax.
+The `${}` syntax activates the special parser.
 
-## Template Objects
+## Template objects
 
-These are the currently supported template objects:
+The following template objects are currently supported:
 
 * [**cluster**](./cluster-reference.md)
 * [**node, nodearray**](./node-nodearray-reference.md)