Fix LICH CRC having been included in the bit count.

Based of current implementations and history of the protocol the LICH CRC appeared to have been accidentally counted in the bits.

pages/04.appendix/04.ip-networking/docs.md

@@ -25,7 +25,7 @@ Field          | Size     | Description
 -----          | ----     | -----------
 MAGIC          | 32 bits  | Magic bytes 0x4d313720 (“M17 “)
 StreamID (SID) | 16 bits  | Random bits, changed for each PTT or stream, but consistent from frame to frame within a stream
-LICH           | 240 bits | The meaningful contents of a LICH frame (dst, src, streamtype, META field, CRC16) as defined earlier.
+LICH           | 224 bits | The meaningful contents of a LICH frame (dst, src, streamtype, META field) as defined earlier.
 FN             | 16 bits  | Frame number (exactly as would be transmitted as an RF stream frame, including the last frame indicator at (FN & 0x8000)
 Payload        | 128 bits | Payload (exactly as would be transmitted in an RF stream frame)
 CRC16          | 16 bits  | CRC for the entire packet, as defined earlier [CRC definition](https://spec.m17project.org/part-1/data-link-layer#crc)
@@ -96,4 +96,4 @@ Bytes | Purpose
 Bytes | Purpose
 ----- | -------
 0..3  | Magic - ASCII "DISC"
-4..9  | 6-byte ‘From’ callsign including module in last character (e.g. “A1BCD D”) encoded as per Address Encoding
+4..9  | 6-byte ‘From’ callsign including module in last character (e.g. “A1BCD D”) encoded as per Address Encoding