From dde099104a11f03923195cee4b7b90c1e885c639 Mon Sep 17 00:00:00 2001
From: Matt Wojciakowski <mattwoj@microsoft.com>
Date: Tue, 19 Nov 2024 13:58:34 -0800
Subject: [PATCH] Fix warnings (#2065)

---
 WSL/build-custom-distro.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/WSL/build-custom-distro.md b/WSL/build-custom-distro.md
index 1005d8bb..d54348b3 100644
--- a/WSL/build-custom-distro.md
+++ b/WSL/build-custom-distro.md
@@ -104,7 +104,7 @@ done
 
 WSL automatically generates a Windows Terminal profile when a distribution is installed. Distribution maintainers can customize the generated profile generated by setting ` windowsterminal.profileTemplate` in the WSL configuration file, `/etc/wsl-distribution.conf`. 
 
-The json file follows [the terminal profile json format](https://learn.microsoft.com/en-us/windows/terminal/json-fragment-extensions#structure-of-the-json-files).  Here’s an example profile: 
+The json file follows [the terminal profile json format](/windows/terminal/json-fragment-extensions#structure-of-the-json-files).  Here’s an example profile: 
 
 ```
 
@@ -157,7 +157,7 @@ The distribution author determines whether systemd is enabled by default by sett
 
 See the [Systemd recommendations](#systemd-recommendations) if you chose to enable systemd by default.
 
-See [Advanced settings configuration in WSL](./wsl-config#wslconf) for all supported settings in `/etc/wsl.conf`.
+See [Advanced settings configuration in WSL](./wsl-config.md) for all supported settings in `/etc/wsl.conf`.
 
 ### Create the tar file
 
@@ -178,7 +178,7 @@ See the [Configuration file recommendations](#configuration-file-recommendations
 
 To obtain a tar file of an existing Linux distribution, find guidance on how to export a docker container in [Import any Linux distribution to use with WSL](./use-custom-distro.md).
 
-Once the tar file archive is ready, see [Overriding the distribution manifest](#adding-your-distro-to-wsl---install-for-your-enterprise-or-group) to try it out locally.
+Once the tar file archive is ready, see [Test the distribution locally](#test-the-distribution-locally) to try it out locally.
 
 ## Create a .wsl file extension
 
@@ -252,7 +252,7 @@ $ wsl --install my-distro-v2 # Installs 'my-distro-v2' explicitly
 
 ## Adding your distribution to `wsl --install` for all WSL users
 
-To make your WSL distribution available to all users, open a pull request on the [WSL GitHub repository](github.com/microsoft/wsl) that modifies the [DistributionInfo.json](https://github.com/microsoft/WSL/blob/master/distributions/DistributionInfo.json) file to include your distribution information. 
+To make your WSL distribution available to all users, open a pull request on the [WSL GitHub repository](https://github.com/microsoft/wsl) that modifies the [DistributionInfo.json](https://github.com/microsoft/WSL/blob/master/distributions/DistributionInfo.json) file to include your distribution information. 
 
 This pull request will be reviewed by the WSL team.
 
@@ -269,7 +269,7 @@ Both registry values are strings (REG_SZ) and are expected to be in URL format.
 
 Starting with WSL release 2.4.4, the `file://` protocol is supported to make local testing easier. The expected format is: `file:///C:/path/to/file`.
 
-### Testing a local distribution
+### Test the distribution locally
 
 To test a distribution tar, you can use the following sample powershell script to override the distribution manifest with the new distribution. First save the script below as `override-manifest.ps1`: