Remove SLAM glossary tooltips from generated motion API includes

The motion service docs reference SLAM via glossary tooltips. Since
the SLAM glossary entry is removed, replace tooltips with plain text
in the static include files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: shannonbradshaw

static/include/services/apis/generated/motion-table.md

@@ -2,7 +2,7 @@
 | Method Name | Description |
 | ----------- | ----------- |
 | [`Move`](/reference/apis/services/motion/#move) | The `Move` method is the primary way to move multiple components, or to move any object to any other location. |
-| [`MoveOnMap`](/reference/apis/services/motion/#moveonmap) | Move a base component to a destination pose on a {{< glossary_tooltip term_id="slam" text="SLAM" >}} map. |
+| [`MoveOnMap`](/reference/apis/services/motion/#moveonmap) | Move a base component to a destination pose on a SLAM map. |
 | [`MoveOnGlobe`](/reference/apis/services/motion/#moveonglobe) | Move a base component to a destination GPS point, represented in geographic notation _(latitude, longitude)_. |
 | [`GetPose`](/reference/apis/services/motion/#getpose) | `GetPose` gets the location and orientation of a component within the frame system. |
 | [`StopPlan`](/reference/apis/services/motion/#stopplan) | Stop a base component being moved by an in progress `MoveOnGlobe` or `MoveOnMap` call. |

static/include/services/apis/generated/motion.md

@@ -158,7 +158,7 @@ For more information, see the [TypeScript SDK Docs](https://ts.viam.dev/classes/
 
 ### MoveOnMap
 
-Move a [base](/operate/reference/components/base/) component to a destination [pose](/motion-planning/reference/orientation-vectors/) on a {{< glossary_tooltip term_id="slam" text="SLAM" >}} map.
+Move a [base](/operate/reference/components/base/) component to a destination [pose](/motion-planning/reference/orientation-vectors/) on a SLAM map.
 
 `MoveOnMap()` is non blocking, meaning the motion service will move the component to the destination [pose](/motion-planning/reference/orientation-vectors/) after `MoveOnMap()` returns.
 
@@ -170,7 +170,7 @@ If you specify a goal pose and the robot's current position is already within th
 
 You can monitor the progress of the `MoveOnMap()` call by querying `GetPlan()` and `ListPlanStatuses()`.
 
-Use the machine's position reported by the {{< glossary_tooltip term_id="slam" text="SLAM" >}} service to check the location of the machine.
+Use the machine's position reported by the SLAM service to check the location of the machine.
 
 `MoveOnMap()` is intended for use with the [navigation service](/operate/reference/services/navigation/), providing autonomous indoor navigation for rover [bases](/operate/reference/components/base/).
 

static/include/services/apis/overrides/protos/motion.MoveOnMap.md

@@ -1,4 +1,4 @@
-Move a [base](/operate/reference/components/base/) component to a destination [pose](/motion-planning/reference/orientation-vectors/) on a {{< glossary_tooltip term_id="slam" text="SLAM" >}} map.
+Move a [base](/operate/reference/components/base/) component to a destination [pose](/motion-planning/reference/orientation-vectors/) on a SLAM map.
 
 `MoveOnMap()` is non blocking, meaning the motion service will move the component to the destination [pose](/motion-planning/reference/orientation-vectors/) after `MoveOnMap()` returns.
 
@@ -10,7 +10,7 @@ If you specify a goal pose and the robot's current position is already within th
 
 You can monitor the progress of the `MoveOnMap()` call by querying `GetPlan()` and `ListPlanStatuses()`.
 
-Use the machine's position reported by the {{< glossary_tooltip term_id="slam" text="SLAM" >}} service to check the location of the machine.
+Use the machine's position reported by the SLAM service to check the location of the machine.
 
 `MoveOnMap()` is intended for use with the [navigation service](/operate/reference/services/navigation/), providing autonomous indoor navigation for rover [bases](/operate/reference/components/base/).