Final edits before PR.

Author: TimShererWithAquent

articles/service-bus-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md

@@ -13,18 +13,16 @@ ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: conceptual
-ms.date: 11/01/2018
+ms.date: 09/12/2019
 ms.author: spelluru
 
 ---
 # Expose an on-premises WCF service to a web application in the cloud by using Azure Relay
 
 This article shows how to build a hybrid cloud application with Microsoft Azure and Visual Studio. You create an application that uses multiple Azure resources up and running in the cloud.
 
-* How to create or adapt an existing web service for consumption by a
-  web solution.
-* How to use the Azure Windows Communication Foundation (WCF) Relay service to share data between
-  an Azure application and a web service hosted elsewhere.
+* How to create or adapt an existing web service for consumption by a web solution.
+* How to use the Azure Windows Communication Foundation (WCF) Relay service to share data between an Azure application and a web service hosted elsewhere.
 
 You take the following steps in this tutorial:
 
@@ -93,7 +91,7 @@ First, you build a simulated on-premises product catalog system.  This project i
    ![Configure your new project][11]
 
 1. In **Solution Explorer**, right-click the **ProductsServer** project, then select **Manage NuGet Packages**.
-1. Select **Browse**, then search for and choose *WindowsAzure.ServiceBus*. Select **Install**, and accept the terms of use.
+1. Select **Browse**, then search for and choose **WindowsAzure.ServiceBus**. Select **Install**, and accept the terms of use.
 
    ![Select NuGet package][13]
 
@@ -193,7 +191,7 @@ First, you build a simulated on-premises product catalog system.  This project i
     }
     ```
 
-1. In **Solution Explorer**, double-click **App.config** to open *App.config* in the Visual Studio editor. At the bottom of the `<system.ServiceModel>` element, but still within `<system.ServiceModel>`, add the following XML code. Be sure to replace `yourServiceNamespace` with the name of your namespace, and `yourKey` with the SAS key you retrieved earlier from the portal:
+1. In **Solution Explorer**, double-click **App.config** to open the file in the Visual Studio editor. At the bottom of the `<system.ServiceModel>` element, but still within `<system.ServiceModel>`, add the following XML code. Be sure to replace `yourServiceNamespace` with the name of your namespace, and `yourKey` with the SAS key you retrieved earlier from the portal:
 
     ```xml
     <system.serviceModel>
@@ -217,7 +215,8 @@ First, you build a simulated on-premises product catalog system.  This project i
     </system.serviceModel>
     ```
 
-    The error caused by `transportClientEndpointBehavior` is just a warning and isn't a blocking issue for this example.
+    > [!NOTE]
+    > The error caused by `transportClientEndpointBehavior` is just a warning and isn't a blocking issue for this example.
 
 1. Still in *App.config*, in the `<appSettings>` element, replace the connection string value with the connection string you previously obtained from the portal.
 
@@ -273,7 +272,7 @@ In this section, you build a simple ASP.NET application that displays data retri
 	}
     ```
 
-1. In **Solution Explorer**, expand **Controllers**, then double-click **HomeController.cs** to open *HomeController.cs* in Visual Studio.
+1. In **Solution Explorer**, expand **Controllers**, then double-click **HomeController.cs** to open the file in Visual Studio.
 1. In *HomeController.cs*, replace the existing namespace definition with the following code:
 
     ```csharp
@@ -296,13 +295,13 @@ In this section, you build a simple ASP.NET application that displays data retri
     }
     ```
 
-1. In **Solution Explorer**, expand **Views** > **Shared**, then double-click **_Layout.cshtml** to open *_Layout.cshtml* in the Visual Studio editor.
+1. In **Solution Explorer**, expand **Views** > **Shared**, then double-click **_Layout.cshtml** to open the file in the Visual Studio editor.
 1. Change all occurrences of `My ASP.NET Application` to *Northwind Traders Products*.
-1. Remove the **Home**, **About**, and **Contact** links. In the following example, delete the highlighted code.
+1. Remove the `Home`, `About`, and `Contact` links. In the following example, delete the highlighted code.
 
     ![Delete the generated list items][41]
 
