fix broken links

Signed-off-by: ismetatabay <[email protected]>

docs/how-to-guides/integrating-autoware/launch-autoware/index.md

@@ -16,10 +16,10 @@ We will explain how to run and launch autoware with these modules:
 
 Please complete these steps for integration Autoware on your vehicle:
 
-- [Create your Autoware meta-repository](../creating-your-autoware-meta-repository/creating-autoware-meta-repository.md).
-- [Create your vehicle and sensor model](../creating-vehicle-and-sensor-description/creating-vehicle-and-sensor-description.md).
-- [Calibrate your sensors](../creating-vehicle-and-sensor-description/calibrating-sensors.md).
-- [Create your Autoware compatible vehicle interface](../creating-vehicle-interface-package/creating-a-vehicle-interface-for-an-ackermann-kinematic-model.md).
+- [Create your Autoware meta-repository](../creating-your-autoware-repositories/creating-autoware-repositories.md).
+- [Create your vehicle and sensor model](../creating-vehicle-and-sensor-model/index.md).
+- [Calibrate your sensors](../creating-vehicle-and-sensor-model/calibrating-sensors/index.md).
+- [Create your Autoware compatible vehicle interface](../creating-vehicle-interface-package/vehicle-interface.md).
 - [Create your environment map](../creating-maps).
 
 After the completion of these steps according to your individual vehicle,
@@ -115,7 +115,9 @@ For example, if you disable it, then `vehicle_interface.launch.xml` will not be
 ```
 
 Please be sure your vehicle interface driver included in `vehicle_interface.launch.xml`,
-for more information you can refer the [creating vehicle interface](../creating-vehicle-interface-package/creating-a-vehicle-interface-for-an-ackermann-kinematic-model.md#3-prepare-a-launch-file) page.
+for more information you can refer the
+[creating vehicle interface](../creating-vehicle-interface-package/creating-vehicle-interface.md#3-prepare-a-launch-file)
+page.
 
 ### Map
 

docs/how-to-guides/integrating-autoware/launch-autoware/localization/eagleye/index.md

@@ -88,7 +88,7 @@ common:
 
 ### Conversion from fix to pose
 
-The parameters for converting `sensor_msgs/msg/NavSatFix` to `geometry_msgs/msg/PoseWithCovarianceStamped` is listed in [`fix2pose.yaml`](https://github.com/MapIV/eagleye/blob/autoware-main/eagleye_util/fix2pose/launch/fix2pose.xml).
+The parameters for converting `sensor_msgs/msg/NavSatFix` to `geometry_msgs/msg/PoseWithCovarianceStamped` is listed in [`geo_pose_converter.launch.xml`](https://github.com/MapIV/eagleye/blob/autoware-main/eagleye_util/geo_pose_converter/launch/geo_pose_converter.launch.xml).
 If you use a different geoid or projection type, change these parameters.
 
 ### Other parameters

docs/how-to-guides/integrating-autoware/launch-autoware/sensing/index.md

@@ -30,7 +30,7 @@ The sensing launch is more related to your sensor kit,
 so if you want to modify your launch, we recommend applying
 these modifications to the <YOUR-SENSOR-KIT> packages.
 Please look
-at [creating sensor and vehicle model](../../creating-vehicle-and-sensor-description) pages for more information but there
+at [creating sensor and vehicle model](../../creating-vehicle-and-sensor-model/index.md) pages for more information but there
 is are some modifications on which can you done at top-level launch files.
 
 For example, if you do not want to launch the sensor driver with Autoware,