diff --git a/docs/MISSION_DESIGNER_GUIDE.md b/docs/MISSION_DESIGNER_GUIDE.md
index f2f41f6..489eef1 100644
--- a/docs/MISSION_DESIGNER_GUIDE.md
+++ b/docs/MISSION_DESIGNER_GUIDE.md
@@ -150,8 +150,7 @@ Minimum Eden setup:
 
 Transport nodes are generic paid travel points. They can represent ferries,
 airports, bus stops, teleport terminals, or any other mission transport system.
-The framework owns the menu, billing, cargo scan, and movement logic. The
-mission only needs placed objects and arrival markers.
+The framework owns the menu, billing, cargo scan, and movement logic.
 
 ![Eden transport location one](images/eden/transport_loc_1.jpg)
 
diff --git a/docs/TRANSPORT_SERVICE_GUIDE.md b/docs/TRANSPORT_SERVICE_GUIDE.md
index 188dbec..f4301f2 100644
--- a/docs/TRANSPORT_SERVICE_GUIDE.md
+++ b/docs/TRANSPORT_SERVICE_GUIDE.md
@@ -2,7 +2,7 @@
 
 The transport service provides paid point-to-point travel for players and
 nearby vehicles or passengers. It is framework-owned: missions only need placed
-transport objects and optional arrival markers with the expected variable names.
+transport objects and arrival markers with the expected variable names.
 
 ## Mission Contract
 
@@ -135,9 +135,3 @@ These screenshots show the default transport setup and player workflow:
 ![Player transport destination submenu](images/player/transport_destination_menu.jpg)
 
 ![Player transport completion notification](images/player/transport_complete.jpg)
-
-## Mission-Side Code Requirement
-
-No mission-side transport service, addAction script, or server event bridge is
-required. The framework handles menu discovery, destination selection, pricing,
-billing, cargo movement, and EventBus notifications.