Update post

content/news/20.2release.md

@@ -3,6 +3,7 @@ title: "NeoForge 20.2 for Minecraft 1.20.2"
 date: 2023-10-30T19:50:00+01:00
 categories:
 - News
+- Releases
 author: neoforgedteam
 summary: |
     All you need to know about NeoForge 20.2, now released for Minecraft 1.20.2.

content/news/20.3release.md

@@ -3,6 +3,7 @@ title: "NeoForge 20.3 for Minecraft 1.20.3 and 1.20.4"
 date: 2023-12-05T20:25:00+01:00
 categories:
 - News
+- Releases
 author: neoforgedteam
 summary: |
     All you need to know about NeoForge 20.3, now released for Minecraft 1.20.3.

content/news/20.5release.md

@@ -3,6 +3,7 @@ title: "NeoForge 20.5 for Minecraft 1.20.5"
 date: 2024-04-23T22:50:00+02:00
 categories:
 - News
+- Releases
 author: neoforgedteam
 summary: |
     All you need to know about NeoForge 20.5, now released for Minecraft 1.20.5.

content/news/21.0release.md

@@ -13,27 +13,27 @@ description: "All you need to know about NeoForge 21.0, now released for Minecra
 It's that time of the year again! Mojang has just released a new Minecraft major version: 1.21, followed by the first beta release of NeoForge 21.0.
 
 ## Previous changes
-Before diving into the changes brought by 1.21, we would like to quickly go through the changes made to NeoForge since 1.20.1, for those that haven't updated all the way to 1.20.6. You will also find the respective blog posts for each version outlining important Vanilla changes:
+Before diving into the changes brought by 1.21, we would like to quickly go through the changes made to NeoForge since 1.20.1, for those that haven't updated all the way to 1.20.6. You will also find the respective blog posts for each version, outlining important Vanilla changes:
 
 - [1.20.2](20.2release.md):
   - The package renames
   - The [EventBus changes](20.2eventbus-changes.md)
-  - The [registry rework](20.2registry-rework.md)
+  - The [Registry Rework](20.2registry-rework.md)
 - [1.20.3](20.3release.md):
-  - The [capability rework](20.3capability-rework.md)
+  - The [Capability Rework](20.3capability-rework.md)
 - 1.20.4:
-  - The introduction of [data maps](https://github.com/neoforged/NeoForge/pull/519)
-  - The [networking refactor](20.4networking-refactor.md)
+  - The introduction of [Data Maps](https://github.com/neoforged/NeoForge/pull/519)
+  - The [Networking Refactor](20.4networking-refactor.md)
   - The [switch to Fabric Mixin](https://github.com/neoforged/FancyModLoader/pull/94)
 - [1.20.5](20.5release.md):
   - The `mods.toml` file was renamed to `neoforge.mods.toml`
-  - The [second networking rework](20.5release/#network-api-rework)
-  - The [Tick event refactor](https://github.com/neoforged/NeoForge/pull/542)
+  - The [Second Networking Rework](20.5release/#network-api-rework)
+  - The [Tick Event Refactor](https://github.com/neoforged/NeoForge/pull/542)
 - 1.20.6:
   - The [removal of `Event.Result`](https://github.com/neoforged/NeoForge/pull/588)
 
 ## The Vanilla 1.21 changes
-And now, let's get into the most important changes in Vanilla.  
+Now, let's get into the most important changes in Vanilla.  
 
 First of all, the `ResourceLocation` constructors were made private, and replaced with static factory methods:
 - `ResourceLocation#fromNamespaceAndPath`: takes in the namespace and the path of the resource location. This is functionally equivalent to the `ResourceLocation(String, String)` constructor in 1.20.6 and below. Accompanied by `#tryBuild` which returns `null` instead of throwing if the parameters aren't valid.
@@ -52,8 +52,8 @@ Several data folder names that were plural have been renamed:
 - `advancements` -> `advancement`
 
 ### Data-driven enchantments
-Enchantments are no longer a static, built-in registry, and instead are a datapack registry.  
-With this change, methods that previously took an `Enchantment` will now take a `Holder<Enchantment>`, and all fields in the `Enchantments` class are `ResourceKey<Enchantment>`s.  
+Enchantments are no longer a static, built-in registry, and are instead a datapack registry.  
+With this change, methods that previously took an `Enchantment` will now take a `Holder<Enchantment>` (which can be grabbed from a registry obtained through a level's `RegistryAccess`), and all fields in the `Enchantments` class are `ResourceKey<Enchantment>`s.  
 Additionally, your code should now use `EnchantmentEffectComponents` to determine whether an enchantment should affect something, instead of relying on direct level checks.
 
 For more information, we encourage you to consult [ChampionAsh](https://github.com/ChampionAsh5357)'s [1.21 primer](https://gist.github.com/ChampionAsh5357/d895a7b1a34341e19c80870720f9880f).