Index: user/06_features/hierarchic/index.html
===================================================================
--- user/06_features/hierarchic/index.html	(revision 10262)
+++ user/06_features/hierarchic/index.html	(revision 10263)
@@ -120,7 +120,7 @@
 components and nets twice, there is a mechanism for creating objects in the
 <i>sheet local</i> scope. This is done by prefixing the component or net name
 by ./ (a dot and a slash). This prefix is removed by the compiler and the
-name is transformed into something unqiue - by default this is done prepending
+name is transformed into something unique - by default this is done prepending
 the <i>hierarchic path</i>, which is a slash separated list of sheet ref sym
 names from root to the given object. This is how Q1 becomes two FETs:
 S1/Q1 and S2/Q1. This system works side by side with the basic
@@ -316,7 +316,7 @@
 
 <h4 autotoc="yes"> Expert: hlibrary </h4>
 <p>
-The simpler usage discussed above, is also the self-containe usage: when
+The simpler usage discussed above, is also the self-contained usage: when
 all sheets files of the hierarchy are placed in a single project directory
 and all sheets are listed in the project file (as root and aux sheets).
 A variation for large projects is placing all sheet files in a directory
@@ -329,9 +329,9 @@
 embedded in the sheet files, all project-specific configuration embedded in
 the project file.
 <p>
-Another usa case of hierarchic pages is maintaining a library of child sheets;
-for example in IC design it is common to have symbols for blocks like a xor gate
-and then have the "few FET implementation" of that xor gate as a child sheet
+Another use case of hierarchic pages is maintaining a library of child sheets;
+for example in IC design it is common to have symbols for blocks like a XOR gate
+and then have the "few FET implementation" of that XOR gate as a child sheet
 in a library. The advantage is that different projects can share and reuse
 the same child sheets. The drawback is that these child sheets are not copied
 into the project directory and the <b>project is not self-contained</b>: the
@@ -347,7 +347,7 @@
 found by name in the project file, sch-rnd announces this in the
 message log and automatically searches the hlibrary path and picks the first
 file with a matching name. The name is either in the form of "foo.rs" or
-just "foo" (sch-rnd automatically macthes the .rs or .lht endings).
+just "foo" (sch-rnd automatically matches the .rs or .lht endings).
 <p>
 Example project:
 <a href="../../../examples/hierarchic/50_hlibrary/">50_hlibrary</a> is
@@ -370,10 +370,10 @@
 
 <h4 autotoc="yes"> Expert: addressing sheets by path </h4>
 <p>
-Another way of addressing extenal chold sheets that are not listed in the
+Another way of addressing external child sheets that are not listed in the
 project file is path based addressing. This is done by using the sheet
 ref sym attribute <i>cschem/child/path</i> instead of cschem/child/name.
-The path must be relative to the parent sheet's path on thefile system.
+The path must be relative to the parent sheet's path on the file system.
 The sheet is automatically loaded as an external sheet during compilation.
 <p>
 Example project: