Fixing unnecessary en-us from links using batch update model

Author: VesaJuvonen

README.md

@@ -65,27 +65,27 @@ You can also tweet / follow [@officedev](https://twitter.com/officedev) or [@off
 
 ## Get Started
 
-* [Setup your Office 365 Developer Tenant](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-developer-tenant)
-* [Setup your Machine](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment)
-* [Go build your first web part](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part)
+* [Setup your Office 365 Developer Tenant](https://docs.microsoft.com/sharepoint/dev/spfx/set-up-your-developer-tenant)
+* [Setup your Machine](https://docs.microsoft.com/sharepoint/dev/spfx/set-up-your-development-environment)
+* [Go build your first web part](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part)
 
 ## Reference
-* [sp-application-base](https://docs.microsoft.com/en-us/javascript/api/sp-application-base)
-* [sp-component-base](https://docs.microsoft.com/en-us/javascript/api/sp-component-base)
-* [sp-core-library](https://docs.microsoft.com/en-us/javascript/api/sp-core-library)
-* [sp-dialog](https://docs.microsoft.com/en-us/javascript/api/sp-dialog)
-* [sp-extension-base](https://docs.microsoft.com/en-us/javascript/api/sp-extension-base)
-* [sp-http](https://docs.microsoft.com/en-us/javascript/api/sp-http)
-* [sp-listview-extensibility](https://docs.microsoft.com/en-us/javascript/api/sp-listview-extensibility)
-* [sp-odata-types](https://docs.microsoft.com/en-us/javascript/api/sp-odata-types)
-* [sp-page-context](https://docs.microsoft.com/en-us/javascript/api/sp-page-context)
-* [sp-webpart-base](https://docs.microsoft.com/en-us/javascript/api/sp-webpart-base)
+* [sp-application-base](https://docs.microsoft.com/javascript/api/sp-application-base)
+* [sp-component-base](https://docs.microsoft.com/javascript/api/sp-component-base)
+* [sp-core-library](https://docs.microsoft.com/javascript/api/sp-core-library)
+* [sp-dialog](https://docs.microsoft.com/javascript/api/sp-dialog)
+* [sp-extension-base](https://docs.microsoft.com/javascript/api/sp-extension-base)
+* [sp-http](https://docs.microsoft.com/javascript/api/sp-http)
+* [sp-listview-extensibility](https://docs.microsoft.com/javascript/api/sp-listview-extensibility)
+* [sp-odata-types](https://docs.microsoft.com/javascript/api/sp-odata-types)
+* [sp-page-context](https://docs.microsoft.com/javascript/api/sp-page-context)
+* [sp-webpart-base](https://docs.microsoft.com/javascript/api/sp-webpart-base)
 
 ## Learn More
 
-* [Background and Philosophy](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview)
-* [Design Great Web Parts](https://docs.microsoft.com/en-us/sharepoint/dev/design/design-guidance-overview)
-* [API Docs](https://docs.microsoft.com/en-us/javascript/api/sp-application-base)
+* [Background and Philosophy](https://docs.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
+* [Design Great Web Parts](https://docs.microsoft.com/sharepoint/dev/design/design-guidance-overview)
+* [API Docs](https://docs.microsoft.com/javascript/api/sp-application-base)
 
 ## Updates & Feedback
 

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 http://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.

docs/apis/alm-api-for-spfx-add-ins.md

@@ -28,7 +28,7 @@ ALM APIs can be used to perform exactly the same operations that are available f
 ALM APIs are natively provided by using REST APIs, but there are additional CSOM extensions, PowerShell cmdlets, and the cross-platform Office 365 CLI available through SharePoint PnP Community channels.
 
 > [!IMPORTANT]
-> Tenant-scoped permissions which require [tenant administrative approval](https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/how-to-provide-add-in-app-only-tenant-administrative-permissions-in-sharepoint-online) are not supported with the ALM APIs.
+> Tenant-scoped permissions which require [tenant administrative approval](https://docs.microsoft.com/sharepoint/dev/solution-guidance/how-to-provide-add-in-app-only-tenant-administrative-permissions-in-sharepoint-online) are not supported with the ALM APIs.
 
 ## REST API
 
@@ -243,7 +243,7 @@ POST /_api/web/tenantappcatalog/SyncSolutionToTeams(id=xxxxx)
 
 ## SharePoint PnP PowerShell cmdlets 
 
-By using [PnP PowerShell](https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps), you can automate deploying, publishing, installing, upgrading, and retracting your apps. 
+By using [PnP PowerShell](https://docs.microsoft.com/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps), you can automate deploying, publishing, installing, upgrading, and retracting your apps. 
 
 > [!NOTE]
 > Support for scope option was released on the April 2018 release of PnP PowerShell.

docs/apis/export-amr-api.md

@@ -28,7 +28,7 @@ This document targets ISVs and any third-party vendors/developers who are develo
 
 
 ### Background:
-Currently, the SharePoint Online Migration API, [CreateMigrationJob](https://docs.microsoft.com/en-us/sharepoint/dev/apis/migration-api-overview), lets your migration tool efficiently migrate large amounts data to SharePoint Online. However, the lack of an official API to read content from SharePoint Online means that these tools must rely on CSOM function calls to perform individual metadata read operations.
+Currently, the SharePoint Online Migration API, [CreateMigrationJob](https://docs.microsoft.com/sharepoint/dev/apis/migration-api-overview), lets your migration tool efficiently migrate large amounts data to SharePoint Online. However, the lack of an official API to read content from SharePoint Online means that these tools must rely on CSOM function calls to perform individual metadata read operations.
 
 </br>
 Large numbers of CSOM calls increase the likelihood of throttling which impacts migration performance and customer experience. Ineffective CSOM usage results in large SQL round trip per function calls that can potentially bring down the database and impact its reliability.
@@ -130,7 +130,7 @@ If an invalid value is detected, other than NULL, an error will be generated, an
 
 This is an optional parameter. If it is specified, the AES256CBCKey is used to encrypt output files and queue messages. Otherwise, there is no encryption. 
 
-For more information, see [EncryptionOption Class](https://docs.microsoft.com/en-us/dotnet/api/microsoft.sharepoint.client.encryptionoption).
+For more information, see [EncryptionOption Class](https://docs.microsoft.com/dotnet/api/microsoft.sharepoint.client.encryptionoption).
 
 
 #### azureContainerManifestUri
@@ -204,7 +204,7 @@ It returns the AES256CBC encryption key used to decrypt the message in azureMani
 |EncryptionKey|AES256CBC encryption key used to decrypt messages from job/manifest queue|
 
 ## Set up Guidelines
-The following provides high level guidelines for implementing the asynchronous metadata migration function. This documentation does not go into details on how to interact with SharePoint RESTful service. It is assumed that the ISV has prior knowledge and will be able to access the target website with proper permission. </br>,</br>For more information on how to access the SharePoint website, refer to [Get to Know the SharePoint Rest Service](https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/get-to-know-the-sharepoint-rest-service).
+The following provides high level guidelines for implementing the asynchronous metadata migration function. This documentation does not go into details on how to interact with SharePoint RESTful service. It is assumed that the ISV has prior knowledge and will be able to access the target website with proper permission. </br>,</br>For more information on how to access the SharePoint website, refer to [Get to Know the SharePoint Rest Service](https://docs.microsoft.com/sharepoint/dev/sp-add-ins/get-to-know-the-sharepoint-rest-service).
 
 1. Install and update the latest Microsoft.SharePointOnline.CSOM version. The minimum version requirement is V16.1.9119.1200 or later.
 2. ISVs figure out the folder, document library or files of interested to be query and issued with CreateSPAsyncReadJob function. 

docs/apis/migrate-webparts-with-migrationapi.md

@@ -35,15 +35,15 @@ To get the Serializer .dll, perform following steps:
 
 For a complete list of the supported web parts, see:
 
-- [SPMT & Migration API supported SharePoint web parts](https://docs.microsoft.com/en-us/sharepointmigration/spmt-supported-webparts)
+- [SPMT & Migration API supported SharePoint web parts](https://docs.microsoft.com/sharepointmigration/spmt-supported-webparts)
 
 
 
 ## Schema:
 
 For an explanation of the **SPWebPart** fields see:
 
-- [SPWebPart](https://docs.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-primepf/25cfceeb-7769-4331-9936-ce3b9ced87ad)
+- [SPWebPart](https://docs.microsoft.com/openspecs/sharepoint_protocols/ms-primepf/25cfceeb-7769-4331-9936-ce3b9ced87ad)
 
 
 
@@ -200,7 +200,7 @@ Here is the list of web parts that will be ignored by server-side code (treated
 *Question:*  How to fetch the web part connection info as the input for serialization API?
 *Answer:*    The web part connections could be found in <SPWebPartConnection> elements from the web part page in the response of operation ‘GetWebPartPage’ in ‘WebPartPagesWebService’.
 
-View flags: refer to this https://docs.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-wssfob/252d2086-6571-430f-863d-bcaf9d267e62, for example, all the view flags https://docs.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-wssfob/16a9d8ca-185d-40ec-956e-bb6bf3488cf7. You will need to convert all flag values to PRIME element ‘flags’.
+View flags: refer to this https://docs.microsoft.com/openspecs/sharepoint_protocols/ms-wssfob/252d2086-6571-430f-863d-bcaf9d267e62, for example, all the view flags https://docs.microsoft.com/openspecs/sharepoint_protocols/ms-wssfob/16a9d8ca-185d-40ec-956e-bb6bf3488cf7. You will need to convert all flag values to PRIME element ‘flags’.
 
 ## Appendix