remove trailing space from spec files

c/include/libsbp/legacy/system.h

@@ -222,8 +222,8 @@ typedef struct SBP_ATTR_PACKED SBP_DEPRECATED {
  *
  * The local time used to timestamp the PPS pulse must be generated by the
  * same clock which is used to timestamp the IMU/wheel sensor data and should
- * follow the same roll-over rules (i.e. it should roll over to zero  after
- * 604800 seconds). A separate MSG_PPS_TIME message should be sent  for each
+ * follow the same roll-over rules (i.e. it should roll over to zero after
+ * 604800 seconds). A separate MSG_PPS_TIME message should be sent for each
  * source of sensor data which uses local timestamping.  The sender ID for
  * each of these MSG_PPS_TIME messages should match the sender ID of the
  * respective sensor data.

haskell/src/SwiftNav/SBP/System.hs

@@ -459,8 +459,8 @@ msgPpsTime = 0xFF08
 --
 -- The local time used to timestamp the PPS pulse must be generated by the
 -- same clock which is used to timestamp the IMU/wheel sensor data and should
--- follow the same roll-over rules (i.e. it should roll over to zero  after
--- 604800 seconds). A separate MSG_PPS_TIME message should be sent  for each
+-- follow the same roll-over rules (i.e. it should roll over to zero after
+-- 604800 seconds). A separate MSG_PPS_TIME message should be sent for each
 -- source of sensor data which uses local timestamping.  The sender ID for
 -- each of these MSG_PPS_TIME messages should match the sender ID of the
 -- respective sensor data.

javascript/sbp/system.js

@@ -464,8 +464,8 @@ MsgGnssTimeOffset.prototype.fieldSpec.push(['flags', 'writeUInt8', 1]);
  * or wheeltick messages) where GNSS time is unknown to the sender.  The local time
  * used to timestamp the PPS pulse must be generated by the same clock which is
  * used to timestamp the IMU/wheel sensor data and should follow the same roll-over
- * rules (i.e. it should roll over to zero  after 604800 seconds). A separate
- * MSG_PPS_TIME message should be sent  for each source of sensor data which uses
+ * rules (i.e. it should roll over to zero after 604800 seconds). A separate
+ * MSG_PPS_TIME message should be sent for each source of sensor data which uses
  * local timestamping.  The sender ID for each of these MSG_PPS_TIME messages
  * should match the sender ID of the respective sensor data.
  *

jsonschema/MsgPpsTime.json

@@ -13,7 +13,7 @@
   "$schema": "http://json-schema.org/draft-06/schema#",
   "$id": "#MsgPpsTime",
   "title":"MsgPpsTime",
