fix broken links from OPS report

craigcaseyMSFT · craigcaseyMSFT · commit e294b5ea221d · 2020-04-25T08:14:21.000-07:00
diff --git a/articles/app-service/environment/app-service-app-service-environment-create-ilb-ase-resourcemanager.md b/articles/app-service/environment/app-service-app-service-environment-create-ilb-ase-resourcemanager.md
@@ -46,7 +46,7 @@ Once the *azuredeploy.parameters.json* file has been filled in for an ILB ASE, t
 After the Azure Resource Manager template is submitted it will take a few hours for the ILB ASE to be created.  Once the creation completes, the ILB ASE will show up in the portal UX in the list of App Service Environments for the subscription that triggered the deployment.
 
 ## Uploading and Configuring the "Default" TLS/SSL Certificate
-Once the ILB ASE is created, a TLS/SSL certificate should be associated with the ASE as the "default" TLS/SSL certificate use for establishing TLS/SSL connections to apps.  Continuing with the hypothetical Contoso Corporation example, if the ASE's default DNS suffix is *internal-contoso.com*, then a connection to *https://some-random-app.internal-contoso.com* requires a TLS/SSL certificate that is valid for **.internal-contoso.com*. 
+Once the ILB ASE is created, a TLS/SSL certificate should be associated with the ASE as the "default" TLS/SSL certificate use for establishing TLS/SSL connections to apps.  Continuing with the hypothetical Contoso Corporation example, if the ASE's default DNS suffix is *internal-contoso.com*, then a connection to *`https://some-random-app.internal-contoso.com`* requires a TLS/SSL certificate that is valid for **.internal-contoso.com*. 
 
 There are a variety of ways to obtain a valid TLS/SSL certificate including internal CAs, purchasing a certificate from an external issuer, and using a self-signed certificate.  Regardless of the source of the TLS/SSL certificate, the following certificate attributes need to be configured properly:
 
@@ -118,7 +118,7 @@ Once the *azuredeploy.parameters.json* file has been filled in, the default TLS/
 
 After the Azure Resource Manager template is submitted it will take roughly forty minutes per ASE front-end to apply the change.  For example, with a default sized ASE using two front-ends, the template will take around one hour and twenty minutes to complete.  While the template is running the ASE will not be able to scaled.  
 
-Once the template completes, apps on the ILB ASE can be accessed over HTTPS and the connections will be secured using the default TLS/SSL certificate.  The default TLS/SSL certificate will be used when apps on the ILB ASE are addressed using a combination of the application name plus the default hostname.  For example *https://mycustomapp.internal-contoso.com* would use the default TLS/SSL certificate for **.internal-contoso.com*.
+Once the template completes, apps on the ILB ASE can be accessed over HTTPS and the connections will be secured using the default TLS/SSL certificate.  The default TLS/SSL certificate will be used when apps on the ILB ASE are addressed using a combination of the application name plus the default hostname.  For example *`https://mycustomapp.internal-contoso.com`* would use the default TLS/SSL certificate for **.internal-contoso.com*.
 
 However, just like apps running on the public multi-tenant service, developers can also configure custom host names for individual apps, and then configure unique SNI TLS/SSL certificate bindings for individual apps.  
 
