Merge pull request #301145 from Padmalathas/Cyclecloud_Content_Fixes

CycleCloud_Content_Quality_Improvements

Author: PMEds28

articles/cyclecloud/api.md

@@ -3,7 +3,7 @@ title: API Reference
 description: Read the Azure CycleCloud REST API Reference. Review commands for operations and resources, such as getting cluster nodes or getting the status of the cluster.
 author: adriankjohnson
 ms.topic: reference
-ms.date: 7/15/2024
+ms.date: 06/10/2025
 ms.author: adjohnso
 monikerRange: '>= cyclecloud-8'
 ---

articles/cyclecloud/cli.md

@@ -2,8 +2,8 @@
 title: Azure CycleCloud CLI Reference
 description: CycleCloud CLI reference 
 author: rokeptne
-ms.date: 07/15/2024
-ms.author: rokeptne
+ms.date: 06/10/2025
+ms.author: padmalathas
 ---
 
 # CycleCloud CLI

articles/cyclecloud/cookbook-reference.md

@@ -3,7 +3,7 @@ title: Cookbook Reference
 description: See reference information for Chef Cookbooks in Azure CycleCloud. Understand basic Chef concepts, attributes, and the thunderball resource.
 author: adriankjohnson
 ms.topic: reference
-ms.date: 03/09/2020
+ms.date: 06/10/2025
 ms.author: adjohnso
 ---
 
@@ -26,7 +26,7 @@ However, CycleCloud clusters are provisioned using a set of *Common Cookbooks* a
 
 Common Cookbook attributes are subject to change. Attribute settings are commonly superseded as the features they control become available as more general or powerful features of CycleCloud. If a customization is available in both the Cluster Template and via a Chef attribute, always prefer the Cluster Template method since it's the more general solution.
 
-For more information on the Opscode Chef framework, see the [Opscode website](https://docs.opscode.com/).
+For more information on the Opscode Chef framework, see the [Opscode website](https://www.chef.io/).
 
 ## Using Chef attributes
 
@@ -81,4 +81,4 @@ To download objects from another repository, use custom configuration sections.
 | proxy_host  | Host to use as proxy.    |
 | proxy_port  | Port to use for proxy.  |
 | user        | Local system user for the configuration. If you specify the `user` attribute, the `filename` attribute is ignored. the user's home directory contains the configuration file. |
-| username    | Access_key/username for Azure.  |
+| username    | Access_key/username for Azure.  |

articles/cyclecloud/cycleserver-configuration-reference.md

@@ -2,7 +2,7 @@
 title: CycleServer Configuration Reference
 description: Configuration reference for cycle_server.properties file
 author: atomic-penguin
-ms.date: 03/28/2025
+ms.date: 06/10/2025
 ms.author: erwolfe
 ---
 

articles/cyclecloud/data-policy.md

@@ -2,7 +2,7 @@
 title: Data Usage Policy
 description: Read about data usage policy. See how telemetry data is collected and used within Azure CycleCloud. 
 author: KimliW
-ms.date: 06/26/2021
+ms.date: 06/10/2025
 ms.author: adjohnso
 ---
 

articles/cyclecloud/download-cluster-templates.md

@@ -2,7 +2,7 @@
 title: Download Cluster Projects and Templates
 description: Azure CycleCloud has built-in templates you can configure and edit to make your own custom templates.
 author: adriankjohnson
-ms.date: 07/17/2019
+ms.date: 06/10/2025
 ms.author: adjohnso
 ---
 

articles/cyclecloud/error-messages.md

@@ -2,12 +2,13 @@
 title: Error Messages
 description: List of common CycleCloud error messages.
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/10/2025
 ms.author: adjohnso
 ---
+
 # Error Messages
 
-A list of error messages one encounters in CycleCloud
+A compilation of error messages encountered in Azure CycleCloud.
 
 ## Staging Resources
 

articles/cyclecloud/events.md

@@ -2,7 +2,7 @@
 title: Node Events
 description: Use the CycleCloud Events integration to get notified on state changes 
 author: dougclayton
-ms.date: 08/16/2020
+ms.date: 06/10/2025
 ms.author: doclayto
 monikerRange: '>= cyclecloud-8'
 ---
@@ -15,7 +15,7 @@ You can configure CycleCloud to publish to an Event Grid *topic* by connecting i
 
 ## Event objects
 
-The events are in the standard Event Grid schema. All CycleCloud-specific elements are in the `data` property on the event.
+The events follow the standard Event Grid schema, with all CycleCloud-specific details contained within the `data` property.
 
 | Name | Type | Description |
 | - | - | - |
@@ -71,7 +71,7 @@ This event is fired when nodes are added to the cluster. There's one event for e
 
 ### Node events
 
-CycleCloud sends events when nodes change state. Node events contain additional information in the `data` property:
+CycleCloud sends events whenever nodes transition between states. These node events include additional context within the `data` property:
 
 | Property | Type | Description |
 | - | - | - |
@@ -91,33 +91,33 @@ CycleCloud sends events when nodes change state. Node events contain additional
 
 #### Microsoft.CycleCloud.NodeAdded
 
-This event is fired for each node that is added to a cluster. To get an event for a set of nodes added at once, see [ClusterSizeIncreased](#microsoftcyclecloudclustersizeincreased). This event is sent when the node first appears in the UI, so it doesn't have any timing information.
+This event is triggered for each node added to a cluster. To receive a single event for multiple nodes added simultaneously, see [ClusterSizeIncreased](#microsoftcyclecloudclustersizeincreased). This event is sent when the node first appears in the UI, so it doesn't have any timing information.
 
 #### Microsoft.CycleCloud.NodeCreated
 
-This event is fired each time a node starts for the first time (that is, a VM is created for the node). This event contains the following timing information:
+This event is triggered each time a node starts for the first time (that is, when a VM is created for the node). It includes the following timing details:
 
   - `Create`: The total time to create the node. This time includes creating the VM and configuring the VM.
   - `CreateVM`: How long it took to create the VM.
   - `Configure`: How long it took to install software and configure the node.
 
 #### Microsoft.CycleCloud.NodeDeallocated
 
-This event is fired each time a node is deallocated. This event contains the following timing information:
+This event is triggered each time a node is deallocated. It includes the following timing details:
 
   - `Deallocate`: The total time to deallocate the node.
   - `DeallocateVM`: How long it took to deallocate the VM.
 
 #### Microsoft.CycleCloud.NodeStarted
 
-This event is fired each time a node restarts from a deallocated state. This event contains the following timing information:
+This event is triggered each time a node restarts from a deallocated state. It includes the following timing details:
 
   - `Start`: The total time it took to restart the deallocated node.
   - `StartVM`: How long it took to start the deallocated VM.
 
 #### Microsoft.CycleCloud.NodeTerminated
 
-This event is fired each time a node is terminated and its VM is deleted. This event contains the following timing information:
+This event is triggered each time a node is terminated and its VM is deleted. It includes the following timing details:
 
   - `Terminate`: The total time it took to terminate the node.
   - `DeleteVM`: How long it took to delete the VM.
@@ -191,4 +191,3 @@ You can use this timing to track how long a spot VM was running before it was ev
 ### Retry Count
 
 In CycleCloud, you can retry some operations if they fail. These operations are reflected in the `NodeCreated`, `NodeDeallocated`, `NodeStarted`, and `NodeTerminated` events. These events contain an optional `retryCount` property on the event's `data` property that indicates how many times the operation was attempted prior to this event. This property is included on subsequent retries, whether those attempts succeeded or failed.
-