Fixed link and minor layout bug.

ralph-lange · ralph-lange · commit fedf6b8de18e · 2020-11-11T18:24:19.000+01:00
Signed-off-by: Ralph Lange &lt;ralph.lange@de.bosch.com&gt;
diff --git a/_docs/overview/features/index.md b/_docs/overview/features/index.md
@@ -9,9 +9,9 @@ redirect_from:
 <script src="https://code.jquery.com/jquery-1.12.4.min.js"></script>
 <script>
 function updateVisibilityOfFeatureDescriptions() {
-  $('.feature').not('feature_is_active').find('.three_dots').css({ 'color': '#BBBBBB' });
+  $('.feature').not('feature_is_active').find('.three_dots').show();
   $('.feature').not('feature_is_active').find('.feature_description').slideUp(500);
-  $('.feature_is_active').find('.three_dots').css({ 'color': 'white' });
+  $('.feature_is_active').find('.three_dots').hide();
   $('.feature_is_active').find('.feature_description').slideDown(500);
 }
 
@@ -32,13 +32,15 @@ $(document).ready( function() {
 </script>
 
 <style>
+  .three_dots {
+    color: #BBBBBB;
+  }
   .feature_title {
     font-weight: bold;
     margin: 0 0 2pt 0;
   }
   .feature_description {
-    text-align: justify;
-    margin-left: 1.6em;
+    margin-left: 3em;
   }
   .feature_description ~ p {
     margin: 0 0 2pt 0;
@@ -98,7 +100,7 @@ Micro-ROS offers **seven key features** that make it ready for use in your micro
  <p class="feature_title">&#9745; Long-term maintainability and interoperability<span class="three_dots"> (...)</span></p>
  <div class="feature_description">
   <p>Micro-ROS is made up of well-established components: Famous open-source RTOSs, a standardized middleware, and the standard ROS 2 Client Support Library (rcl). In this way, the amount of micro-ROS-specific code was minimized for long-term maintainability. At the same time, the micro-ROS stack preserves the modularity of the standard ROS 2 stack. Micro-ROS can be used with a custom middleware layer - and thus standard - or a custom ROS client library.</p>
-  <p>Furthermore, by the [System-Of-Systems Synthesizer](https://soss.docs.eprosima.com/) (SOSS), a fast and lightweight <a href="https://www.omg.org/spec/DDS-XTypes">OMG DDS-XTYPES standard</a> integration tool, further middleware protocols can be connected. For example, we have developed the SOSS-FIWARE and SOSS-ROS2 System-Handles, which connect ROS 2 and micro-ROS with the <a href="https://www.fiware.org/">FIWARE Context Broker</a> by the NGSIv2 (Next Generation Service Interface) standard by leveraging the integration capabilities of the SOSS core.</p>
+  <p>Furthermore, by the <a href="https://soss.docs.eprosima.com/">System-Of-Systems Synthesizer</a> (SOSS), a fast and lightweight <a href="https://www.omg.org/spec/DDS-XTypes">OMG DDS-XTYPES standard</a> integration tool, further middleware protocols can be connected. For example, we have developed the SOSS-FIWARE and SOSS-ROS2 System-Handles, which connect ROS 2 and micro-ROS with the <a href="https://www.fiware.org/">FIWARE Context Broker</a> by the NGSIv2 (Next Generation Service Interface) standard by leveraging the integration capabilities of the SOSS core.</p>
  </div>
 </div>
 
@@ -108,4 +110,4 @@ Micro-ROS follows the [ROS 2 architecture](https://index.ros.org/doc/ros2/) and
 
 <img src="/img/micro-ROS_architecture.png" style="display: block; margin: auto; width: 100%; max-width: 500px;"/>
 
-Dark blue components are developed specifically for micro-ROS. Light blue components are taken from the standard ROS 2 stack. We seek to contribute as much code back to the ROS 2 mainline codebase as possible.
+Dark blue components are developed specifically for micro-ROS. Light blue components are taken from the standard ROS 2 stack. We seek to contribute as much code back to the ROS 2 mainline codebase as possible.
