Update README.md

README.md

@@ -32,14 +32,12 @@ The `localisation_packet_payload` length depends on the `localisation_packet_typ
 
 ### Header structure
 
-|         4b         |             1b              |           4b          |            4b              |    3b    |
-|--------------------|-----------------------------|-----------------------|----------------------------|----------|
-| `protocol_version` | `movement_id_presence_flag` | `source_address_size` | `localisation_packet_type` | reserved |
+|         4b         |           4b          |            4b              |             1b              |    3b    |
+|--------------------|-----------------------|----------------------------|-----------------------------|----------|
+| `protocol_version` | `source_address_size` | `localisation_packet_type` | `movement_id_presence_flag` | reserved |
 
 The `protocol_version` field indicates the version of the localisation packet used. This documentation describes the version #1 of the localisation packet protocol.
 
-The `movement_id_presence_flag` must be set to 1 if the `movement_id` field is present in the packet.
-
 The `source_address_size` indicates the number of Bytes of the adresse of the sender. A length of 0 means that no source address is present in the packet.
 
 The `localisation_packet_type` indicates the structure of the payload. These types of packet have been described:
@@ -47,6 +45,8 @@ The `localisation_packet_type` indicates the structure of the payload. These typ
   * `type 0` : Universal GNSS localisation
   * `type 1` : Locally referenced localisation
 
+The `movement_id_presence_flag` must be set to 1 if the `movement_id` field is present in the packet.
+
 ### Payload structure by packet type
 
 #### Type 0 : Universal GNSS localisation