Get rid of documentation warnings.

Documentation warnings are annoying. So i've get rid of them.

Author: GueLaKais

rclrs/src/parameter.rs

@@ -696,9 +696,9 @@ impl<'a> Parameters<'a> {
     /// Returns:
     /// * `Ok(())` if setting was successful.
     /// * [`Err(DeclarationError::TypeMismatch)`] if the type of the requested value is different
-    /// from the parameter's type.
+    ///   from the parameter's type.
     /// * [`Err(DeclarationError::OutOfRange)`] if the requested value is out of the parameter's
-    /// range.
+    ///   range.
     /// * [`Err(DeclarationError::ReadOnly)`] if the parameter is read only.
     pub fn set<T: ParameterVariant>(
         &self,

rclrs/src/parameter/range.rs

@@ -32,7 +32,7 @@ impl From<()> for ParameterRanges {
 /// Usually only one of these ranges will be applied, but all have to be stored since:
 ///
 /// * A dynamic parameter can change its type at runtime, in which case a different range could be
-/// applied.
+///   applied.
 /// * Introspection through service calls requires all the ranges to be reported to the user.
 #[derive(Clone, Debug, Default)]
 pub struct ParameterRanges {

rclrs/src/subscription/message_info.rs

@@ -7,23 +7,23 @@ use crate::rcl_bindings::*;
 /// To quote the `rmw` documentation:
 ///
 /// > The identifier uniquely identifies the publisher for the local context, but
-/// it will not necessarily be the same identifier given in other contexts or processes
-/// for the same publisher.
-/// Therefore the identifier will uniquely identify the publisher within your application
-/// but may disagree about the identifier for that publisher when compared to another
-/// application.
-/// Even with this limitation, when combined with the publisher sequence number it can
-/// uniquely identify a message within your local context.
-/// Publisher GIDs generated by the RMW implementation could collide at some point, in which
-/// case it is not possible to distinguish which publisher sent the message.
-/// The details of how GIDs are generated are RMW implementation dependent.
+/// > it will not necessarily be the same identifier given in other contexts or processes
+/// > for the same publisher.
+/// > Therefore the identifier will uniquely identify the publisher within your application
+/// > but may disagree about the identifier for that publisher when compared to another
+/// > application.
+/// > Even with this limitation, when combined with the publisher sequence number it can
+/// > uniquely identify a message within your local context.
+/// > Publisher GIDs generated by the RMW implementation could collide at some point, in which
+/// > case it is not possible to distinguish which publisher sent the message.
+/// > The details of how GIDs are generated are RMW implementation dependent.
 ///
 /// > It is possible the the RMW implementation needs to reuse a publisher GID,
-/// due to running out of unique identifiers or some other constraint, in which case
-/// the RMW implementation may document what happens in that case, but that
-/// behavior is not defined here.
-/// However, this should be avoided, if at all possible, by the RMW implementation,
-/// and should be unlikely to happen in practice.
+/// > due to running out of unique identifiers or some other constraint, in which case
+/// > the RMW implementation may document what happens in that case, but that
+/// > behavior is not defined here.
+/// > However, this should be avoided, if at all possible, by the RMW implementation,
+/// > and should be unlikely to happen in practice.
 #[derive(Clone, Debug, PartialEq, Eq)]
 pub struct PublisherGid {
     /// Bytes identifying a publisher in the RMW implementation.

rclrs/src/wait.rs

@@ -329,7 +329,7 @@ impl WaitSet {
     ///
     /// - Passing a wait set with no wait-able items in it will return an error.
     /// - The timeout must not be so large so as to overflow an `i64` with its nanosecond
-    /// representation, or an error will occur.
+    ///   representation, or an error will occur.
     ///
     /// This list is not comprehensive, since further errors may occur in the `rmw` or `rcl` layers.
     ///