SpaceTeam · carofcons · Mar 28, 2026 · Mar 28, 2026 · Copilot · Mar 28, 2026
diff --git a/sections/05_field_management.tex b/sections/05_field_management.tex
@@ -66,7 +66,7 @@ \subsection{Registration}\label{subsec:registration}
 \paragraph{}
 After registration was initialized, a node sends out \texttt{field\_registration} messages, one for each 
 parameter/telemetryValue. The FieldRegistration includes a field ID, the datatype of the field, and 
-a human-readable name. The name and field ID have to be unique per node. The first bit of paramter field IDs is 0 and the first bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
+a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
-a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
+a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a deterministic way. This ensures that named fields have the same fieldID between reboots.
-a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
+a human-readable name. The name and field ID have to be unique per node. The most significant bit of parameter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
-a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
+a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a deterministic way. This ensures that named fields have the same fieldID between reboots.
-a human-readable name. The name and field ID have to be unique per node. The most significant bit of paramter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
+a human-readable name. The name and field ID have to be unique per node. The most significant bit of parameter field IDs is 0 and the most significant bit of telemetryValue field IDs is 1. From this point on, the server knows which fields the node has. The fieldID \texttt{0} is reserved to indicate an invalid fieldID. It must not be assigned to a field. FieldIDs must be assigned in a determenistic way. This ensures that named fields have the same fieldID between reboots.
 
 \paragraph{}
 Next, the node sends \texttt{telemetry\_group\_definition} messages.
@@ -97,4 +97,4 @@ \subsubsection{Requesting Field Data}\label{subsubsec:requesting-field-data}
 Nodes respond with a \texttt{field\_get\_res} message, containing the field ID, a field status (see FieldStatus enum in \ref{subsec:FieldStatus}), and the value of the field. If the field is not found (field\_status = NotFound), the field\_id should still contain the requested field ID from the request message, and the value field content is undefined.
 
 \subsubsection{Field name Lookup}\label{subsubsec:field-name-lookup}
-The field name lookup covers the case where nodes need to access fields from other nodes. Since they don't recieve the \texttt{field\_registration} messages, they don't know the fieldIDs of the named fields they want to access. \texttt{field\_id\_lookup\_req} messages contain the remote field name. The Node responds with a \texttt{field\_id\_lookup\_res} message, containing the fieldID, the datatype of the field, and a field status (see FieldStatus enum in \ref{subsec:FieldStatus}). If the field is not found (field\_status = NotFound), the field\_id should still contain the requested field ID from the request message.
+The field name lookup covers the case where nodes need to access fields from other nodes. Since they don't recieve the \texttt{field\_registration} messages, they don't know the fieldIDs of the named fields they want to access. \texttt{field\_id\_lookup\_req} messages contain the remote field name. The Node responds with a \texttt{field\_id\_lookup\_res} message, containing the fieldID, the datatype of the field, and a field status (see FieldStatus enum in \ref{subsec:FieldStatus}). If the field is not found (field\_status = NotFound), the field\_id should still contain the requested field ID from the request message.