From 0daaa8d5b16ed0837f4dc688eb1dab2e974dc92e Mon Sep 17 00:00:00 2001
From: Raymond <101374892+raymonable@users.noreply.github.com>
Date: Mon, 30 Jan 2023 21:16:04 -0500
Subject: [PATCH] Add additional info about the topic.

---
 docs/Common Issues/RakNet Removal of Authorization.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/docs/Common Issues/RakNet Removal of Authorization.md b/docs/Common Issues/RakNet Removal of Authorization.md
index 0c8415e..702ccec 100644
--- a/docs/Common Issues/RakNet Removal of Authorization.md	
+++ b/docs/Common Issues/RakNet Removal of Authorization.md	
@@ -3,8 +3,11 @@ Guide created by Raymond, with lots of help by Yakov
 
 <hr>
 
-We're jumping around a function inside of RakPeer.cpp.
-Note that this method is more secure than setting the FFlag, but it *could* cause issues down the line (*client incompatibility, so on*)
+This was made for users who are having trouble connecting to their `RCCService` due to invalid RakNet keys.<br>
+This is *technically* more secure than setting the FFlag, but it *could* cause issues down the line (you'll probably be fine.)
+
+We're jumping around a function inside of RakPeer.cpp,<br>
+essentially we're just guiding the program around the code that'll check if it's a valid key and shooting right towards the `return true`.
 
 Pattern used: `6A016A088D45` (This was created from a 2017L build, it may have been changed in newer builds, but that's unlikely.)
 
@@ -17,4 +20,5 @@ Instructions to modify, starting from the first `nop` above the `push 1 & push 8
 	2. First `jne`, should be the **same instruction** as the `je` we just changed *(make sure the address to jump is modified too.)*<br>
 	3. And the first `jne` above the `nop`, of which was mentioned earlier.
 
-Save the patches, and try launching RCC. It should be able to connect without having to authorize your client passwords.
+Save the patches, and try launching RCC.<br>
+It should be able to connect without having to authorize your client passwords.