diff --git a/articles/app-service/faq-availability-performance-application-issues.md b/articles/app-service/faq-availability-performance-application-issues.md
@@ -43,7 +43,7 @@ For descriptions and syntax for all App Service web apps cmdlets, see [Az.Websit
 
 To view your web app's event logs:
 
-1. Sign in to your [Kudu website](https://*yourwebsitename*.scm.azurewebsites.net).
+1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. In the menu, select **Debug Console** > **CMD**.
 3. Select the **LogFiles** folder.
 4. To view event logs, select the pencil icon next to **eventlog.xml**.
@@ -53,7 +53,7 @@ To view your web app's event logs:
 
 To capture a user-mode memory dump of your web app:
 
-1. Sign in to your [Kudu website](https://*yourwebsitename*.scm.azurewebsites.net).
+1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. Select the **Process Explorer** menu.
 3. Right-click the **w3wp.exe** process or your WebJob process.
 4. Select **Download Memory Dump** > **Full Dump**.
@@ -66,7 +66,7 @@ You have two options for viewing process-level information for your web app:
     1. Open the **Process Explorer** for the web app.
     2. To see the details, select the **w3wp.exe** process.
 *   In the Kudu console:
-    1. Sign in to your [Kudu website](https://*yourwebsitename*.scm.azurewebsites.net).
+    1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
     2. Select the **Process Explorer** menu.
     3. For the **w3wp.exe** process, select **Properties**.
 
diff --git a/articles/app-service/faq-configuration-and-management.md b/articles/app-service/faq-configuration-and-management.md
@@ -121,7 +121,7 @@ For more information about using deployment slots, see [Set up a staging environ
 
 To review WebJob logs:
 
-1. Sign in to your [Kudu website](https://*yourwebsitename*.scm.azurewebsites.net).
+1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. Select the WebJob.
 3. Select the **Toggle Output** button.
 4. To download the output file, select the **Download** link.
diff --git a/articles/app-service/faq-open-source-technologies.md b/articles/app-service/faq-open-source-technologies.md
@@ -24,7 +24,7 @@ This article has answers to frequently asked questions (FAQs) about issues with
 
 To turn on PHP logging:
 
-1. Sign in to your [Kudu website](https://*yourwebsitename*.scm.azurewebsites.net).
+1. Sign in to your **Kudu website** (`https://*yourwebsitename*.scm.azurewebsites.net`).
 2. In the top menu, select **Debug Console** > **CMD**.
 3. Select the **Site** folder.
 4. Select the **wwwroot** folder.
@@ -54,7 +54,7 @@ To change the version of the Node.js application, you can use one of the followi
   1. In the Azure portal, go to your web app.
   2. On the **Settings** blade, select **Application settings**.
   3. In **App settings**, you can include WEBSITE_NODE_DEFAULT_VERSION as the key, and the version of Node.js you want as the value.
-  4. Go to your [Kudu console](https://*yourwebsitename*.scm.azurewebsites.net).
+  4. Go to your **Kudu console** (`https://*yourwebsitename*.scm.azurewebsites.net`).
   5. To check the Node.js version, enter the following command:  
      ```
      node -v
@@ -89,7 +89,7 @@ If you see this error in your debug.log or php_errors.log files, your app is exc
 
 ## How do I debug a Node.js app that's hosted in App Service?
 
-1.  Go to your [Kudu console](https://*yourwebsitename*.scm.azurewebsites.net/DebugConsole).
+1.  Go to your **Kudu console** (`https://*yourwebsitename*.scm.azurewebsites.net/DebugConsole`).
 2.  Go to your application logs folder (D:\home\LogFiles\Application).
 3.  In the logging_errors.txt file, check for content.
 
diff --git a/articles/azure-functions/functions-create-function-linux-custom-image.md b/articles/azure-functions/functions-create-function-linux-custom-image.md
@@ -145,7 +145,7 @@ mvn clean package
 mvn azure-functions:run
 ```
 ::: zone-end
-Once you see the `HttpExample` endpoint appear in the output, navigate to [`http://localhost:7071/api/HttpExample?name=Functions`](http://localhost:7071/api/HttpExample?name=Functions). The browser should display a "hello" message that echoes back `Functions`, the value supplied to the `name` query parameter.
+Once you see the `HttpExample` endpoint appear in the output, navigate to `http://localhost:7071/api/HttpExample?name=Functions`. The browser should display a "hello" message that echoes back `Functions`, the value supplied to the `name` query parameter.
 
 Use **Ctrl**-**C** to stop the host.
 
@@ -174,7 +174,7 @@ Once the image is running in a local container, open a browser to `http://localh
 
 ::: zone-end
 ::: zone pivot="programming-language-java"  
-Once the image is running in a local container, browse to [`http://localhost:8080/api/HttpExample?name=Functions`](http://localhost:8080/api/HttpExample?name=Functions), which should display the same "hello" message as before. Because the Maven archetype generates an HTTP triggered function that uses anonymous authorization, you can still call the function even though it's running in the container. 
+Once the image is running in a local container, browse to `http://localhost:8080/api/HttpExample?name=Functions`, which should display the same "hello" message as before. Because the Maven archetype generates an HTTP triggered function that uses anonymous authorization, you can still call the function even though it's running in the container. 
 ::: zone-end  
 
 After you've verified the function app in the container, stop docker with **Ctrl**+**C**.
diff --git a/articles/azure-monitor/app/profiler-settings.md b/articles/azure-monitor/app/profiler-settings.md
@@ -12,7 +12,7 @@ ms.reviewer: mbullwin
 # Configure Application Insights Profiler
 
 ## Updated Profiler Agent
-The trigger features only work with version 2.6 or newer of the profiler agent. If you are running an Azure App Service, your agent will be updated automatically. You can see what version of the agent you are running if you go to the Kudu URL for your website and append \DiagnosticServices to the end of it, like this:  https://yourwebsite.scm.azurewebsites.net/diagnosticservices. The Application Insights Profiler Webjob should version 2.6 or newer. You can force an upgrade by restarting your web app. 
+The trigger features only work with version 2.6 or newer of the profiler agent. If you are running an Azure App Service, your agent will be updated automatically. You can see what version of the agent you are running if you go to the Kudu URL for your website and append \DiagnosticServices to the end of it, like this:  `https://yourwebsite.scm.azurewebsites.net/diagnosticservices`. The Application Insights Profiler Webjob should version 2.6 or newer. You can force an upgrade by restarting your web app. 
 
 If you are running the profiler on a VM or Cloud Service, you need to have Windows Azure Diagnostics (WAD) extension version 16.0.4 or newer installed. You can check the version of WAD by logging onto your VM and looking this directory: C:\Packages\Plugins\Microsoft.Azure.Diagnostics.IaaSDiagnostics\1.16.0.4. The directory name is the version of WAD that is installed. The Azure VM agent will update WAD automatically when new versions are available.
 
diff --git a/articles/azure-signalr/signalr-concept-authenticate-oauth.md b/articles/azure-signalr/signalr-concept-authenticate-oauth.md
@@ -539,8 +539,8 @@ The last thing you need to do is update the **Homepage URL** and **Authorization
 
     | Setting | Example |
     | ------- | ------- |
-    | Homepage URL | https://signalrtestwebapp22665120.azurewebsites.net/home |
-    | Authorization callback URL | https://signalrtestwebapp22665120.azurewebsites.net/signin-github |
+    | Homepage URL | `https://signalrtestwebapp22665120.azurewebsites.net/home` |
+    | Authorization callback URL | `https://signalrtestwebapp22665120.azurewebsites.net/signin-github` |
 
 3. Navigate to your web app URL and test the application.
 
diff --git a/articles/cognitive-services/form-recognizer/quickstarts/label-tool.md b/articles/cognitive-services/form-recognizer/quickstarts/label-tool.md
@@ -57,7 +57,7 @@ You'll use the Docker engine to run the sample labeling tool. Follow these steps
     docker run -it -p 3000:80 mcr.microsoft.com/azure-cognitive-services/custom-form/labeltool eula=accept
     ```
 
-   This command will make the sample labeling tool available through a web browser. Go to [http://localhost:3000](http://localhost:3000).
+   This command will make the sample labeling tool available through a web browser. Go to `http://localhost:3000`.
 
 > [!NOTE]
 > You can also label documents and train models using the Form Recognizer REST API. To train and Analyze with the REST API, see [Train with labels using the REST API and Python](./python-labeled-data.md).
diff --git a/articles/cognitive-services/immersive-reader/tutorial-multiple-resources.md b/articles/cognitive-services/immersive-reader/tutorial-multiple-resources.md
@@ -255,7 +255,7 @@ The **getimmersivereaderlaunchparams** API endpoint should be secured behind som
     npm start
     ```
 
-4. Open your browser and navigate to [http://localhost:3000](http://localhost:3000). You should see the above content on the page. Click on either the **EastUS Immersive Reader** button or the **WestUS Immersive Reader** button to launch the Immersive Reader using those respective resources.
+4. Open your browser and navigate to `http://localhost:3000`. You should see the above content on the page. Click on either the **EastUS Immersive Reader** button or the **WestUS Immersive Reader** button to launch the Immersive Reader using those respective resources.
 
 ## Next steps
 
diff --git a/articles/container-service/dcos-swarm/container-service-monitoring.md b/articles/container-service/dcos-swarm/container-service-monitoring.md
@@ -26,7 +26,7 @@ Datadog is a monitoring service that gathers monitoring data from your container
 ## Configure a Datadog deployment with Marathon
 These steps will show you how to configure and deploy Datadog 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 "Datadog" and click "Install."
+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 "Datadog" and click "Install."
 
 ![Datadog package within the DC/OS Universe](./media/container-service-monitoring/datadog1.png)
 
