Fix typos in proto files

Signed-off-by: ClemensLinnhoff <clemens.linnhoff@partner.bmw.de>

Author: ClemensLinnhoff

osi_common.proto

@@ -159,7 +159,7 @@ message Dimension3d
 // \f$ Rotation_{yaw,pitch,roll} =
 // Rotation_{yaw}*Rotation_{pitch}*Rotation_{roll} \f$
 //
-// \f$ vector_{gobal coord system} := Rotation_{yaw, pitch, roll} * vector_{local coord system} +local_{origin::position} \f$
+// \f$ vector_{global coord system} := Rotation_{yaw, pitch, roll} * vector_{local coord system} +local_{origin::position} \f$
 //
 // \attention This definition changed in OSI version 3.0.0. Previous OSI
 // versions  (V2.xx) had an other definition.
@@ -195,7 +195,7 @@ message Orientation3d
 // truth, the identifier of an item (object, lane, sign, etc.) must remain
 // stable over its lifetime. \c Identifier values may be only be reused if the
 // available address space is exhausted and the specific values have not been in
-// use for several timesteps. Sensor specific tracking IDs have no restrictions
+// use for several time steps. Sensor specific tracking IDs have no restrictions
 // and should behave according to the sensor specifications.
 //
 // The value MAX(uint64) = 2^(64) -1 =
@@ -250,7 +250,7 @@ message ExternalReference
     // The external identifier reference value.
     //
     // The repeated string is chosen as a common description of the external
-    // identifier, because a variety of identificatier types could be
+    // identifier, because a variety of identifier types could be
     // involved .
     //
     // For example, referencing a unique lane in OpenDRIVE requires the

osi_detectedobject.proto

@@ -80,11 +80,11 @@ message DetectedItemHeader
         //
         MEASUREMENT_STATE_OTHER = 1;
 
-        // Entity has been measured by the sensor in the current timestep.
+        // Entity has been measured by the sensor in the current time step.
         //
         MEASUREMENT_STATE_MEASURED = 2;
 
-        // Entity has not been measured by the sensor in the current timestep.
+        // Entity has not been measured by the sensor in the current time step.
         // Values provided by tracking only.
         //
         MEASUREMENT_STATE_PREDICTED = 3;

osi_featuredata.proto

@@ -36,7 +36,7 @@ message FeatureData
     //
     // \note Required for ultrasonic sensors: Detections will be send by the
     // emitting ultrasonic sensor, including all indirect detections received
-    // by neighbouring sensors.
+    // by neighboring sensors.
     //
     repeated UltrasonicDetectionData ultrasonic_sensor = 4;
 
@@ -332,7 +332,7 @@ message RadarDetection
     //
     // \note Unambiguous measurements have the ambiguity ID 0.
     //
-    // \note Multiple seperate detections, from e.g. a large object, do not
+    // \note Multiple separate detections, from e.g. a large object, do not
     // necessarily on their own create any ambiguity. Therefore they do not
     // usually share an ambiguity ID. They can however be ambiguous
     // with other detections.
@@ -509,7 +509,7 @@ message UltrasonicDetectionSpecificHeader
 //
 // \image html OSI_USSensor.svg
 //
-// \note Direct detecions lies on circles with the sending sensor as centre.
+// \note Direct detections lie on circles with the sending sensor as centre.
 //
 message UltrasonicDetectionData
 {
@@ -544,7 +544,7 @@ message UltrasonicDetectionData
 //
 // \image html OSI_USSensor_direct.svg
 //
-// \note Direct detecions lies on circles with the sensor as centre.
+// \note Direct detections lie on circles with the sensor as centre.
 //
 message UltrasonicDetection
 {
@@ -594,7 +594,7 @@ message UltrasonicDetection
 //
 // \image html OSI_USSensor_indirect.svg
 //
-// \note Indirect detecions lies on ellipses with the sending resp. receiving
+// \note Indirect detections lie on ellipses with the sending resp. receiving
 // sensor in the focal points.
 //
 message UltrasonicIndirectDetection
@@ -730,7 +730,7 @@ message CameraDetection
     //
     optional bool shape_classification_background = 5;
 
-    // The defined shape is foregroud.
+    // The defined shape is foreground.
     // The probability for this classification is at least
     // \c #shape_classification_probability.
     //
@@ -856,7 +856,7 @@ message CameraDetection
     //
     optional bool shape_classification_pedestrian_rear = 26;
 
-    // This probability defines the mininimum probability for each selected
+    // This probability defines the minimum probability for each selected
     // shape classification.
     //
     // \rules
@@ -989,7 +989,7 @@ message CameraDetection
         // Allowed number of referenced points: 2 or 3
         //
         // Allowed number of referenced points = 2: first and third corner of
-        // the box. Box is alligned horizontal resp. vertical.
+        // the box. Box is aligned horizontal resp. vertical.
         //
         // Allowed number of referenced points = 3: first, second and third
         // corner of the box. fourth corner is calculated by first+third-second
@@ -1057,7 +1057,7 @@ message CameraPoint
     //
     optional double existence_probability = 1;
 
-    // Measured point refered by one camera detection given in spherical
+    // Measured point referred by one camera detection given in spherical
     // coordinates in the sensor coordinate system.
     //
     optional Spherical3d point = 2;

osi_hostvehicledata.proto

@@ -144,7 +144,7 @@ message HostVehicleData
             //
             OPERATING_STATE_BOARDING = 4;
 
-            // Entertainment, navigation or similiar systems can be used by the driver.
+            // Entertainment, navigation or similar systems can be used by the driver.
             // The vehicle can not be driven.
             // Usually the driver sits in the vehicle before or after a drive.
             //

osi_lane.proto

@@ -58,7 +58,7 @@ message Lane
     //
     // For example, to reference a lane defined in an OpenDRIVE map
     // the items should be set as follows:
-    // * reference = URI to map, can remain empty if identical with definiton
+    // * reference = URI to map, can remain empty if identical with definition
     //               in \c GroundTruth::map_reference
     // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road
@@ -209,8 +209,8 @@ message Lane
         // cl: center line
         // lb: lane boundary
         //
-        // \attention The points desribing the center line must be set in the 
-        // same ordering (ascending or descending) as the points desribing the 
+        // \attention The points describing the center line must be set in the 
+        // same ordering (ascending or descending) as the points describing the 
         // lane boundaries. Example: If the points are deducted from a map format, 
         // the order of points is recommended to be in line with the road coordinate 
         // (e.g. s-coordinate in OpenDRIVE). 
@@ -441,7 +441,7 @@ message Lane
             //
             SUBTYPE_NORMAL = 2;
 
-            // A lane that is designated for bicylists.
+            // A lane that is designated for bicycles.
             //
             // Since it is not intended to be used for normal automotive
             // driving, it should be used in combination with TYPE_NONDRIVING.

osi_logicallane.proto

@@ -318,7 +318,7 @@ message LogicalLaneBoundary
 // - The red area is the area where \c l1 overlaps \c l2. This is recorded in
 //   #overlapping_lane of \c l1.
 //
-// As can be seen in the images, the two highlighted lanes are neighbours for
+// As can be seen in the images, the two highlighted lanes are neighbors for
 // part of their length, but it makes no sense for them to have the same
 // reference line, since they diverge significantly.
 //
@@ -347,7 +347,7 @@ message LogicalLane
     //
     // For example, to reference a lane defined in an OpenDRIVE map
     // the items should be set as follows:
-    // * reference = URI to map, can remain empty if identical with definiton
+    // * reference = URI to map, can remain empty if identical with definition
     //               in \c GroundTruth::map_reference
     // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road
@@ -420,10 +420,10 @@ message LogicalLane
     // not required that the reference line has the same direction as the
     // driving direction of the lane.
     //
-    // Neighbouring lanes (i.e. lanes that are neighbours and whose directions
+    // Neighboring lanes (i.e. lanes that are neighbors and whose directions
     // do not diverge significantly) are strongly encouraged to reference the
     // same ReferenceLine, so that vehicles that are next to each other on
-    // neighbouring lanes have comparable S positions.
+    // neighboring lanes have comparable S positions.
     //
     // The S coordinate of the reference line makes it easy to find e.g. which
     // object is next on a lane, using the LogicalLaneAssignment of the
@@ -616,7 +616,7 @@ message LogicalLane
         //
         TYPE_NORMAL = 2;
 
-        // A lane that is designated for bicylists.
+        // A lane that is designated for bicycles
         // Note that biking lanes that cross the road (e.g. on an intersection)
         // are also labeled with this type.
         //

osi_object.proto

@@ -252,7 +252,7 @@ message StationaryObject
             //
             MATERIAL_STONE = 6;
 
-            // Glas structure.
+            // Glass structure.
             //
             MATERIAL_GLAS = 7;
 
@@ -609,7 +609,7 @@ message MovingObject
         repeated WheelData wheel_data = 7;
 
         // Angle of the steering wheel.
-        // Zero means the steering wheel is in its center postion, a positive value
+        // Zero means the steering wheel is in its center position, a positive value
         // means the steering wheel is turned to the left and a negative value
         // means the steering wheel is turned to the right of the center position.
         //
@@ -752,7 +752,7 @@ message MovingObject
         // TYPE_MEDIUM_CAR in OSI.
         //
         // \note Vehicle type classification is a complex area and there are no
-        // universally recognised standards.  As such, the boundaries between some of the
+        // universally recognized standards.  As such, the boundaries between some of the
         // OSI vehicle types are not well-defined.  It is left to the implementor to
         // decide how to distinguish between them and agree that with any applications which
         // make use of that specific interface instance.  For example, how to distinguish
@@ -782,7 +782,7 @@ message MovingObject
 
             // Vehicle is a medium car.
             //
-            // Definition: Hatchback or sedan with lenght between 4.5 and 5 m.
+            // Definition: Hatchback or sedan with length between 4.5 and 5 m.
             //
             TYPE_MEDIUM_CAR = 4;
 

osi_referenceline.proto

@@ -53,7 +53,7 @@ message ReferenceLine
         // ReferenceLine is a polyline, where the coordinates of points are
         // calculated by projection onto the nearest point on the line.
         //
-        // \attention DEPRECATED: Due to the shortcomings documenten below, this
+        // \attention DEPRECATED: Due to the shortcomings documented below, this
         //            type will be removed in 4.0.0.
         //
         TYPE_POLYLINE = 0;

osi_sensorview.proto

@@ -301,15 +301,15 @@ message LidarSensorView
 
         // normal to surface angle.
         //
-        // The normal of the transmitted beam to the object, roadmarking etc
+        // The normal of the transmitted beam to the object, road marking etc
         // encounter. \note data is in Lidar coordinate system
         //
         // Unit: unit vector
         //
         optional Vector3d normal_to_surface = 5;
 
         // ID of the detected object this reflection is associated to.
-        // can be used for raytracing debug
+        // can be used for ray tracing debug
         //
         // \note ID = MAX(uint64) indicates no reference to an object.
         optional Identifier object_id = 6;

osi_streamingupdate.proto

@@ -23,7 +23,7 @@ package osi3;
 //
 // \note The receiver of partial streaming update messages can only rely on the
 // most up-to-date information at the corresponding timestamp. E.g. omitting
-// objects does not indicate static behaviour but it may be sufficient for the
+// objects does not indicate static behavior but it may be sufficient for the
 // use case to update certain objects at a later point in time.
 //
 message StreamingUpdate