Update request-reply.md doc link

src/pages/tutorials/jcsmp/request-reply.md

@@ -32,7 +32,7 @@ The goal of this tutorial is to understand the following:
 
 Request-reply messaging is supported by the Solace message router for all delivery modes. For direct messaging, the Solace APIs provide the Requestor object for convenience. This object makes it easy to send a request and wait for the reply message. It is a convenience object that makes use of the API provided “inbox” topic that is automatically created for each Solace client and automatically correlates requests with replies using the message correlation ID. (See Message Correlation below for more details). On the reply side another convenience method enables applications to easily send replies for specific requests. Direct messaging request reply is the delivery mode that is illustrated in this sample.
 
-It is also possible to use guaranteed messaging for request reply scenarios. In this case the replier can listen on a queue for incoming requests and the requestor can use a temporary endpoint to attract replies. The requestor and replier must manually correlate the messages. This is explained further in the [Solace documentation](https://docs.solace.com/Solace-PubSub-Messaging-APIs/API-Developer-Guide/Request-Reply-Messaging.htm) and shown in the API samples named `RRGuaranteedRequestor` and `RRGuaranteedReplier`.
+It is also possible to use guaranteed messaging for request reply scenarios. In this case the replier can listen on a queue for incoming requests and the requestor can use a temporary endpoint to attract replies. The requestor and replier must manually correlate the messages. This is explained further in the [Solace documentation](https://docs.solace.com/API/API-Developer-Guide/Request-Reply-Messaging.htm) and shown in the API samples named `RRGuaranteedRequestor` and `RRGuaranteedReplier`.
 
 ### Message Correlation