Merge pull request #308753 from sethmanheim/addcon

Restore related content per guidelines

Author: prmerger-automator[bot]

articles/iot-operations/manage-mqtt-broker/howto-broker-diagnostics.md

@@ -87,6 +87,6 @@ az iot ops create ... --broker-config-file <FILE>.json
 
 Learn more in [Azure CLI support for advanced MQTT broker configuration](https://aka.ms/aziotops-broker-config) and [Broker examples](/rest/api/iotoperations/broker/create-or-update#examples).
 
-## Next steps
+## Related content
 
 - [Deploy observability resources and set up logs](../configure-observability-monitoring/howto-configure-observability.md)

articles/iot-operations/manage-mqtt-broker/howto-broker-mqtt-client-options.md

@@ -90,7 +90,7 @@ The `maxMessageExpirySeconds` setting defines a global upper limit for message e
 
 By default, `maxMessageExpirySeconds` is not set. In this case, retained messages do not expire unless an expiry interval is explicitly defined in the message.
 
-## Next steps
+## Related content
 
 - [Configure listeners for the MQTT broker](./howto-configure-brokerlistener.md)
 - [Test connectivity to the MQTT broker](./howto-test-connection.md)

articles/iot-operations/manage-mqtt-broker/howto-broker-persistence.md

@@ -345,6 +345,6 @@ az iot ops broker persist update --resource-group myResourceGroup --instance myA
 
 ---
 
-## Next steps
+## Related content
 
 To learn more about Azure CLI support for advanced MQTT broker configuration, see [Azure CLI support for advanced MQTT broker configuration](https://aka.ms/aziotops-broker-config).

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

@@ -1305,7 +1305,7 @@ SAT clients send an AUTH client with the fields `method: K8S-SAT` and `data: <to
 
 Successful reauthentication updates the client's credential expiry with the expiry time of its new credential. The broker responds with a `Success` AUTH packet. Failed authentication because of transient issues, such as the custom authentication server being unavailable, causes the broker to respond with a `ContinueAuthentication` AUTH packet. The client can try again later. Other authentication failures cause the broker to send a DISCONNECT packet and close the client's network connection.
 
-## Next steps
+## Related content
 
 - [BrokerListener resource](howto-configure-brokerlistener.md)
 - [Configure authorization for a BrokerListener](./howto-configure-authorization.md)

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

@@ -338,6 +338,6 @@ affinity:
 
 These rules are the only anti-affinity rules set for the broker.
 
-## Next steps
+## Related content
 
 - [Configure listeners for the MQTT broker](./howto-configure-brokerlistener.md)

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

@@ -997,7 +997,7 @@ mqtts-endpoint         LoadBalancer   10.X.X.X        172.X.X.X     8885:30674/T
 
 From here, follow the same steps as previously shown to create a server certificate with this external IP in `--san` and create the Kubernetes secret in the same way. After the secret is created, it's automatically imported to the listener.
 
-## Next steps
+## Related content
 
 - [Configure MQTT broker authorization](howto-configure-authorization.md)
 - [Configure MQTT broker authentication](howto-configure-authentication.md)

articles/iot-operations/manage-mqtt-broker/howto-encrypt-internal-traffic.md

@@ -67,6 +67,6 @@ Then, deploy IoT Operations by using the `az iot ops create` command with `--bro
 
 To learn more, see [Azure CLI support for advanced MQTT broker configuration](https://aka.ms/aziotops-broker-config) and [Broker examples](/rest/api/iotoperations/broker/create-or-update#examples).
 
-## Next steps
+## Related content
 
 - [Configure broker listeners](./howto-configure-brokerlistener.md)

articles/iot-operations/manage-mqtt-broker/howto-test-connection.md

@@ -574,7 +574,7 @@ spec:
 
 ---
 
-## Next steps
+## Related content
 
 - [Configure TLS with manual certificate management to secure MQTT communication](howto-configure-tls-manual.md)
 - [Configure authentication](howto-configure-authentication.md)

articles/iot-operations/manage-mqtt-broker/overview-broker.md

@@ -242,6 +242,6 @@ kubectl get broker default -n azure-iot-operations -o yaml
 
 ---
 
-## Next steps
+## Related content
 
 - [Deploy IoT Operations to an Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-deploy-iot-operations.md)