Get ready for 20.3 release

content/news/20.3capability-rework.md

@@ -1,6 +1,6 @@
 ---
 title: "The Capability rework"
-date: 2023-12-04T19:00:00+01:00 # TODO: change time to be after the 20.3 release post
+date: 2023-12-05T20:30:00+01:00
 categories:
 - News
 author: technici4n
@@ -88,14 +88,14 @@ chunk.setUnsaved(true); // must be done manually because we did not use setData
 
 Before we move on to capabilities, here are a few points to take note of with respect to the data attachment system:
 - **Level attachments were removed**: please use SavedData instead.
-- Item stack attachments are always synced with the client now.
+- Serializable item stack attachments are always synced with the client now.
 - Entity attachments are copied when a player is teleported back from the end. (Previously this was not the case).
 - Entity attachments that have `copyOnDeath` set in their builder will automatically be copied on player death (and on mob conversion).
 
 ### Future work for attachments
 We have plans to work on the following improvements to the attachment system over the coming weeks:
 - **Attachments in recipe JSONs**: Just like we add support for count and NBT to recipe results, we will add support to specify data attachments in recipe result JSONs.
-- **Syncable data attachments**: Currently, all item stack attachments are synced automatically from the logical server to the logical client.
+- **Syncable data attachments**: Currently, all serializable item stack attachments are synced automatically from the logical server to the logical client.
 We will look into opt-in syncing for block entity, chunk, and entity attachments in the future.
 - **Custom copy handler**: Currently, all data attachments are copied by serializing to NBT and then deserializing a new copy.
 This is a good default, but we want to allow modders to provide their own copy implementation for better performance.
@@ -184,7 +184,7 @@ if (object != null) {
 }
 ```
 
-Block capabilities are used different, to accommodate for capabilities provided by blocks without block entities.
+Block capabilities are used differently, to accommodate for capabilities provided by blocks without block entities.
 The query is performed on a `level`:
 ```java
 var object = level.getCapability(CAP, pos, context);
@@ -401,8 +401,8 @@ Otherwise:
 | `player.getCapability(..., null)` | `player.getCapability(Capabilities.ItemHandler.ENTITY)` |
 
 ### Future plans for capabilities
-Composters NeoForge now support the item handler capability. However, cauldrons still do not support the fluid handler capability. This will be addressed in the coming weeks, and mods using the block fluid handler capability will work with cauldrons out of the box.
+Composters now support the item handler capability. However, cauldrons still do not support the fluid handler capability. This will be addressed in the coming weeks, and mods using the block fluid handler capability will work with cauldrons out of the box.
 
-We have reviewed and tested this capability overhaul extensively. Nonehtless, we expect that issues will be discovered after the release. Please don't hesitate to get in touch with us, be it on Discord or GitHub!
+We have reviewed and tested this capability overhaul extensively. Nonetheless, we expect that issues will be discovered after the release. Please don't hesitate to get in touch with us, be it on Discord or GitHub!
 
 That's all for now, happy porting!

content/news/20.3release.md

@@ -1,6 +1,6 @@
 ---
 title: "NeoForge 20.3 for Minecraft 1.20.3"
-date: 2023-11-30T19:50:00+01:00 # TODO: update time
+date: 2023-12-05T20:25:00+01:00
 categories:
 - News
 author: neoforgedteam
@@ -10,7 +10,7 @@ description: |
     All you need to know about NeoForge 20.3, now released for Minecraft 1.20.3.
 ---
 
-The first beta release of NeoForge for Minecraft 1.20.3, NeoForge 20.3.TODO-beta is now released! <!-- TODO update version (you can never be sure that it will be .1 :D) -->
+The first beta release of NeoForge for Minecraft 1.20.3, NeoForge 20.3.1-beta is now released!
 Please try it out, play with it, develop with it, and give us feedback!
 **We are not stable yet**, so expect a few breaking changes in the coming weeks.