From dd3946d409254a4aeb35055286525da207bc0fa2 Mon Sep 17 00:00:00 2001
From: MCDeltaT <68516357+MustardChef@users.noreply.github.com>
Date: Thu, 19 Jan 2023 20:22:18 +0000
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index d9f32ac..e9ea304 100644
--- a/README.md
+++ b/README.md
@@ -85,8 +85,8 @@
    What `Add-AppxPackage -Register .\AppxManifest.xml` does is to register an appx package with some existing unpackaged files,
    so you need to keep them as long as you want to use WSA.
    Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
-3. You need to register your WSA appx package before you can run WSA (the 8th step in the instructions).
-   For [MagiskOnWSALocal](https://github.com/LSPosed/MagiskOnWSALocal) users, you need to run `Run.bat` in the extracted dir.
+3. You need to register your WSA appx package before you can run WSA.
+   For [WSABuilds](https://github.com/MustardChef/WSABuilds) and [MagiskOnWSALocal](https://github.com/LSPosed/MagiskOnWSALocal) users, you need to run `Run.bat` in the extracted dir.
    If the script fails, you can take the following steps for diagnosis (admin privilege required):
     1. Open a PowerShell window and change working directory to your WSA directory.
     2. Run `Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml` in PowerShell.