Port fuse_tutorials

Signed-off-by: methylDragon <methylDragon@gmail.com>

fuse_core/include/fuse_core/async_motion_model.hpp

@@ -47,7 +47,7 @@ namespace fuse_core
 {
 
 /**
- * @brief A motion model base class that provides an internal node and an internal callback queue.
+ * @brief A motion model base class that provides an internal callback queue and executor.
  *
  * A model model plugin is responsible for generating constraints that link together timestamps
  * introduced by other sensors in the system. The AsyncMotionModel class is designed similar to a

fuse_core/include/fuse_core/async_publisher.hpp

@@ -77,9 +77,9 @@ class AsyncPublisher : public Publisher
   /**
    * @brief Initialize the AsyncPublisher object
    *
-   * This will store the provided name and graph object, and create an internal node for this
+   * This will store the provided name and graph object, and create an internal executor for this
    * instance that will use an internal callback queue serviced by a local thread. The
-   * AsyncPublisher::onInit() method will be called from here, once the internal node is properly
+   * AsyncPublisher::onInit() method will be called from here, once the callback queue is properly
    * configured.
    *
    * @param[in] interfaces The node interfaces to be used with the publisher

fuse_core/include/fuse_core/async_sensor_model.hpp

@@ -48,7 +48,7 @@ namespace fuse_core
 {
 
 /**
- * @brief A sensor model base class that provides an internal node and an internal callback queue.
+ * @brief A sensor model base class that provides an internal callback queue and executor.
  *
  * A sensor model plugin is responsible for generating new constraints, packaging them in a
  * fuse_core::Transaction object, and passing them along to the optimizer. The asynchronous
@@ -59,7 +59,7 @@ namespace fuse_core
  * standard ROS node. First and most obvious, the sensor model is designed as a plugin, with all
  * of the stipulations and requirements that come with all ROS plugins (must be derived from a
  * known base class, will be default constructed). Second, the base AsyncSensorModel class
- * provides an internal node that is hooked to a local callback queue and local executor on
+ * accepts node interfaces for a node that is hooked to a local callback queue and local executor on
  * init. This makes it act like a full ROS node -- subscriptions trigger message callbacks,
  * callbacks will fire sequentially, etc. However, authors of derived sensor models should be
  * aware of this fact and avoid creating additional sub-nodes, or at least take care when