More Relay articles

Author: spelluru

articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md

@@ -3,7 +3,7 @@ title: Azure Relay Hybrid Connections - HTTP requests in .NET
 description: Write a C# console application for Azure Relay Hybrid Connections HTTP requests in .NET.
 ms.topic: tutorial
 ms.custom: devx-track-csharp, mode-ui, mode-api, devx-track-dotnet
-ms.date: 08/10/2023
+ms.date: 12/11/2024
 ---
 
 # Get started with Relay Hybrid Connections HTTP requests in .NET
@@ -52,7 +52,6 @@ In Visual Studio, write a C# console application to send messages to the relay.
 1. Run the client application. You see `hello!` in the client window. The client sent an HTTP request to the server, and server responded with a `hello!`. 
 3. Now, to close the console windows, press **ENTER** in both the console windows. 
 
-Congratulations, you've created a complete Hybrid Connections application!
 
 ## Next steps
 

articles/azure-relay/relay-hybrid-connections-node-ws-api-overview.md

@@ -2,15 +2,15 @@
 title: Overview of the Azure Relay Node APIs | Microsoft Docs
 description: This article provides an overview of the Node.js API for the Azure Relay service. It also shows how to use the hyco-ws Node package. 
 ms.topic: article
-ms.date: 08/10/2023
+ms.date: 12/11/2024
 ms.custom: devx-track-js
 ---
 
 # Relay Hybrid Connections Node.js API overview
 
 ## Overview
 
-The [`hyco-ws`](https://www.npmjs.com/package/hyco-ws) Node package for Azure Relay Hybrid Connections is built on and extends the [`ws`](https://www.npmjs.com/package/ws) NPM package. This package re-exports all exports of that base package and adds new exports that enable integration with the Azure Relay service Hybrid Connections feature. 
+The [`hyco-ws`](https://www.npmjs.com/package/hyco-ws) Node package for Azure Relay Hybrid Connections is built on and extends the [`ws`](https://www.npmjs.com/package/ws) Node Package Manager (npm) package. This package re-exports all exports of that base package and adds new exports that enable integration with the Azure Relay service Hybrid Connections feature. 
 
 Existing applications that `require('ws')` can use this package with `require('hyco-ws')` instead, which also enables hybrid scenarios in which an application can listen for WebSocket connections locally from "inside the firewall" and via Hybrid Connections, all at the same time.
 
@@ -123,17 +123,17 @@ Constructor arguments:
 
 #### Events
 
-`RelayedServer` instances emit three events that enable you to handle incoming requests, establish connections, and detect error conditions. You must subscribe to the `connect` event to handle messages. 
+`RelayedServer` instances emit three events that enable you to handle incoming requests, establish connections, and detect the error conditions. You must subscribe to the `connect` event to handle messages. 
 
-##### headers
+##### Headers
 
 ```JavaScript 
 function(headers)
 ```
 
 The `headers` event is raised just before an incoming connection is accepted, enabling modification of the headers to send to the client. 
 
-##### connection
+##### Connection
 
 ```JavaScript
 function(socket)
@@ -142,7 +142,7 @@ function(socket)
 Emitted when a new WebSocket connection is accepted. The object is of type `ws.WebSocket`, same as with the base package.
 
 
-##### error
+##### Error
 
 ```JavaScript
 function(error)

articles/azure-relay/relay-hybrid-connections-protocol.md

@@ -2,7 +2,7 @@
 title: Azure Relay Hybrid Connections protocol guide | Microsoft Docs
 description: This article describes the client-side interactions with the Hybrid Connections relay for connecting clients in listener and sender roles.
 ms.topic: article
-ms.date: 08/10/2023
+ms.date: 12/11/2024
 ---
 
 # Azure Relay Hybrid Connections protocol
@@ -43,7 +43,7 @@ to be accepted for establishing a bi-directional communication path. "Connect,"
 
 Any relayed communication model has either party making outbound connections
 towards a service endpoint. This makes the "listener" also a "client" in
-colloquial use, and may also cause other terminology overloads. The precise
+colloquial use, and might also cause other terminology overloads. The precise
 terminology therefore used for Hybrid Connections is as follows:
 
 The programs on both sides of a connection are called "clients," since they're
@@ -115,8 +115,8 @@ The listener can respond to HTTP requests using an equivalent response gesture.
 The request/response flow uses the control channel by default, but can be
 "upgraded" to a distinct rendezvous WebSocket whenever required. Distinct
 WebSocket connections improve throughput for each client conversation, but they
-burden the listener with more connections that need to be handled, which may
-not be desire able for lightweight clients.
+burden the listener with more connections that need to be handled, which might
+not be desirable for lightweight clients.
 
 On the control channel, request and response bodies are limited to at most 64 kB
 in size. HTTP header metadata is limited to a total of 32 kB. If either the
@@ -125,7 +125,7 @@ to a rendezvous WebSocket using a gesture equivalent to handling the
 [Accept](#accept-message).
 
 For requests, the service decides whether to route requests over the control
-channel. This includes, but may not be limited to cases where a request exceeds
+channel. This includes, but might not be limited to cases where a request exceeds
 64 kB (headers plus body) outright, or if the request is sent with ["chunked"
 transfer-encoding](https://tools.ietf.org/html/rfc7230#section-4.1) and the
 service has reason to expect for the request to exceed 64 kB or reading the
@@ -155,7 +155,7 @@ in progress.
 #### Renew operation
 
 The security token that must be used to register the listener and maintain the
-control channel may expire while the listener is active. The token expiry doesn't affect ongoing connections, but it does cause the control channel to be
+control channel might expire while the listener is active. The token expiry doesn't affect ongoing connections, but it does cause the control channel to be
 dropped by the service at or soon after the moment of expiry. The "renew"
 operation is a JSON message that the listener can send to replace the token
 associated with the control channel, so that the control channel can be

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

@@ -1,11 +1,12 @@
 ---
-title: Expose an on-premises WCF REST service to clients using Azure Relay
+title: Expose on-premises WCF REST service to clients
 description: This tutorial describes how to expose an on-premises WCF REST service to an external client by using Azure WCF Relay.
 ms.topic: tutorial
-ms.date: 08/11/2023
+ms.date: 12/11/2024
+# Customer intent: I want to know how to expose an on-premises WCF REST service to external clients using WCF Relay.
 ---
 
-# Tutorial: Expose an on-premises WCF REST service to external client by using Azure WCF Relay
+# Tutorial: Expose an on-premises Windows Communication Foundation (WCF) REST service to external client by using Azure WCF Relay
 
 This tutorial describes how to build a WCF Relay client application and a service using Azure Relay. Like their original WCF counterparts, a service is a construct that exposes one or more endpoints. Each **endpoint** exposes one or more service operations. The endpoint of a service specifies an **address** where the service can be found, a **binding** that contains the information that a client must communicate with the service, and a **contract** that defines the functionality provided by the service to its clients. The main difference between WCF and WCF Relay is that the endpoint is exposed in the cloud instead of locally on your computer.
 
@@ -758,7 +759,7 @@ namespace Microsoft.ServiceBus.Samples
 
 1. You can continue sending text messages from the client to the service in this manner. When you're finished, select Enter in the client and service console windows to end both applications.
 
-## Next steps
+## Next step
 
 Advance to the following tutorial: