chore: fix docs

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

sensing/autoware_pointcloud_preprocessor/docs/distortion-corrector.md

@@ -49,7 +49,7 @@ ros2 launch autoware_pointcloud_preprocessor distortion_corrector.launch.xml
 - The node requires time synchronization between the topics from lidars, twist, and IMU.
 - If you want to use a 3D distortion corrector without IMU, please check that the linear and angular velocity fields of your twist message are not empty.
 - The node updates the per-point azimuth and distance values based on the undistorted XYZ coordinates when the input point cloud is in the sensor frame and the `sensor_azimuth_coordinate` parameter is set to either `velodyne` or `hesai`. The azimuth values are calculated using the `cv::fastAtan2` function. Please note that updating the azimuth and distance fields increases the execution time by approximately 13%. Additionally, due to the `cv::fastAtan2` algorithm's accuracy of about 0.3 degrees, there is a **possibility of changing beam order for high azimuth resolution LiDAR**.
-- Currently, `sensor_azimuth_coordinate` only support `velodyne` and `hesai`. The `velodyne` and `hesai` coordinate are illustrated below. If a LiDAR uses the same coordinates as velodyne or hesai, users can use them as well.
+- Currently, `sensor_azimuth_coordinate` only supports `velodyne` and `hesai`. The `velodyne` and `hesai` coordinates are illustrated below. If a LiDAR uses the same coordinates as `velodyne` or `hesai`, users can use them as well.
 
 <table>
   <tr>