Azure Relay freshness review

Author: spelluru

articles/azure-relay/includes/trusted-services.md

@@ -2,7 +2,7 @@
 author: spelluru
 ms.service: azure-relay
 ms.topic: include
-ms.date: 06/26/2023
+ms.date: 12/11/2024
 ms.author: spelluru
 ---
 
@@ -11,11 +11,11 @@ When you enable the **Allow trusted Microsoft services to bypass this firewall**
 
 | Trusted service | Supported usage scenarios | 
 | --------------- | ------------------------- | 
-| Azure Machine Learning | AML Kubernetes uses Azure Relay to facilitate communication between AML services and the Kubernetes cluster. Azure Relay is a fully managed service that provides secure bi-directional communication between applications hosted on different networks. This makes it ideal for use in private link environments, where communication between Azure resources and on-premises resources is restricted. |
-| Azure Arc | Azure Arc-enabled services associated with the Resource Providers above will be able to connect to the hybrid connections in your Azure Relay namespace as a sender without being blocked by the IP firewall rules set on the Azure Relay namespace. `Microsoft.Hybridconnectivity` service creates the hybrid connections in your Azure Relay namespace and provides the connection information to the relevant Arc service based on the scenario. These services communicate only with your Azure Relay namespace if you're using Azure Arc, with the following Azure Services: <br/><br> - Azure Kubernetes<br/> - Azure Machine Learning <br/> - Microsoft Purview |
+| Azure Machine Learning | AML Kubernetes uses Azure Relay to facilitate communication between AML services and the Kubernetes cluster. Azure Relay is a fully managed service that provides secure bi-directional communication between applications hosted on different networks. This feature makes it ideal for use in private link environments, where communication between Azure resources and on-premises resources is restricted. |
+| Azure Arc | Azure Arc-enabled services associated with the resource providers can connect to the hybrid connections in your Azure Relay namespace as a sender without being blocked by the IP firewall rules set on the Azure Relay namespace. `Microsoft.Hybridconnectivity` service creates the hybrid connections in your Azure Relay namespace and provides the connection information to the relevant Arc service based on the scenario. These services communicate only with your Azure Relay namespace if you're using Azure Arc, with the following Azure Services: <br/><br> - Azure Kubernetes<br/> - Azure Machine Learning <br/> - Microsoft Purview |
 
 
-The other trusted services for Azure Relay can be found below:
+The other trusted services for Azure Relay are:
 - Azure Event Grid
 - Azure IoT Hub
 - Azure Stream Analytics
@@ -35,7 +35,7 @@ The other trusted services for Azure Relay can be found below:
 > "trustedServiceAccessEnabled": "True"
 > ```
 
-For example, based on the ARM template provided above, we can modify it to include this Network Rule Set property for the enablement of Trusted Services:
+For example, based on the ARM template provided, you can modify it to include this Network Rule Set property for the enablement of Trusted Services:
 
 ```json
 {

articles/azure-relay/relay-metrics-azure-monitor.md

@@ -3,7 +3,7 @@ title: Azure Relay metrics in Azure Monitor  | Microsoft Docs
 description: This article provides information on how you can use Azure Monitor to monitor to state of Azure Relay. 
 services: service-bus-relay
 ms.topic: article
-ms.date: 08/10/2023
+ms.date: 12/11/2024
 ---
 
 # Azure Relay metrics in Azure Monitor 
@@ -32,7 +32,7 @@ For metrics supporting dimensions, you must filter with the desired dimension va
 
 ## Billing
 
-Using metrics in Azure Monitor is currently free while in preview. However, if you use additional solutions that ingest metrics data, you may be billed by these solutions. For example, you're billed by Azure Storage if you archive metrics data to an Azure Storage account. You're also billed by Azure Monitor logs if you stream metrics data to Azure Monitor logs for advanced analysis.
+Using metrics in Azure Monitor is currently free while in preview. However, if you use additional solutions that ingest metrics data, you might be billed by these solutions. For example, you're billed by Azure Storage if you archive metrics data to an Azure Storage account. You're also billed by Azure Monitor logs if you stream metrics data to Azure Monitor logs for advanced analysis.
 
 The following metrics give you an overview of the health of your service. 
 

articles/azure-relay/relay-port-settings.md

@@ -2,7 +2,7 @@
 title: Azure Relay port settings | Microsoft Docs
 description: This article includes a table that describes the required configuration for port values for Azure Relay.
 ms.topic: article
-ms.date: 08/10/2023
+ms.date: 12/11/2024
 ---
 
 # Azure Relay port settings
@@ -11,9 +11,9 @@ The following table describes the required configuration for port values for Azu
 
 ## Hybrid Connections
 
-Hybrid Connections uses WebSockets on port 443 with TLS as the underlying transport mechanism, which uses **HTTPS** only. 
+Hybrid Connections uses WebSockets on port 443 with Transport Layer Security (TLS) as the underlying transport mechanism, which uses **HTTPS** only. 
 
-## WCF Relays
+## Windows Communication Foundation (WCF) Relays
 
 |Binding|Transport Security|Port|  
 |-------------|------------------------|----------|  

articles/azure-relay/service-bus-relay-tutorial.md

@@ -433,7 +433,7 @@ The next task is to create a client application and define the service contract
 
    1. In **Solution Explorer**, right-click the current solution (not the project), and select **Add** > **New Project**.
    1. In **Add a new project**, select **Console App (.NET Framework)** for C#, and select **Next**.
-   1. Name project *EchoClient* and select **Create**.
+   1. Specify *EchoClient* as the name of the proejct and select **Create**.
 
 1. In **Solution Explorer**, in the **EchoClient** project, double-click **Program.cs** to open the file in the editor, if it isn't already open.
 1. Change the namespace name from its default name of `EchoClient` to `Microsoft.ServiceBus.Samples`.
@@ -744,7 +744,7 @@ namespace Microsoft.ServiceBus.Samples
     `Press [Enter] to exit`
 
 1. In the **EchoClient** console window, enter the same information that you entered previously for the service application. Enter the same service namespace and SAS key values for the client application.
-1. After entering these values, the client opens a channel to the service and prompts you to enter some text as seen in the following console output example.
+1. After you enter these values, the client opens a channel to the service and prompts you to enter some text as seen in the following console output example.
 
     `Enter text to echo (or [Enter] to exit):`