add ref

Author: vicancy

articles/azure-web-pubsub/quickstart-use-client-sdk.md

@@ -128,7 +128,7 @@ Note that the SDK is available as a [NuGet packet](https://www.nuget.org/package
 
 ### Create and connect to the Web PubSub service
 
-This code example creates a Web PubSub client that connects to the Web PubSub service instance.  A client uses a Client Access URL to connect and authenticate with the service. It's best practice to not hard code the Client Access URL in your code. In the production world, we usually set up an app server to return this URL on demand.  
+This code example creates a Web PubSub client that connects to the Web PubSub service instance.  A client uses a Client Access URL to connect and authenticate with the service. It's best practice to not hard code the Client Access URL in your code. In the production world, we usually set up an app server to return this URL on demand. [Generate Client Access URL](./howto-generate-client-access-url.md) describes the practice in detail.
 
 For this example, you can use the Client Access URL you generated in the portal.
 

articles/azure-web-pubsub/quickstarts-event-notifications-from-clients.md

@@ -48,7 +48,7 @@ npm install @azure/web-pubsub-client
 #### 2. Connect to Web PubSub
 A client, be it a browser, a mobile app, or an IoT device, uses a **Client Access URL** to connect and authenticate with your resource. 
 This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`. 
-A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram.
+A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram. It's best practice to not hard code the Client Access URL in your code. In the production world, we usually set up an app server to return this URL on demand. [Generate Client Access URL](./howto-generate-client-access-url.md) describes the practice in detail.
 
 ![The diagram shows how to get **Client Access Url**.](./media/quickstarts-event-notifications-from-clients/generate-client-url-no-group.png)
 

articles/azure-web-pubsub/quickstarts-pubsub-among-clients.md

@@ -55,7 +55,7 @@ dotnet add package Azure.Messaging.WebPubSub.Client --prerelease
 
 ## Connect to Web PubSub
 
-A client, be it a browser 💻, a mobile app 📱, or an IoT device 💡, uses a **Client Access URL** to connect and authenticate with your resource. This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`. A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram.
+A client, be it a browser 💻, a mobile app 📱, or an IoT device 💡, uses a **Client Access URL** to connect and authenticate with your resource. This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`. A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram. It's best practice to not hard code the Client Access URL in your code. In the production world, we usually set up an app server to return this URL on demand. [Generate Client Access URL](./howto-generate-client-access-url.md) describes the practice in detail.
 
 ![The diagram shows how to get client access url.](./media/howto-websocket-connect/generate-client-url.png)
 

articles/azure-web-pubsub/quickstarts-push-messages-from-server.md

@@ -63,7 +63,7 @@ npm install @azure/web-pubsub-client
 
 #### Connect to your Web PubSub resource and register a listener for the `server-message` event 
 A client uses a ***Client Access URL*** to connect and authenticate with your resource. 
-This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`. A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram.
+This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/hubs/<hub_name>?access_token=<token>`. A client can have a few ways to obtain the Client Access URL. For this quick start, you can copy and paste one from Azure portal shown in the following diagram. It's best practice to not hard code the Client Access URL in your code. In the production world, we usually set up an app server to return this URL on demand. [Generate Client Access URL](./howto-generate-client-access-url.md) describes the practice in detail.
 
 ![The diagram shows how to get client access url.](./media/quickstarts-push-messages-from-server/push-messages-from-server.png)