@@ -10,8 +10,8 @@ use crate::{RclrsError, ToResult};
1010/// This is locked whenever initializing or dropping any middleware entity
1111/// because we have found issues in RCL and some RMW implementations that
1212/// make it unsafe to simultaneously initialize and/or drop middleware
13- /// entities such as [ `rcl_context_t`] and [ `rcl_node_t`] as well middleware
14- /// primitives such as [ `rcl_publisher_t`], [ `rcl_subscription_t`] , etc.
13+ /// entities such as `rcl_context_t` and `rcl_node_t` as well middleware
14+ /// primitives such as `rcl_publisher_t`, `rcl_subscription_t`, etc.
1515/// It seems these C and C++ based libraries will regularly use
1616/// unprotected global variables in their object initialization and cleanup.
1717///
@@ -59,10 +59,10 @@ pub struct Context {
5959 pub ( crate ) handle : Arc < ContextHandle > ,
6060}
6161
62- /// This struct manages the lifetime and access to the [ `rcl_context_t`] . It will also
62+ /// This struct manages the lifetime and access to the `rcl_context_t`. It will also
6363/// account for the lifetimes of any dependencies, if we need to add
6464/// dependencies in the future (currently there are none). It is not strictly
65- /// necessary to decompose [ `Context`] and [ `ContextHandle`] like this, but we are
65+ /// necessary to decompose `Context` and `ContextHandle` like this, but we are
6666/// doing it to be consistent with the lifecycle management of other rcl
6767/// bindings in this library.
6868pub ( crate ) struct ContextHandle {
0 commit comments