Merge pull request #31 from VirxEC/fix

32-bit -> 16-bit

Author: NicEastvillage

docs/v5/framework/sockets-specification.md

@@ -10,7 +10,7 @@ Packet types are named from the POV of the sender.
 - [CorePacket](https://github.com/RLBot/flatbuffers-schema/blob/main/schema/corepacket.fbs) - Wraps `CoreMessage`, a union of all valid message types that can be sent _by_ RLBotServer, _to_ interfaces.
 
 ??? question "What is an interface? What is core?"
-    - "Interface" refers to the layer of abstraction that sits in between the RLBotServer API and the bot/script someone wants to make. While not strictly required, it a good interface makes working with RLBot fun & easy - even without knowing anything about TCP, FlatBuffers, or the RLBotServer API.
+    - "Interface" refers to the layer of abstraction that sits in between the RLBotServer API and the bot/script someone wants to make. While not strictly required, a good interface makes working with RLBot fun & easy - even without knowing anything about TCP, FlatBuffers, or the RLBotServer API.
     - "Core" refers to RLBotServer itself, which is considered the shared "core" of RLBot that implements various functions related to starting and running matches that are accessable via the RLBotServer API.
 
 ## Connecting to RLBotServer
@@ -22,10 +22,10 @@ Packet types are named from the POV of the sender.
 ## Packet format
 
 This project uses [FlatBuffers](https://flatbuffers.dev/) as the data format,
-prefixed with a 32-bit unsigned integer.
+prefixed with a 16-bit unsigned integer.
 All packets should be big endian.
 
-- Read the first 32 bits as an unsigned integer. This is `n`, the length of the flatbuffer in bytes.
+- Read the first 16 bits as an unsigned integer. This is `n`, the length of the flatbuffer in bytes.
 - Read `n` bytes, and deserialize this into the correct flatbuffer according to the data type.
 
 Replace "read" with "write" to send a packet.