Fix mostly mrs_msgs links

Author: filipopo

docs/40-api/30-trajectories.md

@@ -10,14 +10,14 @@ This page is describing the upcoming ROS2 version of the MRS UAV System (however
 
 ## Definitions
 
-**Path** ([mrs_msgs/Path.msg](https://ctu-mrs.github.io/mrs_msgs/msg/Path.html))
+**Path** ([mrs_msgs/Path.msg](https://ctu-mrs.github.io/mrs_msgs/interfaces/msg/Path.html))
 
 - An ordered sequence of geometric poses without any notion of time.
 - Specifies what poses should the UAV fly through: no control over dynamics.
 - Has to be sampled first by sampling period `T`.
 - See [below](https://ctu-mrs.github.io/docs/system/trajectories.html#generating-trajectories-from-paths) on how to generate dynamically feasible trajectories from paths.
 
-**Trajectory** ([mrs_msgs/TrajectoryReference.msg](https://ctu-mrs.github.io/mrs_msgs/msg/TrajectoryReference.html))
+**Trajectory** ([mrs_msgs/TrajectoryReference.msg](https://ctu-mrs.github.io/mrs_msgs/interfaces/msg/TrajectoryReference.html))
 
 - An ordered time-parametrized sequence of geometric poses.
 - Specifies what pose should the UAV be in at given time: more control over dynamics.

docs/50-features/30-trajectory_generation/index.md

@@ -14,7 +14,7 @@ This page is describing the upcoming ROS2 version of the MRS UAV System (however
 
 ## General description
 
-The [mrs_uav_trajectory_generation](https://github.com/ctu-mrs/mrs_uav_trajectory_generation) package provides a method for generation a time-parametrized [trajectory](https://ctu-mrs.github.io/mrs_msgs/msg/TrajectoryReference.html) out of a [path](https://ctu-mrs.github.io/mrs_msgs/msg/Path.html) (a sequence of waypoints).
+The [mrs_uav_trajectory_generation](https://github.com/ctu-mrs/mrs_uav_trajectory_generation/tree/ros2) package provides a method for generation a time-parametrized [trajectory](https://ctu-mrs.github.io/mrs_msgs/interfaces/msg/TrajectoryReference.html) out of a [path](https://ctu-mrs.github.io/mrs_msgs/interfaces/msg/Path.html) (a sequence of waypoints).
 The resulting trajectory satisfies the current dynamics constraints of the UAV **and** completes the path in **minimum possible time**.
 The **maximum deviation** of the resulting trajectory from the supplied path is a user-configurable parameter.
 
@@ -46,12 +46,12 @@ The main differences are:
 
 ### ROS interface
 
-Input: [service](https://ctu-mrs.github.io/mrs_msgs/srv/PathSrv.html) and [topic](https://ctu-mrs.github.io/mrs_msgs/msg/Path.html) address:
+Input: [service](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/PathSrv.html) and [topic](https://ctu-mrs.github.io/mrs_msgs/interfaces/msg/Path.html) address:
 ```
 /uav*/trajectory_generation/path
 ```
 
-Output: by default, the node calls [/uav*/control_manager/trajectory_reference](https://ctu-mrs.github.io/mrs_msgs/srv/TrajectoryReferenceSrv.html) service to the [ControlManager](https://github.com/ctu-mrs/mrs_uav_managers).
+Output: by default, the node calls [/uav*/control_manager/trajectory_reference](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/TrajectoryReferenceSrv.html) service to the [ControlManager](../01-managers/index.md#controlmanager).
 
 ### Minimum waypoint distance
 

docs/50-features/55-octomap/octomap_planner.md

@@ -28,7 +28,7 @@ After the planning request to **user-specified goal** is obtained, the **Octomap
 
 ### ROS interface
 
-Input: The **user-specified goal** can be passed to **Octomap Planner** as a service of type [mrs_msgs/Vec4](https://ctu-mrs.github.io/mrs_msgs/srv/Vec4.html) or [mrs_msgs/ReferenceStampedSrv](https://ctu-mrs.github.io/mrs_msgs/srv/ReferenceStampedSrv.html) on topics:
+Input: The **user-specified goal** can be passed to **Octomap Planner** as a service of type [mrs_msgs/Vec4](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/Vec4.html) or [mrs_msgs/ReferenceStampedSrv](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/ReferenceStampedSrv.html) on topics:
 ```
 /uav*/octomap_planner/goto
 /uav*/octomap_planner/reference
@@ -40,7 +40,7 @@ The planning can be stopped by calling service
 ```
 which stops the planning process and sets the UAV to hovering state.
 
-Output: after each planning phase the node calls [/uav*/control_manager/trajectory_reference](https://ctu-mrs.github.io/mrs_msgs/srv/TrajectoryReferenceSrv.html) service provided by the [ControlManager](https://github.com/ctu-mrs/mrs_uav_managers#controlmanager).
+Output: after each planning phase the node calls [/uav*/control_manager/trajectory_reference](https://ctu-mrs.github.io/mrs_msgs/interfaces/srv/TrajectoryReferenceSrv.html) service provided by the [ControlManager](../01-managers/index.md#controlmanager).
 
 ### Planner types