Merge pull request #125102 from ArieHein/Spelling-Wave-28

v-dirichards · web-flow · commit ce4e0fcefc6b · 2024-12-11T10:18:42.000-06:00
Spelling Fixes
diff --git a/articles/iot-hub-device-update/device-update-configuration-file.md b/articles/iot-hub-device-update/device-update-configuration-file.md
@@ -34,8 +34,8 @@ When installing Debian agent on an IoT Device with a Linux OS, modify the `/etc/
 | manufacturer | Reported by the **AzureDeviceUpdateCore:4.ClientMetadata:4** interface to classify the device for targeting the update deployment. |
 | model | Reported by the **AzureDeviceUpdateCore:4.ClientMetadata:4** interface to classify the device for targeting the update deployment. |
 | iotHubProtocol| Accepted values are `mqtt` or `mqtt/ws` to change the protocol used to connect with IoT hub. Default value is 'mqtt' |
-| compatPropertyNames | These properties are used to check for compatibility of the device to target the update deployment. For all the properties specified to be used for compatabiity, the values must be in lower case only |
-| additionalProperties | Optional field. Additional device reported properties can be set and used for comaptibility checking . Limited to five device properties. These properties should be in lower case only. |
+| compatPropertyNames | These properties are used to check for compatibility of the device to target the update deployment. For all the properties specified to be used for compatibility, the values must be in lower case only |
+| additionalProperties | Optional field. Additional device reported properties can be set and used for compatibility checking . Limited to five device properties. These properties should be in lower case only. |
 | connectionType | Accepted values are `string` or `AIS`. Use `string` when connecting the device to IoT Hub manually for testing purposes. For production scenarios, use `AIS` when using the IoT Identity Service to connect the device to IoT Hub. For more information, see [understand IoT Identity Service configurations](https://azure.github.io/iot-identity-service/configuration.html). |
 | connectionData  |If connectionType = "string", add your IoT device's device or module connection string here. If connectionType = "AIS", set the connectionData to empty string (`"connectionData": ""`). |
 | manufacturer | Reported by the Device Update agent as part of the **DeviceInformation** interface. |
diff --git a/articles/iot-hub-device-update/device-update-simulator.md b/articles/iot-hub-device-update/device-update-simulator.md
@@ -114,7 +114,7 @@ The Device Update agent runs on every device that's managed by Device Update. Fo
    For more information about the parameters in this step, see [Device Update configuration file](device-update-configuration-file.md).
 
    > [!NOTE]
-   >You can also use the IoT Identity Service to provision the device. To do, that [install the iot indentity service](https://azure.github.io/iot-identity-service/installation.html) before installing the Device Update agent. Then, configure the Device Update agent with `"connectionType": "AIS"` and `connectionData` as a blank string in the configuration file.
+   >You can also use the IoT Identity Service to provision the device. To do, that [install the iot identity service](https://azure.github.io/iot-identity-service/installation.html) before installing the Device Update agent. Then, configure the Device Update agent with `"connectionType": "AIS"` and `connectionData` as a blank string in the configuration file.
 
 1. Save and close the file. `CTRL`+`X`, `Y`, and `Enter`.
 
diff --git a/articles/iot-hub/iot-hub-devguide-quotas-throttling.md b/articles/iot-hub/iot-hub-devguide-quotas-throttling.md
@@ -89,7 +89,7 @@ The same throttle limits apply to identity operations made through [bulk registr
 
 ### Device connections throttle
 
-The *device connections* throttle governs the rate at which new device connections can be established with an IoT hub. The *device connections* throttle doesn't relate to the maximum number of simultaneously connected devices. Increate the number of units in an IoT hub to increase the *device connections* rate.
+The *device connections* throttle governs the rate at which new device connections can be established with an IoT hub. The *device connections* throttle doesn't relate to the maximum number of simultaneously connected devices. Increase the number of units in an IoT hub to increase the *device connections* rate.
 
 For example, if you buy a single S1 unit, you get a throttle of 100 connections/second. Therefore, to connect 100,000 devices, it takes at least 1,000 seconds (approximately 16 minutes). However, you can have as many simultaneously connected devices as you have devices registered in your identity registry (up to 1,000,000).
 
diff --git a/articles/iot-hub/iot-hub-ip-filtering.md b/articles/iot-hub/iot-hub-ip-filtering.md
@@ -141,7 +141,7 @@ Your IoT Hub's IP filters can be retrieved and set through [Azure PowerShell](/p
 
 ```powershell
 # Get your IoT Hub resource using its name and its resource group name
-$iothubResource = Get-AzResource -ResourceGroupName <resourceGroupNmae> -ResourceName <iotHubName> -ExpandProperties
+$iothubResource = Get-AzResource -ResourceGroupName <resourceGroupName> -ResourceName <iotHubName> -ExpandProperties
 
 # Access existing IP filter rules
 $iothubResource.Properties.networkRuleSets.ipRules |% { Write-host $_ }
diff --git a/articles/iot-hub/iot-hub-scaling.md b/articles/iot-hub/iot-hub-scaling.md
@@ -97,7 +97,7 @@ Once you've chosen the tier that provides the best features for your solution, d
 
 Each IoT Hub tier is available in three sizes, based around how much data throughput they can handle in any given day. These sizes are numerically identified as 1, 2, and 3.
 
-A tier-size pair is represented as an *edition*. A basic tier IoT hub of size 2 is represented by the edition **B2**. Similarly, a standard tier IoT hub of size 3 is represented by the edition **S3**. For more information, includig pricing details, see [IoT Hub edition](https://azure.microsoft.com/pricing/details/iot-hub/)
+A tier-size pair is represented as an *edition*. A basic tier IoT hub of size 2 is represented by the edition **B2**. Similarly, a standard tier IoT hub of size 3 is represented by the edition **S3**. For more information, including pricing details, see [IoT Hub edition](https://azure.microsoft.com/pricing/details/iot-hub/)
 
 Once you choose an edition for your IoT hub, you can multiple its messaging capacity by increasing the number of *units*.
 
diff --git a/articles/iot-hub/tutorial-connectivity.md b/articles/iot-hub/tutorial-connectivity.md
@@ -117,7 +117,7 @@ In some scenarios, such as in a cloud protocol gateway or as part of a custom au
 > [!NOTE]
 > The SimulatedDevice-2.js sample includes examples of generating a SAS token both with and without the SDK.
 
-1. Run the [az iot hub genereate-sas-token](/cli/azure/iot/hub#az-iot-hub-generate-sas-token) command to generate a known-good SAS token using the CLI:
+1. Run the [az iot hub generate-sas-token](/cli/azure/iot/hub#az-iot-hub-generate-sas-token) command to generate a known-good SAS token using the CLI:
 
    ```azurecli-interactive
    az iot hub generate-sas-token --device-id {your_device_id} --hub-name {your_iot_hub_name}
diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-adlsv2-endpoint.md b/articles/iot-operations/connect-to-cloud/howto-configure-adlsv2-endpoint.md
@@ -312,7 +312,7 @@ dataLakeStorageSettings: {
   authentication: {
     method: 'UserAssignedManagedIdentity'
     userAssignedManagedIdentitySettings: {
-      cliendId: '<ID>'
+      clientId: '<ID>'
       tenantId: '<ID>'
       // Optional, defaults to 'https://storage.azure.com/.default'
       // scope: 'https://<SCOPE_URL>'
diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint.md b/articles/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint.md
@@ -63,7 +63,7 @@ Once the Azure Event Hubs namespace and event hub is configured, you can create
     | Setting              | Description                                                                                       |
     | -------------------- | ------------------------------------------------------------------------------------------------- |
     | Name                 | The name of the dataflow endpoint.                                     |
-    | Host                 | The hostname of the Kafka broker in the format `<NAMEPSACE>.servicebus.windows.net:9093`. Include port number `9093` in the host setting for Event Hubs. |
+    | Host                 | The hostname of the Kafka broker in the format `<NAMESPACE>.servicebus.windows.net:9093`. Include port number `9093` in the host setting for Event Hubs. |
     | Authentication method| The method used for authentication. We recommend that you choose [*System assigned managed identity*](#system-assigned-managed-identity) or [*User assigned managed identity*](#user-assigned-managed-identity). |
 
 1. Select **Apply** to provision the endpoint.
@@ -238,7 +238,7 @@ To configure a dataflow endpoint for non-Event-Hub Kafka brokers, set the host,
     | Setting              | Description                                                                                       |
     | -------------------- | ------------------------------------------------------------------------------------------------- |
     | Name                 | The name of the dataflow endpoint.                                     |
-    | Host                 | The hostname of the Kafka broker in the format `<Kafa-broker-host>:xxxx`. Include port number in the host setting. |
+    | Host                 | The hostname of the Kafka broker in the format `<Kafka-broker-host>:xxxx`. Include port number in the host setting. |
     | Authentication method| The method used for authentication. Choose [*SASL*](#sasl). |
     | SASL type            | The type of SASL authentication. Choose *Plain*, *ScramSha256*, or *ScramSha512*. Required if using *SASL*. |
     | Synced secret name   | The name of the secret. Required if using *SASL*. |
diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md b/articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md
@@ -509,7 +509,7 @@ mqttSettings: {
   authentication: {
     method: 'UserAssignedManagedIdentity'
     userAssignedManagedIdentitySettings: {
-      cliendId: '<ID>'
+      clientId: '<ID>'
       tenantId: '<ID>'
       // Optional, defaults to 'https://eventgrid.azure.net/.default'
       // scope: 'https://<SCOPE_URL>' 
diff --git a/articles/iot-operations/create-edge-apps/concept-about-state-store-protocol.md b/articles/iot-operations/create-edge-apps/concept-about-state-store-protocol.md
@@ -305,7 +305,7 @@ Assume that `Client1` goes first with a request of `SET LockName Client1 NEX PX
 
 ### Use the fencing tokens on SET requests
 
-When `Client1` successfully does a `SET` ("AquireLock") on `LockName`, the state store returns the version of `LockName` as a Hybrid Logical Clock (HLC) in the MQTT5 user property `__ts`.
+When `Client1` successfully does a `SET` ("AcquireLock") on `LockName`, the state store returns the version of `LockName` as a Hybrid Logical Clock (HLC) in the MQTT5 user property `__ts`.
 
 When a client performs a `SET` request, it can optionally include the MQTT5 user property `__ft` to represent a "fencing token". The `__ft` is represented as an HLC. The fencing token associated with a given key-value pair provides lock ownership checking. The fencing token can come from anywhere. For this scenario, it should come from the version of `LockName`.
 
diff --git a/articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md b/articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md
@@ -150,7 +150,7 @@ Use these steps if you chose the **Test settings** option on the **Dependency ma
 
         | Parameter | Value | Description |
         | --------- | ----- | ----------- |
-        | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.enpoint=4317**. |
+        | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.endpoint=4317**. |
         | `--ops-config` | `observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>` | Provide the **check_interval** value you configured in the otel-collector-values.yaml file.<br><br>The sample value used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) is **check_interval=60**. |
   
       * If you followed the optional prerequisites to set up your own certificate authority issuer, add the `--trust-settings` parameters to the `create` command:
@@ -221,7 +221,7 @@ Use these steps if you chose the **Secure settings** option on the **Dependency
 
       | Optional parameter | Value | Description |
       | --------- | ----- | ----------- |
-      | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.enpoint=4317**. |
+      | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.endpoint=4317**. |
       | `--ops-config` | `observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>` | Provide the **check_interval** value you configured in the otel-collector-values.yaml file.<br><br>The sample value used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) is **check_interval=60**. |
 
       This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md
@@ -87,7 +87,7 @@ You should complete this step in an *internet facing environment outside of the
     ```
     
     > [!IMPORTANT]
-    > Be sure to use the `--disable=traefik` parameter to disable treafik. Otherwise, you might have an issue when you try to allocate public IP for the Layered Network Management service in later steps.
+    > Be sure to use the `--disable=traefik` parameter to disable traefik. Otherwise, you might have an issue when you try to allocate public IP for the Layered Network Management service in later steps.
 
     As an alternative, you can configure the K3S offline using the steps in the [Air-Gap Install](https://docs.k3s.io/installation/airgap) documentation *after* you move the device to the isolated network environment.
 1. Copy the K3s configuration yaml file to `.kube/config`.
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md
@@ -60,7 +60,7 @@ The following steps for setting up [AKS Edge Essentials](/azure/aks/hybrid/aks-e
     Refer to the [K3s quick-start guide](https://docs.k3s.io/quick-start) for more detail.
 
     > [!IMPORTANT]
-    > Be sure to use the `--disable=traefik` parameter to disable treafik. Otherwise, you might have an issue when you try to allocate public IP for the Layered Network Management service in later steps.
+    > Be sure to use the `--disable=traefik` parameter to disable traefik. Otherwise, you might have an issue when you try to allocate public IP for the Layered Network Management service in later steps.
 
 1. Copy the K3s configuration yaml file to `.kube/config`.
 
diff --git a/articles/iot-operations/manage-layered-network/howto-configure-layered-network.md b/articles/iot-operations/manage-layered-network/howto-configure-layered-network.md
@@ -151,7 +151,7 @@ After setting up the K3S cluster and moving it to the level 3 isolated layer, co
     Address 1: 20.81.111.118
     pod "busybox" deleted
     
-    # Note: confirm that the resolved ip addresss matches the ip address of the level 4 Layered Network Management instance.
+    # Note: confirm that the resolved ip address matches the ip address of the level 4 Layered Network Management instance.
     ```
 
 1. The previous step sets the DNS configuration to resolve the allowlisted URLs inside the cluster to level 4. To ensure that DNS outside the cluster is doing the same, you need to configure systemd-resolved to forward traffic to CoreDNS inside the K3S cluster. Run the following commands on the K3S host:
diff --git a/articles/iot-operations/troubleshoot/known-issues.md b/articles/iot-operations/troubleshoot/known-issues.md
@@ -43,7 +43,7 @@ This article lists the known issues for Azure IoT Operations.
 
 ## Azure IoT Layered Network Management (preview)
 
-- If the Layered Network Management service doesn't get an IP address while running K3S on Ubuntu host, reinstall K3S without _trafeik ingress controller_ by using the `--disable=traefik` option.
+- If the Layered Network Management service doesn't get an IP address while running K3S on Ubuntu host, reinstall K3S without _traefik ingress controller_ by using the `--disable=traefik` option.
 
     ```bash
     curl -sfL https://get.k3s.io | sh -s - --disable=traefik --write-kubeconfig-mode 644