-  "description":"The PPS time message contains the value of the sender's local time in microseconds at the moment a pulse is detected on the PPS input. This is to be used for synchronisation of sensor data sampled with a local timestamp (e.g. IMU or wheeltick messages) where GNSS time is unknown to the sender.,\n,\nThe local time used to timestamp the PPS pulse must be generated by the same clock which is used to timestamp the IMU/wheel sensor data and should follow the same roll-over rules (i.e. it should roll over to zero  after 604800 seconds). A separate MSG_PPS_TIME message should be sent  for each source of sensor data which uses local timestamping.  The sender ID for each of these MSG_PPS_TIME messages should match the sender ID of the respective sensor data.\n",
+  "description":"The PPS time message contains the value of the sender's local time in microseconds at the moment a pulse is detected on the PPS input. This is to be used for synchronisation of sensor data sampled with a local timestamp (e.g. IMU or wheeltick messages) where GNSS time is unknown to the sender.,\n,\nThe local time used to timestamp the PPS pulse must be generated by the same clock which is used to timestamp the IMU/wheel sensor data and should follow the same roll-over rules (i.e. it should roll over to zero after 604800 seconds). A separate MSG_PPS_TIME message should be sent for each source of sensor data which uses local timestamping.  The sender ID for each of these MSG_PPS_TIME messages should match the sender ID of the respective sensor data.\n",
   "type": "object",
   "properties": {
     "time": {"type": "integer"},

proto/system.proto

@@ -184,8 +184,8 @@ message MsgGnssTimeOffset {
  *
  * The local time used to timestamp the PPS pulse must be generated by the
  * same clock which is used to timestamp the IMU/wheel sensor data and should
- * follow the same roll-over rules (i.e. it should roll over to zero  after
- * 604800 seconds). A separate MSG_PPS_TIME message should be sent  for each
+ * follow the same roll-over rules (i.e. it should roll over to zero after
+ * 604800 seconds). A separate MSG_PPS_TIME message should be sent for each
  * source of sensor data which uses local timestamping.  The sender ID for
  * each of these MSG_PPS_TIME messages should match the sender ID of the
  * respective sensor data.

python/sbp/system.py

@@ -1224,8 +1224,8 @@ class MsgPpsTime(SBP):
 
   The local time used to timestamp the PPS pulse must be generated by the same
   clock which is used to timestamp the IMU/wheel sensor data and should follow
-  the same roll-over rules (i.e. it should roll over to zero  after 604800
-  seconds). A separate MSG_PPS_TIME message should be sent  for each source of
+  the same roll-over rules (i.e. it should roll over to zero after 604800
+  seconds). A separate MSG_PPS_TIME message should be sent for each source of
   sensor data which uses local timestamping.  The sender ID for each of these
   MSG_PPS_TIME messages should match the sender ID of the respective sensor
   data.

rust/sbp/src/messages/system.rs

@@ -1850,8 +1850,8 @@ pub mod msg_pps_time {
     ///
     /// The local time used to timestamp the PPS pulse must be generated by the
     /// same clock which is used to timestamp the IMU/wheel sensor data and should
-    /// follow the same roll-over rules (i.e. it should roll over to zero  after
-    /// 604800 seconds). A separate MSG_PPS_TIME message should be sent  for each
+    /// follow the same roll-over rules (i.e. it should roll over to zero after
+    /// 604800 seconds). A separate MSG_PPS_TIME message should be sent for each
     /// source of sensor data which uses local timestamping.  The sender ID for
     /// each of these MSG_PPS_TIME messages should match the sender ID of the
     /// respective sensor data.

sbpjson/elm/SbpJson.elm

@@ -2419,8 +2419,8 @@ time is unknown to the sender.,
 ,
 The local time used to timestamp the PPS pulse must be generated by the same clock which
 is used to timestamp the IMU/wheel sensor data and should follow the same roll-over rules
-(i.e. it should roll over to zero  after 604800 seconds). A separate MSG_PPS_TIME message
-should be sent  for each source of sensor data which uses local timestamping.  The sender
+(i.e. it should roll over to zero after 604800 seconds). A separate MSG_PPS_TIME message
+should be sent for each source of sensor data which uses local timestamping.  The sender
 ID for each of these MSG_PPS_TIME messages should match the sender ID of the respective
 sensor data.
 -}

sbpjson/typescript/SbpJson.ts

@@ -1997,8 +1997,8 @@ export interface MsgPoseRelative {
  * ,
  * The local time used to timestamp the PPS pulse must be generated by the same clock which
  * is used to timestamp the IMU/wheel sensor data and should follow the same roll-over rules
- * (i.e. it should roll over to zero  after 604800 seconds). A separate MSG_PPS_TIME message
- * should be sent  for each source of sensor data which uses local timestamping.  The sender
+ * (i.e. it should roll over to zero after 604800 seconds). A separate MSG_PPS_TIME message
+ * should be sent for each source of sensor data which uses local timestamping.  The sender
  * ID for each of these MSG_PPS_TIME messages should match the sender ID of the respective
  * sensor data.
  */

spec/yaml/swiftnav/sbp/system.yaml

@@ -458,8 +458,8 @@ definitions:
 
       The local time used to timestamp the PPS pulse must be generated by the
       same clock which is used to timestamp the IMU/wheel sensor data and
-      should follow the same roll-over rules (i.e. it should roll over to zero 
-      after 604800 seconds). A separate MSG_PPS_TIME message should be sent 
+      should follow the same roll-over rules (i.e. it should roll over to zero
+      after 604800 seconds). A separate MSG_PPS_TIME message should be sent
       for each source of sensor data which uses local timestamping.  The sender
       ID for each of these MSG_PPS_TIME messages should match the sender ID of
       the respective sensor data.