Index: user/06_features/hierarchic/index.html
===================================================================
--- user/06_features/hierarchic/index.html	(revision 10187)
+++ user/06_features/hierarchic/index.html	(revision 10188)
@@ -8,13 +8,17 @@
 
 <H2 autotoc="yes"> sch-rnd hierarchic design </H2>
 
+<p>
 This is an user guide; the formal specificaiton of the feature is
 documented in the design doc as 
 <a href="../../../design/06_hierarchy.html"> feature design </a> and
 <a href="../../../design/06_hierarchy_imp.html"> implementation notes </a>.
 
+<p>
 
-<h3> Non-hierarchic cases </h3>
+
+
+<h3 autotoc="yes"> Non-hierarchic cases </h3>
 <p>
 A non-hierarchic design has a single sheet or a set of sheets, with or
 without a project file. The latter is also called <i>flat multisheet</i>
@@ -27,7 +31,7 @@
 	<li> if two or more concrete nets have the same name, they are merged into a single abstract net
 </ul>
 
-<h3> Hierarchic design basics </h3>
+<h3 autotoc="yes"> Hierarchic design intro </h3>
 <p>
 In a hierarchic design a schematic sheet contains a symbol that represents
 a subsheet. This symbol is called the <i>sheet reference symbol</i> or
@@ -48,9 +52,9 @@
 a multi-level hierarchy. The only restriction is that the hierarchy needs to
 be free of loops (circuilar references).
 
-<h3> Scopes, addressing </h3>
+<h3 autotoc="yes"> Scopes, addressing </h3>
 
-<h4> Basic: using only the global scope </h4>
+<h4 autotoc="yes"> Basic: using only the global scope </h4>
 <p>
 In the simplest setup each child sheet is used only once. There are two
 ways to make connections across sheets:
@@ -93,7 +97,7 @@
 slightly different way by doing the wiring between sheet ref syms on the
 project-specific top (root) sheet differently.
 
-<h4> Intermediate: sheet-local objects </h4>
+<h4 autotoc="yes"> Intermediate: sheet-local objects </h4>
 <p>
 Hierarchy can also be used to produce repetitve parts. In this (oversimplified)
 <a href="../../../examples/hierarchic/20_led/">20_led example circuit </a>
@@ -127,7 +131,7 @@
 up being global in the intermediate use case.
 
 
-<h4> Intermediate: more on final names </h4>
+<h4 autotoc="yes"> Intermediate: more on final names </h4>
 <p>
 A slightly modified version of the same example is 
 <a href="../../../examples/hierarchic/22_led/"> 22_led</a>.
@@ -140,7 +144,7 @@
 In case the child sheet did not name the control net, a globally unique
 anon net name would have been generated for this net.
 
-<h4> Intermediate: passing down global nets </h4>
+<h4 autotoc="yes"> Intermediate: passing down global nets </h4>
 <p>
 Another modification of the original LED example is 
 <a href="../../../examples/hierarchic/24_led/"> 24_led</a>.
@@ -153,7 +157,7 @@
 <p>
 This is the same mechanism that the GND symbol uses.
 
-<h4> Advanced: subtree scope </h4>
+<h4 autotoc="yes"> Advanced: subtree scope </h4>
 <p>
 The intermediate setup covers the situation of reusable single-sheet
 modules, locking internal networks and components into the sheet local scope
@@ -195,15 +199,15 @@
 	- describe the example once the net names are known
 	- explain how auto is searching
 
-<h4> Expert: addressing by path </h4>
+<h4 autotoc="yes"> Expert: addressing by path </h4>
 <p>
 Not yet supported. (TODO)
 
-<h4> Expert: hlibrary </h4>
+<h4 autotoc="yes"> Expert: hlibrary </h4>
 <p>
 Not yet supported. (TODO)
 
-<h4> Expert: spice unslotting </h4>
+<h4 autotoc="yes"> Expert: spice unslotting </h4>
 <p>
 A special use case fr hierarchic designs is "unslotting" a symbol
 that was drawn as monolithic symbol. E.g. a dual opamp drawn