doc: cosmetics in the graphical toc of platforms

[simgrid.git] / docs / source / platform.rst

diff --git a/docs/source/platform.rst b/docs/source/platform.rst
index 1909927..b8286be 100644 (file)
--- a/docs/source/platform.rst
+++ b/docs/source/platform.rst
@@ -7,6 +7,11 @@
    window.onload=function() { // Wait for the SVG to be loaded before changing it
      var elem=document.querySelector("#TOC").contentDocument.getElementById("PlatformBox")
      elem.style="opacity:0.93999999;fill:#ff0000;fill-opacity:0.1;stroke:#000000;stroke-width:0.35277778;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1";
+
+     for (name of ["RoutingBox", "ProfileBox"]) {
+       var elem=document.querySelector("#TOC").contentDocument.getElementById(name)
+       elem.style="fill-opacity:0;opacity:0.93999999;stroke:#000000;stroke-width:0.35277778;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1";
+     }
    }
    </script>
    <br/>
@@ -75,7 +80,7 @@ Networking zones (:ref:`pf_tag_zone`) are used to factorize the description
 to reduce the size of your platform on disk and in memory. Then, when
 a host wants to communicate with another host belonging to the same
 zone, it is the zone's duty to find the list of links that are
-involved in the communication. In the above example, since we use
+involved in the communication. In the above examples, since we use
 ``routing="Full"``, all routes must be explicitly given using the
 :ref:`pf_tag_route` and :ref:`pf_tag_link_ctn` tags (this :ref:`routing
 model <pf_rm>` is both simple and inefficient :) It is OK to not