Minor corrections

Author: dominicbetts

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

@@ -169,10 +169,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
 
    > [!TIP]
    > The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
-<!--
-    > [!IMPORTANT]
-    > When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
--->
 
    This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md

@@ -154,10 +154,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
     > The `init` command only needs to be run once per cluster. If you followed the optional prerequisite to set up your own certificate authority issuer, follow the steps in [Bring your own issuer](../secure-iot-ops/howto-manage-certificates.md#bring-your-own-issuer).
 
     This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
-<!--
-    > [!IMPORTANT]
-    > When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
--->
 
 1. To deploy Azure IoT Operations, copy and run the provided [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command. This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 

articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md

@@ -254,10 +254,6 @@ Before deploying Azure IoT Operations, you will need to update the Pod Security
 ```azurecli
 kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/tanzu-config/psa.yaml
 ```
-<!--
-> [!IMPORTANT]
-> When you initialize your Azure IoT Operations instance on a VKS cluster with its [pod security admission controller running in restricted mode](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vsphere-supervisor-services-and-standalone-components/latest/managing-vsphere-kuberenetes-service-clusters-and-workloads/managing-security-for-tkg-service-clusters/configure-psa-for-tkr-1-25-and-later.html) you must include the `--cm-config global.telemetry.logs.enabled=false` flag when you run `az iot ops init`.
--->
 
 ### Arc-enable your cluster
 

articles/iot-operations/includes/supported-environments.md

@@ -10,4 +10,4 @@ ms.custom:
 ---
 
 > [!IMPORTANT]
-> Currently, K3s on Ubuntu 24.04 and Tanzu Kubernetes Service are the only platforms for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).
+> Currently, K3s on Ubuntu 24.04 and Tanzu Kubernetes are the only platforms for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).