Update TROUBLESHOOTING.md (Azure#33317)

fixed port documentation for AMQP 1.0

Author: michel-douma

sdk/servicebus/Azure.Messaging.ServiceBus/TROUBLESHOOTING.md

@@ -127,7 +127,7 @@ To troubleshoot:
 
 - Verify that the connection string or fully qualified domain name specified when creating the client is correct. For information on how to acquire a connection string, see: [Get a Service Bus connection string][GetConnectionString].
 
-- Check the firewall and port permissions in your hosting environment and that the AMQP ports 5671 and 5762 are open and that the endpoint is allowed through the firewall.
+- Check the firewall and port permissions in your hosting environment and that the AMQP ports 5671 and 5672 are open and that the endpoint is allowed through the firewall.
 
 - Try using the Web Socket transport option, which connects using port 443. For details, see: [configure the transport][TransportSample].
 
@@ -335,4 +335,4 @@ Information about Service Bus quotas can be found [here][ServiceBusQuotas].
 [DiagnoseThreadPoolExhaustion]: https://docs.microsoft.com/shows/on-net/diagnosing-thread-pool-exhaustion-issues-in-net-core-apps
 [TransactionTimeout]: https://docs.microsoft.com/azure/service-bus-messaging/service-bus-transactions#timeout
 [MessageBody]: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md#message-body
-[Throttling]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-throttling
+[Throttling]: https://learn.microsoft.com/azure/service-bus-messaging/service-bus-throttling