From 868c5be5b294bbde718f8b428a3d9bd433a191d1 Mon Sep 17 00:00:00 2001
From: Tiziano Guadagnino <37455909+tizianoGuadagnino@users.noreply.github.com>
Date: Wed, 16 Oct 2024 14:23:07 +0200
Subject: [PATCH] Update README.md (#6)

More accurate statement in the readme, the system does not need to follow a unicycle motion model, just the pose correction needs to do that, which applies to much more robotics platforms.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index a6c1f64..7f9f688 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ Our system operates on ROS2, supporting **ROS Humble**, **Iron**, and **Jazzy**.
 
 # TF Requirements
 
-Kinematic ICP can enhance existing odometry using a 3D LiDAR. However, there are specific requirements regarding motion and transformations due to the assumption that the robot operates on a unicycle kinematic model. Below are the key requirements:
+Kinematic ICP can enhance existing odometry using a 3D LiDAR. However, there are specific requirements regarding motion and transformations since we use a kinematic motion model for the pose correction. Below are the key requirements:
 
 1. **Planar Movement**: The robot is expected to move primarily on a planar surface.