From eff503cd93ec505e7848c1a7b632590a75b1d45b Mon Sep 17 00:00:00 2001
From: Ahnaf Mahmud <44692189+infinitepower18@users.noreply.github.com>
Date: Sun, 12 Nov 2023 12:32:21 +0000
Subject: [PATCH] Update WSA-Sideloader.md
---
.../Usage Guides/Sideloading Guides/WSA-Sideloader.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/Usage Guides/Sideloading Guides/WSA-Sideloader.md b/Documentation/Usage Guides/Sideloading Guides/WSA-Sideloader.md
index 0354561..1480c15 100644
--- a/Documentation/Usage Guides/Sideloading Guides/WSA-Sideloader.md
+++ b/Documentation/Usage Guides/Sideloading Guides/WSA-Sideloader.md
@@ -21,7 +21,7 @@ Operating System|Downloads
***Step 1. Once installed, you should see this screen:***
-
+
> [!NOTE]
> If you get a message that says WSA is not installed, check that you have downloaded and installed WSA correctly as per the WSABuilds instructions.
@@ -36,13 +36,13 @@ Operating System|Downloads
***Step 3. Now, you can click the Browse button to select your APK file. You can also double click a file in File Explorer to automatically open WSA Sideloader with the APK file already selected.***
-
+
***Step 4. The first time you install an APK, it will ask to allow ADB debugging. Allow it and attempt the installation again. Check the always allow box if you don't want to manually accept the permission every time you install an app.***
-
+
@@ -70,7 +70,7 @@ Therefore, it's highly recommended you keep it up to date.
## Troubleshooting
If you get an error like the one below, check that you have allowed the ADB authorization and enabled Developer Mode. Also try disabling and enabling USB debugging under manage developer settings as that can sometimes fix issues with the ADB connection.
-
+
If you get a message saying `No connection could be made because the target machine actively refused it`, follow [this guide](https://github.com/MustardChef/WSABuilds/blob/master/Documentation/Fix%20Guides/Post-Install%20Issues/TargetMachineActivelyRefusedConnection.md)