-1. In **Solution Explorer**, expand **Views** > **Home**, then double-click **Index.cshtml** to open *Index.cshtml* in the Visual Studio editor. Replace the entire contents of the file with the following code:
+1. In **Solution Explorer**, expand **Views** > **Home**, then double-click **Index.cshtml** to open the file in the Visual Studio editor. Replace the entire contents of the file with the following code:
 
    ```html
    @model IEnumerable<ProductsWeb.Models.Product>
@@ -355,7 +354,7 @@ Your application should appear, running in a browser.
 
 The next step is to hook up the on-premises products server with the ASP.NET application.
 
-1. If it isn't already open, in Visual Studio reopen the **ProductsPortal** project you created in the [Create an ASP.NET application](#create-an-aspnet-application) section.
+1. If it isn't already open, in Visual Studio, open the **ProductsPortal** project you created in the [Create an ASP.NET application](#create-an-aspnet-application) section.
 1. Similar to the step in the [Create an On-Premises Server](#create-an-on-premises-server) section, add the NuGet package to the project references. In **Solution Explorer**, right-click the **ProductsPortal** project, then select **Manage NuGet Packages**.
 1. Search for *WindowsAzure.ServiceBus* and select the **WindowsAzure.ServiceBus** item. Then complete the installation and close this dialog box.
 1. In **Solution Explorer**, right-click the **ProductsPortal** project, then select **Add** > **Existing Item**.
@@ -460,7 +459,7 @@ Before running the application in the cloud, you must ensure that **ProductsPort
 
 ## Run the application
 
-Press **F5** to build and run the application. The on-premises server (the **ProductsServer** console application) should start first, then the **ProductsPortal** application should start in a browser window, as shown here:
+Press **F5** to build and run the application. The on-premises server, which is the **ProductsServer** console application, should start first, then the **ProductsPortal** application should start in a browser window, as shown here:
 
    ![Run the web app on Azure][1]
 

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

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/06/2018
+ms.date: 09/12/2019
 ms.author: spelluru
 
 ---
@@ -23,7 +23,7 @@ This tutorial describes how to build an Azure Relay host application that expose
 
 The tutorial uses the Windows Communication Foundation (WCF) REST programming model to construct a REST service on Azure Relay. For more information, see [WCF REST Programming Model](/dotnet/framework/wcf/feature-details/wcf-web-http-programming-model) and [Designing and Implementing Services](/dotnet/framework/wcf/designing-and-implementing-services).
 
-You take the following steps in this tutorial:
+You do the following tasks in this tutorial:
 
 > [!div class="checklist"]
 >
@@ -49,7 +49,7 @@ To begin using the relay features in Azure, you must first create a service name
 
 When you create a WCF REST-style service, you must define the contract. The contract specifies what operations the host supports. A service operation can be thought of as a web service method. Contracts are created by defining a C++, C#, or Visual Basic interface. Each method in the interface corresponds to a specific service operation. The [ServiceContractAttribute](/dotnet/api/system.servicemodel.servicecontractattribute) attribute must be applied to each interface, and the [OperationContractAttribute](/dotnet/api/system.servicemodel.operationcontractattribute) attribute must be applied to each operation. If a method in an interface that has the [ServiceContractAttribute](/dotnet/api/system.servicemodel.servicecontractattribute) doesn't have the [OperationContractAttribute](/dotnet/api/system.servicemodel.operationcontractattribute), that method isn't exposed. The code used for these tasks is shown in the example following the procedure.
 
-The primary difference between a WCF contract and a REST-style contract is the addition of a property to the [OperationContractAttribute](/dotnet/api/system.servicemodel.operationcontractattribute): [WebGetAttribute](/dotnet/api/system.servicemodel.web.webgetattribute). This property enables you to map a method in your interface to a method on the other side of the interface. This example uses the [WebGetAttribute](/dotnet/api/system.servicemodel.web.webgetattribute) attribute to link a method to HTTP GET. This approach enables Service Bus to accurately retrieve and interpret commands sent to the interface.
+The primary difference between a WCF contract and a REST-style contract is the addition of a property to the [OperationContractAttribute](/dotnet/api/system.servicemodel.operationcontractattribute): [WebGetAttribute](/dotnet/api/system.servicemodel.web.webgetattribute). This property enables you to map a method in your interface to a method on the other side of the interface. This example uses the [WebGetAttribute](/dotnet/api/system.servicemodel.web.webgetattribute) attribute to link a method to `HTTP GET`. This approach enables Service Bus to accurately retrieve and interpret commands sent to the interface.
 
 ### To create a contract with an interface
 
@@ -65,8 +65,8 @@ The primary difference between a WCF contract and a REST-style contract is the a
 
     This step adds references to Service Bus and *System.ServiceModel.dll*. This package automatically adds references to the Service Bus libraries and the WCF `System.ServiceModel`.
 
-1. Explicitly add a reference to `System.ServiceModel.Web.dll` to the project. In **Solution Explorer**, right-click **References** under the project folder. and select **Add Reference**.
-1. In **Add Reference**, select **Framework** on the left side and enter *System.ServiceModel.Web* in **Search**. Select the **System.ServiceModel.Web** check box, then click **OK**.
+1. Explicitly add a reference to `System.ServiceModel.Web.dll` to the project. In **Solution Explorer**, right-click **References** under the project folder, and select **Add Reference**.
+1. In **Add Reference**, select **Framework** and enter *System.ServiceModel.Web* in **Search**. Select the **System.ServiceModel.Web** check box, then click **OK**.
 
 Next, make the following code changes to the project:
 
@@ -169,7 +169,7 @@ namespace Microsoft.ServiceBus.Samples
 
 ## Implement the REST-based WCF service contract
 
-To create a REST-style WCF Relay service, first create the contract, which is defined by using an interface. The next step is to implement the interface. This procedure involves creating a class named `ImageService` that implements the user-defined `IImageContract` interface. After you implement the contract, you then configure the interface using an *App.config* file. The configuration file contains necessary information for the application. This information includes the name of the service, the name of the contract, and the type of protocol that is used to communicate with the relay service. The code used for these tasks is provided in the example following the procedure.
+To create a REST-style WCF Relay service, first create the contract, which is defined by using an interface. The next step is to implement the interface. This procedure involves creating a class named `ImageService` that implements the user-defined `IImageContract` interface. After you implement the contract, you then configure the interface by using an *App.config* file. The configuration file contains necessary information for the application. This information includes the name of the service, the name of the contract, and the type of protocol that is used to communicate with the relay service. The code used for these tasks is provided in the example following the procedure.
 
 As with the previous steps, there's little difference between implementing a REST-style contract and a WCF Relay contract.
 
@@ -202,7 +202,7 @@ As with the previous steps, there's little difference between implementing a RES
 
     The rest of this tutorial assumes that the name of the image is *image.jpg*. If you have a different file, you must rename the image, or change your code to compensate.
 
-1. To make sure that the running service can find the image file, in **Solution Explorer** right-click the image file, then choose **Properties**. In the **Properties** pane, set **Copy to Output Directory** to **Copy if newer**.
+1. To make sure that the running service can find the image file, in **Solution Explorer** right-click the image file, then choose **Properties**. In **Properties**, set **Copy to Output Directory** to **Copy if newer**.
 
 1. Use the procedure in [#to-create-a-contract-with-an-interface](#to-create-a-contract-with-an-interface) to add a reference to the *System.Drawing.dll* assembly to the project.
 
@@ -252,7 +252,7 @@ As with the previous steps, there's little difference between implementing a RES
 
 ### To define the configuration for running the web service on Service Bus
 
-1. In **Solution Explorer**, double-click **App.config** to open *App.config* in the Visual Studio editor.
+1. In **Solution Explorer**, double-click **App.config** to open the file in the Visual Studio editor.
 
     The *App.config* file includes the service name, endpoint, and binding. The endpoint is the location Azure Relay exposes for clients and hosts to communicate with each other. The binding is the type of protocol that is used to communicate. The main difference here is that the configured service endpoint refers to a [WebHttpRelayBinding](/dotnet/api/microsoft.servicebus.webhttprelaybinding) binding.
 
@@ -506,11 +506,11 @@ This section describes how to run a web service using a console application with
 
 Still in `Main()`, create the web service host, using the URI address created earlier in this section.
 
-    ```csharp
-    WebServiceHost host = new WebServiceHost(typeof(ImageService), address);
-    ```
+```csharp
+WebServiceHost host = new WebServiceHost(typeof(ImageService), address);
+```
 
-    The service host is the WCF object that instantiates the host application. This example passes it the type of host you want to create (an `ImageService`), and also the address at which you want to expose the host application.
+The service host is the WCF object that instantiates the host application. This example passes it the type of host you want to create, which is an `ImageService`, and also the address at which you want to expose the host application.
 
 ### To run the web service host
 
@@ -540,7 +540,7 @@ Still in `Main()`, create the web service host, using the URI address created ea
 
 ### Example of the service contract and implementation
 
-The following example includes the service contract and implementation from previous steps in the tutorial and hosts the service in a console application. Compile the following code into an executable named ImageListener.exe.
+The following example includes the service contract and implementation from previous steps in the tutorial and hosts the service in a console application. Compile the following code into an executable named *ImageListener.exe*.
 
 ```csharp
 using System;

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

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/01/2018
+ms.date: 09/12/2019
 ms.author: spelluru
 
 ---
