Index: 06_features/funcmap/index.html
===================================================================
--- 06_features/funcmap/index.html	(revision 9392)
+++ 06_features/funcmap/index.html	(revision 9393)
@@ -20,7 +20,7 @@
 However these are time consuming procedures and prone to error as some
 functionality are in group, e.g. an SPI typically requires a clock and at
 least a MISO or a MOSI (but usually both). With the above manual processes
-the software is not doing any verification whether function-terminal assigments
+the software is not doing any verification whether function-terminal assignments
 are valid (the given terminal indeed has the given function) or whether a
 group of functions, like SPI, have all relevant terminals marked.
 <p>
@@ -38,7 +38,7 @@
 each port of the component to compute a funcmap name to display - this is
 how the alternate function is applied. Instead of a hardwired string, the
 symbol shall print the computed funcmap name attribute. This way, after
-a succesful compilation, the sheet shows the dynamically calculated,
+a successful compilation, the sheet shows the dynamically calculated,
 verified alternate function of each port.
 <p>
 Furthermore CLI actions and GUI dialog boxes are provided to overview and
@@ -61,7 +61,7 @@
 <H4 autotoc="yes"> Funcmap data model and file format </H4>
 <p id="format">
 A funcmap operates on the abstract model. It lists alternate functions
-of each port and optiopnally groups those functions in weak and strong
+of each port and optionally groups those functions in weak and strong
 function groups.
 <p>
 A typical example is a microcontroller (MCU) that can have the same port
@@ -160,7 +160,7 @@
 <p id="attr">
 Component attribute: <b>funcmap</b>. Specifies the name of the
 funcmap to use. This is the file name in the external library, without
-the .funcmpa suffix. The attribute is typically specified in the symbol.
+the .funcmap suffix. The attribute is typically specified in the symbol.
 If the component is compiled from multiple symbols, the attribute should
 be specified only in one of the symbols. If not specified, the component
 is not affected by funcmap.
@@ -167,7 +167,7 @@
 <p>
 Port attribute: <b>funcmap/name</b> (typically specified in a terminal).
 Specifies the function the given port should take. Shall be one of the
-functions avialable for the given port. Shall be used only for ports in
+functions available for the given port. Shall be used only for ports in
 components with the funcmap attribute set. If a port in a component with
 the funcmap attribute does not specify its funcmap/name, it is computed
 by the funcmap plugin (the port name is copied into the funcmap/name attribute).
@@ -190,7 +190,7 @@
 <p>
 Both the sheet local library and the external library can be browsed
 using the funcmap library dialog. The sheet local library can be
-flushed (removed) from the File/Maintenance menu; upon the next compiation
+flushed (removed) from the File/Maintenance menu; upon the next compilation
 all funcmap references are imported into the sheet local library from the
 external libraries again. This is how external library changes can be
 applied to a sheet.
@@ -209,7 +209,7 @@
 	<li> <b>FuncmapPrintTable</b> that prints the funcmap state table for a
 	     component to stdout (same table that the component funcmap dialog
 	     presents)
-	<li> <b>FuncmapChange</b> that can changeport function selection in
+	<li> <b>FuncmapChange</b> that can change port function selection in
 	     a verified way and can select function for multiple ports by
 	     a function group.
 </ul>
@@ -224,7 +224,7 @@
 <p>
 The per component funcmap summary table dialog can be invoked from the right
 click context menu of symbols. This dialog box presents the tabular view
-of all ports (rows) and funtions (columns). Once a port is selected,
+of all ports (rows) and functions (columns). Once a port is selected,
 the function of that port can be easily stepped through its available
 functions. Alternatively the function can also be set by explicitly
 selecting one of the alternate functions (using the change button).
@@ -263,14 +263,14 @@
 utilized, which is an error that is reported as a DRC violation.
 <p>
 For example on the <a href="#example">attiny24</a>, there are two
-very similar sync serial devides are available with shared
+very similar sync serial devices are available with shared
 ports: SPI and USI. SPI has SCK, MISO and MOSI while USI has SCK, DI and DO.
 Both SPI and USI are strong function groups. Considerations when running the
 verification for the SPI function group:
 <ul>
-	<li> SCK is present in both SPI and USI using the same name; if it is assigned to a port, it's <i>multi</i> state, oterhwise it is in <i>unused</i>state
+	<li> SCK is present in both SPI and USI using the same name; if it is assigned to a port, it's <i>multi</i> state, otherwise it is in <i>unused</i>state
 	<li> If MISO is assigned but MOSI is not, that is a violation
-	<li> If MOIS is assigned but MISO is not, that is a violation
+	<li> If MOSI is assigned but MISO is not, that is a violation
 	<li> If MISO and MISO are assigned but SCK is not, that is a violation
 	<li> If SCK is assigned but neither MISO nor MOSI, that is not reported as a violation (because SCK is <i>multi</i> so it is assumed it'd be used for another group, e.g. USI - but it is not verified while checking on SPI)
 </ul>
@@ -295,7 +295,7 @@
 <p>
 Boxsym-rnd does not generate the funcmap file; the funcmap file shall be
 written manually. It is common that an MCU or CPU symbol is a heavy symbol
-thta works with only one funcmap. In that case the funcmap attribute could
+that works with only one funcmap. In that case the funcmap attribute could
 be specified on component level (in the global section of the boxsym
 input file).