acrolix fixes

Author: xpillons

articles/cyclecloud/how-to/ccws/configure-open-ondemand.md

@@ -2,15 +2,15 @@
 title: Configure Open Demand with CycleCloud
 description: How to configure Open OnDemand with CycleCloud
 author: xpillons
-ms.date: 04/30/2025
+ms.date: 05/27/2025
 ms.author: padmalathas
 ---
 
 # Configure Open OnDemand with CycleCloud
 Open OnDemand is a web-based interface that provides a user-friendly way to interact with the Slurm cluster deployed by Azure CycleCloud. Open OnDemand is automatically installed and configured when deploying Azure CycleCloud Workspace for Slurm, but there remain few steps that must be manually executed.
 
 ## Update settings for Microsoft Entra ID authentication
-The Open OnDemand front end uses Open ID Connect (OIDC) for authentication. The OIDC provider is an Microsoft Entra ID application that was registered specifically for this purpose (see [How to register an Microsoft Entra ID application for Open OnDemand Authentication](./register-entra-id-app.md)). The following steps describe how to update the settings for Entra ID authentication.
+The Open OnDemand front end uses Open ID Connect (OIDC) for authentication. The OIDC provider is a Microsoft Entra ID application that was registered specifically for this purpose (see [How to register a Microsoft Entra ID application for Open OnDemand Authentication](./register-entra-id-app.md)). The following steps describe how to update the settings for Entra ID authentication.
 
 Browse to the CycleCloud web portal, select the OpenOnDemand cluster, and click on the Edit button. This opens the cluster template definition. 
 1. Select Advanced settings,
@@ -24,7 +24,7 @@ Browse to the CycleCloud web portal, select the OpenOnDemand cluster, and click
  
 Press `Save` and then `Start Cluster` and wait for the Open OnDemand virtual machine to be ready.
 
-::image type="content" source="../../images/ccws/open-ondemand-advanced-settings.png" alt-text="Screenshot of Open OnDemand cluster configuration.":::
+:::image type="content" source="../../images/ccws/open-ondemand-advanced-settings.png" alt-text="Screenshot of Open OnDemand cluster configuration.":::
 
 ## Resources
 * [Add users for Open OnDemand](./open-ondemand-add-users.md)

articles/cyclecloud/how-to/ccws/connect-to-login-node-with-bastion.md

@@ -2,20 +2,20 @@
 title: How to connect to a Login Node through Bastion
 description: How to securily connect using SSH to a Login Node through Bastion
 author: xpillons
-ms.date: 08/30/2024
-ms.author: xpillons
+ms.date: 05/27/2025
+ms.author: padmalathas
 ---
 
 # How to connect to a Login Node through Bastion
-There is no SSH route open from your local environment to Virtual Machines running in an Azure CycleCloud Workspace for Slurm by default for security reasons. However, an Azure Bastion can be deployed and used to SSH through to your Virtual Machines. Below are the instructions on how to do based on this documentation: [Connect to a VM using Bastion](/azure/bastion/connect-vm-native-client-linux).
+There's no SSH route open from your local environment to Virtual Machines running in an Azure CycleCloud Workspace for Slurm by default for security reasons. However, an Azure Bastion can be deployed and used to SSH through to your Virtual Machines. Below are the instructions on how to do based on this documentation: [Connect to a VM using Bastion](/azure/bastion/connect-vm-native-client-linux).
 
 ## Step 1 – Identify the SSH private key locally
-Locate the private SSH key file associated with the public key provided during the deployment. If it is not accessible locally, then download it.
+Locate the private SSH key file associated with the public key provided during the deployment. If it isn't accessible locally, then download it.
 
 ## Step 2 – Retrieve the Resource ID of the Login Node
 From the CycleCloud UI, select the Login node to which you want to connect and double click on that line to open the detail view of the node. Select the VM tab to display the resource details below and copy the `ResourceId`.
 
-::image type="content" source="../../images/ccws/login-node-resource-id.png" alt-text="Login Node properties":::
+:::image type="content" source="../../images/ccws/login-node-resource-id.png" alt-text="Login Node properties":::
 
 ## Step 3 – Create a connect script
 Create a login script using the template below. Paste the login node `resourceID` retrieved above and specify the resource group and the private SSH key file to use.

articles/cyclecloud/how-to/ccws/connect-to-portal-with-bastion.md

@@ -1,16 +1,16 @@
 ---
 title: How to connect to the CycleCloud Portal through Bastion
-description: How to securily connect to the CycleCloud Portal using Bastion
+description: How to securely connect to the CycleCloud Portal using Bastion
 author: xpillons
