Acrolinx fixes

Author: denrea

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

@@ -60,7 +60,7 @@ If not already set up, use the following steps to enable workload identity on an
                           --enable-oidc-issuer --enable-workload-identity 
    ```
 
-1. Use the [az connectedk8s show](/cli/azure/connectedk8s#az-connectedk8s-show) command to to get the cluster's issuer url. Take a note to add it later in K3s config file.
+1. Use the [az connectedk8s show](/cli/azure/connectedk8s#az-connectedk8s-show) command to get the cluster's issuer url. Take a note to add it later in K3s config file.
 
    ```azurecli
    #!/bin/bash
@@ -102,7 +102,7 @@ Secrets Management for Azure IoT Operations uses Secret Store extension to sync
 
 Secret Store extension requires a user-assigned managed identity with access to the Azure Key Vault where secrets are stored. To learn more, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview).
 
-1. Create an [Azure Key Vault](/azure/key-vault/secrets/quick-create-cli) which will be used to store secrets.
+1. Create an [Azure Key Vault](/azure/key-vault/secrets/quick-create-cli) that will be used to store secrets.
 2. Make sure you have `Key Vaults Secrets Officer` role on the Azure Key Vault.
 3. Create a [User Assigned Managed Identity](/entra/identity/managed-identities-azure-resources/overview) for secret store extension.
 5. Use the [az iot ops secretsync enable](/cli/azure/iot/ops/secretsync#az-iot-ops-secretsync-enable) command to set up the Azure IoT Operations instance for secret synchronization.