Apply suggestions from code review

Co-authored-by: Pat Altimore <[email protected]>

Author: Albertyang0

articles/iot-operations/manage-mqtt-broker/howto-configure-authentication.md

@@ -17,7 +17,7 @@ ms.date: 11/11/2024
 
 [!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
 
-MQTT broker supports multiple authentication methods for clients, and you can configure each listener port to have its own authentication settings with a *BrokerAuthentication* resource. For a list of the available settings, see the [Broker Authentication](/azure/templates/microsoft.iotoperationsmq/change-log/mq/broker/authentication) API reference.
+MQTT broker supports multiple authentication methods for clients, and you can configure each listener port to have its own authentication settings with a *BrokerAuthentication* resource. For a list of the available settings, see the [Broker Authentication](/rest/api/iotoperations/broker-authentication) API reference.
 
 ## Link BrokerListener and BrokerAuthentication
 

articles/iot-operations/manage-mqtt-broker/howto-configure-authorization.md

@@ -30,7 +30,7 @@ To learn more about *BrokerListener*, see [BrokerListener resource](howto-config
 
 ## Authorization rules
 
-To configure authorization, create a *BrokerAuthorization* resource in your Kubernetes cluster. The following sections provide examples of how to configure authorization for clients that use usernames, attributes, X.509 certificates, and Kubernetes Service Account Tokens (SATs). For a list of the available settings, see the [Broker Authorization](/azure/templates/microsoft.iotoperationsmq/change-log/mq/broker/authorization) API reference.
+To configure authorization, create a *BrokerAuthorization* resource in your Kubernetes cluster. The following sections provide examples of how to configure authorization for clients that use usernames, attributes, X.509 certificates, and Kubernetes Service Account Tokens (SATs). For a list of the available settings, see the [Broker Authorization](/rest/api/iotoperations/broker-authorization) API reference.
 
 The following example shows how to create a *BrokerAuthorization* resource using both usernames and attributes:
 

articles/iot-operations/manage-mqtt-broker/howto-configure-availability-scale.md

@@ -19,7 +19,7 @@ The Broker resource is the main resource that defines the overall settings for M
 
 You can horizontally scale the MQTT broker by adding more frontend replicas and backend partitions. The frontend replicas are responsible for accepting MQTT connections from clients and forwarding them to the backend partitions. The backend partitions are responsible for storing and delivering messages to the clients. The frontend pods distribute message traffic across the backend pods, and the backend redundancy factor determines the number of data copies to provide resiliency against node failures in the cluster.
 
-For a list of the available settings, see the [Broker](/azure/templates/microsoft.iotoperationsmq/change-log/mq/broker) API reference.
+For a list of the available settings, see the [Broker](/rest/api/iotoperations/broker) API reference.
 
 ## Configure scaling settings
 

articles/iot-operations/manage-mqtt-broker/howto-configure-brokerlistener.md

@@ -33,7 +33,7 @@ Broker listeners have the following characteristics:
 - **TLS**: [Manual](#enable-tls-manual-certificate-management-for-a-port) or [automatic](#enable-tls-automatic-certificate-management-for-a-port) TLS configuration is applied per port.
 - **Protocol**: [MQTT over WebSockets](#websockets-support) can be enabled per port.
 
-For a list of all available settings, see the [Broker Listener API reference](/azure/templates/microsoft.iotoperationsmq/change-log/mq/broker/listener).
+For a list of all available settings, see the [Broker Listener API reference](/rest/api/iotoperations/broker-listener).
 
 ## Default BrokerListener
 
@@ -652,7 +652,7 @@ Once the BrokerListener resource is configured, MQTT broker automatically create
 
 The only required parameters are Issuer name and Issuer kind. All other properties of the generated TLS server certificates are automatically chosen. However, MQTT broker allows certain properties to be customized following the same syntax as cert-manager Certificates. For example, you can specify the private key algorithm and rotation policy. These settings are under `tls.certManagerCertificateSpec` or the **TLS configuration** pane in the Azure portal.
 
-For a full list of these settings, see [Broker Listener CertManagerCertificateSpec API reference](/azure/templates/microsoft.iotoperationsmq/change-log/mq/broker/listener).
+For a full list of these settings, see [Broker Listener CertManagerCertificateSpec API reference](/rest/api/iotoperations/broker-listener/create-or-update#certmanagercertificatespec).
 
 #### Verify deployment