Fix dead links

Author: niels9001

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "hub/apps/windows-app-sdk/composition.md",
+      "redirect_url": "/windows/apps/develop/composition/visual-layer",
+      "redirect_document_id": false
+    },
     {
       "source_path": "hub/apps/design/shell/tiles-and-notifications/notification-mirroring.md",
       "redirect_url": "/previous-versions/windows/uwp/notifications/notification-mirroring",

hub/apps/develop/composition/composition-lighting.md

@@ -76,7 +76,7 @@ Depending on the type of light used, a light can have properties for attenuation
 
 Property | Description
 --- | ---
-**Color** | The [Color](/uwp/api/windows.ui.color) of the light. Lighting color values are defined by [D3D](../graphics-concepts/light-properties.md) Diffuse, Ambient, and Specular that defines the color being emitted. Lighting uses RGBA values for lights; the alpha color component is not used.
+**Color** | The [Color](/uwp/api/windows.ui.color) of the light. Lighting color values are defined by [D3D](/windows/win32/direct3d9/light-properties) Diffuse, Ambient, and Specular that defines the color being emitted. Lighting uses RGBA values for lights; the alpha color component is not used.
 **Direction** | The direction of light. The direction in which the light is pointing is specified relative to its [CoordinateSpace](/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.distantlight.coordinatespace) Visual.
 **Coordinate Space** | Every Visual has an implicit 3D coordinate space. X direction is from left to right. Y direction is from top to bottom. Z direction is a point out of the plane. The original point of this coordinate is the upper-left corner of the visual, and the unit is Device Independent Pixel (DIP). A light's offset is defined in this coordinate.
 **Inner and Outer Cones** | Spotlights emit a cone of light that has two parts: a bright inner cone and an outer cone. Composition allows you control over inner and outer cone angles and color.
@@ -155,8 +155,8 @@ CompositionBrush CreateNormalMapBrush(ICompositionSurface normalMapImage)
 ## Related articles
 
 - [Creating Materials and Lights in the Visual Layer](https://blogs.windows.com/buildingapps/2017/08/04/creating-materials-lights-visual-layer/)
-- [Lighting Overview](../graphics-concepts/lighting-overview.md)
+- [Lighting Overview](/windows/win32/direct3d9/lighting-overview)
 - [CompositionCapabilities API](/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.compositioncapabilities)
-- [Mathematics of Lighting](../graphics-concepts/mathematics-of-lighting.md)
+- [Mathematics of Lighting](/windows/win32/direct3d9/mathematics-of-lighting)
 - [SceneLightingEffect](/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.effects.scenelightingeffect)
 - [WindowsCompositionSamples GitHub Repo](https://github.com/microsoft/WindowsCompositionSamples)

hub/apps/develop/composition/composition-native-interop.md

@@ -42,7 +42,7 @@ For performance reasons, when an application calls [**BeginDraw**](/windows/desk
 
 The following code example illustrates an interoperation scenario for composition interop in a Windows App SDK context. The example combines types from the Windows Runtime-based surface area of Microsoft.UI.Composition, together with types from the interop headers, and code that renders text using the COM-based DirectWrite and Direct2D APIs. The example uses [**BeginDraw**](/windows/desktop/api/windows.ui.composition.interop/nf-windows-ui-composition-interop-icompositiondrawingsurfaceinterop-begindraw) and [**EndDraw**](/windows/desktop/api/windows.ui.composition.interop/nf-windows-ui-composition-interop-icompositiondrawingsurfaceinterop-enddraw) to make it seamless to interoperate between these technologies. The example uses DirectWrite to lay out the text, and then it uses Direct2D to render it. The composition graphics device accepts the Direct2D device directly at initialization time. This allows **BeginDraw** to return an **ID2D1DeviceContext** interface pointer, which is considerably more efficient than having the application create a Direct2D context to wrap a returned ID3D11Texture2D interface at each drawing operation.
 
-To try out the C++/WinRT code example below, first create a new WinUI app project in Visual Studio (for requirements, see [Visual Studio support for C++/WinRT](../cpp-and-winrt-apis/intro-to-using-cpp-with-winrt.md#visual-studio-support-for-cwinrt-xaml-the-vsix-extension-and-the-nuget-package)). Replace the contents of your `pch.h` and `App.cpp` source code files with the code listings below, then build and run. The application renders the string "Hello, World!" in black text on a transparent background.
+To try out the C++/WinRT code example below, first create a new WinUI app project in Visual Studio (for requirements, see [Visual Studio support for C++/WinRT](/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt#visual-studio-support-for-cwinrt-xaml-the-vsix-extension-and-the-nuget-package)). Replace the contents of your `pch.h` and `App.cpp` source code files with the code listings below, then build and run. The application renders the string "Hello, World!" in black text on a transparent background.
 
 ```cppwinrt
 // NOTE: This example uses UWP-specific APIs. For WinUI, replace CoreWindow with your app's Window handle.

hub/apps/develop/composition/using-the-visual-layer-with-xaml.md

@@ -191,7 +191,7 @@ private void InitializeDropShadow(UIElement shadowHost, Shape shadowTarget)
 }
 ```
 
-The following listing shows the [C++/WinRT](../cpp-and-winrt-apis/index.md) equivalent of the previous C# code using the same XAML structure.
+The following listing shows the [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/) equivalent of the previous C# code using the same XAML structure.
 
 ```cppwinrt
 #include <winrt/Microsoft.UI.Composition.h>

hub/apps/develop/composition/visual-layer.md

@@ -76,7 +76,7 @@ The **Microsoft.UI.Composition** compositor runs entirely within a Windows App S
 
 An example of external content is the (**Microsoft.UI.Xaml.Controls**) [MediaPlayerElement](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mediaplayerelement). The Windows media stack provides to XAML an opaque media swap chain handle. XAML gives that handle to the compositor, which in turn hands it off to Windows (via **Windows.UI.Composition**) to display. Since the compositor can't see any of the pixels in the media swap chain, it can't composite that as part of the overall rendering for the window. Instead, it gives the media swap chain to Windows to render it below the compositor's rendering, with a hole cut out of the compositor's rendering in order to allow the media swap chain below it to be visible.
 
-[![Diagram of rendering external content](../windows-app-sdk/images/external-content.png) ](../windows-app-sdk/images/external-content.png#lightbox)
+[![Diagram of rendering external content](../../windows-app-sdk/images/external-content.png) ](../../windows-app-sdk/images/external-content.png#lightbox)
 
 In the Windows App SDK/WinUI, the following APIs all create external content:
 
@@ -103,4 +103,4 @@ Explore the samples on GitHub: [WindowsAppSDK-Samples / SceneGraph](https://gith
 ## Related topics
 
 * [**Microsoft.UI.Composition API reference**](/windows/windows-app-sdk/api/winrt/microsoft.ui.composition)
-* [Using the Visual layer in desktop apps](../desktop/modernize/ui/visual-layer-in-desktop-apps.md)
+* [Using the Visual layer in desktop apps](../../desktop/modernize/ui/visual-layer-in-desktop-apps.md)

hub/apps/develop/composition/xaml-lighting.md

@@ -258,7 +258,7 @@ struct MainPage : MainPageT<MainPage>
 You can then apply this light to any XAML UIElement or Brush to light them. This example shows different potential usages.
 
 > [!Important]
-> For [C++/WinRT](../cpp-and-winrt-apis/intro-to-using-cpp-with-winrt.md), remove the two occurrences of `local:OrangeSpotLight.IsTarget="True"` from the markup below. The attached properties are already set in code-behind.
+> For [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt), remove the two occurrences of `local:OrangeSpotLight.IsTarget="True"` from the markup below. The attached properties are already set in code-behind.
 
 ```xaml
 <StackPanel Width="100">

hub/apps/windows-app-sdk/migrate-to-windows-app-sdk/what-is-supported.md

@@ -17,7 +17,7 @@ WinUI and the Windows App SDK are new technologies and, when compared to UWP, th
 | [Background tasks](/windows/uwp/launch-resume/create-and-register-a-winmain-background-task) | ✅ Supported; see [BackgroundTaskBuilder](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.background.backgroundtaskbuilder) (introduced in 1.7). |
 | Common UI controls | ✅ Supported |
 | [CameraCaptureUI](https://github.com/microsoft/WindowsAppSDK/pull/4721) | ✅ Supported; see [CameraCaptureUI](/windows/windows-app-sdk/api/winrt/microsoft.windows.media.capture) (introduced in 1.7). For alternative APIs, see [Using video capture](/windows/win32/multimedia/using-video-capture). |
-| [Composition/DirectX interop](https://github.com/microsoft/microsoft-ui-xaml/issues/5025) | ✅ Most Composition and Drawing features are supported (global composition effects aren't supported in 1.7); see [Enhance UI with the Visual layer](../composition.md). |
+| [Composition/DirectX interop](https://github.com/microsoft/microsoft-ui-xaml/issues/5025) | ✅ Most Composition and Drawing features are supported (global composition effects aren't supported in 1.7); see [Enhance UI with the Visual layer](../develop/composition/visual-layer.md). |
 | Distributing via Store | ✅ Supported |
 | Live Tiles (on Windows 10) | ✅ Supported |
 | [MapControl](/uwp/api/windows.ui.xaml.controls.maps.mapcontrol) | ✅ Supported; see [MapControl](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.mapcontrol) (introduced in 1.5). |