diff --git a/hub/apps/develop/ui/controls/buttons.md b/hub/apps/develop/ui/controls/buttons.md
index e5b6496924..c86305060a 100644
--- a/hub/apps/develop/ui/controls/buttons.md
+++ b/hub/apps/develop/ui/controls/buttons.md
@@ -277,7 +277,7 @@ private void AlignmentMenuFlyoutItem_Click(object sender, RoutedEventArgs e)
 {
     var option = ((MenuFlyoutItem)sender).Tag.ToString();
 
-    Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+    Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
     if (selectedText != null)
     {
         // Apply the alignment to the selected paragraphs.
@@ -403,10 +403,10 @@ public sealed partial class MainPage : Page
     private void ChangeColor()
     {
         // Apply the color to the selected text in a RichEditBox.
-        Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+        Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
         if (selectedText != null)
         {
-            Windows.UI.Text.ITextCharacterFormat charFormatting = selectedText.CharacterFormat;
+            Microsoft.UI.Text.ITextCharacterFormat charFormatting = selectedText.CharacterFormat;
             charFormatting.ForegroundColor = CurrentColorBrush.Color;
             selectedText.CharacterFormat = charFormatting;
         }
@@ -522,7 +522,7 @@ private void ListStylesListView_SelectionChanged(object sender, SelectionChanged
 
 private void ApplyListStyle(string listStyle)
 {
-    Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+    Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
     if (selectedText != null)
     {
         // Apply the list style to the selected text.
diff --git a/hub/apps/develop/ui/controls/custom-transport-controls.md b/hub/apps/develop/ui/controls/custom-transport-controls.md
index 0834f66bdd..751403bc0f 100644
--- a/hub/apps/develop/ui/controls/custom-transport-controls.md
+++ b/hub/apps/develop/ui/controls/custom-transport-controls.md
@@ -15,7 +15,7 @@ ms.localizationpriority: medium
 
 MediaPlayerElement has customizable XAML transport controls to manage control of audio and video content within a Windows app. Here, we demonstrate how to customize the MediaTransportControls template. We'll show you how to work with the overflow menu, add a custom button and modify the slider.
 
-> **Important APIs**: [MediaPlayerElement](/uwp/api/windows.ui.xaml.controls.mediaplayerelement), [MediaPlayerElement.AreTransportControlsEnabled](/uwp/api/windows.ui.xaml.controls.mediaplayerelement.aretransportcontrolsenabled), [MediaTransportControls](/uwp/api/Windows.Media.SystemMediaTransportControls)
+> **Important APIs**: [MediaPlayerElement](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement), [MediaPlayerElement.AreTransportControlsEnabled](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement.aretransportcontrolsenabled), [MediaTransportControls](/uwp/api/Windows.Media.SystemMediaTransportControls)
 
 Before starting, you should be familiar with the MediaPlayerElement and the MediaTransportControls classes. For more info, see the MediaPlayerElement control guide.
 
@@ -24,7 +24,7 @@ Before starting, you should be familiar with the MediaPlayerElement and the Medi
 
 ## When should you customize the template?
 
-**MediaPlayerElement** has built-in transport controls that are designed to work well without modification in most video and audio playback apps. They're provided by the [**MediaTransportControls**](/uwp/api/Windows.UI.Xaml.Controls.MediaTransportControls) class and include buttons to play, stop, and navigate media, adjust volume, toggle full screen, cast to a second device, enable captions, switch audio tracks, and adjust the playback rate. MediaTransportControls has properties that let you control whether each button is shown and enabled. You can also set the [**IsCompact**](/uwp/api/windows.ui.xaml.controls.mediatransportcontrols.iscompact) property to specify whether the controls are shown in one row or two.
+**MediaPlayerElement** has built-in transport controls that are designed to work well without modification in most video and audio playback apps. They're provided by the [**MediaTransportControls**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.MediaTransportControls) class and include buttons to play, stop, and navigate media, adjust volume, toggle full screen, cast to a second device, enable captions, switch audio tracks, and adjust the playback rate. MediaTransportControls has properties that let you control whether each button is shown and enabled. You can also set the [**IsCompact**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediatransportcontrols.iscompact) property to specify whether the controls are shown in one row or two.
 
 However, there may be scenarios where you need to further customize the look of the control or change its behavior. Here are some examples:
 - Change the icons, slider behavior, and colors.
@@ -42,17 +42,17 @@ You can customize the appearance of the control by modifying the default templat
 
 ## Template structure
 
-The [**ControlTemplate**](/uwp/api/Windows.UI.Xaml.Controls.ControlTemplate) is part of the default style. You can copy this default style into your project to modify it. The ControlTemplate is divided into sections similar to other XAML control templates.
-- The first section of the template contains the [**Style**](/uwp/api/Windows.UI.Xaml.Style) definitions for the various components of the MediaTransportControls.
+The [**ControlTemplate**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ControlTemplate) is part of the default style. You can copy this default style into your project to modify it. The ControlTemplate is divided into sections similar to other XAML control templates.
+- The first section of the template contains the [**Style**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Style) definitions for the various components of the MediaTransportControls.
 - The second section defines the various visual states that are used by the MediaTransportControls.
-- The third section contains the [**Grid**](/uwp/api/Windows.UI.Xaml.Controls.Grid) that holds that various MediaTransportControls elements together and defines how the components are laid out.
+- The third section contains the [**Grid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Grid) that holds that various MediaTransportControls elements together and defines how the components are laid out.
 
 > [!NOTE]
 > For more info about modifying templates, see [Control templates](../../platform/xaml/xaml-control-templates.md). You can use a text editor or similar editors in your IDE to open the XAML files in \(*Program Files*)\Windows Kits\10\DesignTime\CommonConfiguration\Neutral\UAP\\(*SDK version*)\Generic. The default style and template for each control is defined in the **generic.xaml** file. You can find the MediaTransportControls template in generic.xaml by searching for "MediaTransportControls".
 
 In the following sections, you learn how to customize several of the main elements of the transport controls:
-- [**Slider**](/uwp/api/Windows.UI.Xaml.Controls.Slider): allows a user to scrub through their media and also displays progress
-- [**CommandBar**](/uwp/api/Windows.UI.Xaml.Controls.CommandBar): contains all of the buttons.
+- [**Slider**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Slider): allows a user to scrub through their media and also displays progress
+- [**CommandBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.CommandBar): contains all of the buttons.
 For more info, see the Anatomy section of the MediaTransportControls reference topic.
 
 ## Customize the transport controls
@@ -100,9 +100,9 @@ public sealed class CustomMediaTransportControls : MediaTransportControls
 }
 ```
 
-3. Copy the default style for [**MediaTransportControls**](/uwp/api/Windows.UI.Xaml.Controls.MediaTransportControls) into a [ResourceDictionary](/uwp/api/Windows.UI.Xaml.ResourceDictionary) in your project. This is the style and template you modify.
+3. Copy the default style for [**MediaTransportControls**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.MediaTransportControls) into a [ResourceDictionary](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.ResourceDictionary) in your project. This is the style and template you modify.
 (In the Media Transport Controls sample, a new folder called "Themes" is created, and a ResourceDictionary file called generic.xaml is added to it.)
-4. Change the [**TargetType**](/uwp/api/windows.ui.xaml.style.targettype) of the style to the new custom control type. (In the sample, the TargetType is changed to `local:CustomMediaTransportControls`.)
+4. Change the [**TargetType**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.style.targettype) of the style to the new custom control type. (In the sample, the TargetType is changed to `local:CustomMediaTransportControls`.)
 
 ```xaml
 xmlns:local="using:CustomMediaTransportControls">
@@ -110,7 +110,7 @@ xmlns:local="using:CustomMediaTransportControls">
 <Style TargetType="local:CustomMediaTransportControls">
 ```
 
-5. Set the [**DefaultStyleKey**](/uwp/api/windows.ui.xaml.controls.control.defaultstylekey) of your custom class. This tells your custom class to use a Style with a TargetType of `local:CustomMediaTransportControls`.
+5. Set the [**DefaultStyleKey**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.control.defaultstylekey) of your custom class. This tells your custom class to use a Style with a TargetType of `local:CustomMediaTransportControls`.
 
 ```csharp
 public sealed class CustomMediaTransportControls : MediaTransportControls
@@ -122,7 +122,7 @@ public sealed class CustomMediaTransportControls : MediaTransportControls
 }
 ```
 
-6. Add a [**MediaPlayerElement**](/uwp/api/windows.ui.xaml.controls.mediaplayerelement) to your XAML markup and add the custom transport controls to it. One thing to note is that the APIs to hide, show, disable, and enable the default buttons still work with a customized template.
+6. Add a [**MediaPlayerElement**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement) to your XAML markup and add the custom transport controls to it. One thing to note is that the APIs to hide, show, disable, and enable the default buttons still work with a customized template.
 
 ```xaml
 <MediaPlayerElement Name="MediaPlayerElement1" AreTransportControlsEnabled="True" Source="video.mp4">
@@ -146,13 +146,13 @@ You can now modify the control style and template to update the look of your cus
 
 You can move MediaTransportControls command buttons into an overflow menu, so that less commonly used commands are hidden until the user needs them.
 
-In the MediaTransportControls template, the command buttons are contained in a [**CommandBar**](/uwp/api/Windows.UI.Xaml.Controls.CommandBar) element. The command bar has the concept of primary and secondary commands. The primary commands are the buttons that appear in the control by default and are always visible (unless you disable the button, hide the button or there is not enough room). The secondary commands are shown in an overflow menu that appears when a user clicks the ellipsis (…) button. For more info, see the [App bars and command bars](../../../design/controls/command-bar.md) article.
+In the MediaTransportControls template, the command buttons are contained in a [**CommandBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.CommandBar) element. The command bar has the concept of primary and secondary commands. The primary commands are the buttons that appear in the control by default and are always visible (unless you disable the button, hide the button or there is not enough room). The secondary commands are shown in an overflow menu that appears when a user clicks the ellipsis (…) button. For more info, see the [App bars and command bars](../../../design/controls/command-bar.md) article.
 
 To move an element from the command bar primary commands to the overflow menu, you need to edit the XAML control template.
 
 **To move a command to the overflow menu:**
 1. In the control template, find the CommandBar element named `MediaControlsCommandBar`.
-2. Add a [**SecondaryCommands**](/uwp/api/windows.ui.xaml.controls.commandbar.secondarycommands) section to the XAML for the CommandBar. Put it after the closing tag for the [**PrimaryCommands**](/uwp/api/windows.ui.xaml.controls.commandbar.primarycommands).
+2. Add a [**SecondaryCommands**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.commandbar.secondarycommands) section to the XAML for the CommandBar. Put it after the closing tag for the [**PrimaryCommands**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.commandbar.primarycommands).
 
 ```xaml
 <CommandBar x:Name="MediaControlsCommandBar" ... >  
@@ -175,7 +175,7 @@ To move an element from the command bar primary commands to the overflow menu, y
 </CommandBar>
 ```
 
-3. To populate the menu with commands, cut and paste the XAML for the desired [**AppBarButton**](/uwp/api/Windows.UI.Xaml.Controls.AppBarButton) objects from the PrimaryCommands to the SecondaryCommands. In this example, we move the `PlaybackRateButton` to the overflow menu.
+3. To populate the menu with commands, cut and paste the XAML for the desired [**AppBarButton**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.AppBarButton) objects from the PrimaryCommands to the SecondaryCommands. In this example, we move the `PlaybackRateButton` to the overflow menu.
 
 4. Add a label to the button and remove the styling information, as shown here.
 Because the overflow menu is comprised of text buttons, you must add a text label to the button and also remove the style that sets the height and width of the button. Otherwise, it won't appear correctly in the overflow menu.
@@ -208,10 +208,10 @@ One reason you might want to customize MediaTransportControls is to add a custom
 
 You must add it to the CommandBar in the appropriate location. (For more information, see the Working with the overflow menu section.) How it's positioned in the UI is determined by where the button is in the markup. For example, if you want this button to appear as the last element in the primary commands, add it at the very end of the primary commands list.
 
-You can also customize the icon for the button. For more information, see the <a href="/uwp/api/Windows.UI.Xaml.Controls.AppBarButton"><b>AppBarButton</b></a> reference.
+You can also customize the icon for the button. For more information, see the <a href="/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.AppBarButton"><b>AppBarButton</b></a> reference.
     
 
-2. In the [**OnApplyTemplate**](/uwp/api/windows.ui.xaml.frameworkelement.onapplytemplate) override, get the button from the template and register a handler for its [**Click**](/uwp/api/windows.ui.xaml.controls.primitives.buttonbase.click) event. This code goes in the `CustomMediaTransportControls` class.
+2. In the [**OnApplyTemplate**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.frameworkelement.onapplytemplate) override, get the button from the template and register a handler for its [**Click**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.primitives.buttonbase.click) event. This code goes in the `CustomMediaTransportControls` class.
 
 ```csharp
 public sealed class CustomMediaTransportControls :  MediaTransportControls
@@ -265,9 +265,9 @@ public sealed class CustomMediaTransportControls : MediaTransportControls
 
 ### Modifying the slider
 
-The "seek" control of the MediaTransportControls is provided by a [**Slider**](/uwp/api/Windows.UI.Xaml.Controls.Slider) element. One way you can customize it is to change the granularity of the seek behavior.
+The "seek" control of the MediaTransportControls is provided by a [**Slider**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Slider) element. One way you can customize it is to change the granularity of the seek behavior.
 
-The default seek slider is divided into 100 parts, so the seek behavior is limited to that many sections. You can change the granularity of the seek slider by getting the Slider from the XAML visual tree in your [**MediaOpened**](/uwp/api/windows.media.playback.mediaplayer.mediaopened) event handler on [**MediaPlayerElement.MediaPlayer**](/uwp/api/windows.ui.xaml.controls.mediaplayerelement). This example shows how to use [**VisualTreeHelper**](/uwp/api/Windows.UI.Xaml.Media.VisualTreeHelper) to get a reference to the Slider, then change the default step frequency of the slider from 1% to 0.1% (1000 steps) if the media is longer than 120 minutes. The MediaPlayerElement is named `MediaPlayerElement1`.
+The default seek slider is divided into 100 parts, so the seek behavior is limited to that many sections. You can change the granularity of the seek slider by getting the Slider from the XAML visual tree in your [**MediaOpened**](/uwp/api/windows.media.playback.mediaplayer.mediaopened) event handler on [**MediaPlayerElement.MediaPlayer**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement). This example shows how to use [**VisualTreeHelper**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Media.VisualTreeHelper) to get a reference to the Slider, then change the default step frequency of the slider from 1% to 0.1% (1000 steps) if the media is longer than 120 minutes. The MediaPlayerElement is named `MediaPlayerElement1`.
 
 ```csharp
 protected override void OnNavigatedTo(NavigationEventArgs e)
diff --git a/hub/apps/develop/ui/controls/date-and-time.md b/hub/apps/develop/ui/controls/date-and-time.md
index fbc34a3cad..06add4aa1b 100644
--- a/hub/apps/develop/ui/controls/date-and-time.md
+++ b/hub/apps/develop/ui/controls/date-and-time.md
@@ -187,8 +187,8 @@ A related concept is the Calendar class, which influences how dates are interpre
 ## Get the sample code
 
 - [WinUI 3 Gallery sample](https://github.com/Microsoft/WinUI-Gallery)
-- [Calendar sample](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/Calendar)
-- [Date and time formatting sample](https://github.com/microsoft/Windows-universal-samples/tree/master/Samples/DateTimeFormatting)
+- [Calendar view sample](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/Samples/ControlPages/CalendarViewPage.xaml)
+- [DatePicker sample](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/Samples/ControlPages/DatePickerPage.xaml)
 
 ## Related topics
 
diff --git a/hub/apps/develop/ui/controls/dialogs-and-flyouts/dialogs.md b/hub/apps/develop/ui/controls/dialogs-and-flyouts/dialogs.md
index 1882299ebd..dbb8b87495 100644
--- a/hub/apps/develop/ui/controls/dialogs-and-flyouts/dialogs.md
+++ b/hub/apps/develop/ui/controls/dialogs-and-flyouts/dialogs.md
@@ -328,4 +328,4 @@ A typical confirmation dialog has two buttons: an affirmation ("OK") button and
 - [Tooltips](../../../../design/controls/tooltips.md)
 - [Menus and context menu](../../../../design/controls/menus.md)
 - [Flyout class](/windows/windows-app-sdk/api/winrt/microsoft.UI.Xaml.Controls.Flyout)
-By default, content dialogs display modally relative to the root [ApplicationView](/uwp/api/windows.ui.viewmanagement.applicationview). When you use ContentDialog inside of either an [AppWindow](/uwp/api/windows.ui.windowmanagement.appwindow) or a [XAML Island](../../../../desktop/modernize/xaml-islands/xaml-islands.md), you need to manually set the [XamlRoot](/uwp/api/windows.ui.xaml.uielement.xamlroot) on the dialog to the root of the XAML host.
+By default, content dialogs display modally relative to the root [ApplicationView](/uwp/api/windows.ui.viewmanagement.applicationview). When you use ContentDialog inside of either an [AppWindow](/uwp/api/windows.ui.windowmanagement.appwindow) or a [XAML Island](../../../../desktop/modernize/xaml-islands/xaml-islands.md), you need to manually set the [XamlRoot](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.xamlroot) on the dialog to the root of the XAML host.
diff --git a/hub/apps/develop/ui/controls/flipview.md b/hub/apps/develop/ui/controls/flipview.md
index edf1df4a13..e1c5ef0554 100644
--- a/hub/apps/develop/ui/controls/flipview.md
+++ b/hub/apps/develop/ui/controls/flipview.md
@@ -222,7 +222,7 @@ For larger collections (10 or more items), we highly recommend using a contextua
 
 :::image type="content" source="images/controls-context-indicator.jpg" alt-text="A film strip of thumbnails underneath a FlipView photo album.":::
 
-For a full example showing how to add a context indicator to a FlipView, see [XAML FlipView sample](https://github.com/microsoftarchive/msdn-code-gallery-microsoft/tree/411c271e537727d737a53fa2cbe99eaecac00cc0/Official%20Windows%20Platform%20Sample/Windows%208%20app%20samples/%5BC%23%5D-Windows%208%20app%20samples/C%23/Windows%208%20app%20samples/XAML%20FlipView%20control%20sample%20(Windows%208)).
+For a full example showing how to add a context indicator to a FlipView, see the [WinUI Gallery FlipView sample](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/Samples/ControlPages/FlipViewPage.xaml).
 
 ## Related articles
 
diff --git a/hub/apps/develop/ui/controls/item-templates-gridview.md b/hub/apps/develop/ui/controls/item-templates-gridview.md
index 7911d59111..5ef2bb6e79 100644
--- a/hub/apps/develop/ui/controls/item-templates-gridview.md
+++ b/hub/apps/develop/ui/controls/item-templates-gridview.md
@@ -153,5 +153,5 @@ Use this template to display a media collection with text overlay.
 - [GridView class](/windows/windows-app-sdk/api/winrt/microsoft.UI.Xaml.Controls.GridView)
 - [Data binding overview](/windows/uwp/data-binding/data-binding-quickstart)
 - [Accessibility overview](../../../design/accessibility/accessibility-overview.md)
-- [ListView and GridView sample](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/XamlListView)
+- [GridView sample](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/Samples/ControlPages/GridViewPage.xaml)
 - [Thumbnail images](/windows/uwp/files/thumbnails)
diff --git a/hub/apps/develop/ui/controls/item-templates-listview.md b/hub/apps/develop/ui/controls/item-templates-listview.md
index 88e1fb15d5..4c46722615 100644
--- a/hub/apps/develop/ui/controls/item-templates-listview.md
+++ b/hub/apps/develop/ui/controls/item-templates-listview.md
@@ -126,5 +126,5 @@ Use this template to display a list of items with text in defined columns.
 - [ListView class](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.listview)
 - [Data binding overview](/windows/uwp/data-binding/data-binding-quickstart)
 - [Accessibility overview](../../../design/accessibility/accessibility-overview.md)
-- [ListView and GridView sample](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/XamlListView)
+- [ListView sample](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/Samples/ControlPages/ListViewPage.xaml)
 - [Thumbnail images](/windows/uwp/files/thumbnails)
diff --git a/hub/apps/develop/ui/controls/lists.md b/hub/apps/develop/ui/controls/lists.md
index f41670166f..447e5c27be 100644
--- a/hub/apps/develop/ui/controls/lists.md
+++ b/hub/apps/develop/ui/controls/lists.md
@@ -1,5 +1,5 @@
 ---
-description: Learn about collections and lists as representations of multiple related data items that appear together. 
+description: Learn about collections and lists as representations of multiple related data items that appear together.
 title: Collections and lists
 ms.assetid: C73125E8-3768-46A5-B078-FDDF42AB1077
 label: Collections and Lists
@@ -210,7 +210,7 @@ Use an ItemsRepeater if:
 
 ### Examples
 
-The following three examples are all ItemsRepeater controls that are bound to the same data source (a collection of numbers). The collection of numbers is represented in three ways, with each of the ItemsRepeaters below using a different custom [Layout](/uwp/api/microsoft.ui.xaml.controls.layout) and a different custom [ItemTemplate](/uwp/api/microsoft.ui.xaml.controls.itemsrepeater.itemtemplate).
+The following three examples are all ItemsRepeater controls that are bound to the same data source (a collection of numbers). The collection of numbers is represented in three ways, with each of the ItemsRepeaters below using a different custom [Layout](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.layout) and a different custom [ItemTemplate](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.itemsrepeater.itemtemplate).
 
 ![ItemsRepeater with horizontal bars](images/itemsrepeater-1.png)
 ![ItemsRepeater with vertical bars](images/itemsrepeater-2.png)
diff --git a/hub/apps/develop/ui/controls/menus.md b/hub/apps/develop/ui/controls/menus.md
index 9052eaa1a2..29e1678b9b 100644
--- a/hub/apps/develop/ui/controls/menus.md
+++ b/hub/apps/develop/ui/controls/menus.md
@@ -65,13 +65,13 @@ This example creates a [MenuFlyout](/windows/windows-app-sdk/api/winrt/microsoft
 private void ChangeColorItem_Click(object sender, RoutedEventArgs e)
 {
     // Change the color from red to blue or blue to red.
-    if (rectangleFill.Color == Windows.UI.Colors.Red)
+    if (rectangleFill.Color == Microsoft.UI.Colors.Red)
     {
-        rectangleFill.Color = Windows.UI.Colors.Blue;
+        rectangleFill.Color = Microsoft.UI.Colors.Blue;
     }
     else
     {
-        rectangleFill.Color = Windows.UI.Colors.Red;
+        rectangleFill.Color = Microsoft.UI.Colors.Red;
     }
 }
 ````
@@ -102,13 +102,13 @@ private void Rectangle_Tapped(object sender, TappedRoutedEventArgs e)
 private void ChangeColorItem_Click(object sender, RoutedEventArgs e)
 {
     // Change the color from red to blue or blue to red.
-    if (rectangleFill.Color == Windows.UI.Colors.Red)
+    if (rectangleFill.Color == Microsoft.UI.Colors.Red)
     {
-        rectangleFill.Color = Windows.UI.Colors.Blue;
+        rectangleFill.Color = Microsoft.UI.Colors.Blue;
     }
     else
     {
-        rectangleFill.Color = Windows.UI.Colors.Red;
+        rectangleFill.Color = Microsoft.UI.Colors.Red;
     }
 }
 ````
diff --git a/hub/apps/develop/ui/controls/navigationview.md b/hub/apps/develop/ui/controls/navigationview.md
index 8481ff7b6b..cb458f7263 100644
--- a/hub/apps/develop/ui/controls/navigationview.md
+++ b/hub/apps/develop/ui/controls/navigationview.md
@@ -403,7 +403,7 @@ You can hide or disable the back button by setting these properties:
 
 This example shows how you can use NavigationView with both a top navigation pane on large window sizes and a left navigation pane on small window sizes. It can be adapted to left-only navigation by removing the *top* navigation settings in the VisualStateManager.
 
-The example demonstrates a common way to set up navigation data that will work for many scenarios. In this example, you first store (in the tag of the [NavigationViewItem](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.navigationviewitem)) the full type name of the page to which you want to navigate. In the event handler, you unbox that value, turn it into a [Type]()(C#) or  [**Windows::UI::Xaml::Interop::TypeName**](/uwp/api/windows.ui.xaml.interop.typename)(C++/WinRT) object, and use that to navigate to the destination page. This lets you create unit tests to confirm that the values inside your tags are of a valid type. (Also see [Boxing and unboxing values to IInspectable with C++/WinRT](/windows/uwp/cpp-and-winrt-apis/boxing)). It also demonstrates how to implement backwards navigation with NavigationView's back button.
+The example demonstrates a common way to set up navigation data that will work for many scenarios. In this example, you first store (in the tag of the [NavigationViewItem](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.navigationviewitem)) the full type name of the page to which you want to navigate. In the event handler, you unbox that value, turn it into a [Type](/dotnet/api/system.type)(C#) or **Microsoft::UI::Xaml::Interop::TypeName** (C++/WinRT) object, and use that to navigate to the destination page. This lets you create unit tests to confirm that the values inside your tags are of a valid type. (Also see [Boxing and unboxing values to IInspectable with C++/WinRT](/windows/uwp/cpp-and-winrt-apis/boxing)). It also demonstrates how to implement backwards navigation with NavigationView's back button.
 
 This code assumes that your app contains pages with the following names to navigate to: *HomePage*, *AppsPage*, *GamesPage*, *MusicPage*, *MyContentPage*, and *SettingsPage*. Code for these pages is not shown.
 
@@ -597,7 +597,7 @@ runtimeclass MainPage : Microsoft.UI.Xaml.Controls.Page
 
 // pch.h
 ...
-#include <winrt/Windows.UI.Xaml.Interop.h>
+#include <winrt/Microsoft.UI.Xaml.Interop.h>
 #include <winrt/Microsoft.UI.Xaml.Media.Animation.h>
 
 
@@ -635,7 +635,7 @@ namespace winrt::NavigationViewDemo::implementation
             muxc::NavigationView const& /* sender */,
             muxc::NavigationViewSelectionChangedEventArgs const& args);
         void NavView_Navigate(
-            Windows::UI::Xaml::Interop::TypeName navPageType,
+            Microsoft::UI::Xaml::Interop::TypeName navPageType,
             Microsoft::UI::Xaml::Media::Animation::NavigationTransitionInfo const& transitionInfo);
         void NavView_BackRequested(
             muxc::NavigationView const& /* sender */,
@@ -722,9 +722,9 @@ namespace winrt::NavigationViewDemo::implementation
         }
         else if (args.InvokedItemContainer())
         {
-            Windows::UI::Xaml::Interop::TypeName pageTypeName;
+            Microsoft::UI::Xaml::Interop::TypeName pageTypeName;
             pageTypeName.Name = unbox_value<hstring>(args.InvokedItemContainer().Tag());
-            pageTypeName.Kind = Windows::UI::Xaml::Interop::TypeKind::Primitive;
+            pageTypeName.Kind = Microsoft::UI::Xaml::Interop::TypeKind::Primitive;
             NavView_Navigate(pageTypeName, args.RecommendedNavigationTransitionInfo());
         }
     }
@@ -743,20 +743,20 @@ namespace winrt::NavigationViewDemo::implementation
         }
         else if (args.SelectedItemContainer())
         {
-            Windows::UI::Xaml::Interop::TypeName pageTypeName;
+            Microsoft::UI::Xaml::Interop::TypeName pageTypeName;
             pageTypeName.Name = unbox_value<hstring>(args.SelectedItemContainer().Tag());
-            pageTypeName.Kind = Windows::UI::Xaml::Interop::TypeKind::Primitive;
+            pageTypeName.Kind = Microsoft::UI::Xaml::Interop::TypeKind::Primitive;
             NavView_Navigate(pageTypeName, args.RecommendedNavigationTransitionInfo());
         }
     }
 
     void MainPage::NavView_Navigate(
-        Windows::UI::Xaml::Interop::TypeName navPageType,
+        Microsoft::UI::Xaml::Interop::TypeName navPageType,
         Microsoft::UI::Xaml::Media::Animation::NavigationTransitionInfo const& transitionInfo)
     {
         // Get the page type before navigation so you can prevent duplicate
         // entries in the backstack.
-        Windows::UI::Xaml::Interop::TypeName preNavPageType =
+        Microsoft::UI::Xaml::Interop::TypeName preNavPageType =
             ContentFrame().CurrentSourcePageType();
 
         // Navigate only if the selected page isn't currently loaded.
@@ -1068,7 +1068,7 @@ import "Category.idl";
 namespace HierarchicalNavigationViewDataBinding
 {
     [default_interface]
-    runtimeclass MainPage : Windows.UI.Xaml.Controls.Page
+    runtimeclass MainPage : Microsoft.UI.Xaml.Controls.Page
     {
         MainPage();
         Windows.Foundation.Collections.IObservableVector<Category> Categories{ get; };
diff --git a/hub/apps/develop/ui/controls/person-picture.md b/hub/apps/develop/ui/controls/person-picture.md
index 0e8e67fac6..11f3c7b66e 100644
--- a/hub/apps/develop/ui/controls/person-picture.md
+++ b/hub/apps/develop/ui/controls/person-picture.md
@@ -80,13 +80,13 @@ using System.Linq;
 using System.Runtime.InteropServices.WindowsRuntime;
 using Windows.Foundation;
 using Windows.Foundation.Collections;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
-using Windows.UI.Xaml.Controls.Primitives;
-using Windows.UI.Xaml.Data;
-using Windows.UI.Xaml.Input;
-using Windows.UI.Xaml.Media;
-using Windows.UI.Xaml.Navigation;
+using Microsoft.UI.Xaml;
+using Microsoft.UI.Xaml.Controls;
+using Microsoft.UI.Xaml.Controls.Primitives;
+using Microsoft.UI.Xaml.Data;
+using Microsoft.UI.Xaml.Input;
+using Microsoft.UI.Xaml.Media;
+using Microsoft.UI.Xaml.Navigation;
 using Windows.ApplicationModel.Contacts;
 
 namespace SampleApp
diff --git a/hub/apps/develop/ui/controls/radio-button.md b/hub/apps/develop/ui/controls/radio-button.md
index 9bc470d61e..8ccf7800dc 100644
--- a/hub/apps/develop/ui/controls/radio-button.md
+++ b/hub/apps/develop/ui/controls/radio-button.md
@@ -235,7 +235,7 @@ The following table describes how Narrator handles a `RadioButtons` group and wh
 |Focus moves to an unselected item<br> *(If navigating with Ctrl-arrow keys or Xbox gamepad,<br>which indicates selection is not following focus.)* | "_name_, RadioButton, non-selected, _x_ of _N_"  |
 
 > [!NOTE]
-> The _**name**_ that Narrator announces for each item is the value of the [AutomationProperties.Name](/uwp/api/windows.ui.xaml.automation.automationproperties.nameproperty) attached property if it is available for the item; otherwise, it is the value returned by the item's [ToString](/dotnet/api/system.object.tostring?view=dotnet-uwp-10.0&preserve-view=true) method.
+> The _**name**_ that Narrator announces for each item is the value of the [AutomationProperties.Name](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.automationproperties.nameproperty) attached property if it is available for the item; otherwise, it is the value returned by the item's [ToString](/dotnet/api/system.object.tostring?view=dotnet-uwp-10.0&preserve-view=true) method.
 >
 > _**x**_ is the number of the current item. _**N**_ is the total number of items in the group.
 
diff --git a/hub/apps/develop/ui/controls/rich-edit-box.md b/hub/apps/develop/ui/controls/rich-edit-box.md
index b405650434..0e4e274d22 100644
--- a/hub/apps/develop/ui/controls/rich-edit-box.md
+++ b/hub/apps/develop/ui/controls/rich-edit-box.md
@@ -154,7 +154,7 @@ private async void SaveButton_Click(object sender, RoutedEventArgs e)
 
 private void BoldButton_Click(object sender, RoutedEventArgs e)
 {
-    Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+    Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
     if (selectedText != null)
     {
         Windows.UI.Text.ITextCharacterFormat charFormatting = selectedText.CharacterFormat;
@@ -165,7 +165,7 @@ private void BoldButton_Click(object sender, RoutedEventArgs e)
 
 private void ItalicButton_Click(object sender, RoutedEventArgs e)
 {
-    Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+    Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
     if (selectedText != null)
     {
         Windows.UI.Text.ITextCharacterFormat charFormatting = selectedText.CharacterFormat;
@@ -176,7 +176,7 @@ private void ItalicButton_Click(object sender, RoutedEventArgs e)
 
 private void UnderlineButton_Click(object sender, RoutedEventArgs e)
 {
-    Windows.UI.Text.ITextSelection selectedText = editor.Document.Selection;
+    Microsoft.UI.Text.ITextSelection selectedText = editor.Document.Selection;
     if (selectedText != null)
     {
         Windows.UI.Text.ITextCharacterFormat charFormatting = selectedText.CharacterFormat;
diff --git a/hub/apps/develop/ui/controls/text-box.md b/hub/apps/develop/ui/controls/text-box.md
index 390e0ba438..ab15e41448 100644
--- a/hub/apps/develop/ui/controls/text-box.md
+++ b/hub/apps/develop/ui/controls/text-box.md
@@ -217,12 +217,12 @@ textBox.Text = "Sample Text";
 textBox.IsReadOnly = true;
 textBox.FontFamily = new FontFamily("Verdana");
 textBox.FontSize = 24;
-textBox.FontWeight = Windows.UI.Text.FontWeights.Bold;
-textBox.FontStyle = Windows.UI.Text.FontStyle.Italic;
+textBox.FontWeight = Microsoft.UI.Text.FontWeights.Bold;
+textBox.FontStyle = Microsoft.UI.Text.FontStyle.Italic;
 textBox.CharacterSpacing = 200;
 textBox.Width = 300;
-textBox.Background = new SolidColorBrush(Windows.UI.Colors.Beige);
-textBox.Foreground = new SolidColorBrush(Windows.UI.Colors.Blue);
+textBox.Background = new SolidColorBrush(Microsoft.UI.Colors.Beige);
+textBox.Foreground = new SolidColorBrush(Microsoft.UI.Colors.Blue);
 // Add the TextBox to the visual tree.
 rootGrid.Children.Add(textBox);
 ```
diff --git a/hub/apps/develop/ui/controls/tree-view.md b/hub/apps/develop/ui/controls/tree-view.md
index a970fc5446..771d96babf 100644
--- a/hub/apps/develop/ui/controls/tree-view.md
+++ b/hub/apps/develop/ui/controls/tree-view.md
@@ -546,8 +546,8 @@ This example shows how to create a simple tree view structure in XAML. The tree
 ```
 
 ```csharp
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
+using Microsoft.UI.Xaml;
+using Microsoft.UI.Xaml.Controls;
 using muxc = Microsoft.UI.Xaml.Controls;
 
 namespace TreeViewTest
@@ -664,8 +664,8 @@ This example shows how to create the same tree view as the previous example. How
 
 ```csharp
 using System.Collections.ObjectModel;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
+using Microsoft.UI.Xaml;
+using Microsoft.UI.Xaml.Controls;
 using muxc = Microsoft.UI.Xaml.Controls;
 
 namespace TreeViewTest
@@ -897,8 +897,8 @@ A custom item template is used to display the data items, which are of type [ISt
 using System;
 using System.Collections.Generic;
 using Windows.Storage;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
+using Microsoft.UI.Xaml;
+using Microsoft.UI.Xaml.Controls;
 using muxc = Microsoft.UI.Xaml.Controls;
 
 namespace TreeViewTest
@@ -1227,8 +1227,8 @@ The following example demonstrates how to create two tree views whose items can
 ```csharp
 using System;
 using Windows.ApplicationModel.DataTransfer;
-using Windows.UI.Xaml;
-using Windows.UI.Xaml.Controls;
+using Microsoft.UI.Xaml;
+using Microsoft.UI.Xaml.Controls;
 
 namespace TreeViewTest
 {
diff --git a/hub/apps/develop/ui/display-ui-objects.md b/hub/apps/develop/ui/display-ui-objects.md
index 3ea404159a..5eab54d4a3 100644
--- a/hub/apps/develop/ui/display-ui-objects.md
+++ b/hub/apps/develop/ui/display-ui-objects.md
@@ -40,7 +40,7 @@ These classes implement [**IInitializeWithWindow**](/windows/win32/api/shobjidl_
 * [**Windows.System.LauncherOptions**](/uwp/api/windows.system.launcheroptions)&mdash;Windows 10, version 1903 (10.0; Build 18362) and later
 * [**Windows.UI.Core.CoreWindowDialog**](/uwp/api/windows.ui.core.corewindowdialog)
 * [**Windows.UI.Core.CoreWindowFlyout**](/uwp/api/windows.ui.core.corewindowflyout)
-* [**Windows.UI.Popups.MessageDialog**](/uwp/api/windows.ui.popups.messagedialog). But for new apps we recommend using the [**ContentDialog**](/uwp/api/windows.ui.xaml.controls.contentdialog) control instead.
+* [**Windows.UI.Popups.MessageDialog**](/uwp/api/windows.ui.popups.messagedialog). But for new apps we recommend using the [**ContentDialog**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.contentdialog) control instead.
 * [**Windows.UI.Popups.PopupMenu**](/uwp/api/windows.ui.popups.popupmenu)
 * [**Windows.UI.StartScreen.SecondaryTile**](/uwp/api/windows.ui.startscreen.secondarytile)
 * [**Windows.Web.Http.Filters.HttpBaseProtocolFilter**](/uwp/api/windows.web.http.filters.httpbaseprotocolfilter)
diff --git a/hub/apps/develop/ui/layout-panels.md b/hub/apps/develop/ui/layout-panels.md
index a966170804..f915bde777 100644
--- a/hub/apps/develop/ui/layout-panels.md
+++ b/hub/apps/develop/ui/layout-panels.md
@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 ---
 # Layout panels
 
-Layout panels are containers that allow you to arrange and group UI elements in your app. The built-in XAML layout panels include [**RelativePanel**](/uwp/api/Windows.UI.Xaml.Controls.RelativePanel), [**StackPanel**](/uwp/api/Windows.UI.Xaml.Controls.StackPanel), [**Grid**](/uwp/api/Windows.UI.Xaml.Controls.Grid), [**VariableSizedWrapGrid**](/uwp/api/Windows.UI.Xaml.Controls.VariableSizedWrapGrid), and [**Canvas**](/uwp/api/Windows.UI.Xaml.Controls.Canvas). Here, we describe each panel and show how to use it to layout XAML UI elements.
+Layout panels are containers that allow you to arrange and group UI elements in your app. The built-in XAML layout panels include [**RelativePanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.RelativePanel), [**StackPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.StackPanel), [**Grid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Grid), [**VariableSizedWrapGrid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.VariableSizedWrapGrid), and [**Canvas**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Canvas). Here, we describe each panel and show how to use it to layout XAML UI elements.
 
 There are several things to consider when choosing a layout panel:
 - How the panel positions its child elements.
@@ -59,18 +59,18 @@ Using the built-in border properties reduces the XAML element count, which can i
 
 ## RelativePanel
 
-[**RelativePanel**](/uwp/api/Windows.UI.Xaml.Controls.RelativePanel) lets you layout UI elements by specifying where they go in relation to other elements and in relation to the panel. By default, an element is positioned in the upper left corner of the panel. You can use RelativePanel with [**VisualStateManager**](/uwp/api/Windows.UI.Xaml.VisualStateManager) and [**AdaptiveTrigger**](/uwp/api/Windows.UI.Xaml.AdaptiveTrigger) to rearrange your UI for different window sizes.
+[**RelativePanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.RelativePanel) lets you layout UI elements by specifying where they go in relation to other elements and in relation to the panel. By default, an element is positioned in the upper left corner of the panel. You can use RelativePanel with [**VisualStateManager**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.VisualStateManager) and [**AdaptiveTrigger**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.AdaptiveTrigger) to rearrange your UI for different window sizes.
 
 This table shows the attached properties you can use to align an element in relation to the panel or other elements.
 
 Panel alignment | Sibling alignment | Sibling position
 ----------------|-------------------|-----------------
-[**AlignTopWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel.aligntopwithpanelproperty) | [**AlignTopWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.aligntopwithproperty) | [**Above**](/uwp/api/windows.ui.xaml.controls.relativepanel)  
-[**AlignBottomWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignbottomwithpanelproperty) | [**AlignBottomWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignbottomwithproperty) | [**Below**](/uwp/api/windows.ui.xaml.controls.relativepanel.belowproperty)  
-[**AlignLeftWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel) | [**AlignLeftWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.getalignleftwith) | [**LeftOf**](/uwp/api/windows.ui.xaml.controls.relativepanel.leftofproperty)  
-[**AlignRightWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignrightwithpanelproperty) | [**AlignRightWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignrightwithproperty) | [**RightOf**](/uwp/api/windows.ui.xaml.controls.relativepanel.setrightof)  
-[**AlignHorizontalCenterWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignhorizontalcenterwithpanelproperty) | [**AlignHorizontalCenterWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignhorizontalcenterwithproperty) | &nbsp;   
-[**AlignVerticalCenterWithPanel**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignverticalcenterwithpanelproperty) | [**AlignVerticalCenterWith**](/uwp/api/windows.ui.xaml.controls.relativepanel.alignverticalcenterwithproperty) | &nbsp;   
+[**AlignTopWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.aligntopwithpanelproperty) | [**AlignTopWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.aligntopwithproperty) | [**Above**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel)  
+[**AlignBottomWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignbottomwithpanelproperty) | [**AlignBottomWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignbottomwithproperty) | [**Below**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.belowproperty)  
+[**AlignLeftWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel) | [**AlignLeftWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.getalignleftwith) | [**LeftOf**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.leftofproperty)  
+[**AlignRightWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignrightwithpanelproperty) | [**AlignRightWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignrightwithproperty) | [**RightOf**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.setrightof)  
+[**AlignHorizontalCenterWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignhorizontalcenterwithpanelproperty) | [**AlignHorizontalCenterWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignhorizontalcenterwithproperty) | &nbsp;   
+[**AlignVerticalCenterWithPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignverticalcenterwithpanelproperty) | [**AlignVerticalCenterWith**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.relativepanel.alignverticalcenterwithproperty) | &nbsp;   
 
  
 This XAML shows how to arrange elements in a RelativePanel.
@@ -106,9 +106,9 @@ Here are a few things to note about the sizing of the rectangles:
 
 ## StackPanel
 
-[**StackPanel**](/uwp/api/Windows.UI.Xaml.Controls.StackPanel) arranges its child elements into a single line that can be oriented horizontally or vertically. StackPanel is typically used to arrange a small subsection of the UI on a page.
+[**StackPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.StackPanel) arranges its child elements into a single line that can be oriented horizontally or vertically. StackPanel is typically used to arrange a small subsection of the UI on a page.
 
-You can use the [**Orientation**](/uwp/api/windows.ui.xaml.controls.stackpanel.orientation) property to specify the direction of the child elements. The default orientation is [**Vertical**](/uwp/api/Windows.UI.Xaml.Controls.Orientation).
+You can use the [**Orientation**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.stackpanel.orientation) property to specify the direction of the child elements. The default orientation is [**Vertical**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Orientation).
 
 The following XAML shows how to create a vertical StackPanel of items.
 
@@ -130,7 +130,7 @@ In a StackPanel, if a child element's size is not set explicitly, it stretches t
 
 ## Grid
 
-The [**Grid**](/uwp/api/Windows.UI.Xaml.Controls.Grid) panel supports fluid layouts and allows you to arrange controls in multi-row and multi-column layouts. You specify a Grid's rows and columns by using the [**RowDefinitions**](/uwp/api/windows.ui.xaml.controls.grid.rowdefinitions) and [**ColumnDefinitions**](/uwp/api/windows.ui.xaml.controls.grid.columndefinitions) properties.
+The [**Grid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Grid) panel supports fluid layouts and allows you to arrange controls in multi-row and multi-column layouts. You specify a Grid's rows and columns by using the [**RowDefinitions**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.grid.rowdefinitions) and [**ColumnDefinitions**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.grid.columndefinitions) properties.
 
 To position objects in specific cells of the Grid, use the [**Grid.Column**](/dotnet/api/system.windows.controls.grid.column) and [**Grid.Row**](/dotnet/api/system.windows.controls.grid.row) attached properties.
 
@@ -167,9 +167,9 @@ In this example, the sizing works like this:
 
 You can distribute space within a column or a row by using **Auto** or star sizing. You use auto sizing to let UI elements resize to fit their content or parent container. You can also use auto sizing with the rows and columns of a grid. To use auto sizing, set the Height and/or Width of UI elements to **Auto**.
 
-You use proportional sizing, also called *star sizing*, to distribute available space among the rows and columns of a grid by weighted proportions. In XAML, star values are expressed as \* (or *n*\* for weighted star sizing). For example, to specify that one column is 5 times wider than the second column in a 2-column layout, use "5\*" and "\*" for the [**Width**](/uwp/api/windows.ui.xaml.controls.columndefinition.width) properties in the [**ColumnDefinition**](/uwp/api/Windows.UI.Xaml.Controls.ColumnDefinition) elements.
+You use proportional sizing, also called *star sizing*, to distribute available space among the rows and columns of a grid by weighted proportions. In XAML, star values are expressed as \* (or *n*\* for weighted star sizing). For example, to specify that one column is 5 times wider than the second column in a 2-column layout, use "5\*" and "\*" for the [**Width**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.columndefinition.width) properties in the [**ColumnDefinition**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ColumnDefinition) elements.
 
-This example combines fixed, auto, and proportional sizing in a [**Grid**](/uwp/api/Windows.UI.Xaml.Controls.Grid) with 4 columns.
+This example combines fixed, auto, and proportional sizing in a [**Grid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Grid) with 4 columns.
 
 | Column | Sizing | Description |
 | ------ | ------ | ----------- |
@@ -198,13 +198,13 @@ In the Visual Studio XAML designer, the result looks like this.
 
 ## VariableSizedWrapGrid
 
-[**VariableSizedWrapGrid**](/uwp/api/Windows.UI.Xaml.Controls.VariableSizedWrapGrid) is a Grid-style layout panel where rows or columns automatically wrap to a new row or column when the [**MaximumRowsOrColumns**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid.maximumrowsorcolumns) value is reached. 
+[**VariableSizedWrapGrid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.VariableSizedWrapGrid) is a Grid-style layout panel where rows or columns automatically wrap to a new row or column when the [**MaximumRowsOrColumns**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid.maximumrowsorcolumns) value is reached. 
 
-The [**Orientation**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid.orientation) property specifies whether the grid adds its items in rows or columns before wrapping. The default orientation is **Vertical**, which means the grid adds items from top to bottom until a column is full, then wraps to a new column. When the value is **Horizontal**, the grid adds items from left to right, then wraps to a new row.
+The [**Orientation**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid.orientation) property specifies whether the grid adds its items in rows or columns before wrapping. The default orientation is **Vertical**, which means the grid adds items from top to bottom until a column is full, then wraps to a new column. When the value is **Horizontal**, the grid adds items from left to right, then wraps to a new row.
 
-Cell dimensions are specified by the [**ItemHeight**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid.itemheight) and [**ItemWidth**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid.itemwidth). Each cell is the same size. If ItemHeight or ItemWidth is not specified, then the first cell sizes to fit its content, and every other cell is the size of the first cell.
+Cell dimensions are specified by the [**ItemHeight**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid.itemheight) and [**ItemWidth**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid.itemwidth). Each cell is the same size. If ItemHeight or ItemWidth is not specified, then the first cell sizes to fit its content, and every other cell is the size of the first cell.
 
-You can use the [**VariableSizedWrapGrid.ColumnSpan**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid) and [**VariableSizedWrapGrid.RowSpan**](/uwp/api/windows.ui.xaml.controls.variablesizedwrapgrid.getrowspan) attached properties to specify how many adjacent cells a child element should fill.
+You can use the [**VariableSizedWrapGrid.ColumnSpan**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid) and [**VariableSizedWrapGrid.RowSpan**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.variablesizedwrapgrid.getrowspan) attached properties to specify how many adjacent cells a child element should fill.
 
 Here's how to use a VariableSizedWrapGrid in XAML.
 
@@ -230,7 +230,7 @@ In this example, the maximum number of rows in each column is 3. The first colum
 
 ## Canvas
 
-The [**Canvas**](/uwp/api/Windows.UI.Xaml.Controls.Canvas) panel positions its child elements using fixed coordinate points and does not support fluid layouts. You specify the points on individual child elements by setting the [**Canvas.Left**](/dotnet/api/system.windows.controls.canvas.left) and [**Canvas.Top**](/dotnet/api/system.windows.controls.canvas.top) attached properties on each element. The parent Canvas reads these attached property values from its children during the [Arrange](/uwp/api/windows.ui.xaml.uielement.arrange) pass of layout.
+The [**Canvas**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.Canvas) panel positions its child elements using fixed coordinate points and does not support fluid layouts. You specify the points on individual child elements by setting the [**Canvas.Left**](/dotnet/api/system.windows.controls.canvas.left) and [**Canvas.Top**](/dotnet/api/system.windows.controls.canvas.top) attached properties on each element. The parent Canvas reads these attached property values from its children during the [Arrange](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.arrange) pass of layout.
 
 Objects in a Canvas can overlap, where one object is drawn on top of another object. By default, the Canvas renders child objects in the order in which they’re declared, so the last child is rendered on top (each element has a default z-index of 0). This is the same as other built-in panels. However, Canvas also supports the [**Canvas.ZIndex**](/previous-versions/windows/silverlight/dotnet-windows-silverlight/cc190397(v=vs.95)) attached property that you can set on each of the child elements. You can set this property in code to change the draw order of elements during run time. The element with the highest Canvas.ZIndex value draws last and therefore draws over any other elements that share the same space or overlap in any way. Note that alpha value (transparency) is respected, so even if elements overlap, the contents shown in overlap areas might be blended if the top one has a non-maximum alpha value.
 
@@ -255,7 +255,7 @@ Use the Canvas panel with discretion. While it's convenient to be able to precis
 
 ## Panels for ItemsControl
 
-There are several special-purpose panels that can be used only as an [**ItemsPanel**](/uwp/api/windows.ui.xaml.controls.itemscontrol.itemspanel) to display items in an [**ItemsControl**](/uwp/api/Windows.UI.Xaml.Controls.ItemsControl). These are [**ItemsStackPanel**](/uwp/api/Windows.UI.Xaml.Controls.ItemsStackPanel), [**ItemsWrapGrid**](/uwp/api/Windows.UI.Xaml.Controls.ItemsWrapGrid), [**VirtualizingStackPanel**](/uwp/api/Windows.UI.Xaml.Controls.VirtualizingStackPanel), and [**WrapGrid**](/uwp/api/Windows.UI.Xaml.Controls.WrapGrid). You can't use these panels for general UI layout.
+There are several special-purpose panels that can be used only as an [**ItemsPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.itemscontrol.itemspanel) to display items in an [**ItemsControl**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ItemsControl). These are [**ItemsStackPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ItemsStackPanel), [**ItemsWrapGrid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.ItemsWrapGrid), [**VirtualizingStackPanel**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.VirtualizingStackPanel), and [**WrapGrid**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.Controls.WrapGrid). You can't use these panels for general UI layout.
 
 ## Get the sample code
 
diff --git a/hub/apps/develop/ui/navigation/navigate-between-two-pages.md b/hub/apps/develop/ui/navigation/navigate-between-two-pages.md
index a88087fa85..35337f9c3d 100644
--- a/hub/apps/develop/ui/navigation/navigate-between-two-pages.md
+++ b/hub/apps/develop/ui/navigation/navigate-between-two-pages.md
@@ -185,7 +185,7 @@ private void HyperlinkButton_Click(object sender, RoutedEventArgs e)
 // pch.h
 // Add this include in pch.h to support winrt::xaml_typename
 
-#include <winrt/Windows.UI.Xaml.Interop.h>
+#include <winrt/Microsoft.UI.Xaml.Interop.h>
 
 ////////////////////
 // MainPage.xaml.h
@@ -203,7 +203,7 @@ void winrt::BasicNavigation::implementation::MainPage::HyperlinkButton_Click(win
 
 `MainPage` is a subclass of the [Page](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page) class. The `Page` class has a read-only [Frame](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.frame) property that gets the `Frame` containing the `Page`. When the `Click` event handler of the `HyperlinkButton` in `MainPage` calls `Frame.Navigate(typeof(Page2))`, the `Frame` displays the content of `Page2.xaml`.
 
-Whenever a page is loaded into the frame, that page is added as a [PageStackEntry](/uwp/api/Windows.UI.Xaml.Navigation.PageStackEntry) to the [BackStack](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.backstack) or [ForwardStack](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.forwardstack) of the [Frame](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.frame), allowing for [history and backwards navigation](navigation-history-and-backwards-navigation.md).
+Whenever a page is loaded into the frame, that page is added as a [PageStackEntry](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.navigation.pagestackentry) to the [BackStack](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.backstack) or [ForwardStack](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.forwardstack) of the [Frame](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.frame), allowing for [history and backwards navigation](navigation-history-and-backwards-navigation.md).
 
 Now, do the same in `Page2.xaml`. Replace the existing page content with the following content:
 
@@ -351,7 +351,7 @@ Page content and state is not cached by default, so if you'd like to cache infor
 
 In our basic peer-to-peer example, when you click the `Click to go to page 1` link on `Page2`, the `TextBox` (and any other field) on `MainPage` is set to its default state. One way to work around this is to use the [NavigationCacheMode](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.navigationcachemode) property to specify that a page be added to the frame's page cache.
 
-By default, a new page instance is created with its default values every time navigation occurs. In `MainPage.xaml`, set `NavigationCacheMode` to `Enabled` (in the opening `Page` tag) to cache the page and retain all content and state values for the page until the page cache for the frame is exceeded. Set [NavigationCacheMode](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.navigationcachemode) to [Required](/uwp/api/Windows.UI.Xaml.Navigation.NavigationCacheMode) if you want to ignore [CacheSize](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.cachesize) limits, which specify the number of pages in the navigation history that can be cached for the frame. However, keep in mind that cache size limits might be crucial, depending on the memory limits of a device.
+By default, a new page instance is created with its default values every time navigation occurs. In `MainPage.xaml`, set `NavigationCacheMode` to `Enabled` (in the opening `Page` tag) to cache the page and retain all content and state values for the page until the page cache for the frame is exceeded. Set [NavigationCacheMode](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.page.navigationcachemode) to [Required](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.navigation.navigationcachemode) if you want to ignore [CacheSize](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.frame.cachesize) limits, which specify the number of pages in the navigation history that can be cached for the frame. However, keep in mind that cache size limits might be crucial, depending on the memory limits of a device.
 
 ```xaml
 <Page