copy edit

Author: tfitzmac

articles/cyclecloud/common-issues/staging-resources.md

@@ -2,25 +2,25 @@
 title: Common Issues - Staging Resources| Microsoft Docs
 description: Azure CycleCloud common issue - Staging Resources
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Staging Resources
+# Common issues: Staging resources
 
-## Possible Error Messages
+## Possible error messages
 
 - `Staging Resources (Unable to determine AccessKey for URL)`
 - `pogo.exceptions.FrameworkError: 'az://.../blobs' is not a directory`
 - `pogo.exceptions.FrameworkError: Cannot sync from directory to file!`
 
 ## Resolution
 
-Typically, this error is caused when the service principal associated with Azure CycleCloud does not have the appropriate permissions to read the access key for the storage account locker. To resolve, you must grant "Microsoft.Storage/storageAccounts/listKeys/action" to the service principal.
+Typically, this error happens when the service principal associated with Azure CycleCloud doesn't have the right permissions to read the access key for the storage account locker. To fix this error, grant the **Microsoft.Storage/storageAccounts/listKeys/action** permission to the service principal.
 
-Another common cause of these failures is using a Storage Account with "Hierarchical namespace" enabled for Azure Data Lake Storage Gen 2.  "Hierarchical namespace" *must* be disabled for Blob storage accounts that are used as storage Lockers.  
+Another common cause of these failures is using a Storage Account with **Hierarchical namespace** enabled for Azure Data Lake Storage Gen 2. You must disable **Hierarchical namespace** for Blob storage accounts that you use as storage lockers.
 
-You can check "Hierarchical namespace" is enabled in the Storage Account **Overview** page in the Azure Portal.   Search the page for "Hierarchical namespace."   Once enabled, there is no way to disable hierarchical namespace, so a new Storage Account must be chosen or created for the CycleCloud Storage Locker.
+You can check if **Hierarchical namespace** is enabled in the Storage Account **Overview** page in the Azure portal. Search the page for **Hierarchical namespace**. Once enabled, you can't disable hierarchical namespace. You must choose or create a new Storage Account for the CycleCloud Storage Locker.
 
-## More Information
+## More information
 
