Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-search

Author: HeidiSteen

articles/azure-monitor/app/eventcounters.md

@@ -8,7 +8,7 @@ ms.date: 09/20/2019
 
 # EventCounters introduction
 
-`EventCounter` is .NET/.NET Core mechanism to publish and consume counters or statistics. [This](https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md) document gives an overview of `EventCounters` and examples on how to publish and consume them. EventCounters are supported in all OS platforms - Windows, Linux, and macOS. It can be thought of as a cross-platform equivalent for the [PerformanceCounters](https://docs.microsoft.com/dotnet/api/system.diagnostics.performancecounter) that is only supported in Windows systems.
+`EventCounter` is .NET/.NET Core mechanism to publish and consume counters or statistics. [This](https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md) document gives an overview of `EventCounters` and examples on how to publish and consume them. EventCounters are supported in all OS platforms - Windows, Linux, and macOS. It can be thought of as a cross-platform equivalent for the [PerformanceCounters](https://docs.microsoft.com/dotnet/api/system.diagnostics.performancecounter) that is only supported in Windows systems.
 
 While users can publish any custom `EventCounters` to meet their needs, the .NET Core 3.0 runtime publishes a set of these counters by default. The document will walk through the steps required to collect and view `EventCounters` (system defined or user defined) in Azure Application Insights.
 

articles/container-service/dcos-swarm/container-service-monitoring-dynatrace.md

@@ -28,7 +28,7 @@ The following figure shows the Dynatrace UI:
 ## Configure a Dynatrace deployment with Marathon
 These steps show you how to configure and deploy Dynatrace applications to your cluster with Marathon.
 
-1. Access your DC/OS UI via [http://localhost:80/](http://localhost:80/). Once in the DC/OS UI, navigate to the **Universe** tab and then search for **Dynatrace**.
+1. Access your DC/OS UI via `http://localhost:80/`. Once in the DC/OS UI, navigate to the **Universe** tab and then search for **Dynatrace**.
 
     ![Dynatrace in DC/OS Universe](./media/container-service-monitoring-dynatrace/dynatrace-universe.png)
 

articles/container-service/dcos-swarm/container-service-monitoring-elk.md

@@ -24,7 +24,7 @@ Azure Container Service. Explore the DC/OS dashboard and Marathon services [here
 ELK stack is a combination of Elasticsearch, Logstash, and Kibana that provides an end to end stack that can be used to monitor and analyze logs in your cluster.
 
 ## Configure the ELK stack on a DC/OS cluster
-Access your DC/OS UI via [http://localhost:80/](http://localhost:80/) Once in the DC/OS UI navigate to **Universe**. Search and 
+Access your DC/OS UI via `http://localhost:80/` Once in the DC/OS UI navigate to **Universe**. Search and 
 install Elasticsearch, Logstash, and Kibana from the DC/OS Universe and in that specific order. You can learn more about configuration 
 if you go to the **Advanced Installation** link.
 

articles/container-service/dcos-swarm/container-service-monitoring-sysdig.md

@@ -26,7 +26,7 @@ Sysdig is a monitoring service that allows you to monitor your containers within
 ## Configure a Sysdig deployment with Marathon
 These steps will show you how to configure and deploy Sysdig applications to your cluster with Marathon. 
 
-Access your DC/OS UI via [http://localhost:80/](http://localhost:80/) Once in the DC/OS UI navigate to the "Universe", which is on the bottom left and then search for "Sysdig."
+Access your DC/OS UI via `http://localhost:80/` Once in the DC/OS UI navigate to the "Universe", which is on the bottom left and then search for "Sysdig."
 
 ![Sysdig in DC/OS Universe](./media/container-service-monitoring-sysdig/sysdig1.png)
 

articles/cosmos-db/sql-api-nodejs-application.md

@@ -433,7 +433,7 @@ The second form contains two input fields and a button that allows you to create
 
 Now that you have built the application, you can run it locally by using the following steps:  
 
-1. To test the application on your local machine, run `npm start` in the terminal to start your application, and then refresh the [http://localhost:3000](http://localhost:3000) browser page. The page should now look as shown in the following screenshot:
+1. To test the application on your local machine, run `npm start` in the terminal to start your application, and then refresh the `http://localhost:3000` browser page. The page should now look as shown in the following screenshot:
 
     ![Screenshot of the MyTodo List application in a browser window](./media/sql-api-nodejs-application/cosmos-db-node-js-localhost.png)
 

articles/cosmos-db/tutorial-develop-mongodb-nodejs-part6.md

@@ -80,7 +80,7 @@ Before starting this part of the tutorial, ensure you've completed the steps in
 
 5. Check that everything worked by running the app. In Visual Studio Code, save all your changes, select the **Debug** button ![Debug icon in Visual Studio Code](./media/tutorial-develop-mongodb-nodejs-part6/debug-button.png) on the left side, then select the **Start Debugging** button ![Start debugging icon in Visual Studio Code](./media/tutorial-develop-mongodb-nodejs-part6/start-debugging-button.png).
 
-6. Now go back to your internet browser and open the Developer tools Network tab by pressing F12 on most machines. Navigate to [http://localhost:3000](http://localhost:3000) to watch the calls made over the network.
+6. Now go back to your internet browser and open the Developer tools Network tab by pressing F12 on most machines. Navigate to `http://localhost:3000` to watch the calls made over the network.
 
     ![Networking tab in Chrome that shows network activity](./media/tutorial-develop-mongodb-nodejs-part6/add-new-hero.png)
 

articles/data-factory/v1/data-factory-spark.md

@@ -242,7 +242,7 @@ In this step, you create a pipeline with an HDInsightSpark activity. Currently,
 
 ### Verify the results
 
-1. Start the Jupyter Notebook for your HDInsight Spark cluster by going to [this website](https://CLUSTERNAME.azurehdinsight.net/jupyter). You also can open a cluster dashboard for your HDInsight Spark cluster, and then start the Jupyter Notebook.
+1. Start the Jupyter Notebook for your HDInsight Spark cluster by going to `https://CLUSTERNAME.azurehdinsight.net/jupyter`. You also can open a cluster dashboard for your HDInsight Spark cluster, and then start the Jupyter Notebook.
 
 1. Select **New** > **PySpark** to start a new notebook.
 

articles/dev-spaces/quickstart-cli.md

@@ -101,12 +101,12 @@ Step 7/8 : COPY . .
 Step 8/8 : CMD ["npm", "start"]
 Built container image in 6m 17s
 Waiting for container...13s
-Service 'webfrontend' port 'http' is available at http://webfrontend.1234567890abcdef1234.eus.azds.io/
+Service 'webfrontend' port 'http' is available at `http://webfrontend.1234567890abcdef1234.eus.azds.io/`
 Service 'webfrontend' port 80 (http) is available at http://localhost:54256
 ...
 ```
 
-You can see the service running by opening the public URL, which is displayed in the output from the `azds up` command. In this example, the public URL is *http://webfrontend.1234567890abcdef1234.eus.azds.io/*.
+You can see the service running by opening the public URL, which is displayed in the output from the `azds up` command. In this example, the public URL is *`http://webfrontend.1234567890abcdef1234.eus.azds.io/`*.
 
 > [!NOTE]
 > When you navigate to your service while running `azds up`, the HTTP request traces are also displayed in the output of the `azds up` command. These traces can help you troubleshoot and debug your service. You can disable these traces using `--disable-http-traces` when running `azds up`.

articles/dev-spaces/quickstart-netcore-visualstudio.md

@@ -83,12 +83,12 @@ Built container image in 39s
 Waiting for container...
 36s
 
-Service 'webfrontend' port 'http' is available at http://default.webfrontend.1234567890abcdef1234.eus.azds.io/
+Service 'webfrontend' port 'http' is available at `http://default.webfrontend.1234567890abcdef1234.eus.azds.io/`
 Service 'webfrontend' port 80 (http) is available at http://localhost:62266
 Completed warmup for project 'webfrontend' in 125 seconds.
 ```
 
-In the above example, the public URL is http://default.webfrontend.1234567890abcdef1234.eus.azds.io/. 
+In the above example, the public URL is `http://default.webfrontend.1234567890abcdef1234.eus.azds.io/`. 
 
 Select **Debug** then **Start Debugging**. After a few seconds, your service will start and Visual Studio will open a browser with the public URL of the service. If a browser does not automatically open, navigate to your service's public URL in a browser and interact with the service running in your dev space.
 

articles/dev-spaces/team-development-netcore-visualstudio.md

@@ -118,7 +118,7 @@ Here is a diagram that will help you understand how the different spaces work. T
 This built-in capability of Azure Dev Spaces enables you to test code end-to-end in a shared environment without requiring each developer to re-create the full stack of services in their space. This routing requires propagation headers to be forwarded in your app code, as illustrated in the previous step of this guide.
 
 ### Test code running in the _dev/scott_ space
-To test your new version of *mywebapi* in conjunction with *webfrontend*, open your browser to the public access point URL for *webfrontend* (for example, http://dev.webfrontend.123456abcdef.eus.azds.io) and go to the About page. You should see the original message "Hello from webfrontend and Hello from mywebapi".
+To test your new version of *mywebapi* in conjunction with *webfrontend*, open your browser to the public access point URL for *webfrontend* (for example, `http://dev.webfrontend.123456abcdef.eus.azds.io`) and go to the About page. You should see the original message "Hello from webfrontend and Hello from mywebapi".
 
 Now, add the "scott.s." part to the URL so it reads something like http\://scott.s.dev.webfrontend.123456abcdef.eus.azds.io and refresh the browser. The breakpoint you set in your *mywebapi* project should get hit. Click F5 to proceed and in your browser you should now see the new message "Hello from webfrontend and mywebapi now says something new." This is because the path to your updated code in *mywebapi* is running in the _dev/scott_ space.