Update Creating bot waypoints

diff --git a/Creating-bot-waypoints.md b/Creating-bot-waypoints.md
index c8a89adc585e00d68828855369c5cc20c9f802e8..73d869b3605dead6ad2b429c1a7c4f166bf1e01d 100644 (file)
--- a/Creating-bot-waypoints.md
+++ b/Creating-bot-waypoints.md
@@ -132,7 +132,7 @@ The command spawning a waypoint at crosshair is very handy to add more jump link
 To create a crouch waypoint you can use the command `wpeditor spawn crouch`. They are automatically linked to other waypoints but only if really close (less than 100 qu).
 
 * *Support waypoint and linking*  
-Some teleporters and jumppads refuse to create links from waypoints that aren't in front of them, to fix them you can create a support waypoint: spawn it very close to the problematic waypoint with the command `wpeditor spawn support`, then aim at the problematic teleporter / jumppad waypoint and run `wpeditor spawn crosshair` to create a special link and remove all the other links going to the problematic waypoint. Since the support waypoint doesn't have any other outgoing link, bots will always use it as intermediate waypoint to reach the problematic waypoint. If you used a normal waypoint instead, it would create a lot of useless outgoing links.
+Some teleporters and jumppads refuse to create links from waypoints that aren't in front of them, to fix them you can create a support waypoint: spawn it very close to the problematic waypoint with the command `wpeditor spawn support`, then aim at the problematic teleporter / jumppad waypoint and execute `wpeditor spawn crosshair` to create a special link that is exclusive for that teleporter / jumppad. Since the support waypoint doesn't have any other outgoing link, bots will always use it as intermediate waypoint to reach the problematic waypoint. If you used a normal waypoint instead, it would create a lot of useless outgoing links.
 
 
 ## Optimizing waypoints