Merge pull request #250796 from cmcclister/Broken-link-fix-tomvcassidy

Broken Links Fixed

Author: prmerger-automator[bot]

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

@@ -170,9 +170,9 @@ This script can be run on any machine that has administrator access to all the m
 <a id="telemetry"></a>
 
 ## Telemetry data collected and how to opt out of it
-As a default, the product collects telemetry on the Service Fabric usage to improve the product. The Best Practice Analyzer that runs as a part of the setup checks for connectivity to [https://vortex.data.microsoft.com/collect/v1](https://vortex.data.microsoft.com/collect/v1). If it is not reachable, the setup fails unless you opt out of telemetry.
+As a default, the product collects telemetry on the Service Fabric usage to improve the product. If it is not reachable, the setup fails unless you opt out of telemetry.
 
-1. The telemetry pipeline tries to upload the following data to [https://vortex.data.microsoft.com/collect/v1](https://vortex.data.microsoft.com/collect/v1) once every day. It is a best-effort upload and has no impact on the cluster functionality. The telemetry is only sent from the node that runs the failover manager primary. No other nodes send out telemetry.
+1. It is a best-effort upload and has no impact on the cluster functionality. The telemetry is only sent from the node that runs the failover manager primary. No other nodes send out telemetry.
 2. The telemetry consists of the following:
 
 * Number of services

articles/service-fabric/service-fabric-containers-volume-logging-drivers.md

@@ -199,7 +199,7 @@ As shown in the **DriverOption** elements in the snippet above, the Azure Files
 ## Using your own volume or logging driver
 Service Fabric also allows the usage of your own custom [volume](https://docs.docker.com/engine/extend/plugins_volume/) or [logging](https://docs.docker.com/engine/admin/logging/overview/) drivers. If the Docker volume/logging driver is not installed on the cluster, you can install it manually by using the RDP/SSH protocols. You can perform the install with these protocols through a [virtual machine scale set start-up script](https://azure.microsoft.com/resources/templates/vmss-custom-script-windows/) or an [SetupEntryPoint script](./service-fabric-application-model.md).
 
-An example of the script to install the [Docker volume driver for Azure](https://docs.docker.com/docker-for-azure/persistent-data-volumes/) is as follows:
+An example of the script to install the [Docker volume driver for Azure](https://docs.docker.com/cloud/aci-compose-features/) is as follows:
 
 ```bash
 docker plugin install --alias azure --grant-all-permissions docker4x/cloudstor:17.09.0-ce-azure1  \

articles/service-fabric/service-fabric-reliable-services-communication-remoting.md

@@ -90,7 +90,7 @@ Service proxy creation is a lightweight operation, so you can create as many as
 ### Service proxy factory lifetime
 
 [ServiceProxyFactory](/dotnet/api/microsoft.servicefabric.services.remoting.client.serviceproxyfactory) is a factory that creates proxy instances for different remoting interfaces. If you use the API `ServiceProxyFactory.CreateServiceProxy` to create a proxy, the framework creates a singleton service proxy.
-It is useful to create one manually when you need to override [IServiceRemotingClientFactory](/dotnet/api/microsoft.servicefabric.services.remoting.v1.client.iserviceremotingclientfactory) properties.
+It is useful to create one manually when you need to override IServiceRemotingClientFactory properties.
 Factory creation is an expensive operation. A service proxy factory maintains an internal cache of the communication client.
 A best practice is to cache the service proxy factory for as long as possible.