@@ -53,10 +53,11 @@ message Route
5353 //
5454 // \brief A segment of a logical lane.
5555 //
56- // \note The #LogicalLaneSegment allows that #start_s > #end_s.
57- // If #start_s < #end_s, then the traffic agent should traverse the
56+ // \note The \link LogicalLaneSegment logical lane segments\endlink allows that
57+ // start_s > end_s.
58+ // If start_s < end_s, then the traffic agent should traverse the
5859 // segment in the logical lane's reference line definition direction.
59- // If # end_s > # start_s, then the traffic agent should traverse the
60+ // If end_s > start_s, then the traffic agent should traverse the
6061 // segment in the opposite of the logical lane's reference line
6162 // definition direction.
6263 //
@@ -87,14 +88,14 @@ message Route
8788 //
8889 // Each time there is a successor-predecessor relation between the logical
8990 // lanes along the route (i.e. a logical lane ends, and is continued by another
90- // logical lane, e.g. at a junction border), a new #RouteSegment starts. The
91- // #RouteSegment then lists the logical lane segments that can be used to
91+ // logical lane, e.g. at a junction border), a new route segment starts. The
92+ // route segment then lists the logical lane segments that can be used to
9293 // travel through this space of the road.
9394 //
9495 // Together, the listed logical lane segments should form a continuous area,
9596 // where the traffic agent can move freely. These will mostly be parallel
9697 // lanes, though lanes may overlap (e.g. if one lane splits into two on a
97- // junction). In general, the logical lane segments in a #RouteSegment will
98+ // junction). In general, the logical lane segments in a route segment will
9899 // have the same length, though there are exceptions (e.g. if a lane widening
99100 // occurs, the newly appearing lane will have a shorter length).
100101 //
0 commit comments