Bulk - Fix validation issues (#1037)

* Bulk - Fix validation issues

* edits

* edits

iis/extensions/iis-search-engine-optimization-toolkit/managing-robotstxt-and-sitemap-files.md

@@ -127,7 +127,7 @@ Your Robots.txt file will look similar to the following:
 
 In addition to adding the sitemap location to the Robots.txt file, it is recommended that you submit your sitemap location URL to the major search engines. This will allow you to obtain useful status and statistics about your Web site from the search engine's webmasters tools.
 
-- To submit a sitemap to **bing.com,** use the [Bing Webmasters Tools](http://www.bing.com/webmaster)
+- To submit a sitemap to **bing.com,** use the [Bing Webmasters Tools](https://www.bing.com/webmaster)
 - To submit a sitemap to **google.com,** use the [Google Webmasters Tools](https://www.google.com/webmasters/)
 
 ## Summary

iis/extensions/installing-application-request-routing-arr/install-application-request-routing.md

@@ -39,10 +39,7 @@ This walkthrough requires the following prerequisites:
 
 ## Step 1 – Download Microsoft Application Request Routing Version 1
 
-Download the Microsoft Application Request Routing release from the following locations:
-
-- Microsoft Application Request Routing Version 1 for IIS 7 (x86) [here](https://iis-umbraco.azurewebsites.net/downloads).
-- Microsoft Application Request Routing Version 1 for IIS 7 (x64) [here](https://iis-umbraco.azurewebsites.net/downloads).
+Download the Microsoft Application Request Routing release.
 
 ## Step 2 – Install Microsoft Application Request Routing Version 1
 

iis/extensions/introduction-to-iis-express/iis-75-express-readme.md

@@ -30,7 +30,7 @@ You can install IIS 7.5 Express using Web Platform Installer, or through the [Mi
 
 ## Using IIS 7.5 Express
 
-You will most likely need an Integrated Development Environment to build web applications over IIS 7.5 Express. Microsoft WebMatrix provides a simple and integrated user experience for building both ASP.NET and PHP websites using IIS 7.5 Express. You can use IIS 7.5 Express with [Visual Studio 2010 SP1 Beta](https://www.microsoft.com/downloads/en/details.aspx?FamilyID=11ea69cb-cf12-4842-a3d7-b32a1e5642e2&displaylang=en) to build and test web applications instead of the built-in ASP.NET Development Web Server (also known as Cassini). It is also possible to [run IIS 7.5 Express using the command line.](../using-iis-express/running-iis-express-from-the-command-line.md)
+You will most likely need an Integrated Development Environment to build web applications over IIS 7.5 Express. Microsoft WebMatrix provides a simple and integrated user experience for building both ASP.NET and PHP websites using IIS 7.5 Express. You can use IIS 7.5 Express with Visual Studio 2010 SP1 Beta to build and test web applications instead of the built-in ASP.NET Development Web Server (also known as Cassini). It is also possible to [run IIS 7.5 Express using the command line.](../using-iis-express/running-iis-express-from-the-command-line.md)
 
 <a id="SupportedPlatforms"></a>
 

iis/extensions/planning-for-arr/using-the-application-request-routing-module.md

@@ -37,11 +37,6 @@ Microsoft Application Request Routing for IIS includes the following key feature
 - **Management and monitoring by using the UI** You can use IIS Manager to manage and view all configuration settings and aggregated runtime statistics for ARR.
 - **Failed request tracing rules** Specific traces have been added to quickly troubleshoot and diagnose ARR.
 
-## Getting the Module
-
-Download Microsoft Application Request Routing Version 2 for IIS 7 (x86) [here](https://iis-umbraco.azurewebsites.net/downloads).  
-Download Microsoft Application Request Routing Version 2 for IIS 7 (x64) [here](https://iis-umbraco.azurewebsites.net/downloads).
-
 ## Using the Module
 
 These articles explain how to configure and achieve the core scenarios by using ARR. It is recommended that you read the articles in the following order because the scenarios get richer with each article:

iis/extensions/url-rewrite-module/importing-apache-modrewrite-rules.md

@@ -96,7 +96,7 @@ Also, if you try either of these URLs:
 
 the Web browser gets redirected to `http://www_mysite_com:8088/iisstart.htm`.
 
-Note that the rules that were imported from mod\_rewrite enabled the enforcement of canonical host names for a Web site. A Bing search will reveal other [examples of Apache mod\_rewrite rules](http://search.live.com/results.aspx?q=mod_rewrite+examples).
+Note that the rules that were imported from mod\_rewrite enabled the enforcement of canonical host names for a Web site. A Bing search will reveal other examples of Apache mod\_rewrite rules.
 
 ## Disclaimer
 :::image type="icon" source="importing-apache-modrewrite-rules/_static/image1.gif"::: IMPORTANT - The URL Rewrite Module tries to convert Apache mod\_rewrite rules to functionally equivalent IIS URL rewrite rules. However, not all mod\_rewrite rules can be converted because of architectural differences between Apache and IIS. It is highly recommended that you study a mod\_rewrite rule set until you understand its functionality before you begin the conversion process. Then, after converting to IIS URL rewrite rules, review and test the result of the conversion to make sure that the corresponding IIS rewrite rule set provides the same URL rewriting logic.

iis/extensions/url-rewrite-module/url-rewrite-module-20-configuration-reference.md

@@ -198,7 +198,7 @@ When **filterByTags** attribute is not specified in the match element of the rul
 
 Rule pattern syntax can be specified by using the **patternSyntax** attribute of a rule. This attribute can be set to one of the following options:
 
-**ECMAScript** – Perl compatible ([ECMAScript](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf "ECMAScript Standard") standard compliant) regular expression syntax. This is a default option for any rule. This is an example of the pattern format: "^([\_0-9a-zA-Z-]+/)?(wp-.\*)"
+**ECMAScript** – Perl compatible (ECMAScript standard compliant) regular expression syntax. This is a default option for any rule. This is an example of the pattern format: "^([\_0-9a-zA-Z-]+/)?(wp-.\*)"
 
 **Wildcard** – [Wildcard](https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/41c238b2-1188-488f-bf2d-464383b1bb08.mspx?mfr=true "Wildcard syntax") syntax used in IIS HTTP redirection module. This is an example of pattern in this format: "/Scripts/\*.js", where asterisk ("\*") means "match any number of any characters and capture them in a back-reference". Note that wildcard pattern type cannot be used when rule does not have any tag filters.
 

iis/extensions/url-rewrite-module/url-rewrite-module-configuration-reference.md

@@ -115,7 +115,7 @@ A pattern is specified within a <match> element of a rewrite rule.
 
 Rule pattern syntax can be specified by using the **patternSyntax** attribute of a rule. This attribute can be set to one of the following options:
 
-**ECMAScript** – Perl compatible ([ECMAScript](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf "ECMAScript Standard") standard compliant) regular expression syntax. This is a default option for any rule. This is an example of the pattern format: "^([\_0-9a-zA-Z-]+/)?(wp-.\*)"
+**ECMAScript** – Perl compatible (ECMAScript standard compliant) regular expression syntax. This is a default option for any rule. This is an example of the pattern format: "^([\_0-9a-zA-Z-]+/)?(wp-.\*)"
 
 **Wildcard** – [Wildcard](https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/41c238b2-1188-488f-bf2d-464383b1bb08.mspx?mfr=true "Wildcard syntax") syntax used in IIS HTTP redirection module. The following is an example of a pattern in this format: "/Scripts/\*\_in.???", where asterisk ("\*") means "match any number of any characters and capture them in a back-reference" and "?" means match exactly one character (no back-reference is created).
 

iis/extensions/url-rewrite-module/using-custom-rewrite-providers-with-url-rewrite-module.md

@@ -160,7 +160,7 @@ The complete content of the web.config file should look similar to below:
 
 This rule aborts the HTTP connection if the user agent of the HTTP request matches any of the strings listed in disalloweduseragents.txt file. The FileContainsProvider instance named "FileContains" is invoked from the rule's condition and if the result returned from the provider is not empty then the HTTP connection is aborted.
 
-To test the rule open [WFetch](https://www.microsoft.com/downloads/details.aspx?FamilyID=b134a806-d50e-4664-8348-da5c17129210&displaylang=en) and add a user-agent header to the request as below:
+To test the rule open WFetch and add a user-agent header to the request as below:
 
 [!code-console[Main](using-custom-rewrite-providers-with-url-rewrite-module/samples/sample10.cmd)]
 

iis/extensions/url-rewrite-module/using-the-url-rewrite-module.md

@@ -28,7 +28,7 @@ The URL Rewrite module is available both as a download that you can install on y
 The Microsoft URL Rewrite module 2.0 includes the following key features:
 
 - **Rules-based URL rewriting engine**. Rewrite rules define the logic used to analyze request URLs and map them to rewite URLs when the request URL matches a defined rule. Web server and site administrators can use rewrite rule sets to define URL rewriting logic.
-- **Regular expression pattern matching**. Rewrite rules can use regular expression syntax for pattern matching as defined in [ECMA-262](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf).
+- **Regular expression pattern matching**. Rewrite rules can use regular expression syntax for pattern matching as defined in ECMA-262.
 - **Wildcard pattern matching.** Rewrite rules can use wildcard syntax for pattern matching.
 - **Global and distributed rewrite rules**. URL Rewrite uses global rules to define server-wide URL rewriting logic. These rules are defined within the applicationHost.config file, and they supercede rules configured at lower levels in the configuration hierarchy. The module also uses distributed rules to define URL rewrite logic specific to a particular configuration scope. This type of rule can be defined on any configuration level by using Web.config files.
 - **Access to server variables and HTTP headers**. Server variables and HTTP headers provide additional information about current HTTP requests. This information can be used to configure rewrite rules or to compose the output URL.

iis/extensions/using-iis-express/handling-url-binding-failures-in-iis-express.md

@@ -28,7 +28,7 @@ HTTP.sys is an operating system component that handles HTTP and SSL traffic for
 - Serving external traffic
 - Using SSL
 
-You can configure HTTP.sys to permit these operations for IIS Express. On Windows 7 and Windows Vista, you can configure HTTP.sys using the [netsh.exe](/windows/win32/http/netsh-commands-for-http) utility. On Windows XP, HTTP.sys can be configured using the [httpcfg.exe](/previous-versions/windows/it-pro/windows-server-2003/cc781601(v=ws.10)) command-line utility, which is included with [Windows XP Service Pack 2 Support Tools](https://www.microsoft.com/downloads/en/details.aspx?familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en).
+You can configure HTTP.sys to permit these operations for IIS Express. On Windows 7 and Windows Vista, you can configure HTTP.sys using the [netsh.exe](/windows/win32/http/netsh-commands-for-http) utility. On Windows XP, HTTP.sys can be configured using the [httpcfg.exe](/previous-versions/windows/it-pro/windows-server-2003/cc781601(v=ws.10)) command-line utility, which is included with Windows XP Service Pack 2 Support Tools.
 
 ## Using a Reserved Port
 

iis/extensions/working-with-urlscan/urlscan-2-reference.md

@@ -23,7 +23,7 @@ Microsoft later released UrlScan 2.5 as a separate download, which added request
 - [Installing UrlScan 2.x](urlscan-2-reference.md#InstallingUrlScan)
 
     - [Installing UrlScan 2.0 or UrlScan 2.1](urlscan-2-reference.md#Installing_UrlScan_2.0_or_UrlScan_2.1)
-    - [Installing UrlScan 2.5](urlscan-2-reference.md#Installing_UrlScan_2.5)
+    - [Installing UrlScan 2.5](/iis/extensions/working-with-urlscan/urlscan-2-reference#installing-urlscan-25)
 - [Using UrlScan 2.x](urlscan-2-reference.md#UsingUrlScan)
 - [UrlScan.ini Sections](urlscan-2-reference.md#UrlScanIniSections)
 
@@ -46,20 +46,13 @@ Microsoft later released UrlScan 2.5 as a separate download, which added request
 
 UrlScan 2.0 and UrlScan 2.1 are installed as part of the IIS Lockdown Tool.
 
-For more information about installing the IIS Lockdown Tool, see the IIS Lockdown Tool download pages at the following URL:
-
-> [https://www.microsoft.com/downloads/details.aspx?FamilyID=dde9efc0-bb30-47eb-9a61-fd755d23cdec](https://www.microsoft.com/downloads/details.aspx?FamilyID=dde9efc0-bb30-47eb-9a61-fd755d23cdec)
-
-<a id="Installing_UrlScan_2.5"></a>
-
 ### Installing UrlScan 2.5
 
 UrlScan 2.5 installs as a clean install on a computer running IIS 5.1 or later. Upgrade scenarios are also supported.
 
 **To Install UrlScan 2.5**
 
-1. Download the Setup.exe file for UrlScan 2.5 from the following URL to your computer:  
-    [https://www.microsoft.com/downloads/details.aspx?familyid=23d18937-dd7e-4613-9928-7f94ef1c902a](https://www.microsoft.com/downloads/details.aspx?familyid=23d18937-dd7e-4613-9928-7f94ef1c902a)
+1. Download the Setup.exe file for UrlScan 2.5.
 2. Double-click the Setup.exe icon to begin the installation process.
 3. Review the agreement in the UrlScan Installer Package End User Agreement and then click **Yes** to accept the agreement and continue. If you click **No**, the installer will close.
 4. When the installer completes, the following message is displayed: "UrlScan has been successfully installed." Click **OK** to close the installer.

iis/extensions/working-with-urlscan/urlscan-3-reference.md

@@ -26,10 +26,7 @@ UrlScan 3.1 installs as a clean install on a computer running IIS 5.1 or later.
 
 **To Install UrlScan 3.1**
 
-1. Download the setup MSI file for UrlScan 3.1 from one of the following URLs to your computer: 
-
-    - x86: [https://www.microsoft.com/downloads/details.aspx?FamilyID=ee41818f-3363-4e24-9940-321603531989](https://www.microsoft.com/downloads/details.aspx?FamilyID=ee41818f-3363-4e24-9940-321603531989)
-    - x64: [https://www.microsoft.com/downloads/details.aspx?FamilyID=361e5598-c1bd-46b8-b3e7-3980e8bdf0de](https://www.microsoft.com/downloads/details.aspx?FamilyID=361e5598-c1bd-46b8-b3e7-3980e8bdf0de)
+1. Download the setup MSI file for UrlScan 3.1.
 2. Double-click the MSI file to begin the installation process.
 3. Review the agreement in the UrlScan Installer Package End User Agreement and then click **Yes** to accept the agreement and continue. If you click **No**, the installer will close.
 4. When the installer completes, a dialog box stating that UrlScan has been successfully installed will be displayed. Click **Finish** to close the installer.

iis/extensions/working-with-urlscan/urlscan-faq.yml

@@ -60,7 +60,7 @@ sections:
       - question: |
           I have UrlScan v2.5 right now. What will happen if I install v3.1?
         answer: |
-          UrlScan v3.1 will overwrite the pre-existing UrlScan v2.5 filter in the inetsrv directory. It will leave your old UrlScan.ini file intact though and no changes will be needed for this .ini file to make it work with UrlScan v3.1. If you need to restore UrlScan v2.5 you will need to re-install it from [Microsoft Download Center](https://www.microsoft.com/downloads/details.aspx?familyid=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en).
+          UrlScan v3.1 will overwrite the pre-existing UrlScan v2.5 filter in the inetsrv directory. It will leave your old UrlScan.ini file intact though and no changes will be needed for this .ini file to make it work with UrlScan v3.1. If you need to restore UrlScan v2.5 you will need to re-install it.
           
       - question: |
           Has the log format for UrlScan changed?

iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8.md

@@ -25,7 +25,7 @@ IIS 7.0 and later have a new user interface from previous versions of IIS: the I
 **Why did it have to change?** Here are a few top reasons:
 
 - **IIS and ASP.NET work together**: IIS 6.0 users right-click on a web site, select "All Properties", and get a dialog with a number of tabs for different settings. With IIS 7.0 and above, IIS Manager needed to show configuration for new features like Output Caching, [Failed Request Tracing](../../troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis.md), and [Request Filtering](../../manage/configuring-security/use-request-filtering.md), as well as configuration for ASP.NET and relevant portions of the .NET Framework. The new functionality would have required many more of new tabs, an unacceptable option.
-- **Delegated Administration**: Moving our configuration from the metabase to the .NET configuration system means that users can, if permitted, set IIS configuration in web.config files. For example, configuration for an application [http://www.contoso.com/sales](http://www.contoso.com/sales) can be written to the root config file applicationHost.config, to the site [http://www.contoso.com/](http://www.contoso.com/) web.config file, or directly to the application's web.config file. The new IIS Manager has to: 1) allow an administrator to control the configuration permitted in web.config files, 2) show the administrator/user where configuration is being written. The older IIS Manager was not up to these challenges.
+- **Delegated Administration**: Moving our configuration from the metabase to the .NET configuration system means that users can, if permitted, set IIS configuration in web.config files. For example, configuration for an application ```http://www.contoso.com/sales``` can be written to the root config file applicationHost.config, to the site ```http://www.contoso.com/``` web.config file, or directly to the application's web.config file. The new IIS Manager has to: 1) allow an administrator to control the configuration permitted in web.config files, 2) show the administrator/user where configuration is being written. The older IIS Manager was not up to these challenges.
 - **Engineering Reasons**: Software has a shelf life. Time brings new technologies, new requirements, new conventions, and there comes a point where updating existing software becomes more labour intensive and costly that rebuilding the software. IIS Manager was approaching the end of its shelf life.
 
 **Anything else to know?** Once we decided to rewrite IIS Manager, we took the opportunity to improve in a number of key ways:

iis/get-started/whats-new-in-iis-10/new-features-introduced-in-iis-10.md

@@ -34,9 +34,9 @@ Get started with [IIS base images available on Docker Hub](https://hub.docker.co
 
 With the advent of Nano Server and Windows Containers, IIS now provides a better management story for all environments running (including those without a GUI).
 
-### Microsoft IIS Administration ([https://manage.iis.net](https://manage.iis.net))
+### Microsoft IIS Administration
 
-Microsoft IIS Administration is a REST API which allows you to configure and monitor your IIS instance, and it is an [open-source project that is under active development on GitHub](https://github.com/Microsoft/IIS.Administration). With this API users can take advantage of the new IIS Web Manager that is available at [https://manage.iis.net](https://manage.iis.net). This browser based application consumes the IIS Administration API to provide a familiar management experience. Microsoft IIS Administration supports IIS 7.5 and above.
+Microsoft IIS Administration is a REST API which allows you to configure and monitor your IIS instance, and it is an [open-source project that is under active development on GitHub](https://github.com/Microsoft/IIS.Administration).
 
 Learn more: [Microsoft IIS Administration Preview](https://blogs.iis.net/adminapi/microsoft-iis-administration-api-preview).
 

iis/get-started/whats-new-in-iis-7/changes-in-security-between-iis-60-and-iis-7-and-above.md

@@ -57,7 +57,7 @@ Support for legacy Passport authentication was built into IIS 5/6 and Windows Se
 
 In Windows Server 2008 and beyond, the legacy Passport binaries and integration with IIS were removed.
 
-The Passport service has since changed into Windows Live ID. While the new Live ID service certainly grew out of the legacy Passport service, there are major changes. One of the biggest changes is how a partner site integrates with Live ID. You can add Live ID authentication by using the publicly available [Windows Live ID Web Authentication SDK](https://www.microsoft.com/downloads/details.aspx?FamilyId=E565FC92-D5F6-4F5F-8713-4DD1C90DE19F&displaylang=en). While the Windows Live ID service also supports identity Federation and ADFS, that capability is new functionality for specific cases, and is not a replacement for "Passport".
+The Passport service has since changed into Windows Live ID. While the new Live ID service certainly grew out of the legacy Passport service, there are major changes. One of the biggest changes is how a partner site integrates with Live ID. You can add Live ID authentication by using the publicly available Windows Live ID Web Authentication SDK. While the Windows Live ID service also supports identity Federation and ADFS, that capability is new functionality for specific cases, and is not a replacement for "Passport".
 
 ### Forms authentication