Merge pull request #112756 from craigcaseyMSFT/vcraic0424

fix broken links from OPS report

Author: PRMerger6

articles/service-fabric/service-fabric-cluster-creation-for-windows-server.md

@@ -140,7 +140,7 @@ NodeDeactivationInfo NodeName IpAddressOrFQDN NodeType  CodeVersion  ConfigVersi
 ```
 
 ### Step 3: Visualize the cluster using Service Fabric explorer
-[Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) is a good tool for visualizing your cluster and managing applications.  Service Fabric Explorer is a service that runs in the cluster, which you access using a browser by navigating to [http://localhost:19080/Explorer](http://localhost:19080/Explorer).
+[Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) is a good tool for visualizing your cluster and managing applications.  Service Fabric Explorer is a service that runs in the cluster, which you access using a browser by navigating to `http://localhost:19080/Explorer`.
 
 The cluster dashboard provides an overview of your cluster, including a summary of application and node health. The node view shows the physical layout of the cluster. For a given node, you can inspect which applications have code deployed on that node.
 

articles/service-fabric/service-fabric-create-your-first-linux-application-with-csharp.md

@@ -85,7 +85,7 @@ Parameters to these commands can be found in the generated manifests inside the
 
 Once the application has been deployed, open a browser and navigate to
 [Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) at