@@ -185,7 +185,7 @@ Creating an Azure relay requires that you first create the contract, which is de
 
 The configuration file is similar to a WCF configuration file. It includes the service name, endpoint, and binding. The endpoint is the location Azure Relay exposes for clients and hosts to communicate with each other. The binding is the type of protocol that is used to communicate. The main difference is that this configured service endpoint refers to a [NetTcpRelayBinding](/dotnet/api/microsoft.servicebus.nettcprelaybinding) binding, which isn't part of the .NET Framework. [NetTcpRelayBinding](/dotnet/api/microsoft.servicebus.nettcprelaybinding) is one of the bindings defined by the service.
 
-1. In **Solution Explorer**, double-click **App.config** to open the *App.config* file in the Visual Studio editor.
+1. In **Solution Explorer**, double-click **App.config** to open the file in the Visual Studio editor.
 1. In the `<appSettings>` element, replace the placeholders with the name of your service namespace, and the SAS key that you copied in an earlier step.
 1. Within the `<system.serviceModel>` tags, add a `<services>` element. You can define multiple relay applications in a single configuration file. However, this tutorial defines only one.
 
@@ -334,11 +334,11 @@ For this tutorial, the URI is `sb://putServiceNamespaceHere.windows.net/EchoServ
     }
     ```
 