-ms.date: 11/22/2024
+ms.date: 05/27/2025
 ms.author: padmalathas
 ---
 
 # How to connect to the CycleCloud Portal through Bastion
 You can deploy an Azure Bastion to establish an SSH tunnel to your Azure CycleCloud virtual machine when the HTTPS route is unavailable in your local environment. For detailed instructions, see [Connect to a VM - tunnel command](/azure/bastion/connect-vm-native-client-linux#tunnel).
 
 ## Step 1 – Retrieve the Resource ID of the CycleCloud VM
-To retrieve the resource ID of the `ccw-cyclecloud-vm` virtual machine, navigate to the Azure Portal. From the virtual machine view, select **Settings**, then **Properties**, and you will find the **ResourceID**.
+To retrieve the resource ID of the `ccw-cyclecloud-vm` virtual machine, navigate to the Azure portal. From the virtual machine view, select **Settings**, then **Properties**, and you'll find the **ResourceID**.
 
 ## Step 2 – Create a connect script
 Create a bash script using the template below. Paste the CycleCloud `resourceID` retrieved above.

articles/cyclecloud/how-to/ccws/deploy-with-cli.md

@@ -2,8 +2,8 @@
 title: How to deploy a CycleCloud Workspace for Slurm environment using the CLI
 description: How to deploy a CycleCloud Workspace for Slurm environment using the Azure CLI and the Azure portal UI Sandbox
 author: xpillons
-ms.date: 04/30/2025
-ms.author: xpillons
+ms.date: 05/27/2025
+ms.author: padmalathas
 ---
 
 # How to deploy a CycleCloud Workspace for Slurm environment using the CLI

articles/cyclecloud/how-to/ccws/open-ondemand-add-users.md

@@ -2,7 +2,7 @@
 title: Add users for Open OnDemand
 description: How to add users for Open OnDemand
 author: xpillons
-ms.date: 04/30/2025
+ms.date: 05/27/2025
 ms.author: padmalathas
 ---
 

articles/cyclecloud/how-to/ccws/plan-your-deployment.md

@@ -2,7 +2,7 @@
 title: Plan your CycleCloud Workspace for Slurm Deployment
 description: A checklist to help plan for your CycleCloud Workspace for Slurm deployment
 author: xpillons
-ms.date: 04/30/2025
+ms.date: 05/27/2025
 ms.author: padmalathas
 ---
 
@@ -44,8 +44,8 @@ In a brownfield deployment, you can provide existing resources for:
 - The VNET and subnets in which the environment is deployed.
 - Filesystem Storage for the user's home directories and/or other filers, such as external NFS mount points or Azure Managed Lustre Filesystem (AMLS).
 - An Azure Database for MySQL flexible server instance for Slurm Job Accounting.
-- A registered Entra ID application for Open OnDemand authentication.
-- A User-Assigned Managed Identity used by the registered Entra ID application for the federated credentials.
+- A registered Microsoft Entra ID application for Open OnDemand authentication.
+- A User-Assigned Managed Identity used by the registered Microsoft Entra ID application for the federated credentials.
 
 If you're bringing your own VNET, follow these prerequisites:
 - A /29 **cyclecloud** subnet for the CycleCloud VM.
@@ -57,9 +57,9 @@ If you're bringing your own VNET, follow these prerequisites:
 
 ## Open OnDemand
 
-The Azure Bastion tunneling scenario don't work for Open OnDemand. The recommended approach is to use a VPN Gateway with Point-to-Site (P2S) VPN connections or have Azure ExpressRoute configured to allow users to connect securely to the CycleCloud Workspace for Slurm network and access Open OnDemand.
+The Azure Bastion tunneling scenario doesn't work for Open OnDemand. The recommended approach is to use a VPN Gateway with Point-to-Site (P2S) VPN connections or has Azure ExpressRoute configured to allow users to connect securely to the CycleCloud Workspace for Slurm network and access Open OnDemand.
 
-Registration of a Microsoft Entra application is required to support the OpenID Connect authentication mechanism. Ensure that the user or subscription administrator have the proper roles to granted to complete the registration.
+Registration of a Microsoft Entra application is required to support the OpenID Connect authentication mechanism. Ensure that the user or subscription administrator have the proper roles to be granted to complete the registration.
 
 ## Quotas
 

articles/cyclecloud/how-to/ccws/register-entra-id-app.md

@@ -2,15 +2,15 @@
 title: Register a Microsoft Entra ID application for Open OnDemand authentication
 description: How to register a Microsoft Entra ID application for Open OnDemand authentication
 author: xpillons
-ms.date: 04/30/2025
+ms.date: 05/27/2025
 ms.author: padmalathas
 ---
 
 # Register a Microsoft Entra ID application for Open OnDemand authentication
 The Open OnDemand front end use Open ID Connect (OIDC) for authentication. The OIDC provider is a Microsoft Entra ID application that you need to register which uses Federated credentials with a User-Assigned Managed Identity to avoid storing secrets in the Open OnDemand configuration. The following steps describe how to register a Microsoft Entra ID application for Open OnDemand authentication.
 
 ## Microsoft Entra ID application registration right after a successful deployment
-After the deployment is finished, it is necessary to execute the following commands from a Linux shell with Azure CLI installed to register and configure the Microsoft Entra ID application for authentication. The account logged into the CLI must have the appropriate permissions to register an application and its active subscription must be the one used for the deployment if it is not already set.
+After the deployment is finished, it's necessary to execute the following commands from a Linux shell with Azure CLI installed to register and configure the Microsoft Entra ID application for authentication. The account logged into the CLI must have the appropriate permissions to register an application and its active subscription must be the one used for the deployment if it isn't already set.
 
 > [!NOTE]
 > Make sure you have `jq` utility installed on your system.
@@ -29,10 +29,10 @@ Update the redirect URI with either the private IP or the FQDN of the Open OnDem
 Verify that both the `ccw` and `OpenOnDemand` clusters are started. Although there may be some temporary errors, both clusters should be ready within a few minutes. 
 Complete the configuration of the registered application by adding a new redirect URI, 'https://\<ip\>/oidc', in the Authentication settings of the application as illustrated below.
 
-::image type="content" source="../../images/ccws/entraid-redirect-uri.png" alt-text="Screenshot of Microsoft Entra ID redirect URI update.":::
+:::image type="content" source="../../images/ccws/entraid-redirect-uri.png" alt-text="Screenshot of Microsoft Entra ID redirect URI update.":::
 
 ## Register a Microsoft Entra ID application before a deployment
-It is possible to register a Microsoft Entra ID application before the deployment of a full environment and configure it afterwards. 
+It's possible to register a Microsoft Entra ID application before the deployment of a full environment and configure it afterwards. 
 
 Create an  app.json parameter file containing:
 - **appName** : the name of the application to be registered,