Skip to content

Commit ce2e158

Browse files
committed
refining
1 parent 959846f commit ce2e158

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,11 +34,11 @@ The following quickstarts in this series build on this one to define sample asse
3434

3535
This series of quickstarts is intended to help you get started with Azure IoT Operations as quickly as possible so that you can evaluate an end-to-end scenario. In a true development or production environment, these tasks would be performed by multiple teams working together and some tasks might require elevated permissions.
3636

37-
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.
37+
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 provide steps to use 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.
3838

3939
## Prerequisites
4040

41-
For this quickstart, you create a Kubernetes cluster to receive the Azure IoT Operations deployment. We recommend using GitHub Codespaces to host the cluster as a quick way to get started without installing new tools.
41+
For this quickstart, you create a Kubernetes cluster to receive the Azure IoT Operations deployment.
4242

4343
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.
4444

@@ -54,7 +54,7 @@ Before you begin, prepare the following prerequisites:
5454

5555
Azure IoT Operations is a suite of data services that run on Kubernetes clusters. You want these clusters to be managed remotely from the cloud, and able to securely communicate with cloud resources and endpoints. We address these concerns with the following tasks in this quickstart:
5656

57-
1. Connect a Kubernetes cluster to Azure Arc for remote management.
57+
1. Create a Kubernetes cluster and connect it to Azure Arc for remote management.
5858
1. Create an Azure Key Vault to manage secrets for your cluster.
5959
1. Configure your cluster with a secrets store and service principal to communicate with cloud resources.
6060
1. Deploy Azure IoT Operations to your cluster.
@@ -145,7 +145,7 @@ If you want to delete the Azure IoT Operations deployment but plan on reinstalli
145145

146146
1. In your resource group in the Azure portal, select your cluster.
147147
1. On your cluster resource page, select **Extensions**.
148-
1. Select all of the extensions of type **microsoft.iotoperations.x** and **microsoft.deviceregistry.assets**, then select **Uninstall**. You don't need to uninstall the secrets provider extension:
148+
1. Select all of the extensions of type **microsoft.iotoperations.x** and **microsoft.deviceregistry.assets**, then select **Uninstall**. Don't uninstall the secrets provider extension.
149149

150150
:::image type="content" source="media/quickstart-deploy/uninstall-extensions.png" alt-text="Screenshot that shows the extensions to uninstall.":::
151151

articles/iot-operations/get-started/quickstart-upload-telemetry-to-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Create a lakehouse in your Microsoft Fabric workspace:
8080

8181
Your codespace comes with the following sample connector configuration file, `/workspaces/explore-iot-operations/samples/quickstarts/datalake-connector.yaml`:
8282

83-
:::code language="yaml" source="~/azure-iot-operations-samples/samples/quickstarts/datalake-connector.yaml":::
83+
:::code language="yaml" source="~/azure-iot-operations-samples/samples/quickstarts/datalake-connector.yaml":::
8484

8585
1. Open the _datalake-connector.yaml_ file in a text editor and replace `<your-workspace-name>` with the name of your Microsoft Fabric workspace. You made a note of this value when you created the workspace.
8686

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Use GitHub Codespaces to try Azure IoT Operations on a Kubernetes cluster withou
2020
> [!IMPORTANT]
2121
> Codespaces are easy to set up quickly and tear down later, but they're not suitable for performance evaluation or scale testing. Use GitHub Codespaces for exploration only.
2222
23-
To get started with your codespace:
23+
To create your codespace and cluster, use the following steps:
2424

2525
1. Create a codespace in GitHub Codespaces.
2626

0 commit comments

Comments
 (0)