Merge pull request #302034 from tfitzmac/0630edit1

copy edit

Author: JamesJBarnett

articles/cyclecloud/cluster-references/special-parsing.md

@@ -2,17 +2,17 @@
 title: Special Parsing for Parameters
 description: Read about special parsing for parameters. Azure CycleCloud is able to resolve parameter values and perform logical evaluation of functions.
 author: mvrequa
-ms.date: 07/15/2024
+ms.date: 06/30/2025
 ms.author: mirequa
 ---
 
 # CycleCloud Cluster Template File Parsing
 
-CycleCloud is able to resolve parameter values and perform logical evaluation of functions.
+CycleCloud resolves parameter values and performs logical evaluation of functions.
 
 ## Parameter Types
 
-CycleCloud handles several basic types of parameters. In most cases, it will handle them as expected:
+CycleCloud handles several basic types of parameters. In most cases, it handles them as expected:
 
 ```ini
 Attribute = foo      # string
@@ -22,36 +22,36 @@ Attribute = false    # boolean
 Attribute = foo, bar # string[]
 ```
 
-To be more explicit, string values can be surrounded by double quotes (for example, `Attribute = "foo"`). This may be useful in the case where a value looks like a number but should be interpreted as a string (version numbers, for example). Boolean values can be set to the bare tokens `true` or `false` (case-insensitive). Comma-separated values are interpreted as lists, and elements are in turn interpreted using the same rules as above.
+To be more explicit, string values can be surrounded by double quotes (for example, `Attribute = "foo"`). This syntax is useful when a value looks like a number but should be interpreted as a string, such as version numbers. Set Boolean values to the bare tokens `true` or `false` (case-insensitive). CycleCloud interprets comma-separated values as lists, and it interprets elements using the same rules as previously described.
 
 ## Parameter Value Evaluation
 
-CycleCloud directly interprets parameter values which use the `$` or `${}` notation.
+CycleCloud directly interprets parameter values that use the `$` or `${}` notation.
 
 ```ini
 MyAttribute = $MyParameter
 MyAttribute2 = ${MyParameter2}
 MyAttributeList = $Param1, $Param2
 ```
 
-## Functions using Parameters
+## Functions that use parameters
 
-The CycleCloud template parser is able to perform math and do ternary logic analysis as seen below.
+The CycleCloud template parser can do math and ternary logic analysis, as shown in the following example.
 
 ```ini
 MaxCoreCount = ${HyperthreadedCoreCount/2}
 SubnetId = ${ifThenElse($Autoscale, $BurstSubnet, $FixedSubnet)}
 JetpackPlatform = ${imageselect == "windows" ? "windows" : "centos-7"}
 ```
 
-## Available functions:
+## Available functions
 
-> [!NOTE] 
-> This list is not comprehensive, but covers some of the most commonly-used functions.
+> [!NOTE]
+> This list isn't comprehensive, but it covers some of the most commonly used functions.
 
 ### ifThenElse
 
-Acts as a ternary operator. Returns one of two values given an expression which evaluates to true or false.
+Acts as a ternary operator. Returns one of two values given an expression that evaluates to true or false.
 
 Syntax:
 
@@ -61,13 +61,13 @@ Arguments:
 
 | Name            | Required | Description |
 | --------------- | -------- | ----------- |
-| predicate       | yes      | An expression which evaluates to true or false.
+| predicate       | yes      | An expression that evaluates to true or false.
 | trueValue       | yes      | The value to use when `predicate` evaluates to true.
 | falseValue      | yes      | The value to use when `predicate` evaluates to false.
 
 ### ifUndefined
 
-If the result of evaluating a given expression is undefined, returns a different value instead. Otherwise simply returns the result.
+If the result of evaluating a given expression is undefined, returns a different value. Otherwise, it simply returns the result.
 
 Syntax:
 
@@ -82,7 +82,7 @@ Arguments:
 
 ### regexp
 
