Remove redundant next tutorial links

ros2/example_1.md

@@ -139,6 +139,3 @@ cd catkin_ws/src/stretch_ros_turotials/src/
 python3 move.py
 ``` -->
 To stop the node from sending twist messages, type **Ctrl** + **c**.
-
-
-**Next Example:** [Example 2](example_2.md)

ros2/example_2.md

@@ -176,5 +176,3 @@ rclpy.spin(scan_filter)
 Give control to ROS.  This will allow the callback to be called whenever new
 messages come in.  If we don't put this line in, then the node will not work,
 and ROS will not process any messages.
-
-**Next Example:** [Example 3](example_3.md)

ros2/example_3.md

@@ -155,4 +155,3 @@ Setup Avoider class with `avoider = Avioder()`
 
 Give control to ROS with `rclpy.spin()`. This will allow the callback to be called whenever new messages come in. If we don't put this line in, then the node will not work, and ROS will not process any messages.
 
-**Next Example:** [Example 4](example_4.md)

ros2/gazebo_basics.md

@@ -32,4 +32,3 @@ roslaunch stretch_gazebo gazebo.launch world:=worlds/willowgarage.world
 
 ![image](https://raw.githubusercontent.com/hello-robot/stretch_tutorials/ROS2/images/stretch_willowgarage_world.png)
 
-**Next Tutorial:** [Teleoperating Stretch](teleoperating_stretch.md)

ros2/getting_started.md

@@ -24,4 +24,3 @@ Then source your workspace with the following command
 source ~/ament_ws/install/setup.bash"
 ```
 
-**Next Tutorial:** [Gazebo Basics](gazebo_basics.md)

ros2/internal_state_of_stretch.md

@@ -40,4 +40,3 @@ ros2 run rqt_graph rqt_graph
 
 The graph allows a user to observe and affirm if topics are broadcasted to the correct nodes. This method can also be utilized to debug communication issues.
 
-**Next Tutorial:** [RViz Basics](rviz_basics.md)

ros2/moveit_basics.md

@@ -54,4 +54,3 @@ roslaunch stretch_moveit_config demo_gazebo.launch
 This will launch an Rviz instance that visualizes the joints with markers and an empty world in Gazebo with Stretch and load all the controllers. There are pre-defined positions for each joint group for demonstration purposes. There are three joint groups, namely stretch_arm, stretch_gripper and stretch_head that can be controlled individually via Motion Planning Rviz plugin. Start and goal positions for joints can be selected similar to [this moveit tutorial](https://ros-planning.github.io/moveit_tutorials/doc/quickstart_in_rviz/quickstart_in_rviz_tutorial.html#choosing-specific-start-goal-states).
 ![image](images/gazebo_moveit.gif) -->
 
-**Next Tutorial:** [Follow Joint Trajectory Commands](follow_joint_trajectory.md)

ros2/navigation_stack.md

@@ -54,4 +54,3 @@ roslaunch stretch_navigation teleop_keyboard.launch
 ```
  -->
 
-**Next Tutorial:** [MoveIt! Basics](moveit_basics.md)

ros2/rviz_basics.md

@@ -37,4 +37,3 @@ the `rviz` flag will open an RViz window  to visualize a variety of ROS topics.
 
 Bringup the [keyboard teleop](teleoperating_stretch.md) to drive Stretch and observe its sensor input.
 
-**Next Tutorial:** [Navigation Stack](navigation_stack.md)

ros2/teleoperating_stretch.md

@@ -100,4 +100,3 @@ roslaunch stretch_gazebo teleop_joy.launch
 ```
 Note that the teleop_twist_joy package has a deadman switch by default which disables the drive commands to be published unless pressed. For a Logitech F310 joystick, this button is A.
 
-**Next Tutorial:** [Internal State of Stretch](internal_state_of_stretch.md)