Fix broken links (#385)

* Fix broken links

* Replace links with their auto-redirect target

Author: bart-vmware

docs/docs/v2/configuration/cloud-foundry-provider.md

@@ -112,7 +112,7 @@ var uri = config["vcap:services:service-name:0:credentials:uri"]
 
 A list of all `VCAP_SERVICES` keys is available in the [VCAP_SERVICES](https://docs.CloudFoundry.org/devguide/deploy-apps/environment-variable.html#VCAP-SERVICES) topic of the Cloud Foundry documentation.
 
->NOTE: This provider uses the built-in .NET [JSON Configuration Parser](https://github.com/aspnet/Configuration/tree/dev/src/Microsoft.Extensions.Configuration.Json) when parsing the JSON provided in the `VCAP_*` environment variables. As a result, you can expect the exact same key names and behavior as you see when parsing JSON configuration files (such as `appsettings.json`) in your application.
+>NOTE: This provider uses the built-in .NET [JSON Configuration Parser](https://github.com/dotnet/dotnet/tree/main/src/runtime/src/libraries/Microsoft.Extensions.Configuration.Json) when parsing the JSON provided in the `VCAP_*` environment variables. As a result, you can expect the exact same key names and behavior as you see when parsing JSON configuration files (such as `appsettings.json`) in your application.
 
 ### Access Configuration Data as Options
 

docs/docs/v2/connectors/mysql.md

@@ -51,7 +51,7 @@ The following MySQL connector configuration shows how to connect to a database a
 }
 ```
 
-The following table describes the available settings for the connector. These settings are not specific to Steeltoe. They are passed through to the underlying data provider. See the [Oracle MySQL Connection String docs](https://dev.mysql.com/doc/connector-net/en/connector-net-connection-options.html) or [open source MySQL Connection String docs](https://mysql-net.github.io/MySqlConnector/connection-options/).
+The following table describes the available settings for the connector. These settings are not specific to Steeltoe. They are passed through to the underlying data provider. See the [Oracle MySQL Connection String docs](https://dev.mysql.com/doc/connector-net/en/connector-net-connections-string.html) or [open source MySQL Connection String docs](https://mysqlconnector.net/connection-options/).
 
 | Key | Description | Steeltoe Default |
 | --- | --- | :---: |

docs/docs/v3/configuration/cloud-foundry-provider.md

@@ -103,7 +103,7 @@ var uri = config["vcap:services:service-name:0:credentials:uri"];
 
 A list of all `VCAP_SERVICES` keys is available in the [VCAP_SERVICES](https://docs.CloudFoundry.org/devguide/deploy-apps/environment-variable.html#VCAP-SERVICES) topic of the Cloud Foundry documentation.
 
->This provider uses the built-in .NET [JSON Configuration Parser](https://github.com/aspnet/Configuration/tree/dev/src/Microsoft.Extensions.Configuration.Json) when parsing the JSON provided in the `VCAP_*` environment variables. As a result, you can expect the exact same key names and behavior as you see when parsing JSON configuration files (such as `appsettings.json`) in your application.
+>This provider uses the built-in .NET [JSON Configuration Parser](https://github.com/dotnet/dotnet/tree/main/src/runtime/src/libraries/Microsoft.Extensions.Configuration.Json) when parsing the JSON provided in the `VCAP_*` environment variables. As a result, you can expect the exact same key names and behavior as you see when parsing JSON configuration files (such as `appsettings.json`) in your application.
 
 ### Access Configuration Data as Options
 

docs/docs/v3/connectors/mysql.md

@@ -50,7 +50,7 @@ The following MySQL connector configuration shows how to connect to a database a
 }
 ```
 
-The following table describes the available settings for the connector. These settings are not specific to Steeltoe. They are passed through to the underlying data provider. See the [Oracle MySQL Connection String docs](https://dev.mysql.com/doc/connector-net/en/connector-net-connection-options.html) or [open source MySQL Connection String docs](https://mysql-net.github.io/MySqlConnector/connection-options/).
+The following table describes the available settings for the connector. These settings are not specific to Steeltoe. They are passed through to the underlying data provider. See the [Oracle MySQL Connection String docs](https://dev.mysql.com/doc/connector-net/en/connector-net-connections-string.html) or [open source MySQL Connection String docs](https://mysqlconnector.net/connection-options/).
 
 | Key | Description | Steeltoe Default |
 | --- | --- | :---: |

docs/docs/v3/discovery/initialize-discovery-client.md

@@ -57,7 +57,7 @@ public class Program
 
 The `AddDiscoveryClient` extension shown above uses reflection to find assemblies containing a discovery client. Specifically, assemblies are located by the presence of the attribute `DiscoveryClientAssembly`, which contains a reference to an `IDiscoveryClientExtension` that does the work in configuring options and injecting the required service for the `IDiscoveryClient` to operate.
 
->If no discovery client package is found a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/release/3.2/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) will be used. This will happen when no client has been added or if you publish your application with [`/p:PublishSingleFile=true`](https://docs.microsoft.com/dotnet/core/deploying/single-file))
+>If no discovery client package is found a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) will be used. This will happen when no client has been added or if you publish your application with [`/p:PublishSingleFile=true`](https://docs.microsoft.com/dotnet/core/deploying/single-file))
 
 To avoid this reflection-based approach, use declarative configuration of the client(s) you plan to use, like this:
 
@@ -77,7 +77,7 @@ public class Program
 
 As of version 3.0.2, you may add multiple `Usexxx()` statements to this options builder, so long as only one is configured at runtime.
 
->If no extension is supplied for `AddServiceDiscovery`, a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/3.2/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) will be used.
+>If no extension is supplied for `AddServiceDiscovery`, a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) will be used.
 
 ## Other Extensions
 

docs/docs/v3/discovery/kubernetes.md

@@ -33,4 +33,4 @@ Using native Kubernetes service discovery ensures compatibility with additional
 
 The calling service then need only refer to names resolvable in a particular Kubernetes cluster. This may be as simple as using the service name as the host name, or it may require a fully qualified domain name (FQDN), such as `{service-name}.{namespace}.svc.{cluster}.local:{service-port}` depending on your environment.
 
-In order to use both the discovery client programming model and the platform's native capabilities, a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/release/3.2/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) can be used by either disabling other discovery clients, or not including them in the first place.
+In order to use both the discovery client programming model and the platform's native capabilities, a [NoOpDiscoveryClient](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Discovery/src/ClientBase/SimpleClients/NoOpDiscoveryClient.cs) can be used by either disabling other discovery clients, or not including them in the first place.

docs/docs/v3/management/health.md

@@ -281,4 +281,4 @@ public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerF
 }
 ```
 
-A complete example is available [here](https://github.com/SteeltoeOSS/Samples/tree/3.x/Management/src/AspDotNetCore/MicrosoftHealthChecks).
+A complete example is available [here](https://github.com/SteeltoeOSS/Samples/tree/3.x/Management/src/MicrosoftHealthChecks).

docs/docs/v3/management/using-endpoints.md

@@ -78,7 +78,7 @@ The following table describes the settings that you can apply globally:
 
 ### Custom Serialization Options
 
-As of 3.1.1, the `JsonSerializerOptions` used to serialize actuator responses are configurable, and custom JsonConverters can be used by adding the [assembly-qualified type](https://docs.microsoft.com/dotnet/api/system.type.assemblyqualifiedname").
+As of 3.1.1, the `JsonSerializerOptions` used to serialize actuator responses are configurable, and custom JsonConverters can be used by adding the [assembly-qualified type](https://docs.microsoft.com/dotnet/api/system.type.assemblyqualifiedname).
 
 For example, to have DateTime values serialized as epoch times and all JSON pretty printed:
 

docs/docs/v3/stream/standalone-stream-rabbitmq.md

@@ -125,7 +125,7 @@ namespace UsageSender
 ```
 
 The `[EnableBinding]` attribute indicates that you want to bind your application to messaging middleware.
-The attribute takes one or more interfaces as a parameter, in this case, the [ISource](https://github.com/SteeltoeOSS/Steeltoe/blob/main/src/Stream/src/Abstractions/Messaging/ISource.cs) interface that defines an output channel named `output`.
+The attribute takes one or more interfaces as a parameter, in this case, the [ISource](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Stream/src/Abstractions/Messaging/ISource.cs) interface that defines an output channel named `output`.
 In the case of RabbitMQ, messages sent to the `output` channel are in turn sent to the RabbitMQ message broker by using a `TopicExchange`.
 
 Deriving from [BackgroundService](https://docs.microsoft.com/aspnet/core/fundamentals/host/hosted-services#backgroundservice-base-class) and calling `Task.Delay` makes the UsageGenerator a background task that gets called by the framework every `5` seconds.
@@ -251,7 +251,7 @@ namespace UsageProcessor
 }
 ```
 
-In the preceding application, the `[EnableBinding]` attribute indicates that you want to bind your application to the messaging middleware. The attribute takes one or more interfaces as a parameter, in this case, the [IProcessor](https://github.com/SteeltoeOSS/Steeltoe/blob/main/src/Stream/src/Abstractions/Messaging/IProcessor.cs) that defines and input and output channel.
+In the preceding application, the `[EnableBinding]` attribute indicates that you want to bind your application to the messaging middleware. The attribute takes one or more interfaces as a parameter, in this case, the [IProcessor](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Stream/src/Abstractions/Messaging/IProcessor.cs) that defines and input and output channel.
 
 The `[StreamListener]` attribute binds the application's `input` channel to the `Handle` method and automatically deserializes the incoming JSON into `UsageDetail` object.
 
@@ -337,7 +337,7 @@ namespace UsageLogger
 }
 ```
 
-In the preceding application, the `[EnableBinding]` attribute indicates that you want to bind your application to the messaging middleware. The attribute takes one or more interfaces as a parameter, in this case, the [ISink](https://github.com/SteeltoeOSS/Steeltoe/blob/main/src/Stream/src/Abstractions/Messaging/ISink.cs) interface that defines an input channel.
+In the preceding application, the `[EnableBinding]` attribute indicates that you want to bind your application to the messaging middleware. The attribute takes one or more interfaces as a parameter, in this case, the [ISink](https://github.com/SteeltoeOSS/Steeltoe/blob/3.x/src/Stream/src/Abstractions/Messaging/ISink.cs) interface that defines an input channel.
 
 The `[StreamListener]` attribute binds the application's `input` channel to the `process` method by converting the incoming JSON to a `UsageCostDetail` object.
 

docs/docs/v3/tracing/distributed-tracing-exporting.md

@@ -1,6 +1,6 @@
 # Exporting Distributed Traces
 
-Steeltoe is able to automatically configure several exporters provided by the [OpenTelemetry](https://opentelemetry.io) project, including [Zipkin](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.Zipkin), [Jaeger](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.Jaeger) and [OpenTelemetryProtocol](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol), if a NuGet reference to the desired exporter is included. The `Steeltoe.Management.ExporterBase` and `Steeltoe.Management.ExporterCore` packages are no longer required. In addition, Steeltoe supports exporting traces to [TanzuObservability](https://tanzu.vmware.com/observability) without any other NuGet references.
+Steeltoe is able to automatically configure several exporters provided by the [OpenTelemetry](https://opentelemetry.io) project, including [Zipkin](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.Zipkin), [Jaeger](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/docs/trace/getting-started-jaeger/README.md) and [OpenTelemetryProtocol](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol), if a NuGet reference to the desired exporter is included. The `Steeltoe.Management.ExporterBase` and `Steeltoe.Management.ExporterCore` packages are no longer required. In addition, Steeltoe supports exporting traces to [TanzuObservability](https://tanzu.vmware.com/observability) without any other NuGet references.
 
 ## Common Settings