Editorial changes

Author: MikeDodaro

articles/spring-cloud/spring-cloud-tutorial-circuit-breaker.md

@@ -10,9 +10,9 @@ ms.date: 04/06/2020
 ---
 
 # Use Circuit Breaker Dashboard with Azure Spring Cloud | Microsoft Docs
-Spring Cloud Netflix Turbine is widely used to aggregates multiple Hystrix metrics streams so that streams can be monitored in a single view using Hystrix dashboard. This tutorial demonstrates how to use them on Azure Spring Cloud.
+Spring Cloud Netflix Turbine is widely used to aggregate multiple Hystrix metrics streams so that streams can be monitored in a single view using Hystrix dashboard. This tutorial demonstrates how to use them on Azure Spring Cloud.
 > [!NOTE]
-> Netflix Hystrix is widely used in existing Spring Cloud apps, but it is no longer in active development. If you are developing new project, you can consider resilience4j instead. Circuit Breaker Dashboard for resilience4j dependents on micrometer, which is currently not supported for Azure Spring Cloud, so it will not be covered by this tutorial.
+> Netflix Hystrix is widely used in existing Spring Cloud apps, but it is no longer in active development. If you are developing new project, you can consider resilience4j instead. Circuit Breaker Dashboard for resilience4j depends on micrometer, which is currently not supported for Azure Spring Cloud, so it will not be covered by this tutorial.
 
 ## Prepare your sample applications
 The sample is forked from this [repository](https://github.com/StackAbuse/spring-cloud/tree/master/spring-turbine).
@@ -22,21 +22,21 @@ Clone the sample repository to your develop environment:
 git clone https://github.com/yucwan/spring-cloud.git
 ```
 
-Build the 3 applications that will be used in this tutorial.
-user-service: A simple REST service that has a single endpoint of /personalized/{id}
-recommendation-service: A simple REST service that has a single endpoint of /recommendations, which will be called by user-service.
-hystrix-turbine: A Hystrix dashboard service to display Hystrix streams and a Turbine service aggregating Hystrix metrics stream from other services.
+Build the 3 applications that will be used in this tutorial:
+* user-service: A simple REST service that has a single endpoint of /personalized/{id}
+* recommendation-service: A simple REST service that has a single endpoint of /recommendations, which will be called by user-service.
+* hystrix-turbine: A Hystrix dashboard service to display Hystrix streams and a Turbine service aggregating Hystrix metrics stream from other services.
 ```
 cd spring-cloud/spring-turbine
 mvn clean package -D skipTests -f user-service/pom.xml
 mvn clean package -D skipTests -f recommendation-service/pom.xml
 mvn clean package -D skipTests -f hystrix-turbine/pom.xml
 ```
 ## Provision your Azure Spring Cloud instance
-Follow the procedure as described in [Provision a service instance on the Azure CLI](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-quickstart-launch-app-cli#provision-a-service-instance-on-the-azure-cli).
+Follow the procedure, [Provision a service instance on the Azure CLI](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-quickstart-launch-app-cli#provision-a-service-instance-on-the-azure-cli).
 
 ## Deploy your applications to Azure Spring Cloud
-These apps do not use Config Server, so there is no need to set up **Config Server** for Azure Spring Cloud.  Deploy as follows:
+These apps do not use **Config Server**, so there is no need to set up **Config Server** for Azure Spring Cloud.  Create and deploy as follows:
 ```azurecli
 az spring-cloud app create -n user-service --is-public
 az spring-cloud app create -n recommendation-service
@@ -47,31 +47,31 @@ az spring-cloud app deploy -n recommendation-service --jar-path recommendation-s
 az spring-cloud app deploy -n hystrix-turbine --jar-path hystrix-turbine/target/hystrix-turbine.jar
 ```
 ## Verify your apps
-After all the apps are running and discoverable, access user-service with the path https://yuchensp-user-service.azuremicroservices.io/personalized/1 from your browser. You should get the following output if the user-service can access recommendation-service. If it doesn't work, refresh the web page a few times.
+After all the apps are running and discoverable, access `user-service` with the path https://yuchensp-user-service.azuremicroservices.io/personalized/1 from your browser. If the user-service can access `recommendation-service`, you should get the following output. Refresh the web page a few times if it doesn't work.
 ```json
 [{"name":"Product1","description":"Description1","detailsLink":"link1"},{"name":"Product2","description":"Description2","detailsLink":"link3"},{"name":"Product3","description":"Description3","detailsLink":"link3"}]
 ```
 ## Access your Hystrix dashboard and metrics stream
-Verify using public endpoints or using private test endpoints.
+Verify using public endpoints or private test endpoints.
 
 ### Using public endpoints
 Access hystrix-turbine with the path `https://<SERVICE-NAME>-hystrix-turbine azuremicroservices.io/hystrix` from your browser.  The following figure shows the Hystrix dashboard running in this app.
 
 ![Hystrix dashboard](media/spring-cloud-circuit-breaker/hystrix-dashboard.png)
 
-Copy the Turbine stream url `https://<SERVICE-NAME>-hystrix-turbine.azuremicroservices.io/turbine.stream?cluster=default` into the text box, and click **Monitor Stream**.  This will display the dashboard. If you are not viewing anything, hit the user-service endpoints to generate the streams.
+Copy the Turbine stream url `https://<SERVICE-NAME>-hystrix-turbine.azuremicroservices.io/turbine.stream?cluster=default` into the text box, and click **Monitor Stream**.  This will display the dashboard. If nothing shows in the viewer, hit the `user-service` endpoints to generate streams.
 
 ![Hystrix stream](media/spring-cloud-circuit-breaker/hystrix-stream.png)
-You can experiment with the Circuit Breaker Dashboard.
+Now you can experiment with the Circuit Breaker Dashboard.
 > [!NOTE] 
 > In production, the Hystrix dashboard and metrics stream should not be exposed to the Internet.
 
 ### Using private test endpoints
-Hystrix metrics streams are also accessible from test-endpoint. As backend service, we didn't assign a public end-point for recommendation-service, but we can show its metrics with test-endpoint at `https://primary:<KEY>@<SERVICE-NAME>.test.azuremicroservices.io/recommendation-service/default/actuator/hystrix.stream`
+Hystrix metrics streams are also accessible from `test-endpoint`. As a backend service, we didn't assign a public end-point for `recommendation-service`, but we can show its metrics with test-endpoint at `https://primary:<KEY>@<SERVICE-NAME>.test.azuremicroservices.io/recommendation-service/default/actuator/hystrix.stream`
 
 ![Hystrix test-endpoint stream](media/spring-cloud-circuit-breaker/hystrix-test-endpoint-stream.png)
 
-As a web app, Hystrix dashboard should be working on test endpoint. If it is not working properly, there may be two reasons: First, using test endpoint will change the base URL from `/ to /<APP-NAME>/<DEPLOYMENT-NAME>`, or, second, the web app is using absolute path for static resource. To get it working on test endpoint, you might need to manually edit the <base>in the front-end files.
+As a web app, Hystrix dashboard should be working on `test-endpoint`. If it is not working properly, there may be two reasons: first, using `test-endpoint` changed the base URL from `/ to /<APP-NAME>/<DEPLOYMENT-NAME>`, or, second, the web app is using absolute path for static resource. To get it working on `test-endpoint`, you might need to manually edit the <base>in the front-end files.
 
 ## See also
 * [Provision a service instance on the Azure CLI](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-quickstart-launch-app-cli#provision-a-service-instance-on-the-azure-cli)