-For more information about specific permissions required for CycleCloud, see [Create a custom role and managed identity for CycleCloud](/azure/cyclecloud/managed-identities#create-a-custom-role-and-managed-identity-for-cyclecloud)
+For more information about specific permissions required for CycleCloud, see [Create a custom role and managed identity for CycleCloud](/azure/cyclecloud/managed-identities#create-a-custom-role-and-managed-identity-for-cyclecloud).

articles/cyclecloud/common-issues/unavailable-sku.md

@@ -2,12 +2,12 @@
 title: Common Issues - Unavailable SKU| Microsoft Docs
 description: Azure CycleCloud common issue - Unavailable SKU
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Unavailable Virtual Machine SKU
+# Common issues: Unavailable virtual machine SKU
 
-## Possible Error Messages
+## Possible error messages
 
 - `Creating Virtual Machine (The requested VM size Standard_X is not available in the current region)`
 
@@ -17,8 +17,8 @@ There are two possible resolutions for this issue:
 - Choose a region where the desired VM size is available
 - Select a VM size that is available in the desired region
 
-To check the VM sizes that are available, click Settings, show "Azure" types, and check the Azure VM Size records for the requested region. If the "Restricted" column's value is "true", this VM size is not available for the subscription.
+To check the available VM sizes, select **Settings**, view the **Azure** types, and check the Azure VM Size records for the requested region. If the **Restricted** column shows **true**, this VM size isn't available for your subscription.
 
-## More Information
+## More information
 
-For more information, [this chart](https://azure.microsoft.com/global-infrastructure/services/?products=virtual-machines) contains information on which VM sizes are available in which regions.
+For more information, [this chart](https://azure.microsoft.com/global-infrastructure/services/?products=virtual-machines) shows which VM sizes are available in which regions.

articles/cyclecloud/common-issues/updating-scalesets.md

@@ -2,17 +2,17 @@
 title: Common Issues - Updating Scalesets
 description: Azure CycleCloud common issue - Updating Scalesets
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Updating Scalesets
+# Common issues: Updating scale sets
 
-## Possible Error Messages
+## Possible error messages
 
 - `Updating Scaleset (OperationNotAllowed)`
 
 ## Resolution
 
-Typically, this error arises from exceeding your quota for the scale set's VM type. To determine if you have enough quota in your subscription for the specific VM type, click the "gear" icon at the bottom of the Cluster page, show "Azure" types, and select "Azure Usage." In the search box, type the family name of the VM size to filter the records. If the "Limit" column for the VM size family is too low, you will need to request more quota.
+This error usually happens when you exceed your quota for the scale set's VM type. To check if you have enough quota in your subscription for the specific VM type, select the **gear** icon at the bottom of the Cluster page, show **Azure** types, and select **Azure Usage**. In the search box, type the family name of the VM size to filter the records. If the **Limit** column for the VM size family is too low, you need to request more quota.
 
-Alternatively, you may use the Azure portal to view subscription usage and quotas from the "Usage + quotas" section on the Subscriptions blade.
+Alternatively, you can use the Azure portal to view subscription usage and quotas from the **Usage + quotas** section on the Subscriptions blade.

articles/cyclecloud/how-to/add-disk.md

@@ -2,40 +2,40 @@
 title: Managed Disk Options
 description: Learn about volumes (Azure managed disks) within Azure CycleCloud. Understand persistent volumes and disk type options.
 author: mvrequa
-ms.date: 01/20/2020
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
 
 # Managed Disks
 
-CycleCloud will automatically attach volumes ([Azure Managed Disks](/azure/virtual-machines/linux/disks-types)) to your nodes for additional storage space. The managed disks come in four flavors and have capacities up to 64TiB.
+CycleCloud automatically attaches volumes ([Azure Managed Disks](/azure/virtual-machines/linux/disks-types)) to your nodes for extra storage space. Managed disks come in four types and have capacities up to 64 TiB.
 
-To create a 100GB volume, add the following to your `[[node]]` element in your cluster template:
+To create a 100 GB volume, add the following code to your `[[node]]` element in your cluster template:
 
 ``` ini
 [[[volume example-vol]]]
 Size = 100
 ```
 
-## Persistent Volumes
+## Persistent volumes
 
-By default, a volume will be created when the instance is started, and deleted when the instance is terminated. If you want to preserve the data on the volume even after the instance is terminated, make it a **persistent** volume:
+By default, the volume is created when the instance starts and deleted when the instance terminates. To preserve the data on the volume even after the instance terminates, make it a **persistent** volume:
 
 ``` ini
 [[[volume example-vol]]]
 Size = 100
 Persistent = true
 ```
 
-This volume will be created the first time the instance is started, but will not be deleted when the instance is terminated. Instead, it will be kept and re-attached to the instance the next time the node is started. Persistent volumes are not deleted until the cluster is deleted.
+This volume is created the first time the instance starts but isn't deleted when the instance terminates. Instead, the volume is kept and reattached to the instance the next time the node starts. Persistent volumes are deleted only when the cluster is deleted.
 
 > [!WARNING]
-> When your cluster is deleted, all persistent volumes are deleted as well! If you want your storage to persist longer than your cluster, you must attach a preexisting volume by ID.
+> When you delete your cluster, you also delete all persistent volumes. To keep your storage available after your cluster is deleted, attach a preexisting volume by ID.
 
-## Disk Types
+## Disk types
 
 ::: moniker range="=cyclecloud-7"
-There are four [Azure disk types](/azure/virtual-machines/linux/disks-types). CycleCloud uses standard hard disk drives (HDD) by default. To use a more performant SSD drive for the disk, use `SSD = true`:
+There are four [Azure disk types](/azure/virtual-machines/linux/disks-types). CycleCloud uses standard hard disk drives (HDD) by default. To use a more performant SSD drive for the disk, set `SSD` to `true`:
 
 ``` ini
 [[[volume example-vol]]]
@@ -44,13 +44,13 @@ Persistent = true
 SSD = true
 ```
 
-A premium SSH disk is used by default when you are using a VM series that is premium storage-compatible.
+When you use a VM series that works with premium storage, the default is a premium SSH disk.
 
 ::: moniker-end
 ::: moniker range=">=cyclecloud-8"
 Azure offers four basic storage options: [Ultra](/azure/virtual-machines/windows/disks-types#ultra-disk), [Premium SSD](/azure/virtual-machines/windows/disks-types#premium-ssd), [Standard SSD](/azure/virtual-machines/windows/disks-types#standard-ssd), and [Standard HDD](/azure/virtual-machines/windows/disks-types#standard-hdd).
 
-To specify the storage type to use for your virtual machine, use: `StorageAccountType = [UltraSSD_LRS|Premium_LRS|StandardSSD_LRS|Standard_LRS]` on your volume.
+To specify the storage type for your virtual machine, use: `StorageAccountType = [UltraSSD_LRS|Premium_LRS|StandardSSD_LRS|Standard_LRS]` on your volume.
 
 For example:
 
@@ -61,15 +61,15 @@ Persistent = true
 StorageAccountType = StandardSSD_LRS
 ```
 
-For backwards compatibility, `SSD=true` will select `Premium_LRS` or `StandardSSD_LRS` depending on the capabilities of the VM size selected.
+For backward compatibility, `SSD=true` selects `Premium_LRS` or `StandardSSD_LRS` depending on the capabilities of the VM size you select.
 ::: moniker-end
 
 > [!NOTE]
-> Azure SSD will round up to the next size for [pricing](https://azure.microsoft.com/pricing/details/managed-disks). For example, if you create a disk size of 100GB, you will be charged at the 128GB rate.
+> For [pricing](https://azure.microsoft.com/pricing/details/managed-disks), Azure SSD rounds up to the next size. For example, if you create a disk size of 100 GB, you pay at the 128 GB rate.
 
-Specifying a volume attaches the device(s) to your instance, but does not mount and format the device.
+When you specify a volume, you attach the devices to your instance but don't mount or format the device.
 
-## Further Reading
+## Further reading
 
 * [Mounting Volumes](mount-disk.md)
 * [Creating a Fileserver](create-fileserver.md)

articles/cyclecloud/how-to/add-node-array.md

@@ -2,22 +2,22 @@
 title: Add a Node Array
 description: How to add node arrays to a cluster
 author: dpwatrous
-ms.date: 03/27/2023
+ms.date: 06/30/2025
 ms.author: dawatrou
 ms.custom: compute-evergreen
 ---
 
-# Add a Node Array to a Cluster
+# Add a node array to a cluster
 
-Node arrays are used to define how nodes of a certain type are created/deleted as the cluster scales up and down. Each array has a name, a set of attributes which will be applied to each node in the array, and optional attributes describing how the array should scale (limits, placement groups, scale set configuration, etc).
+Use node arrays to define how the cluster creates and deletes nodes of a certain type as it scales up and down. Each node array has a name, a set of attributes that you apply to each node in the array, and optional attributes that describe how the array scales, such as limits, placement groups, and scale set configuration.
 
-This article shows you how to add a node array to an existing cluster using a template file. [Read more about node arrays.](../concepts/clusters.md#nodes-and-node-arrays)
+This article shows you how to add a node array to an existing cluster by using a template file. [Read more about node arrays.](../concepts/clusters.md#nodes-and-node-node-arrays)
 
-## Edit the Cluster Template
+## Edit the cluster template
 
-In order to add a node array, you must have a [template file](~/articles/cyclecloud/how-to/cluster-templates.md) for your cluster. Edit this file and add a new `[[nodearray]]` section underneath `[cluster]`, giving the array a unique name within that cluster.
+To add a node array, you need a [template file](~/articles/cyclecloud/how-to/cluster-templates.md) for your cluster. Edit this file and add a new `[[nodearray]]` section under the `[cluster]` section. Give the node array a unique name within the cluster.
 
-For example, the template below contains a node array named "highmem" which uses Standard_M64 VMs instead of the value specified in the node defaults (Standard_D4_v2):
+For example, the following template contains a node array named `highmem` that uses Standard_M64 VMs instead of the value specified in the node defaults (Standard_D4_v2):
 
 ```ini
 # hpc-template.txt
@@ -56,18 +56,18 @@ For example, the template below contains a node array named "highmem" which uses
 
 ## Reimport the modified cluster template
 
-To apply the cluster template changes and create the new node array, use the [CycleCloud CLI](../cli.md) to import the template. You must specify the name of the cluster to modify as well as the `--force` flag which tells the CLI to overwrite values in the existing cluster.
+To apply the cluster template changes and create the new node array, use the [CycleCloud CLI](../cli.md) to import the template. You must specify the name of the cluster to modify and include the `--force` flag to tell the CLI to overwrite values in the existing cluster.
 
-The command below would apply the changes above to a cluster named "example-cluster":
+The following command applies the changes to a cluster named `example-cluster`:
 
 ```CycleCloud CLI
 cyclecloud import_cluster example-cluster -f hpc-template.txt -c hpc --force
 ```
 
-To test your new node array, go to the web UI and click the "Add node" button. Select the "highmem" array and click "Add" to create a new node. To make further changes, simply edit the template file and re-run the import command above.
+To test your new node array, go to the web UI and select **Add node**. Select the `highmem` array and select **Add** to create a new node. To make further changes, edit the template file and run the import command again.
 
 ![Add Array Node](../images/node-add-from-array.png)
 
-## Further Reading
+## Further reading
 
 * [Node and Node Array Reference](../cluster-references/node-nodearray-reference.md)