Apply suggestions from code review

Minor spelling fixes

Co-authored-by: caspar-ai <caspar.dehaes@five.ai>
Signed-off-by: clemenshabedank <clemens.habedank@partner.bmw.de>

Author: 2 people

osi_trafficcommand.proto

@@ -65,8 +65,9 @@ message TrafficCommand
 // model that certain actions must or shall be terminated, there are 
 // explicit actions nested inside this message (AbortActionsAction, 
 // EndActionsAction), which hold a reference to the respective actions.
-// It is highly recommended for the scenario engine to handle the state 
-// machine of traffic actions and to use AbortActionsActions / 
+//
+// It is highly recommended that the scenario engine handles the state 
+// machine of traffic actions and uses AbortActionsActions / 
 // EndActionsAction to transfer information to the traffic participant. 
 // Furthermore, the scenario engine shall listen to DismissedActions of 
 // \c TrafficCommandUpdate to reflect this in the evaluation of the 

osi_trafficcommandupdate.proto

@@ -10,7 +10,7 @@ package osi3;
 //
 // \brief This message enables the traffic participant model to send updates 
 // to the scenario engine about the execution of its received \c TrafficCommand input. 
-// While traffic actions are usually executed successfully by the traffic participant 
+// While traffic actions are usually executed successfully by the traffic participant,
 // there may be actions which the traffic participant is not able to execute
 // either for capability or situation-specific reasons. This message gives
 // the traffic participant the basic possiblity to send feedback if an action 
@@ -67,7 +67,7 @@ message TrafficCommandUpdate
 
         // Information about the reason of failure.
         // 
-        // \note This is just a custom, informal string without a standardized meaning. 
+        // \note This is a custom, informal string without a standardized meaning. 
         //
         optional string failure_reason = 2;
     }