Fix reference warnings (#4)

* Fix reference warnings

Signed-off-by: RaulSanchez <raul@eprosima.com>

* Change absolute paths by relative paths in internal links

Signed-off-by: RaulSanchez <raul@eprosima.com>

Signed-off-by: RaulSanchez <raul@eprosima.com>

Author: rsanchez15

source/Concepts.rst

@@ -34,7 +34,6 @@ The Core Stack Developer Concepts are much more detailed conceptual articles int
   Concepts/About-Build-System
   Concepts/About-Internal-Interfaces
   Concepts/About-Middleware-Implementations
-  Concepts/About-ROS-2-Client-Libraries
 
 Quick overview of ROS 2 Concepts
 --------------------------------
@@ -95,7 +94,7 @@ It can be summarized as follows:
 #. Nodes periodically advertise their presence so that connections can be made with new-found entities, even after the initial discovery period.
 #. Nodes advertise to other nodes when they go offline.
 
-Nodes will only establish connections with other nodes if they have compatible :doc:`Quality of Service <../Tutorials/Demos/Quality-of-Service>` settings.
+Nodes will only establish connections with other nodes if they have compatible :doc:`Quality of Service <./Tutorials>` settings.
 
 Take the :ref:`talker-listener demo <talker-listener>` for example.
 Running the C++ talker node in one terminal will publish messages on a topic,

source/How-To-Guides/Developing-a-ROS-2-Package.rst

@@ -17,7 +17,7 @@ It is intended for developers who want to learn how to create custom packages in
 Prerequisites
 -------------
 
-- :doc:`Install ROS <../../Installation>`
+- :doc:`Install ROS <../Installation>`
 
 - `Install colcon <https://colcon.readthedocs.io/en/released/user/installation.html>`__
 

source/How-To-Guides/Releasing/_Next-Steps.rst

@@ -1,5 +1,5 @@
 Once your pull request has been submitted, usually within one or two days, one of the maintainers of rosdistro will review and merge your Pull Request.
-If your package build is successful, in 24-48 hours your packages will become available in the **ros-testing** repository, where you can :doc:`test your pre-release binaries <../../../Installation/Testing>`.
+If your package build is successful, in 24-48 hours your packages will become available in the **ros-testing** repository, where you can :doc:`test your pre-release binaries <../../Installation/Testing>`.
 
 Approximately every two to four weeks, the distribution's release manager manually synchronizes the contents of ros-testing into the main ROS repository.
 This is when your packages actually become available to the rest of the ROS community.

source/Installation/Alternatives/images/windows-vs-studio-install.png

@@ -3,13 +3,6 @@
 Maintain source checkout
 ========================
 
-.. ifconfig:: smv_current_version != '' and smv_current_version != 'rolling'
-
-  .. note::
-
-     For instructions on maintaining a source checkout of the **latest development version** of ROS 2, refer to
-     `Maintaining a source checkout of ROS 2 Rolling <../../rolling/Installation/Maintaining-a-Source-Checkout.html>`__
-
 .. contents::
    :depth: 2
    :local:

source/Installation/Maintaining-a-Source-Checkout.rst

@@ -112,7 +112,7 @@ Hooray!
 
 Next steps after installing
 ---------------------------
-Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
+Continue with the :doc:`tutorials and demos <../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
 Additional RMW implementations (optional)
 -----------------------------------------

source/Installation/RHEL-Install-RPMs.rst

@@ -117,7 +117,7 @@ Hooray!
 
 Next steps after installing
 ---------------------------
-Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
+Continue with the :doc:`tutorials and demos <../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
 Using the ROS 1 bridge
 ----------------------

source/Installation/Ubuntu-Install-Debians.rst

@@ -74,7 +74,7 @@ Hooray!
 
 Next steps after installing
 ---------------------------
-Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
+Continue with the :doc:`tutorials and demos <../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
 Additional RMW implementations (optional)
 -----------------------------------------

source/Installation/Windows-Install-Binary.rst

@@ -63,7 +63,7 @@ Make sure that the Visual C++ features are installed.
 
 An easy way to make sure they're installed is to select the ``Desktop development with C++`` workflow during the install.
 
-   .. image:: /Installation/images/windows-vs-studio-install.png
+   .. image:: ./images/windows-vs-studio-install.png
 
 Make sure that no C++ CMake tools are installed by unselecting them in the list of components to be installed.
 

source/Installation/_Windows-Install-Prerequisites.rst

@@ -174,4 +174,4 @@ As the name implies, Rolling is continuously updated and **can have in-place upd
 We recommend that most people use the most recent stable distribution instead (see :ref:`list_of_distributions`).
 
 Packages released into the Rolling distribution will be automatically released into future stable distributions of ROS 2.
-:doc:`Releasing a ROS 2 package <../How-To-Guides/Releasing/Releasing-a-Package>` into the Rolling distribution follows the same procedures as all other ROS 2 distributions.
+:doc:`Releasing a ROS 2 package <./How-To-Guides/Releasing/Releasing-a-Package>` into the Rolling distribution follows the same procedures as all other ROS 2 distributions.