Line edits5

Author: lootle1

learn-pr/aspnetcore/implement-observability-cloud-native-app-with-opentelemetry/includes/4-exercise-add-observability-cloud-native-app.md

@@ -21,7 +21,7 @@ To use **Visual Studio Code**, clone the [https://github.com/MicrosoftDocs/mslea
 
 The first step to adding observability to the **:::no-loc text="eShopLite":::** app is to introduce a new diagnostic project to the solution. This project contains all the OpenTelemetry packages and configurations that you'll use to add observability to the app.
 
-1. In the Visual Studio Code command palette, enter **>.NET: Open Solution**.
+1. In the Codespace command palette, enter **>.NET: Open Solution**.
 1. Select **dotnet-observability/eShopLite/eShopLite.sln**.
 1. In the **Solution Explorer**, at the bottom of the **EXPLORER** pane, right-click the **eShopLite** solution, and then select **New Project**.
 1. In the **Select a template to create a new .NET project** dialog, select **Class Library (Common, Library)**.
@@ -32,7 +32,7 @@ The first step to adding observability to the **:::no-loc text="eShopLite":::**
 
 Now add the OpenTelemetry packages to the new diagnostic project.
 
-1. By using the **TERMINAL** pane at the bottom of Visual Studio Code, go to the *Diagnostics* project folder:
+1. By using the **TERMINAL** pane at the bottom of Codespace, go to the *Diagnostics* project folder:
 
     ```bash
     cd dotnet-observability/eShopLite/Diagnostics

learn-pr/aspnetcore/implement-observability-cloud-native-app-with-opentelemetry/includes/6-exercise-use-opentelemetry-data-cloud-native-application.md

@@ -4,7 +4,7 @@ In this exercise, you get better visibility of all the data generated by OpenTel
 
 Prometheus and Grafana provide Docker images that make it easy to add them to your projects. You include them in the *docker-compose.yml* file, in the root of the solution.
 
-1. In Visual Studio Code, on the **EXPLORER** pane, select the *docker-compose.yml* file.
+1. On the **EXPLORER** pane, select the *docker-compose.yml* file.
 1. Add this YAML to the bottom of the file:
 
     ```yml
@@ -38,7 +38,7 @@ The preceding Docker yaml adds two new services, **Prometheus** and **Grafana**.
 
 Prometheus needs to be configured so that it knows where to collect the metrics. You add a *prometheus.yml* file to the *prometheus* folder.
 
-1. In Visual Studio Code, on the **EXPLORER** pane, right-click the *dotnet-observability* folder, and then select **New Folder**.
+1. On the **EXPLORER** pane, right-click the *dotnet-observability* folder, and then select **New Folder**.
 1. In the name field, enter **prometheus**.
 1. On the **EXPLORER** pane, right-click the *prometheus* folder, and then select **New File**.
 1. In the name field, enter **prometheus.yml**.
@@ -65,7 +65,7 @@ Prometheus needs to be configured so that it knows where to collect the metrics.
 
 Grafana needs to be configured so that it knows where to collect the metrics.
 
-1. In Visual Studio Code, on the **EXPLORER** pane, right-click the *dotnet-observability* folder and then select **New Folder**.
+1. On the **EXPLORER** pane, right-click the *dotnet-observability* folder and then select **New Folder**.
 1. In the name field, enter **grafana**.
 1. Right-click the *grafana* folder, and then select **New Folder**.
 1. In the name field, enter **datasource**.
@@ -95,7 +95,7 @@ Grafana needs to be configured so that it knows where to collect the metrics.
 
 Now, the diagnostics project is only configured to expose metrics to the console. You update the project to expose metrics to Prometheus instead.
 
-1. In Visual Studio Code, on the **TERMINAL** pane at the bottom, go to the *Diagnostics* folder.
+1. On the **TERMINAL** pane at the bottom, go to the *Diagnostics* folder.
 
 1. Run this command:
 
@@ -223,7 +223,7 @@ You now test the new observability features you added to the app.
 
 You now extend the tracing capabilities of the app by adding Zipkin. As you did before, you add a Zipkin container to your app, and configure it to connect to the OpenTelemetry collector. Then you add the OpenTelemetry Zipkin exporter to your app.
 
-1. In Visual Studio Code, on the **EXPLORER** pane, select the *docker-compose.yml* file inside the *dotnet-observability* folder.
+1. On the **EXPLORER** pane, select the *docker-compose.yml* file inside the *dotnet-observability* folder.
 
 1. Add `prometheus` and `zipkin` in the `depends_on` for the `frontend`.
 
@@ -358,7 +358,7 @@ The last step is to add Application Insights to your app.
 
 ### Create the Application Insights resource in Azure
 
-1. In Visual Studio Code, on the **TERMINAL** pane, sign in to Azure.
+1. On the **TERMINAL** pane, sign in to Azure.
 
     ```azurecli
     az login --use-device-code
@@ -423,7 +423,7 @@ The last step is to add Application Insights to your app.
 
     `InstrumentationKey=b851fa75-85a2-42f7-bb6f-413725d9d8ba;IngestionEndpoint=https://eastus-2.in.applicationinsights.azure.com/;LiveEndpoint=https://eastus.livediagnostics.monitor.azure.com/`
 
-1. In Visual Studio Code, on the **EXPLORER** pane, select the *docker-compose.yml* file.
+1. On the **EXPLORER** pane, select the *docker-compose.yml* file.
 1. You add an environment variable that the diagnostics project uses to connect to Application Insights. Add this YAML to the **Store** service:
 
     ```yml

learn-pr/aspnetcore/implement-observability-cloud-native-app-with-opentelemetry/includes/7-exercise-extend-telemetry.md

@@ -6,7 +6,7 @@ In this exercise, you add new metrics to apps and see how to view them in your o
 
 You want to have greater visibility of how a stock changes over time, so you create a custom metric.
 
-1. In Visual Studio Code, on the **EXPLORER** pane, right-click the *Products* folder and then select **New File**.
+1. On the **EXPLORER** pane, right-click the *Products* folder and then select **New File**.
 
 1. In the **File name** field, enter **ProductsMetrics.cs**.