fix(integrating autoware): fix the wrong name in creating sensor model

docs/how-to-guides/integrating-autoware/creating-vehicle-and-sensor-model/creating-sensor-model/index.md

@@ -9,11 +9,11 @@
 3. `<YOUR-VEHICLE-NAME>_sensor_kit_launch`
 
 Previously,
-we forked our vehicle model at the [creating autoware repositories](../../creating-your-autoware-repositories/creating-autoware-repositories.md) page step.
+we forked our sensor model at the [creating autoware repositories](../../creating-your-autoware-repositories/creating-autoware-repositories.md) page step.
 For instance,
-we created [tutorial_vehicle_launch](https://github.com/leo-drive/tutorial_vehicle_launch)
+we created [tutorial_vehicle_sensor_kit_launch](https://github.com/leo-drive/tutorial_vehicle_sensor_kit_launch)
 as an implementation example for the said step.
-Please ensure that the <YOUR-VEHICLE-NAME>\_vehicle_launch repository is included in Autoware,
+Please ensure that the <YOUR-VEHICLE-NAME>\_sensor_kit_launch repository is included in Autoware,
 following the directory structure below:
 
 ```diff
@@ -26,9 +26,9 @@
                  └─ <YOUR-VEHICLE-NAME>_sensor_kit_launch/
 ```
 
-If your forked Autoware meta-repository doesn't include `<YOUR-VEHICLE-NAME>_vehicle_launch` with the correct folder structure
+If your forked Autoware meta-repository doesn't include `<YOUR-VEHICLE-NAME>_sensor_kit_launch` with the correct folder structure
 as shown above,
-please add your forked `<YOUR-VEHICLE-NAME>_vehicle_launch` repository to the autoware.repos file
+please add your forked `<YOUR-VEHICLE-NAME>_sensor_kit_launch` repository to the autoware.repos file
 and run the vcs import src < autoware.repos command in your terminal
 to import the newly included repositories at autoware.repos file.
 
@@ -75,7 +75,7 @@
 ```
 
 Remember to apply the name changes and project method for **BOTH**
-`<YOUR-VEHICLE-NAME>_vehicle_description`and `<YOUR-VEHICLE-NAME>_vehicle_launch` ROS 2 packages.
+`<YOUR-VEHICLE-NAME>_sensor_kit_description`and `<YOUR-VEHICLE-NAME>_sensor_kit_launch` ROS 2 packages.
 Once finished, we can proceed to build said packages:
 
 ```bash
@@ -155,7 +155,7 @@
         roll: 0.0
         pitch: 0.0
         yaw: 0.0
       rs_bpearl_front_base_link: # Lidar
         x: 0.0
         y: 0.0
         z: 0.0
@@ -196,12 +196,12 @@
 
 ### sensor_kit.xacro
 
 We will add our sensors and remove unnecessary xacros from this file.
 For example,
 we want
 to add our lidar sensor with `velodyne_top` frame from the sensor driver,
 we will add the following xacro to our sensor_kit.xacro file.
 Please add your sensors to this file and remove unnecessary sensor's xacros.
 
 ```xml
     <!-- lidar -->
@@ -258,7 +258,7 @@
                  ${calibration['sensor_kit_base_link']['rs_helios_top_base_link']['yaw']}"
           />
         </xacro:VLS-128>
         <xacro:VLP-16 parent="sensor_kit_base_link" name="rs_bpearl_front" topic="/points_raw" hz="10" samples="220" gpu="$(arg gpu)">
           <origin
             xyz="${calibration['sensor_kit_base_link']['rs_bpearl_front_base_link']['x']}
                  ${calibration['sensor_kit_base_link']['rs_bpearl_front_base_link']['y']}
@@ -346,7 +346,7 @@
 </robot>
 ```
 
-At out tutorial vehicle,
+At our tutorial vehicle,
 there is no directly sensor transformation for base_link,
 thus our sensors.xacro file includes only `base_link` and `sensor_kit_base_link` link.
 
@@ -564,7 +564,7 @@
 
 Then, you can launch tensorrt_yolo node via adding yolo.launch.xml on your design like that:
 (i.e.,
 it is included in [tier4_perception_launch](https://github.com/autowarefoundation/autoware.universe/blob/ad69c2851b7b84e12c9f0c3b177fb6a9032bf284/launch/tier4_perception_launch/launch/object_recognition/detection/camera_lidar_fusion_based_detection.launch.xml#L49-L59) package in autwoare.universe)
 `image_number` argument defines your camera number
 
 ```xml
@@ -609,7 +609,7 @@
       from launch.actions import OpaqueFunction
       import yaml
 
       def launch_setup(context, *args, **kwargs):
 
       output_topic= LaunchConfiguration("output_topic").perform(context)
 
@@ -709,7 +709,7 @@
 launch_arguments = []
 
     def add_launch_arg(name: str, default_value=None, description=None):
         # a default_value of None is equivalent to not passing that kwarg at all
         launch_arguments.append(
             DeclareLaunchArgument(name, default_value=default_value, description=description)
         )