Index: user/06_features/hierarchic/index.html
===================================================================
--- user/06_features/hierarchic/index.html	(revision 10194)
+++ user/06_features/hierarchic/index.html	(revision 10195)
@@ -33,7 +33,7 @@
 design.
 <p>
 In a non-hierarchic case every component and network are in a single
-global namespace. In practice this means:
+project global namespace. In practice this means:
 <ul>
 	<li> if two or more concrete symbols have the same name, they are merged into a single abstract component
 	<li> if two or more concrete nets have the same name, they are merged into a single abstract net
@@ -62,12 +62,12 @@
 
 <h3 autotoc="yes"> Scopes, addressing </h3>
 
-<h4 autotoc="yes"> Basic: using only the global scope </h4>
+<h4 autotoc="yes"> Basic: using only the project global scope </h4>
 <p>
 In the simplest setup each child sheet is used only once. There are two
 ways to make connections across sheets:
 <ul>
-	<li> by naming nets and components in any sheet; they all end up in the global namespace
+	<li> by naming nets and components in any sheet; they all end up in the project global namespace (also called global namespace)
 	<li> by connecting the sheet ref sym's terminal on the parent sheet
 </ul>
 <p>
@@ -268,6 +268,35 @@
 safer choice.
 
 
+<h4 autotoc="yes"> Expert: scope summary and explicit global scoping </h4>
+<p>
+A full list of hierarchic name prefixes (and their scopes) can be
+found in the <a href="../../../design/06_hierarchy.html#des6:8">design document.</a>
+<p>
+The system is designed so that:
+</ul>
+	<li> the <i>auto</i> scope, when no prefix is prepended to the net name,
+	     usually does what's expected, searching from local to global, then if
+	     no existing net of the same name is found, creating a new globla net.
+	     This is the only addressing used in the flat (non-hierarchic) case and
+	     the most commonly used addressing for non-local objects in the
+	     hierarchic case
+	<li> it offers an easy to use ./ prefix, which is the most commonly used
+	     local scope prefix in the hierarchic case, locking the given object
+	     into the current sheet
+	<li> offers a less often used subtree local mechanism for real complicatedcase,
+	     prefixed with v/ for "search downward" or ^/ for "search upward"
+	<li> offers the exotic / prefix for explicitly addressing the global scope.
+<p>
+The explicit global scope prefix can be used in the real exotic case when
+a (near) bottom child sheet needs to address a project global net not being sure
+there was no same named sheet local or subtree local net in the hierarchy.
+The <i>auto</i> scope (no prefix) or the ./ or ^/ prefixes would pick up those
+intermediate nets, may they exist, not reaching the global scope. The / prefix
+turns off the search mechanism and searches right in the project global namespace;
+if the object is not found, it is created in the project global namespace.
+
+
 <h4 autotoc="yes"> Expert: component addressing </h4>