Incorporate suggestions from review

Author: kgremban

articles/iot-operations/get-started/quickstart-deploy.md

@@ -34,17 +34,17 @@ The following quickstarts in this series build on this one to define sample asse
 
 This series of quickstarts is intended to give you an opportunity to evaluate an end-to-end scenario with Azure IoT Operations. In a true development or production environment, these tasks would be performed by multiple teams working together and some tasks might require elevated permissions.
 
-For the best new user experience, we recommend using a free Azure subscription so that you have owner permissions over the resources in these quickstarts. We also recommend using GitHub Codespaces as a virtual environment in which you can quickly begin deploying resources and running commands without installing new tools on your own machines. For more information about these options, continue to the prerequisites.
+For the best new user experience, we recommend using an [Azure free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) so that you have owner permissions over the resources in these quickstarts. We also recommend using GitHub Codespaces as a virtual environment in which you can quickly begin deploying resources and running commands without installing new tools on your own machines. For more information about these options, continue to the prerequisites.
 
 Once you're ready to learn more about the individual roles and tasks, the how-to guides provide more specific implementation and permissions details.
 
 ## Prerequisites
 
 Review the prerequisites based on the environment you use to host the Kubernetes cluster.
 
-For this quickstart, we recommend using a virtual environment as a quick way to get started without installing new tools.
+For this quickstart, we recommend using a virtual environment (GitHub Codespaces) as a quick way to get started without installing new tools.
 
-As part of this quickstart, you create a cluster in either GitHub Codespaces, AKS Edge Essentials, or K3s on Ubuntu Linux. If you want to reuse a cluster that you've deployed Azure IoT Operations to before, refer to the steps in [Clean up resources](#clean-up-resources) to uninstall Azure IoT Operations before continuing.
+As part of this quickstart, you create a cluster in either GitHub Codespaces, AKS Edge Essentials, or K3s on Ubuntu Linux. If you want to rerun this quickstart with a cluster that already has Azure IoT Operations deployed to it, refer to the steps in [Clean up resources](#clean-up-resources) to uninstall Azure IoT Operations before continuing.
 
 # [Virtual](#tab/codespaces)
 
@@ -319,7 +319,15 @@ In this quickstart, you configured your Arc-enabled Kubernetes cluster so that i
 
 If you're continuing on to the next quickstart, keep all of your resources.
 
-If you want to delete the Azure IoT Operations deployment but plan on reinstalling it on your cluster, be sure to keep the secrets provider on your cluster. In your cluster on the Azure portal, select the extensions of the type **microsoft.iotoperations.x** and **microsoft.deviceregistry.assets**, then select **Uninstall**.
+If you want to delete the Azure IoT Operations deployment but plan on reinstalling it on your cluster, be sure to keep the secrets provider on your cluster. 
+
+1. In your resource group in the Azure portal, select your cluster.
+1. On your cluster resource page, select **Extensions**.
+1. Select all of the extensions of type **microsoft.iotoperations.x** and **microsoft.deviceregistry.assets**, then select **Uninstall**. 
+
+   Keep the secrets provider extension on your cluster.
+
+1. Return to your resource group and select the custom location resource, then select **Delete**.
 
 If you want to delete all of the resources you created for this quickstart, delete the Kubernetes cluster that you deployed Azure IoT Operations to and remove the Azure resource group that contained the cluster.
 

articles/iot-operations/includes/connect-cluster.md

@@ -34,6 +34,7 @@ To connect your cluster to Azure Arc:
    # Azure region where the created resource group will be located
    # Currently supported regions: "eastus", "eastus2", "westus", "westus2", "westus3", "westeurope", or "northeurope"
    export LOCATION=<REGION>
+   ```
 
    ```bash
    # Name of a new resource group to create which will hold the Arc-enabled cluster and Azure IoT Operations resources
@@ -75,17 +76,14 @@ To connect your cluster to Azure Arc:
    az connectedk8s connect -n $CLUSTER_NAME -l $LOCATION -g $RESOURCE_GROUP --subscription $SUBSCRIPTION_ID
    ```
 
-1. Get the `objectId` of the Microsoft Entra ID application that the Azure Arc service uses. Run this command in the [Azure Cloud Shell](https://portal.azure.com/#cloudshell), on your local machine, or in a codespace terminal:
+1. Get the `objectId` of the Microsoft Entra ID application that the Azure Arc service uses and save it as an environment variable.
 
    ```azurecli
-   az ad sp show --id bc313c14-388c-4e7d-a58e-70017303ee3b --query id -o tsv
+   export OBJECT_ID=$(az ad sp show --id bc313c14-388c-4e7d-a58e-70017303ee3b --query id -o tsv)
    ```
 
-   Make a note of the `objectId`. You use it in the next step.
-
 1. Use the [az connectedk8s enable-features](/cli/azure/connectedk8s#az-connectedk8s-enable-features) command to enable custom location support on your cluster. This command uses the `objectId` of the Microsoft Entra ID application that the Azure Arc service uses. Run this command on the machine where you deployed the Kubernetes cluster:
 
     ```azurecli
-    export OBJECT_ID=<objectID from the previous step>
     az connectedk8s enable-features -n $CLUSTER_NAME -g $RESOURCE_GROUP --custom-locations-oid $OBJECT_ID --features cluster-connect custom-locations
     ```

articles/iot-operations/includes/prepare-codespaces.md

@@ -3,7 +3,7 @@
  description: include file
  author: kgremban
  ms.topic: include
- ms.date: 03/15/2024
+ ms.date: 03/20/2024
  ms.author: kgremban
 ms.custom:
   - include file
@@ -26,20 +26,16 @@ To get started with your codespace:
 
    [![Create an explore-iot-operations codespace](https://github.com/codespaces/badge.svg)](https://codespaces.new/Azure-Samples/explore-iot-operations?quickstart=1)
 
-1. Provide the following details to configure your codespace:
-
-   | Parameter | Value |
-   | --------- | ----- |
-   | SUBSCRIPTION_ID | Your Azure subscription ID. |
-   | RESOURCE_GROUP | A name for a new Azure resource group where your cluster will be created. Remember the resource group name to use in the following CLI commands. |
-   | LOCATION | An Azure region close to you. The following regions are supported in public preview: eastus, eastus2, westus, westus2, westus3, westeurope, or northeurope. Remember the region to use in the following CLI commands. |
+   You don't have to provide the recommended secrets at this step. If you do, make sure that you use the same values here and in the CLI commands in the next section.
 
 1. Select **Create new codespace**.
 
 1. Once the codespace is ready, select the menu button at the top left, then select **Open in VS Code Desktop**.
 
    ![Open VS Code desktop](media/prepare-codespaces/open-in-vs-code-desktop.png)
 
+1. If prompted, install the **GitHub Codespaces** extension for Visual Studio Code and sign in to GitHub.
+
 1. In Visual Studio Code, select **View** > **Terminal**.
 
    Use this terminal to run all of the command line and CLI commands for managing your cluster.