-[http://localhost:19080/Explorer](http://localhost:19080/Explorer). Then, expand the **Applications** node and note
+`http://localhost:19080/Explorer`. Then, expand the **Applications** node and note
 that there is now an entry for your application type and another for the first instance of that type.
 
 > [!IMPORTANT]

articles/service-fabric/service-fabric-create-your-first-linux-application-with-java.md

@@ -204,7 +204,7 @@ Parameters to these commands can be found in the generated manifests inside the
 
 Once the application has been deployed, open a browser and navigate to
 [Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) at
-[http://localhost:19080/Explorer](http://localhost:19080/Explorer).
+`http://localhost:19080/Explorer`.
 Then, expand the **Applications** node and note that there is now an entry for your application type and another for
 the first instance of that type.
 

articles/service-fabric/service-fabric-get-started-eclipse.md

@@ -98,7 +98,7 @@ After you have built your Service Fabric application, follow these steps to depl
 
 3.  From the context menu, click **Deploy Application**.
 4.  You can follow the progress of the deploy operation in the Console window.
-5.  To verify that your application is running, open Service Fabric Explorer on your local cluster in a browser window [http://localhost:19080/Explorer](http://localhost:19080/Explorer). Expand the **Applications** node and make sure your application is running. 
+5.  To verify that your application is running, open Service Fabric Explorer on your local cluster in a browser window `http://localhost:19080/Explorer`. Expand the **Applications** node and make sure your application is running. 
 
 To learn how to debug your application in Eclipse using the local cluster, see [Debug a Java service in Eclipse](./service-fabric-debugging-your-application-java.md).
 

articles/service-fabric/service-fabric-get-started-linux.md

@@ -174,7 +174,7 @@ Start a local cluster after the installation finishes.
     sudo /opt/microsoft/sdk/servicefabric/common/clustersetup/devclustersetup.sh
     ```
 
-2. Open a web browser and go to [Service Fabric Explorer](http://localhost:19080/Explorer) (`http://localhost:19080/Explorer`). When the cluster starts, you see the Service Fabric Explorer dashboard. It might take several minutes for the cluster to be completely set up. If your browser fails to open the URL or if Service Fabric Explorer doesn't show that the system is ready, wait a few minutes and try again.
+2. Open a web browser and go to **Service Fabric Explorer** (`http://localhost:19080/Explorer`). When the cluster starts, you see the Service Fabric Explorer dashboard. It might take several minutes for the cluster to be completely set up. If your browser fails to open the URL or if Service Fabric Explorer doesn't show that the system is ready, wait a few minutes and try again.
 
     ![Service Fabric Explorer on Linux][sfx-linux]
 

articles/service-fabric/service-fabric-get-started-mac.md

@@ -97,7 +97,7 @@ To set up a local Docker container and have a Service Fabric cluster running on
     >`docker run -itd -p 19080:19080 -p 8080:8080 --name sfonebox mcr.microsoft.com/service-fabric/onebox:latest`
     >
 
-5. The cluster will take a moment to start. When it is running, you can view logs using the following command or jump to the dashboard to view the clusters health [http://localhost:19080](http://localhost:19080):
+5. The cluster will take a moment to start. When it is running, you can view logs using the following command or jump to the dashboard to view the clusters health `http://localhost:19080`:
 
     ```bash 
     docker logs sftestcluster

articles/service-fabric/service-fabric-local-linux-cluster-windows.md

@@ -84,7 +84,7 @@ To set up a local Docker container and have a service fabric cluster running on
     >`docker run -itd -p 19080:19080 -p 8080:8080 --name sfonebox mcr.microsoft.com/service-fabric/onebox:latest`
     >
 
-5. The cluster will take a short amount of time to start, you can view logs using the following command or jump to the dashboard to view the clusters health [http://localhost:19080](http://localhost:19080):
+5. The cluster will take a short amount of time to start, you can view logs using the following command or jump to the dashboard to view the clusters health `http://localhost:19080`:
 
     ```powershell 
     docker logs sftestcluster

articles/service-fabric/service-fabric-reliable-services-quick-start-java.md

@@ -255,7 +255,7 @@ Parameters to these commands can be found in the generated manifests inside the
 
 Once the application has been deployed, open a browser and navigate to
 [Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) at
-[http://localhost:19080/Explorer](http://localhost:19080/Explorer). Then, expand the **Applications** node and note
+`http://localhost:19080/Explorer`. Then, expand the **Applications** node and note
 that there is now an entry for your application type and another for the first instance of that type.
 
 > [!IMPORTANT]

articles/service-fabric/service-fabric-tutorial-monitoring-aspnet.md

@@ -163,7 +163,7 @@ At this point, you are ready to deploy the application. Click **Start** at the t
 >[!NOTE]
 >You may get a build error if you do not have an up-to-date version of the .NET Core SDK installed.
 
-Once the application is done deploying, head over to [localhost:8080](localhost:8080), where you should be able to see the Voting Sample single page application. Vote for a few different items of your choice to create some sample data and telemetry - I went for desserts!
+Once the application is done deploying, head over to `localhost:8080`, where you should be able to see the Voting Sample single page application. Vote for a few different items of your choice to create some sample data and telemetry - I went for desserts!
 
 ![AI sample votes](./media/service-fabric-tutorial-monitoring-aspnet/vote-sample.png)
 
@@ -248,7 +248,7 @@ public async Task<IActionResult> Delete(string name)
 }
 ```
 
-Once you're done making these changes, **Start** the application so that it builds and deploys the latest version of it. Once the application is done deploying, head over to [localhost:8080](localhost:8080), and add and delete some voting options. Then, go back to your Application Insights resource to see the traces for the latest run (as before, traces can take 1-2 min to show up in Application Insights). For all the votes you added and deleted, you should now see a "Custom Event* along with all the response telemetry.
+Once you're done making these changes, **Start** the application so that it builds and deploys the latest version of it. Once the application is done deploying, head over to `localhost:8080`, and add and delete some voting options. Then, go back to your Application Insights resource to see the traces for the latest run (as before, traces can take 1-2 min to show up in Application Insights). For all the votes you added and deleted, you should now see a "Custom Event* along with all the response telemetry.
 
 ![custom events](./media/service-fabric-tutorial-monitoring-aspnet/custom-events.png)
 

articles/storage/files/storage-snapshots-files.md

@@ -33,7 +33,7 @@ After a share snapshot is created, it can be read, copied, or deleted, but not m
 Share snapshot capability is provided at the file share level. Retrieval is provided at individual file level, to allow for restoring individual files. You can restore a complete file share by using SMB, the REST API, the portal, the client library, or PowerShell/CLI tooling.
 
 A share snapshot of a file share is identical to its base file share. The only difference is that a **DateTime** value is appended to the share URI to indicate the
-time at which the share snapshot was taken. For example, if a file share URI is http://storagesample.core.file.windows.net/myshare, the share snapshot URI is similar to:
+time at which the share snapshot was taken. For example, if a file share URI is http:\//storagesample.core.file.windows.net/myshare, the share snapshot URI is similar to:
 ```
 http://storagesample.core.file.windows.net/myshare?snapshot=2011-03-09T01:42:34.9360000Z
 ```