fix: rewrite internals page

Author: zlataovce

src/content/docs/paper/dev/misc/internal-code.md

@@ -8,7 +8,7 @@ The code that runs Minecraft is not open source. Bukkit is an API that allows pl
 is implemented by CraftBukkit and interacts with Minecraft's code. You will often hear the terms NMS and CraftBukkit
 when talking about Minecraft internals.
 
-:::danger[Using Minecraft Internals]
+:::danger[Using Minecraft internals]
 
 Using Minecraft internals is not recommended. This is because using internal code directly is not guaranteed to be
 stable and it changes often. This means that your plugin may break when a new version of Minecraft is released.
@@ -24,7 +24,7 @@ NMS stands for `net.minecraft.server` and refers to a Java package that contains
 proprietary and is not open source. This code is not guaranteed to be stable when invoked externally and may change at
 any time.
 
-## Accessing Minecraft Internals
+## Accessing Minecraft internals
 
 In order to use Mojang and CraftBukkit code, you may either use the `paperweight-userdev` Gradle plugin or use reflection.
 [`paperweight-userdev`](https://github.com/PaperMC/paperweight-test-plugin) is the recommended way to access internal code
@@ -42,17 +42,12 @@ you should cache the [`Field`](jd:java:java.lang.reflect.Field)/
 [`Method`](jd:java:java.lang.reflect.Method) to prevent the performance
 impact of looking up the field/method each time.
 
-The internal CraftBukkit code is relocated to `org.bukkit.craftbukkit.<version>` unless you run a Mojang-mapped version
-of Paper. This is unlikely to be the case in most production environments. This means that any attempts to reflect must
-include the version. For example, `org.bukkit.craftbukkit.v1_20_R2.CraftServer` is the full class and package name
-for the CraftServer class in version 1.20.2. You can access these classes easily with some reflection utilities.
+:::caution[1.20.4 and older]
 
-:::caution[Removal of relocation in 1.20.5]
-
-As of 1.20.5, the versioned relocation of the CraftBukkit package was removed and
-CraftBukkit packages are now located in `org.bukkit.craftbukkit` and not in `org.bukkit.craftbukkit.<version>`.
-
-:::
+The internal CraftBukkit code was relocated to `org.bukkit.craftbukkit.<version>` unless you ran a Mojang-mapped version
+of Paper. This was unlikely to be the case in most production environments until 1.20.5. This means that any attempts to reflect had to
+include the version. For example, `org.bukkit.craftbukkit.v1_20_R2.CraftServer` was the full class and package name
+for the CraftServer class in version 1.20.2. You could access these classes easily with some reflection utilities.
 
 ```java
 private static final String CRAFTBUKKIT_PACKAGE = Bukkit.getServer().getClass().getPackageName();
@@ -65,28 +60,30 @@ public static String cbClass(String clazz) {
 Class.forName(cbClass("entity.CraftBee"));
 ```
 
-Minecraft's code is obfuscated. This means that the names of classes and methods are changed to make them harder to
-understand. Paper deobfuscates these identifiers for development; however, to provide compatibility with legacy plugins,
-Paper is re-obfuscated at runtime. You can use a library like [reflection-remapper](https://github.com/jpenilla/reflection-remapper) to automatically remap the
-reflection references. This will allow you to use the de-obfuscated, Mojang-mapped, names in your code. This is recommended as
-it makes the code easier to understand.
+:::
 
-### Mojang-Mapped Servers
+Minecraft's code is obfuscated. This means that the names of classes and methods are changed to make them harder to
+understand. Paper deobfuscates these identifiers for development and since 1.20.5, also for runtime.
 
-:::note[Mojang-mapped runtime as of 1.20.5]
+:::caution[1.20.4 and older]
 
-As of 1.20.5, Paper ships with a Mojang-mapped runtime instead of reobfuscating the server to Spigot mappings.
-For more information, see the [plugin remapping](/paper/dev/project-setup#plugin-remapping) section and [userdev](/paper/dev/userdev#1205-and-beyond) documentation covering these changes.
+Previously, to provide compatibility with legacy plugins, Paper was reobfuscated at runtime.
+You could use a library like [reflection-remapper](https://github.com/jpenilla/reflection-remapper) to automatically remap the
+reflection references. This allowed you to use the deobfuscated, Mojang-mapped names in your code. This was recommended as
+it made the code easier to understand.
 
 :::
 
-Running a Mojang-Mapped (moj-map) server is an excellent way to streamline your processes because you can develop using
-the same mappings that will be present at runtime. This eliminates the need for remapping in your compilation. If you
-are creating custom plugins for your server, we highly recommend running a moj-map server. It simplifies debugging and
-allows you to hotswap plugins.
+### Mojang-mapped servers
+
+Running a Mojang-mapped (moj-map) server is an excellent way to streamline your processes because you can develop using
+the same mappings that will be present at runtime. This eliminates the need for remapping in your compilation, which in
+turn simplifies debugging and allows you to hotswap plugins.
 
-In the future, the Paper server will no longer undergo remapping. By adopting Mojang mappings now, you can ensure that
-your plugin won't require internal remapping when we make the switch.
+As of 1.20.5, Paper ships with a Mojang-mapped runtime by default instead of reobfuscating the server to Spigot mappings.
+By adopting Mojang mappings, you ensure that your plugin won't require internal remapping at runtime.
+For more information, see the [plugin remapping](/paper/dev/project-setup#plugin-remapping) section
+and [userdev](/paper/dev/userdev#1205-and-beyond) documentation covering these changes.
 
 ### Getting the current Minecraft version