Update _docs/overview/features/index.md

ralph-lange · Julián Bermúdez Ortega · ralph-lange · commit d1bcec107a8a · 2020-03-16T09:13:19.000+01:00
Co-Authored-By: Julián Bermúdez Ortega &lt;julianbermudez@eprosima.com&gt;
diff --git a/_docs/overview/features/index.md b/_docs/overview/features/index.md
@@ -20,7 +20,7 @@ Inter- and intra-process communication using the same API | No shared-memory int
 Composition of node components at compile-, link- or dlopen-time | Composition at compile-time only. Composition at runtime would depend highly on the RTOS.
 Support for nodes with managed lifecycles | Very basic support provided by [rcl_lifecycle](https://github.com/ros2/rcl/tree/master/rcl_lifecycle/) out of the box for micro-ROS. *Further convenience functions are planned.*
 DDS-Security support | DDS security is supported at micro-ROS-Agent. *Security mechanisms in Micro XRCE-DDS are planned for future releases.*
-Command-line introspection tools using an extensible framework | From a remote microprocessor all standard ROS 2 tools can be used to introspect the micro-ROS nodes on an MCU. Micro-ROS nodes appear as ROS 2 nodes (by the agent). Note, however, that the node graph API is currently *not* available on the MCU.
+Command-line introspection tools using an extensible framework | From a remote microprocessor all standard ROS 2 tools can be used to introspect the micro-ROS nodes on an MCU. micro-ROS nodes appear as ROS 2 nodes (by the micro-ROS-Agent). Note, however, that the node graph API is currently *not* available on the MCU.
 Launch system for coordinating multiple nodes | No launch system for the micro-ROS nodes on an MCU available. Such a system would depend highly on the RTOS. The system-modes concept developed with micro-ROS allows runtime configuration/orchestration of ROS 2 and micro-ROS nodes together.
 Namespace support for nodes and topics | Available just as in ROS 2.
 Static remapping of ROS names | *Should be available if passed as argument via standard rcl API - to be checked.*