-    As stated in the previously, you could have declared multiple services and endpoints in the configuration file. If you had, this code would traverse the configuration file and search for every endpoint to which it should apply your credentials. However, for this tutorial, the configuration file has only one endpoint.
+    As stated previously, you could have declared multiple services and endpoints in the configuration file. If you had, this code would traverse the configuration file and search for every endpoint to which it should apply your credentials. However, for this tutorial, the configuration file has only one endpoint.
 
 ### Open the service host
 
-1. Still in `Main()`, add the following lin to open the service.
+1. Still in `Main()`, add the following line to open the service.
 
     ```csharp
     host.Open();
@@ -513,7 +513,7 @@ namespace Microsoft.ServiceBus.Samples
 
 In this step, you create an *App.config* file for a basic client application that accesses the service created previously in this tutorial. This *App.config* file defines the contract, binding, and name of the endpoint. The code used for these tasks is provided in the example following the procedure.
 
-1. In **Solution Explorer**, in the **EchoClient** project, double-click **App.config** to open *App.config* in the Visual Studio editor.
+1. In **Solution Explorer**, in the **EchoClient** project, double-click **App.config** to open the file in the Visual Studio editor.
 2. In the `<appSettings>` element, replace the placeholders with the name of your service namespace, and the SAS key that you copied in an earlier step.
 3. Within the `system.serviceModel` element, add a `<client>` element.
 
@@ -756,7 +756,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. Follow the previous steps to enter the same service namespace and SAS key values for the client application.
+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.
 
     `Enter text to echo (or [Enter] to exit):`