Skip to content

Commit 50dd1ca

Browse files
max-rosinlemmer-fzi
authored andcommitted
fix(docs): Fix typos
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com> Signed-off-by: Markus Lemmer <lemmer@fzi.de>
1 parent ed79614 commit 50dd1ca

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

osi_motionrequest.proto

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ package osi3;
1111
// \brief This message is intended as an interface between a HAD (highly automated driving) function and the actuator management.
1212
//
1313
// The HAD function can send either a desired future trajectory or a desired future state.
14-
// The message can be defined by a additional variable.
14+
// The message can be defined by an additional variable.
1515
//
1616
// \note The coordinate system is defined as right-handed.
1717
// All coordinates and orientations are relative to the global coordinate system.
@@ -43,8 +43,8 @@ message MotionRequest
4343
//
4444
optional Trajectory desired_trajectory = 5;
4545

46-
// Define different options for HAD function ouput.
47-
// Each option is corresponds to a field in the message.
46+
// Define different options for HAD function output.
47+
// Each option corresponds to a field in the message.
4848
//
4949
enum OutputOptions
5050
{
@@ -91,14 +91,14 @@ message MotionRequest
9191
// \brief Defined trajectory desired by the HAD function.
9292
//
9393
// This trajectory is the result of the trajectory planning step in the HAD function.
94-
// The task of the acutator management is to follow this trajectory as closely as possible.
95-
// The timestamps inside the trajecotry must be defined in global simulation time.
94+
// The task of the actuator management is to follow this trajectory as closely as possible.
95+
// The timestamps inside the trajectory must be defined in global simulation time.
9696
//
9797
// \note Trajectory is kept as a separate message for future extensions.
9898
//
9999
message Trajectory
100100
{
101-
// consists of intended position (x, y, and z) and orientation (yaw, pitch and roll) of intended state to be reached.
101+
// Consists of intended position (x, y, and z) and orientation (yaw, pitch and roll) of intended state to be reached.
102102
// A reference to \c StatePoint message.
103103
//
104104
repeated StatePoint trajectory_point = 1;

0 commit comments

Comments
 (0)