Index: non-graphical/index.html
===================================================================
--- non-graphical/index.html	(revision 7099)
+++ non-graphical/index.html	(revision 7100)
@@ -31,7 +31,7 @@
 <p>
 Below are different methods and syntax to describe non-graphical sheets.
 
-<h2> tEDAx (declartive) </h2>
+<h2> tEDAx (declarative) </h2>
 <p>
 tEDAx is very easy to parse, well specified, and is relatively easy to
 read and write as human.
@@ -62,7 +62,7 @@
 of combining graphical and non-graphical sheets: U5 is a network of gates
 that controls chip-select; it's better drawn for clarity.
 
-<h2> fawk (turing complete) </h2>
+<h2> fawk (Turing-complete) </h2>
 <p>
 In some cases parts of the design can be specified using repetitive patterns.
 An easy way to handle this is to write a script that generates a graphical
@@ -75,7 +75,7 @@
 	<li> fawk is always available in librnd
 	<li> fawk supports execution limit and memory allocation limit so opening
 	     a non-graphical sheet specified as a fawk script is safe, an attacker
-	     won't be able to force sch-rnd into an inifinite loop or into allocating
+	     won't be able to force sch-rnd into an infinite loop or into allocating
 	     all system memory.
 </ul>
 <p>
@@ -84,11 +84,11 @@
 in main().
 <p>
 The script doesn't emit a netlist or declarative tEDAx non-graphical sheet.
-The result can be observed in sch-rnd by loading only the fakw script
+The result can be observed in sch-rnd by loading only the fawk script
 as a sheet and using the abstract model dialog.
 <p>
 (An alternative is implementing the cschem functions locally, as vararg
-fawk funcitons and make them print to stdout using fawk_print(). Then the
+fawk functions and make them print to stdout using fawk_print(). Then the
 script can be ran and debugged independently of cschem, using the example
 libfawk command line interpreter.)
 <p>