fixing warnings and suggestions

Author: eross-msft

EssentialsDocs/install/Hosted-Windows-Server-Essentials.md

@@ -23,7 +23,7 @@ This document includes information that is specific to hosters who intend to dep
 ## What is Windows Server Essentials?  
  Windows Server Essentials is a cross-premises small business solution, which incorporates best-of-breed, 64-bit product technologies to deliver a server environment well suited for the vast majority of small businesses. The following technologies are included in Windows Server Essentials.  
 
- **Server Operating System:** Windows Server 2012 product technologies provide the core of Windows Server Essentials. For more information, visit the [Windows Server 2012 website](https://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspx#fbid=ZH0GD_CRAWh).  
+ **Server Operating System:** Windows Server 2012 product technologies provide the core of Windows Server Essentials. For more information, visit the [Windows Server 2012 website](https://www.microsoft.com/server-cloud/products/windows-server-2012-r2/default.aspx#fbid=ZH0GD_CRAWh).  
 
  **Data Protection:** Windows Server Essentials leverages several new features available in Windows Server 2012 to provide greatly improved data protection capabilities. The [new Storage Spaces feature](https://technet.microsoft.com/library/hh831739.aspx) allows you to aggregate the physical storage capacity of disparate hard drives, dynamically add hard drives, and create data volumes with specified levels of resilience. Windows Server Essentials can perform complete system backups and bare-metal restores of the server itself as well as the client computers connected to the network ?now with support for volumes larger than 2 TB. New with Windows Server 2012, the [Windows Azure Online Backup](https://technet.microsoft.com/library/hh831419.aspx) can be used to protect files and folders in a cloud-based storage service that is managed by Microsoft. Windows Server Essentials also centrally manages and configures the File History feature of Windows 8.1 clients, helping users to recover from accidentally deleted or overwritten files without requiring administrator assistance.  
 

EssentialsDocs/migrate/Prepare-your-Source-Server-for-Windows-Server-Essentials-migration.md

@@ -84,7 +84,7 @@ Complete the following preliminary steps to ensure that the settings and data on
 
 ###### To use the Windows Server Solutions BPA to analyze your Source Server  
 
-1. Download and install the [Windows Server Solutions Best Practices Analyzer](https://www.microsoft.com/en-us/download/details.aspx?id=15556) at the Microsoft Download Center.  
+1. Download and install the [Windows Server Solutions Best Practices Analyzer](https://www.microsoft.com/download/details.aspx?id=15556) at the Microsoft Download Center.  
 
 2. After the download is complete, click **Start**, point to **All Programs**, and then click **SBS Best Practices Analyzer Tool**.  
 

ThirdPartyNotices

@@ -9,7 +9,7 @@ may be either trademarks or registered trademarks of Microsoft in the United Sta
 The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
 Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.
 
-Privacy information can be found at https://privacy.microsoft.com/en-us/
+Privacy information can be found at https://privacy.microsoft.com
 
 Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents,
 or trademarks, whether by implication, estoppel or otherwise.

WindowsServerDocs/Windows-Server-2016.md

@@ -97,7 +97,7 @@ Windows Server 2016 is available in Standard, Datacenter, and Essentials edition
 |Shielded Virtual Machines| yes| no|
 |Software Defined Networking Infrastructure (Network Controller, Software Load Balancer, and Multi-tenant Gateway)| yes| no|
 
-For more information, see [Pricing and licensing for Windows Server 2016](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing) and [Compare features in Windows Server versions](https://www.microsoft.com/en-us/cloud-platform/windows-server-comparison).
+For more information, see [Pricing and licensing for Windows Server 2016](https://www.microsoft.com/cloud-platform/windows-server-pricing) and [Compare features in Windows Server versions](https://www.microsoft.com/cloud-platform/windows-server-comparison).
 
 ## Installation options
 

WindowsServerDocs/administration/Linux-Package-Repository-for-Microsoft-Software.md

@@ -21,7 +21,7 @@ Microsoft's Linux Software Repository is comprised of multiple sub-repositories:
 
  - prod – The Production sub-repository is designated for packages intended for use in production. These packages are commercially supported by Microsoft under the terms of the applicable support agreement or program that you have with Microsoft.
 
- - mssql-server - These repositories contain packages for Microsoft SQL Server on Linux - See also: [SQL Server on Linux](https://www.microsoft.com/en-us/sql-server/sql-server-vnext-including-Linux).
+ - mssql-server - These repositories contain packages for Microsoft SQL Server on Linux - See also: [SQL Server on Linux](https://www.microsoft.com/sql-server/sql-server-vnext-including-Linux).
 
 > [!Note]
 > Packages in the Linux software repositories are subject to the license terms located in the packages. Please read the license terms prior to using the package. Your installation and use of the package constitutes your acceptance of these terms. If you do not agree with the license terms, do not use the package.

WindowsServerDocs/administration/performance-tuning/additional-resources.md

@@ -20,15 +20,15 @@ Use the links in this topic to learn more about the concepts that were discussed
 
 -   [Transaction Processing Performance Council](http://www.tpc.org/)
 
--   [Windows Assessment and Deployment Kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit)
+-   [Windows Assessment and Deployment Kit](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
 
 ## Power Management Tuning Resources
 
 -   [Power Policy Configuration and Deployment in Windows](https://msdn.microsoft.com/library/windows/hardware/mt422910.aspx)
 
 -   [Using PowerCfg to Evaluate System Energy Efficiency](https://technet.microsoft.com/library/cc748940.aspx)
 
--   [Interrupt-Affinity Policy Tool](https://support.microsoft.com/en-us/kb/252867)
+-   [Interrupt-Affinity Policy Tool](https://support.microsoft.com/kb/252867)
 
 ## Networking Subsystem Tuning Resources
 

WindowsServerDocs/administration/performance-tuning/role/active-directory-server/capacity-planning-for-active-directory-domain-services.md

@@ -255,8 +255,8 @@ The only recommendation for consideration is to ensure that 110% of the NTDS.dit
 
 The first and most important consideration is evaluating how large the NTDS.dit and SYSVOL will be. These measurements will lead into sizing both fixed disk and RAM allocation. Due to the (relatively) low cost of these components, the math does not need to be rigorous and precise. Content about how to evaluate this for both existing and new environments can be found in the [Data Storage](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc961771(v=technet.10)) series of articles. Specifically, refer to the following articles:
 
-- **For existing environments –** The section titled “To activate logging of disk space that is freed by defragmentation” in the article [Storage Limits](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc961769(v=technet.10)).
-- **For new environments –** The article titled [Growth Estimates for Active Directory Users and Organizational Units](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc961779(v=technet.10)).
+- **For existing environments –** The section titled “To activate logging of disk space that is freed by defragmentation” in the article [Storage Limits](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc961769(v=technet.10)).
+- **For new environments –** The article titled [Growth Estimates for Active Directory Users and Organizational Units](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc961779(v=technet.10)).
 
   > [!NOTE]
   > The articles are based on data size estimates made at the time of the release of Active Directory in Windows 2000. Use object sizes that reflect the actual size of objects in your environment.
@@ -407,7 +407,7 @@ Unfortunately, due to the huge variability of client applications that leverage
 
 As mentioned previously, when planning capacity for an entire site, the goal is to target a design with an *N* + 1 capacity design, such that failure of one system during the peak period will allow for continuation of service at a reasonable level of quality. That means that in an “*N*” scenario, load across all the boxes should be less than 100% (better yet, less than 80%) during the peak periods.
 
-Additionally, if the applications and clients in the site are using best practices for locating domain controllers (that is, using the [DsGetDcName function](http://msdn.microsoft.com/en-us/library/windows/desktop/ms675983(v=vs.85).aspx)), the clients should be relatively evenly distributed with minor transient spikes due to any number of factors.
+Additionally, if the applications and clients in the site are using best practices for locating domain controllers (that is, using the [DsGetDcName function](http://msdn.microsoft.com/library/windows/desktop/ms675983(v=vs.85).aspx)), the clients should be relatively evenly distributed with minor transient spikes due to any number of factors.
 
 In the next example, the following assumptions are made:
 
@@ -456,7 +456,7 @@ At maximum load, lsass consumes about 485% of one CPU, or 4.85 CPUs running at 1
 
 ### When to tune LDAP weights
 
-There are several scenarios where tuning [LdapSrvWeight](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc957291(v=technet.10)) should be considered. Within the context of capacity planning, this would be done when the application or user loads are not evenly balanced, or the underlying systems are not evenly balanced in terms of capability. Reasons to do so beyond capacity planning are outside of the scope of this article.
+There are several scenarios where tuning [LdapSrvWeight](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc957291(v=technet.10)) should be considered. Within the context of capacity planning, this would be done when the application or user loads are not evenly balanced, or the underlying systems are not evenly balanced in terms of capability. Reasons to do so beyond capacity planning are outside of the scope of this article.
 
 There are two common reasons to tune LDAP Weights:
 
@@ -643,9 +643,9 @@ Returning to the driving analogy used earlier in this section:
 This is why the long term averages for capacity conservatively estimated at 40% allows for head room for abnormal spikes in load, whether said spikes transitory (such as poorly coded queries that run for a few minutes) or abnormal bursts in general load (the morning of the first day after a long weekend).
 
 The above statement regards % Processor Time calculation being the same as the Utilization Law is a bit of a simplification for the ease of the general reader. For those more mathematically rigorous:  
-- Translating the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ms901169(v=msdn.10))
-  - *B* = The number of 100-ns intervals “Idle” thread spends on the logical processor. The change in the “*X*” variable in the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ms901169(v=msdn.10)) calculation
-  - *T* = the total number of 100-ns intervals in a given time range. The change in the “*Y*” variable in the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ms901169(v=msdn.10)) calculation.
+- Translating the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/previous-versions/windows/embedded/ms901169(v=msdn.10))
+  - *B* = The number of 100-ns intervals “Idle” thread spends on the logical processor. The change in the “*X*” variable in the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/previous-versions/windows/embedded/ms901169(v=msdn.10)) calculation
+  - *T* = the total number of 100-ns intervals in a given time range. The change in the “*Y*” variable in the [PERF_100NSEC_TIMER_INV](https://docs.microsoft.com/previous-versions/windows/embedded/ms901169(v=msdn.10)) calculation.
   - *U* k = The utilization percentage of the logical processor by the “Idle Thread” or % Idle Time.  
 - Working out the math:
   - *U* k = 1 – %Processor Time

WindowsServerDocs/administration/software-inventory-logging/manage-software-inventory-logging.md

@@ -25,20 +25,20 @@ The Software Inventory Logging feature can also be added to two versions of Wind
 - **Windows Server 2012 (Standard or Datacenter Edition)** 
 
 > [!NOTE] 
-> Make sure you have [WMF 4.0](https://www.microsoft.com/en-us/download/details.aspx?id=40855) installed before applying the update package below.
+> Make sure you have [WMF 4.0](https://www.microsoft.com/download/details.aspx?id=40855) installed before applying the update package below.
 
--  WMF 4.0 Update package for Windows Server 2012: [KB 3119938](https://support.microsoft.com/en-us/kb/3119938)
+-  WMF 4.0 Update package for Windows Server 2012: [KB 3119938](https://support.microsoft.com/kb/3119938)
 
 - **Windows Server 2008 R2 SP1**
 
 > [!NOTE] 
-> Make sure you have [WMF 4.0](https://www.microsoft.com/en-us/download/details.aspx?id=40855) installed before applying the update package below.
+> Make sure you have [WMF 4.0](https://www.microsoft.com/download/details.aspx?id=40855) installed before applying the update package below.
 
 
-- Requires [.NET Framework 4.5](https://www.microsoft.com/en-us/download/details.aspx?id=30653)
+- Requires [.NET Framework 4.5](https://www.microsoft.com/download/details.aspx?id=30653)
 
 
-- WMF 4.0 Update package for Windows Server 2008 R2: [KB 3109118](https://support.microsoft.com/en-us/kb/3109118)
+- WMF 4.0 Update package for Windows Server 2008 R2: [KB 3109118](https://support.microsoft.com/kb/3109118)
 
 
 There are two primary methods for inventorying using this feature:  

WindowsServerDocs/administration/software-inventory-logging/software-inventory-logging-aggregator.md

@@ -21,7 +21,7 @@ ms.date: 10/16/2017
 ## What is Software Inventory Logging Aggregator?
 Software Inventory Logging Aggregator (SILA) receives, aggregates, and produces basic reports of the number and types of Microsoft enterprise software installed on Windows Servers in a data center.
 
-SILA is software that you install on Windows Server, but is not included in the Windows Server installation. To install the software, first download it for free from the Windows Download Center: [Software Inventory Logging Aggregator 1.0 for Windows Server](https://www.microsoft.com/en-us/download/details.aspx?id=49046)
+SILA is software that you install on Windows Server, but is not included in the Windows Server installation. To install the software, first download it for free from the Windows Download Center: [Software Inventory Logging Aggregator 1.0 for Windows Server](https://www.microsoft.com/download/details.aspx?id=49046)
 
 The Software Inventory Logging framework is intended to reduce the operational costs of inventorying Microsoft software deployed across many servers in an IT environment. This framework consists of two components, this SIL Aggregator, and the Windows Server feature, introduced in Windows Server 2012 R2, Software Inventory Logging (SIL). This Software Inventory Logging Aggregator 1.0 will install on one server and receive inventory data from any Windows Server configured to forward data to it via SIL. The design allows data center administrators to enable SIL in master Windows Server images intended for wide distribution across their environment.  This software package is the target point and intended for customers to install on their premises for easy logging of inventory data over time. This software also allows for periodic creation of basic inventory reports in Microsoft Excel. Software Inventory Logging Aggregator 1.0 reports include counts of installations of Windows Server, System Center, and SQL Server.
 
@@ -588,7 +588,7 @@ When you want to start inventorying servers in your environment with a different
 -   While it is possible to add Windows Server 2008 R2 and Windows Server 2012 hosts to the polling host list, this version (1.0) of SIL Aggregator only supports polling Windows Server 2012 R2, for Windows/Hyper-V based hosts, to have success with all features and functionality.  In particular, it is known that when polling Windows Server 2008 R2 hosts, virtual machines and hosts may not match up in the SIL Aggregator reports.
 
 ## See Also
-[Software Inventory Logging Aggregator 1.0 for Windows Server](https://www.microsoft.com/en-us/download/details.aspx?id=49046)<br>
+[Software Inventory Logging Aggregator 1.0 for Windows Server](https://www.microsoft.com/download/details.aspx?id=49046)<br>
 [SIL Aggregator PowerShell cmdlets](https://technet.microsoft.com/library/mt548455.aspx)<br>
 [SIL PowerShell cmdlets](https://technet.microsoft.com/library/dn283390.aspx)<br>
 [An Overview of SIL](https://technet.microsoft.com/library/dn268301.aspx)<br>

WindowsServerDocs/administration/windows-commands/cleanmgr.md

@@ -83,4 +83,4 @@ cleanmgr /tuneup:1
 
 ## Additional references
 
-[Free up drive space in Windows 10](https://support.microsoft.com/en-us/help/12425/windows-10-free-up-drive-space)
+[Free up drive space in Windows 10](https://support.microsoft.com/help/12425/windows-10-free-up-drive-space)

WindowsServerDocs/administration/windows-server-update-services/deploy/express-update-delivery-isv-support.md

@@ -47,7 +47,7 @@ ISVs can use WSUS and the WU client to support Express update delivery. Microsof
 3.  [**Set up an ISV client agent to direct WU client operations**](#BKMK_3)
 
 >[!NOTE]
->Requires Cumulative Update for Windows 10 Version 1607 release in (or after) January 2017 ([KB3213986 (OS Build 14393.693)](https://support.microsoft.com/en-us/help/4009938/january-10-2017-kb3213986-os-build-14393-693) to be installed.
+>Requires Cumulative Update for Windows 10 Version 1607 release in (or after) January 2017 ([KB3213986 (OS Build 14393.693)](https://support.microsoft.com/help/4009938/january-10-2017-kb3213986-os-build-14393-693) to be installed.
     
    - The ISV client agent determines which updates to approve, and when do download and install updates
    - The WU client determines byte ranges to download and initiates the download request

WindowsServerDocs/administration/windows-server-update-services/manage/wid-to-sql-migration.md

@@ -156,7 +156,7 @@ The **NT AUTHORITY\NETWORK SERVICE** account should be listed.
 ### Edit the registry to point WSUS to the SQL Server Instance
 
 > [!IMPORTANT]
-> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/en-us/help/322756) in case problems occur.
+> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur.
 
 1. Click **Start**, click **Run**, type **regedit**, and then click **OK**.
 2. Locate the following key: **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName**