fix issues

Author: tfitzmac

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

@@ -16,7 +16,7 @@ Find the private SSH key file that matches the public key you provide during dep
 ## Step 2 – Get the resource ID of the authentication node
 In the CycleCloud UI, select the authentication node you want to connect to and double-click that line to open the detail view for the node. Select the **VM** tab to display the resource details, and copy the `ResourceId`.
 
-:::image type="content" source="../../images/ccws/login-node-resource-id.png" alt-text="Authentication node properties":::
+:::image type="content" source="../../images/ccws/login-node-resource-id.png" alt-text="Screenshot of authentication node properties":::
 
 ## Step 3 – Create a connect script
 Create an authentication script using the following template. Paste the authentication node `resourceID` from the previous step, and specify the resource group and the private SSH key file to use.

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

@@ -14,35 +14,35 @@ Prerequisites: Install the Azure CLI and Git, and then sign in or set your Azure
 
 1. Clone the Azure CycleCloud Workspace for Slurm on the latest stable release
 
-```bash
-git clone --depth 1 https://github.com/azure/cyclecloud-slurm-workspace.git
-```
+   ```bash
+   git clone --depth 1 https://github.com/azure/cyclecloud-slurm-workspace.git
+   ```
 
 1. Copy the content of the UI definition file `./uidefinitions/createUiDefinition.json`
 
 1. Browse to the UI Definition Sandbox:
     - For Azure Public Cloud [Azure Public portal](https://portal.azure.com/#view/Microsoft_Azure_CreateUIDef/SandboxBlade)
     - For Azure US Gov [Azure US Gov portal](https://portal.azure.us/#view/Microsoft_Azure_CreateUIDef/SandboxBlade)
 
-- Paste the content of the UI Definition file into the multiline text box on the right,
-- Select `Preview >>` in the bottom-left corner to bring up a UI experience. 
-- Go through each page of the UI flow to make sure that necessary values appear in the output payload described in the next step,
-- Go through the UI flow to the `Review + create` page and then select the link labeled `View outputs payload` to the right of the `Create` button to generate a pane with JSON-formatted text in its body on the right-hand side of the browser window,
-- Copy the JSON-formatted text into a local JSON file, 
-- Save it as `parameters.json` and note the path to it. This file is the Parameters File for the deployment,
-- Open the shell of your choice and go to the folder or directory that contains the `cyclecloud-slurm-workspace` repository you cloned earlier,
-- Accept the terms of the Cycle image plan:
-
-```bash
-az vm image terms accept --urn azurecyclecloud:azure-cyclecloud:cyclecloud8-gen2:latest
-```
-- Run the following deployment command in a shell. Substitute values for fields in square brackets (be sure to delete the brackets). The current directory is as described in the previous step.
-
-```bash
-az deployment sub create --template-file ./cyclecloud-slurm-workspace/bicep/mainTemplate.bicep --parameters parameters.json --location [ANY AZURE LOCATION E.G. eastus] --name [OPTIONAL BUT HELPFUL, DELETE IF UNUSED] 
-```
-
-- Wait until the shell indicates that the deployment was successful. You can also track the progress of the deployment in the Azure portal. Go to the resource group shown in the UI, select **Deployments** from the Settings menu, and check the status of the deployment name that begins with "pid-" at the bottom of the displayed list.
+1. Paste the content of the UI Definition file into the multiline text box on the right.
+1. Select `Preview >>` in the bottom-left corner to bring up a UI experience. 
+1. Go through each page of the UI flow to make sure that necessary values appear in the output payload described in the next step.
+1. Go through the UI flow to the `Review + create` page and then select the link labeled `View outputs payload` to the right of the `Create` button to generate a pane with JSON-formatted text in its body on the right-hand side of the browser window.
+1. Copy the JSON-formatted text into a local JSON file.
+1. Save it as `parameters.json` and note the path to it. This file is the Parameters File for the deployment.
+1. Open the shell of your choice and go to the folder or directory that contains the `cyclecloud-slurm-workspace` repository you cloned earlier.
+1. Accept the terms of the Cycle image plan:
+
+   ```bash
+   az vm image terms accept --urn azurecyclecloud:azure-cyclecloud:cyclecloud8-gen2:latest
+   ```
+1. Run the following deployment command in a shell. Substitute values for fields in square brackets (be sure to delete the brackets). The current directory is as described in the previous step.
+
+   ```bash
+   az deployment sub create --template-file ./cyclecloud-slurm-workspace/bicep/mainTemplate.bicep --parameters parameters.json --location [ANY AZURE LOCATION E.G. eastus] --name [OPTIONAL BUT HELPFUL, DELETE IF UNUSED] 
+   ```
+
+1. Wait until the shell indicates that the deployment was successful. You can also track the progress of the deployment in the Azure portal. Go to the resource group shown in the UI, select **Deployments** from the Settings menu, and check the status of the deployment name that begins with "pid-" at the bottom of the displayed list.
 
 ## Resources