ks-linkfix-202107 (dotnet#25304)

docs/architecture/porting-existing-aspnet-apps/deployment-scenarios.md

@@ -17,7 +17,7 @@ Consider the common scenario of a large web app that currently is hosted on IIS
 
 Assuming the task of porting the app is split such that either the MVC functionality or the API functionality is migrated to ASP.NET Core first, how would the original site continue to function seamlessly with the new ASP.NET Core app running somewhere else? Users of the system should continue to see the same URLs they did prior to the migration, unless it's absolutely necessary to change them.
 
-Fortunately, IIS is a very feature-rich web server, and two features it has had for some time are its [URL Rewrite module and Application Request Routing](/iis/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing). Using these features, IIS can act as a [reverse proxy](/iis/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing), routing client requests to the appropriate back-end web app. To configure IIS as a reverse proxy, check the **Enable proxy** checkbox in the Application Request Routing feature, then add a URL Rewrite rule like this one:
+Fortunately, IIS is a feature-rich web server, and two features it has are [URL Rewrite module](/iis/extensions/url-rewrite-module/url-rewrite-module-video-walkthrough) and [Application Request Routing](/iis/extensions/planning-for-arr/application-request-routing-version-2-overview). Using these features, IIS can act as a [reverse proxy](/iis/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing), routing client requests to the appropriate back-end web app. To configure IIS as a reverse proxy, check the **Enable proxy** checkbox in the Application Request Routing feature, then add a URL Rewrite rule like this one:
 
 ```xml
 <rule name="NetCoreProxy">

docs/framework/data/adonet/dataset-datatable-dataview/security-guidance.md

@@ -213,7 +213,7 @@ If an app must remove all type limiting restrictions from `DataSet` and `DataTab
 * The options available depend on the framework the app targets.
 
 > [!WARNING]
-> Removing all type restrictions can introduce a security hole inside the app. When using this mechanism, ensure the app does **not** use `DataSet` or `DataTable` to read untrusted input. For more information, see [CVE-2020-1147](https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2020-1147) and the following section titled [Safety with regard to untrusted input](#swr).
+> Removing all type restrictions can introduce a security hole inside the app. When using this mechanism, ensure the app does **not** use `DataSet` or `DataTable` to read untrusted input. For more information, see [CVE-2020-1147](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-1147) and the following section titled [Safety with regard to untrusted input](#swr).
 
 #### Through AppContext configuration (.NET Framework 4.6 - 4.8, .NET Core 2.1 and later, .NET 5.0 and later)
 

styleguide/voice-tone.md

@@ -1,3 +1,3 @@
 # Voice and tone recommendations
 
-This content has been moved to the [Contributor guide](https://docs.microsoft.com/contribute/dotnet-voice-tone).
+This content has been moved to the [Contributor guide](/contribute/dotnet-voice-tone).