-Performs a regular expression match on the given string and returns true if there was a match, false otherwise.
+Performs a regular expression match on the given string. Returns true if there's a match, and false otherwise.
 
 Syntax:
 
@@ -94,7 +94,7 @@ Arguments:
 | --------------- | -------- | ----------- |
 | pattern         | yes      | A Java-style regular expression.
 | target          | yes      | The input string.
-| options         | no       | Options to use when evaluating the regular expression. See Java's regular expression flags on `java.util.regex.Pattern` for more details.
+| options         | no       | Options to use when evaluating the regular expression. For more details, see Java's regular expression flags on `java.util.regex.Pattern`.
 
 ### regexps
 
@@ -108,10 +108,10 @@ Arguments:
 
 | Name            | Required | Description |
 | --------------- | -------- | ----------- |
-| pattern         | yes      | A Java-style regular expression which matches the string to substitute.
+| pattern         | yes      | A Java-style regular expression that matches the string to substitute.
 | target          | yes      | The input string.
-| substitution    | yes      | The new string to substitute in place of the part of `target` which matches the regular expression.
-| options         | no       | Options to use when evaluating the regular expression. See Java's regular expression flags on `java.util.regex.Pattern` for more details.
+| substitution    | yes      | The new string to substitute in place of the part of `target` that matches the regular expression.
+| options         | no       | Options to use when evaluating the regular expression. For more details, see Java's regular expression flags on `java.util.regex.Pattern`.
 
 ### size
 
@@ -129,7 +129,7 @@ Arguments:
 
 ### strjoin
 
-Concatenates multiple strings together using a separator.
+Concatenates multiple strings together with a separator.
 
 Syntax:
 
@@ -139,12 +139,12 @@ Arguments:
 
 | Name            | Required | Description |
 | --------------- | -------- | ----------- |
-| separator       | yes      | A string separator to append between strings.
-| strings         | yes      | A list of strings to concatenate. May also be specified as a variable number of function arguments: `strjoin(separator, string1, string2, string3...)`
+| separator       | yes      | A string separator to put between strings.
+| strings         | yes      | A list of strings to concatenate. You can also provide the strings as separate arguments: `strjoin(separator, string1, string2, string3...)`
 
 ### substr
 
