Merged PR 18404: fixing 127 links with LCID in them

fixing 127 links with LCID in them

Author: Steven White

windows.applicationmodel.activation/splashscreen.md

@@ -91,4 +91,4 @@ You can use the object passed to your activated event handler to get information
 
 ## -see-also
 
-[Windows.ApplicationModel.Activation classes](windows_applicationmodel_activation_classes.md), [Splash screen sample](https://github.com/microsoft/Windows-universal-samples/tree/master/Samples/SplashScreen), [App activate and suspend using WinJS sample](https://github.com/microsoftarchive/msdn-code-gallery-microsoft/tree/master/Official%20Windows%20Platform%20Sample/Windows%208.1%20Store%20app%20samples/99866-Windows%208.1%20Store%20app%20samples/App%20activate%20and%20suspend%20using%20WinJS%20sample/JavaScript), [App activated, resume, and suspend using the WRL sample](/samples/browse/), [Splash screens](/en-us/windows/uwp/launch-resume/splash-screens), [Add a splash screen](/windows/uwp/launch-resume/add-a-splash-screen), [App lifecycle](/windows/uwp/launch-resume/app-lifecycle), [Display a splash screen for more time](/windows/uwp/launch-resume/create-a-customized-splash-screen), [Splash screen sample (Windows 10)](https://go.microsoft.com/fwlink/p/?LinkId=620608), [How to extend the splash screen](/previous-versions/windows/apps/hh700390(v=win.10))
+[Windows.ApplicationModel.Activation classes](windows_applicationmodel_activation_classes.md), [Splash screen sample](https://github.com/microsoft/Windows-universal-samples/tree/master/Samples/SplashScreen), [App activate and suspend using WinJS sample](https://github.com/microsoftarchive/msdn-code-gallery-microsoft/tree/master/Official%20Windows%20Platform%20Sample/Windows%208.1%20Store%20app%20samples/99866-Windows%208.1%20Store%20app%20samples/App%20activate%20and%20suspend%20using%20WinJS%20sample/JavaScript), [App activated, resume, and suspend using the WRL sample](/samples/browse/), [Splash screens](/windows/uwp/launch-resume/splash-screens), [Add a splash screen](/windows/uwp/launch-resume/add-a-splash-screen), [App lifecycle](/windows/uwp/launch-resume/app-lifecycle), [Display a splash screen for more time](/windows/uwp/launch-resume/create-a-customized-splash-screen), [Splash screen sample (Windows 10)](https://go.microsoft.com/fwlink/p/?LinkId=620608), [How to extend the splash screen](/previous-versions/windows/apps/hh700390(v=win.10))

windows.applicationmodel.appservice/appserviceconnection_requestreceived.md

@@ -17,7 +17,7 @@ Occurs when a message arrives from the other endpoint of the app service connect
 
 ## -examples
 
-See the code examples in [Create and consume an app service](/en-us/windows/uwp/launch-resume/how-to-create-and-consume-an-app-service).
+See the code examples in [Create and consume an app service](/windows/uwp/launch-resume/how-to-create-and-consume-an-app-service).
 
 ## -see-also
-[AppServiceRequestReceivedEventArgs](appservicerequestreceivedeventargs.md), [TypedEventHandler](../windows.foundation/typedeventhandler_2.md), [Create and consume an app service](/en-us/windows/uwp/launch-resume/how-to-create-and-consume-an-app-service)
+[AppServiceRequestReceivedEventArgs](appservicerequestreceivedeventargs.md), [TypedEventHandler](../windows.foundation/typedeventhandler_2.md), [Create and consume an app service](/windows/uwp/launch-resume/how-to-create-and-consume-an-app-service)

windows.applicationmodel.contacts/pinnedcontactmanager_getdefault_846721868.md

@@ -22,7 +22,7 @@ the default [PinnedContactManager](pinnedcontactmanager.md).
 
 This method must be called from the main UI thread.
 
-To use this object from a desktop app, use [the IInitializeWithWindow::Initialize method](/en-us/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
+To use this object from a desktop app, use [the IInitializeWithWindow::Initialize method](/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
 
 ## -see-also
 

windows.applicationmodel.payments/paymentmediator_paymentmediator_1221375020.md

@@ -13,7 +13,7 @@ public PaymentMediator()
 Creates a new [PaymentMediator](paymentmediator.md) object.
 
 ## -remarks
-To use this object from a desktop app, create the object, and then use [the IInitializeWithWindow::Initialize method](/en-us/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
+To use this object from a desktop app, create the object, and then use [the IInitializeWithWindow::Initialize method](/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
 
 ## -examples
 

windows.devices.enumeration/devicepicker_devicepicker_1221375020.md

@@ -14,7 +14,7 @@ public DevicePicker()
 Creates a [DevicePicker](devicepicker.md) object.
 
 ## -remarks
-To use this object from a desktop app, create the object, and then use [the IInitializeWithWindow::Initialize method](/en-us/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
+To use this object from a desktop app, create the object, and then use [the IInitializeWithWindow::Initialize method](/windows/desktop/api/shobjidl_core/nf-shobjidl_core-iinitializewithwindow-initialize) to associate the object with a window handle.
 
 ## -examples
 

windows.devices.humaninterfacedevice/windows_devices_humaninterfacedevice.md

@@ -106,13 +106,13 @@ In the following joystick and game pad data there is no **Vendor Id** and **Prod
 + Verify the user has granted permission for the application to utilize HIDs.
 + Verify the device type is not one designated as inaccessible.
   + Inaccessible HIDs may still be enumerated by [DeviceInformation.FindAllAsync()](../windows.devices.enumeration/deviceinformation_findallasync_1257462890.md), but cannot be opened by [HumanInterfaceDevice.FromIdAsync()](hiddevice_fromidasync_1634380010.md).  Attemping to open such a device will either throw an exception or return `null`.
-+ Machine-internal devices (`DEVPKEY_Device_InLocalMachineContainer == TRUE`) are generally *not* accessible unless running on a SKU with [embedded mode](/en-us/windows/iot-core/develop-your-app/EmbeddedMode) and `lowLevelDevices` capability.
-+ Devices with stacks that contain upper/lower filter drivers are generally *not* accessible.  These are sometimes added by 3rd parties to enable additional functionality for [custom hardware](/en-us/windows-hardware/drivers/install/inf-addreg-directive).
-  + Device restriction is partially determined by `hidclass.sys` during device enumeration, which may set the device interface property `DEVPKEY_DeviceInterface_Restricted` to `TRUE` on the HID Device Interface [`GUID_DEVINTERFACE_HID`](/en-us/windows-hardware/drivers/install/guid-devinterface-hid) based on the presence of device/class filters.
-  + The presence of device [UpperFilter](/en-us/windows-hardware/drivers/install/devpkey-device-upperfilters)/[LowerFilter](/en-us/windows-hardware/drivers/install/devpkey-device-lowerfilters) drivers can be determined using DeviceManager by looking for `UpperFilters` and `LowerFilters` properties.
-  + The presence of HID class [UpperFilter](/en-us/windows-hardware/drivers/install/devpkey-deviceclass-upperfilters)/[LowerFilter](/en-us/windows-hardware/drivers/install/devpkey-deviceclass-lowerfilters) drivers can be determined using DeviceManager by looking for `Class upper filters` and `Class lower filters` properties.
-  + Device Interface properties can be inspected by calling [`CM_Get_Device_Interface_Property`](/en-us/windows/win32/api/cfgmgr32/nf-cfgmgr32-cm_get_device_interface_propertyw) where `pszDeviceInterface` is the same string as would be passed to [FromIdAsync](hiddevice_fromidasync_1634380010.md).
-+ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/en-us/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
++ Machine-internal devices (`DEVPKEY_Device_InLocalMachineContainer == TRUE`) are generally *not* accessible unless running on a SKU with [embedded mode](/windows/iot-core/develop-your-app/EmbeddedMode) and `lowLevelDevices` capability.
++ Devices with stacks that contain upper/lower filter drivers are generally *not* accessible.  These are sometimes added by 3rd parties to enable additional functionality for [custom hardware](/windows-hardware/drivers/install/inf-addreg-directive).
+  + Device restriction is partially determined by `hidclass.sys` during device enumeration, which may set the device interface property `DEVPKEY_DeviceInterface_Restricted` to `TRUE` on the HID Device Interface [`GUID_DEVINTERFACE_HID`](/windows-hardware/drivers/install/guid-devinterface-hid) based on the presence of device/class filters.
+  + The presence of device [UpperFilter](/windows-hardware/drivers/install/devpkey-device-upperfilters)/[LowerFilter](/windows-hardware/drivers/install/devpkey-device-lowerfilters) drivers can be determined using DeviceManager by looking for `UpperFilters` and `LowerFilters` properties.
+  + The presence of HID class [UpperFilter](/windows-hardware/drivers/install/devpkey-deviceclass-upperfilters)/[LowerFilter](/windows-hardware/drivers/install/devpkey-deviceclass-lowerfilters) drivers can be determined using DeviceManager by looking for `Class upper filters` and `Class lower filters` properties.
+  + Device Interface properties can be inspected by calling [`CM_Get_Device_Interface_Property`](/windows/win32/api/cfgmgr32/nf-cfgmgr32-cm_get_device_interface_propertyw) where `pszDeviceInterface` is the same string as would be passed to [FromIdAsync](hiddevice_fromidasync_1634380010.md).
++ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
 
 ## -remarks
 

windows.devices.serialcommunication/windows_devices_serialcommunication.md

@@ -28,7 +28,7 @@ It is possible that the **DeviceInformation** collection returned by [DeviceInfo
 + Filtering such serial ports from the user's view, so that the user will not be able to interact with such an unsupported serial port at all.
 + If the app decides to let the user interact with such a serial port, then note that when the app calls the [DeviceAccessInformation.CreateFromId()](../windows.devices.enumeration/deviceaccessinformation_createfromid_1774777795.md) function, an exception with the message: "The system cannot find the file specified. (Exception from HRESULT: 0x80070002)" will be thrown. The app should handle such an exception and let the user know that the port is unsupported.
 
-Accessbility/capability policy can always be overridden by writing a custom driver and matching [Hardware Support App](/en-us/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-driver-developers)
+Accessbility/capability policy can always be overridden by writing a custom driver and matching [Hardware Support App](/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-driver-developers)
 
 ## Serial Device Capabilities
 
@@ -77,8 +77,8 @@ Here is an example for defining serial device capabilities. It allows the app to
 + Verify the user has granted permission for the application to utilize serial devices.
 + Machine-internal devices (`DEVPKEY_Device_InLocalMachineContainer == TRUE`) are generally *not* accessible. (e.g. PCI COM port expansion cards)
   + Unless the device interface property `DEVPKEY_DeviceInterface_Restricted` for `GUID_DEVINTERFACE_COMPORT` is set to `FALSE`, internal devices are not accessible.  Certain drivers, especially on IoT SKUs may set this property to `FALSE`.
-  + If accessing a Serial controller based on [`SerCx` or `SerCx2`](/en-us/windows-hardware/drivers/serports/serial-drivers-overview#sercx-and-sercx2) then starting Windows 10 1903 (May 2019 Update) the device can opt-in to be [directly accessible](/en-us/windows/uwp/devices-sensors/enable-usermode-access) from user-mode or by enabling `RhProxy`.
-+ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/en-us/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
+  + If accessing a Serial controller based on [`SerCx` or `SerCx2`](/windows-hardware/drivers/serports/serial-drivers-overview#sercx-and-sercx2) then starting Windows 10 1903 (May 2019 Update) the device can opt-in to be [directly accessible](/windows/uwp/devices-sensors/enable-usermode-access) from user-mode or by enabling `RhProxy`.
++ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
 
 
 ## -remarks

windows.devices.usb/windows_devices_usb.md

@@ -7,7 +7,7 @@
 
 ## -description
 
-This namespace defines Windows Runtime classes that a UWP app can use to communicate with [WinUSB](/en-us/windows-hardware/drivers/usbcon/automatic-installation-of-winusb) devices.  These devices are handled by the inbox `winusb.sys` driver and are identified by a specific [Microsoft OS Descriptor](/en-us/windows-hardware/drivers/usbcon/microsoft-defined-usb-descriptors).
+This namespace defines Windows Runtime classes that a UWP app can use to communicate with [WinUSB](/windows-hardware/drivers/usbcon/automatic-installation-of-winusb) devices.  These devices are handled by the inbox `winusb.sys` driver and are identified by a specific [Microsoft OS Descriptor](/windows-hardware/drivers/usbcon/microsoft-defined-usb-descriptors).
 
 A valid WinUSB device will have a compatible id of `USB\MS_COMP_WINUSB`
 
@@ -38,20 +38,20 @@ A UWP app that accesses a USB device must include specific device capability dat
 
 **Before Windows 10, version 1809 (October 2018 Update)**
 
-Since 1809, the **VendorId**/**ProductId** and **function-type** no longer need to be specified and will be ignored on newer systems.  If targeting systems below 1809, then see [legacy USB device capabilities](/en-us/windows-hardware/drivers/usbcon/updating-the-app-manifest-with-usb-device-capabilities).
+Since 1809, the **VendorId**/**ProductId** and **function-type** no longer need to be specified and will be ignored on newer systems.  If targeting systems below 1809, then see [legacy USB device capabilities](/windows-hardware/drivers/usbcon/updating-the-app-manifest-with-usb-device-capabilities).
 
 ## Troubleshooting
 
 + Verify the USB capability (```usb```) is in the application manifest.
 + Verify the user has granted permission for the application to utilize USB devices.
 + Validate the device type is not one designated as inaccessible.
-+ Machine-internal devices (`DEVPKEY_Device_InLocalMachineContainer == TRUE`) are generally *not* accessible unless running on a SKU with [embedded mode](/en-us/windows/iot-core/develop-your-app/EmbeddedMode) and `lowLevelDevices` capability.
-+ Devices with stacks that contain upper/lower filter drivers are generally *not* accessible.  These are sometimes added by 3rd parties to enable additional functionality for [custom hardware](/en-us/windows-hardware/drivers/install/inf-addreg-directive).
++ Machine-internal devices (`DEVPKEY_Device_InLocalMachineContainer == TRUE`) are generally *not* accessible unless running on a SKU with [embedded mode](/windows/iot-core/develop-your-app/EmbeddedMode) and `lowLevelDevices` capability.
++ Devices with stacks that contain upper/lower filter drivers are generally *not* accessible.  These are sometimes added by 3rd parties to enable additional functionality for [custom hardware](/windows-hardware/drivers/install/inf-addreg-directive).
   + Device restriction is partially determined by `winusb.sys` during device enumeration, which may set the device interface property `DEVPKEY_DeviceInterface_Restricted` to `TRUE` on the WinUSB Device Interface `GUID_DEVINTERFACE_WINUSB_WINRT` based on the presence of device/class filters.
-  + The presence of device [UpperFilter](/en-us/windows-hardware/drivers/install/devpkey-device-upperfilters)/[LowerFilter](/en-us/windows-hardware/drivers/install/devpkey-device-lowerfilters) drivers can be determined using DeviceManager by looking for `UpperFilters` and `LowerFilters` properties.
-  + The presence of WinUSB class [UpperFilter](/en-us/windows-hardware/drivers/install/devpkey-deviceclass-upperfilters)/[LowerFilter](/en-us/windows-hardware/drivers/install/devpkey-deviceclass-lowerfilters) drivers can be determined using DeviceManager by looking for `Class upper filters` and `Class lower filters` properties.
-  + Device Interface properties can be inspected by calling [`CM_Get_Device_Interface_Property`](/en-us/windows/win32/api/cfgmgr32/nf-cfgmgr32-cm_get_device_interface_propertyw) where `pszDeviceInterface` is the same string as would be passed to [FromIdAsync](usbdevice_fromidasync_1322863552.md).
-+ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/en-us/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
+  + The presence of device [UpperFilter](/windows-hardware/drivers/install/devpkey-device-upperfilters)/[LowerFilter](/windows-hardware/drivers/install/devpkey-device-lowerfilters) drivers can be determined using DeviceManager by looking for `UpperFilters` and `LowerFilters` properties.
+  + The presence of WinUSB class [UpperFilter](/windows-hardware/drivers/install/devpkey-deviceclass-upperfilters)/[LowerFilter](/windows-hardware/drivers/install/devpkey-deviceclass-lowerfilters) drivers can be determined using DeviceManager by looking for `Class upper filters` and `Class lower filters` properties.
+  + Device Interface properties can be inspected by calling [`CM_Get_Device_Interface_Property`](/windows/win32/api/cfgmgr32/nf-cfgmgr32-cm_get_device_interface_propertyw) where `pszDeviceInterface` is the same string as would be passed to [FromIdAsync](usbdevice_fromidasync_1322863552.md).
++ These restrictions can be bypassed when making a custom device by working with the driver-developer to create a [Hardware Support App](/windows-hardware/drivers/devapps/hardware-support-app--hsa--steps-for-app-developers)
 
 ## -remarks
 

windows.foundation.collections/valueset.md

@@ -10,7 +10,7 @@ public class ValueSet : Windows.Foundation.Collections.IIterable<Windows.Foundat
 # Windows.Foundation.Collections.ValueSet
 
 ## -description
-Implements a map with keys of type **String** and values of type [Object](/dotnet/api/system.object?view=dotnet-uwp-10.0&preserve-view=true). Object must be a WinRT [PropertyValue](/en-us/windows/win32/api/windows.foundation/nn-windows-foundation-ipropertyvalue) or ValueSet. As a PropertyValue, it can be any type except [PropertyType](/en-us/windows/win32/api/windows.foundation/ne-windows-foundation-propertytype) **InspectableArray**. This limitation exists to ensure that the value can be serialized; passed by value accoss a process boundary.
+Implements a map with keys of type **String** and values of type [Object](/dotnet/api/system.object?view=dotnet-uwp-10.0&preserve-view=true). Object must be a WinRT [PropertyValue](/windows/win32/api/windows.foundation/nn-windows-foundation-ipropertyvalue) or ValueSet. As a PropertyValue, it can be any type except [PropertyType](/windows/win32/api/windows.foundation/ne-windows-foundation-propertytype) **InspectableArray**. This limitation exists to ensure that the value can be serialized; passed by value accoss a process boundary.
 
 > [!NOTE]
 > Some members are only available for the specified language.

windows.foundation.metadata/activatableattribute_activatableattribute_2016725141.md

@@ -21,7 +21,7 @@ The name of the API contract that can activate the runtime class with no paramet
 (This parameter should have been named `contractName`.)
 
 ## -remarks
-Activation with no parameters is performed by [the RoActivateInstance function](/en-us/windows/desktop/api/roapi/nf-roapi-roactivateinstance).
+Activation with no parameters is performed by [the RoActivateInstance function](/windows/desktop/api/roapi/nf-roapi-roactivateinstance).
 
 ## -examples