From 95b4799ab589375a993cf4c79deb0ff4b32265ab Mon Sep 17 00:00:00 2001
From: Naomi Pentrel <5212232+npentrel@users.noreply.github.com>
Date: Tue, 27 Feb 2024 17:55:48 +0100
Subject: [PATCH] Apply suggestions from code review

---
 docs/mobility/motion/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/mobility/motion/_index.md b/docs/mobility/motion/_index.md
index e0f379b62c..c6af6b09a4 100644
--- a/docs/mobility/motion/_index.md
+++ b/docs/mobility/motion/_index.md
@@ -482,7 +482,7 @@ Use a [movement sensor](/components/movement-sensor/) to check the location of t
 Each successful `MoveOnGlobe()` call returns a unique `ExecutionID` which you can use to identify all plans generated during the `MoveOnGlobe()`.
 
 {{< alert title="Info" color="info" >}}
-If you specify a goal pose or orientation and the robot's current position is already at the goal post or orientation, `MoveonMap` returns an error.
+If you specify a goal pose or orientation and the robot's current position is already within the set `PlanDeviationM` or orientation, `MoveOnGlobe` returns an error.
 {{< /alert >}}
 
 You can monitor the progress of the `MoveOnGlobe()` call by querying `GetPlan()` and `ListPlanStatuses()`.