-Returns part of a string from the start index to the end index (or the end of the string if no end index is given).
+Returns part of a string from the start index to the end index (or the end of the string if you don't provide an end index).
 
 Syntax:
 
@@ -183,7 +183,7 @@ Arguments:
 
 ## Special ClusterName Variable
 
-One variable always provided is `${ClusterName}`. This is evaluated to the name of the CycleCloud cluster.
+The `${ClusterName}` variable always exists. CycleCloud evaluates this variable to the name of the CycleCloud cluster.
 
 ```ini
 EmailAddress = ${strcat("myuser", "@", ClusterName)}
@@ -192,8 +192,7 @@ ResourceId = ${ClusterName}-00-resource
 
 ## Relative Time
 
-CycleCloud interprets back-ticks around time duration as relative time;
-supporting second, minute and day.
+CycleCloud interprets back-ticks around time duration as relative time. It supports seconds, minutes, and days.
 
 ```ini
 ThrottleCapacityTime=`10m` 

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

@@ -2,19 +2,19 @@
 title: Cluster Template Reference - Volumes
 description: Read reference material for including volumes in cluster templates to be used with Azure CycleCloud. A volume represents an Azure Disk.
 author: adriankjohnson
-ms.date: 01/07/2025
+ms.date: 06/30/2025
 ms.author: adjohnso
 ms.topic: conceptual
 ms.service: azure-cyclecloud
 ---
 
 # Volumes
 
-[Volume](~/articles/cyclecloud/how-to/mount-disk.md) objects are rank 3 and subordinate to `node` and `nodearray`. A Volume represents an Azure Disk.
+[Volume](~/articles/cyclecloud/how-to/mount-disk.md) objects are rank 3 and subordinate to `node` and `nodearray` objects. A volume represents an Azure Disk.
 
 ## Example
 
-Adding a `[[[volume]]]` section to a node will create an Azure Disk and attach it to the VM.
+Adding a `[[[volume]]]` section to a node creates an Azure Disk and attaches it to the VM.
 
 ::: moniker range=">=cyclecloud-8"
 ``` ini
@@ -37,36 +37,36 @@ Adding a `[[[volume]]]` section to a node will create an Azure Disk and attach i
 ```
 ::: moniker-end
 
-Attribute values that begin with `$` are referencing parameters.
+Attribute values that start with `$` reference parameters.
 
 ::: moniker range=">=cyclecloud-8"
 Attribute | Type | Definition
 ------ | ----- | ----------
 Size | String | (Required) Size of disk in GB
-VolumeId | String | Resource id for existing Azure Disk.
-StorageAccountType | String | UltraSSD_LRS, Premium_LRS, StandardSSD_LRS, Standard_LRS, PremiumV2_LRS ([Azure Disk Types](/azure/virtual-machines/linux/disks-types)) If not set, defaults to Standard_LRS or Premium_LRS depending on VM size capabilities.
-DiskIOPSReadWrite | Integer | Provisioned IOPS see [Ultra Disks](/azure/virtual-machines/linux/disks-types#ultra-disk)
-DiskMBPSReadWrite | Integer | Disk throughput MB/s see [Ultra Disks](/azure/virtual-machines/linux/disks-types#ultra-disk) 
+VolumeId | String | Resource ID for existing Azure Disk.
+StorageAccountType | String | UltraSSD_LRS, Premium_LRS, StandardSSD_LRS, Standard_LRS, PremiumV2_LRS ([Azure Disk Types](/azure/virtual-machines/linux/disks-types)) If you don't set this value, the default is Standard_LRS or Premium_LRS depending on the VM size capabilities.
+DiskIOPSReadWrite | Integer | Provisioned IOPS. See [Ultra Disks](/azure/virtual-machines/linux/disks-types#ultra-disk).
+DiskMBPSReadWrite | Integer | Disk throughput MB/s. See [Ultra Disks](/azure/virtual-machines/linux/disks-types#ultra-disk).
 Azure.Lun | Integer | Override the auto-assigned LUN ID.
-Mount | String | Name of mount construct, described in `configuration` object
+Mount | String | Name of mount construct, described in the `configuration` object.
 Azure.Caching | String | None, readonly, readwrite. Default is none.
-Persistent | Boolean | If false, disk will be deleted with vm is deleted. Default is false.
-Disabled | Boolean | If true, this volume will be ignored. Default is false.
-SourceUri | String | URI of blob to import into managed disk.
-StorageAccountId | String | Azure resource ID of storage account containing SourceUri blob. Required if blob is in a different subscription.
-SourceResourceId | String | Azure resource ID of source snapshot or managed disk.
-DiskEncryptionSetId (8.5+) | String | Azure resource ID of the Disk Encryption Set to enable Server-Side Encryption with CMK.
-ConfidentialDiskEncryptionSetId (8.5+) | String | Azure resource ID of the Confidential Disk Encryption Set to enable Confidential encryption with CMK. Note: requires `SecurityEncryptionType=DiskWithVMGuestState`. (CycleCloud 8.5+)
+Persistent | Boolean | If false, the disk is deleted when the VM is deleted. Default is false.
+Disabled | Boolean | If true, the volume is ignored. Default is false.
+SourceUri | String | URI of the blob to import into managed disk.
+StorageAccountId | String | Azure resource ID of the storage account containing the SourceUri blob. Required if the blob is in a different subscription.
+SourceResourceId | String | Azure resource ID of the source snapshot or managed disk.
+DiskEncryptionSetId (8.5+) | String | Azure resource ID of the Disk Encryption Set to enable server-side encryption with CMK.
+ConfidentialDiskEncryptionSetId (8.5+) | String | Azure resource ID of the Confidential Disk Encryption Set to enable confidential encryption with CMK. Note: Requires `SecurityEncryptionType=DiskWithVMGuestState`. (CycleCloud 8.5+)
 SecurityEncryptionType (8.5+) | String | One of `VMGuestStateOnly` (the default) or `DiskWithVMGuestState`.
-Azure.Encryption.Type | String | Deprecated, has no effect. Using a Disk Encryption Set provides CMK; otherwise, PMK is in effect.
+Azure.Encryption.Type | String | Deprecated. Has no effect. If you use a Disk Encryption Set, you get CMK; otherwise, you get PMK.
 Azure.Encryption.DiskEncryptionSetId | String | Deprecated. Use `DiskEncryptionSetId` instead, as of CycleCloud 8.5.
 
 ::: moniker-end
 
 ### Boot Volume
 
 ::: moniker range=">=cyclecloud-8"
-For each node, the volume named `boot` exposes some advanced configuration of the OS boot volume. Storage type settings for the boot disk are ignored if `EphemeralOSDisk=true` is specified for the node.
+For each node, the volume named `boot` exposes some advanced configuration of the OS boot volume. The cluster ignores storage type settings for the boot disk if you specify `EphemeralOSDisk=true` for the node.
 
 ``` ini
   [[node scheduler]]
@@ -78,6 +78,6 @@ For each node, the volume named `boot` exposes some advanced configuration of th
       DiskMBPSReadWrite = 2000
 ```
 > [!NOTE]
-> UltraSSD disks can only be used with availability zones (availability sets and single VM deployments outside of zones will not have the ability to attach an ultra disk).
+> You can only use UltraSSD disks with availability zones. You can't use UltraSSD disks with availability sets or single VM deployments outside of zones.
 
 ::: moniker-end

articles/cyclecloud/common-issues/azure-credentials.md

@@ -2,25 +2,25 @@
 title: Common Issues - Credentials Resource
 description: Azure CycleCloud common issue - Credential Resources
 author: adriankjohnson
-ms.date: 05/28/2024
+ms.date: 06/30/2025
 ms.author: adjohnso
 ms.service: azure-cyclecloud
 ms.custom: compute-evergreen
 ---
-# Common Issues: Azure Credentials Resources
+# Common issues: Azure Credentials Resources
 
-## Possible Error Messages
+## Possible error messages
 - `Staging resources (Azure account credentials are not valid)`
 - `Staging resources (No JSON object could be decoded)`
 
 ## Resolution
-Verify that the service principal configured for Azure CycleCloud is valid. This error can occur if the secret for the service principal has expired. To resolve this issue, update the expired secret for the service principal in the Azure portal and then update the secret for the credential in CycleCloud by selecting the "gear" icon at the bottom of the Clusters page and editing the appropriate credential.
+Verify that the service principal you configured for Azure CycleCloud is valid. This error occurs if the secret for the service principal expires. To resolve this issue, update the expired secret for the service principal in the Azure portal. Then, update the secret for the credential in CycleCloud by selecting the **gear** icon at the bottom of the Clusters page and editing the appropriate credential.
 
 To reset the service principal's secret:
 ```azurecli-interactive
 az ad sp credential reset --name "0000000000-0000-0000-0000-00000000" --years 2  --password {Application Secret} --credential-description "My New Credential"
 ```
 
-## More Information
+## More information
 
-For more information on Azure CLI operations with service principals, see [Service Principals](/cli/azure/ad/sp?view=azure-cli-latest&preserve-view=true)
+For more information on Azure CLI operations with service principals, see [Service Principals](/cli/azure/ad/sp?view=azure-cli-latest&preserve-view=true).

articles/cyclecloud/common-issues/chef-exception.md

@@ -2,7 +2,7 @@
 title: Common Issues - Chef Exceptions
 description: Azure CycleCloud common issue - Chef Exceptions
 author: adriankjohnson
-ms.date: 06/20/2023
+ms.date: 06/30/2025
 ms.author: adjohnso
 ms.topic: conceptual
 ms.service: azure-cyclecloud
@@ -17,12 +17,10 @@ ms.custom: compute-evergreen
 
 ## Resolution
 
-Chef exceptions types are numerous. This message will return the Chef resource name, 
-recipe, recipe line number, and stack trace for the occurrence of the exception.
-These exceptions occur during the configuration of the system so they can span 
-all of the functionality that Chef provides as well as arbitrary commands runnable
-as a chef resource. 
+Chef has many exception types. When an exception occurs, Chef returns the resource name, 
+recipe, recipe line number, and stack trace. These exceptions happen during the configuration of the system, so they can affect 
+all of the functionality that Chef provides and arbitrary commands runnable
+as a Chef resource. 
 
-Basic deduction of system administration will be needed to diagnose unhandled
-Chef exceptions.
+To diagnose unhandled Chef exceptions, you need to use your system administration skills.
 

articles/cyclecloud/common-issues/cluster-credentials.md

@@ -2,19 +2,19 @@
 title: Common Issues - Cluster Credentials
 description: Azure CycleCloud common issue - Cluster Credentials
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Cluster Credentials
+# Common issues: Cluster credentials
 
-## Possible Error Messages
+## Possible error messages
 
 - `Validating nodes (Credentials not found)`
 
 ## Resolution
 
-Check that the Credentials specified for the cluster, node, or nodearray exist in your CycleCloud instance. To determine if a credential exists in CycleCloud, click the gear icon at the bottom of the clusters page and verify that the named credential exists in the account list.
+Check that the credentials you specify for the cluster, node, or node array exist in your CycleCloud instance. To see if a credential exists in CycleCloud, select the gear icon at the bottom of the clusters page. Check the account list for the named credential.
 
-## More Information
+## More information
 
 For more information, see [Configuring Azure Credentials](/azure/cyclecloud/configuration).

articles/cyclecloud/common-issues/cluster-init.md

@@ -10,18 +10,18 @@ ms.custom: compute-evergreen
 ---
 
 
-# Common Issues: Cluster Init
+# Common issues: Cluster init
 
-## Possible Error Messages
+## Possible error messages
 
 - `{ERROR} while executing {SCRIPT} in project`
 - `Failed to execute cluster-init script {SCRIPT} in project`
 
 ## Resolution
 
-Azure CycleCloud provides users the ability to configure VMs that become nodes of the cluster by running custom scripts during the VM preparation phase. This functionality is provided through the [CycleCloud Projects](~/articles/cyclecloud/how-to/projects.md) system, and is also known as Cluster-Init.
+Azure CycleCloud lets you configure VMs that become nodes of the cluster by running custom scripts during the VM preparation phase. You get this functionality through the [CycleCloud Projects](~/articles/cyclecloud/how-to/projects.md) system. It's also known as Cluster-Init.
 
-If there are failures or errors when these scripts are executed, Cyclecloud versions 7.9 and later surface these errors in the node details page. The STDERR and STDOUT output of the scripts are included in these error messages. 
+If these scripts fail or return errors, CycleCloud versions 7.9 and later show these errors in the node details page. The error messages include the STDERR and STDOUT output of the scripts.
 
-- If you are able to identify the problem from the STDERR or STDOUT output of the scripts, fix the error in the scripts and re-upload the project using the CycleCloud CLI.
-- Otherwise, SSH into the VM either as the `cyclecloud` user or your own user account and attempt to run the commands in the script manually to troubleshoot. Once you have identified the problem, edit the cluster-init script and re-upload the project.
+- If you can identify the problem from the STDERR or STDOUT output of the scripts, fix the error in the scripts and re-upload the project using the CycleCloud CLI.
+- Otherwise, SSH into the VM as either the `cyclecloud` user or your own user account. Try running the commands in the script manually to troubleshoot. Once you identify the problem, edit the cluster-init script and re-upload the project.