fix spelling

Signed-off-by: mohammad alqudah <alqudah.mohammad@tier4.jp>

Author: mkquda

Diff for: planning/behavior_path_planner/autoware_behavior_path_lane_change_module/README.md

@@ -876,7 +876,7 @@ endif
 
 ## Terminal Lane Change Path
 
-Depending on the space configration around the Ego vehicle, it is possible that a valid LC path cannot be generated. If that happens, then Ego will get stuck at `terminal_start` and will be not be able to proceed. Therefore we introduced the terminal LC path feature; when ego gets near to the terminal point (dist to `terminal_start` is less than the maximum lane change length) a terminal lane changing path will be computed starting from the terminal start point on the current lane and connects to the target lane. The terminal path only needs to be computed once in each execution of LC module. If no valid candidate paths are found in the path generation process, then the terminal path will be used as a fallback candidate path, the safety of the terminal path is not ensured and therefore it can only be force approved. The following images illustrate the expected behavior without and with the terminal path feature respectively:
+Depending on the space configuration around the Ego vehicle, it is possible that a valid LC path cannot be generated. If that happens, then Ego will get stuck at `terminal_start` and will be not be able to proceed. Therefore we introduced the terminal LC path feature; when ego gets near to the terminal point (dist to `terminal_start` is less than the maximum lane change length) a terminal lane changing path will be computed starting from the terminal start point on the current lane and connects to the target lane. The terminal path only needs to be computed once in each execution of LC module. If no valid candidate paths are found in the path generation process, then the terminal path will be used as a fallback candidate path, the safety of the terminal path is not ensured and therefore it can only be force approved. The following images illustrate the expected behavior without and with the terminal path feature respectively:
 
 ![no terminal path](./images/lane_change-no_terminal_path.png)
 

Diff for: planning/behavior_path_planner/autoware_behavior_path_lane_change_module/src/scene.cpp

@@ -1348,7 +1348,8 @@ std::optional<PathWithLaneId> NormalLaneChange::compute_terminal_lane_change_pat
 
   const auto max_lane_changing_length = std::invoke([&]() {
     double max_length = transient_data.dist_to_terminal_end - prep_metric.length;
-    return std::min(max_length, dist_lc_start_to_end_of_lanes - transient_data.next_dist_buffer.min);
+    return std::min(
+      max_length, dist_lc_start_to_end_of_lanes - transient_data.next_dist_buffer.min);
   });
 
   const auto max_path_velocity = prepare_segment.points.back().point.longitudinal_velocity_mps;