Fix some internal links (#33)

Signed-off-by: Raul Sanchez-Mateos <[email protected]>

source/How-To-Guides/Getting-Backtraces-in-ROS-2.rst

@@ -304,7 +304,7 @@ Alternatively, if your node of interest is being launched in these files directl
 
   In this case you may need to remap or provide parameter files to this node if it was previously provided by the launch file.
   Using ``--ros-args`` you can give it the path to the new parameters file, remaps, or names.
-  See :doc:`this tutorial <../../How-To-Guides/Node-arguments>` for the commandline arguments required.
+  See :doc:`this tutorial <../How-To-Guides/Node-arguments>` for the commandline arguments required.
 
   We understand this can be a pain, so it might encourage you to rather have each node possible as a separately included launch file to make debugging easier.
   An example set of arguments might be ``--ros-args -r __node:=<node_name> --params-file /absolute/path/to/params.yaml`` (as a template).

source/Tutorials/Beginner-Client-Libraries/Writing-A-Simple-Py-Service-And-Client.rst

@@ -276,7 +276,7 @@ Finally we have the ``main`` method, which constructs a ``MinimalClientAsync`` o
 .. warning::
 
   Do not use ``rclpy.spin_until_future_complete`` in a ROS 2 callback.
-  For more details see the :doc:`sync deadlock article <../../../How-To-Guides/Sync-Vs-Async>`.
+  For more details see the :doc:`sync deadlock article <../../How-To-Guides/Sync-Vs-Async>`.
 
 3.2 Add an entry point
 ~~~~~~~~~~~~~~~~~~~~~~