Index: 06_features/simulation/index.html
===================================================================
--- 06_features/simulation/index.html	(revision 8842)
+++ 06_features/simulation/index.html	(revision 8843)
@@ -9,9 +9,9 @@
 <p>
 There are two levels of the implementation:
 <ul>
-	<li> low level, which requires more knowledgeon SPICE syntax, plus requires
+	<li> low level, which requires more knowledge on SPICE syntax, plus requires
 	     the drawing to be decorated with SPICE-specific symbols
-	<li> high level, which is further away from teh SPICE syntax and is designed
+	<li> high level, which is further away from the SPICE syntax and is designed
 	     to operate on drawings without having to add extra SPICE or simulation
 	     specific symbols (sources, probes, commands, etc.)
 </ul>
@@ -30,8 +30,8 @@
 <p>
 The low level simulation is recommended if:
 <ul>
-	<li> you already have a lot of expereince with spice and the SPICE syntax
-	<li> you want maximum flexibility on the SPICE side (arbitary commands)
+	<li> you already have a lot of experience with spice and the SPICE syntax
+	<li> you want maximum flexibility on the SPICE side (arbitrary commands)
 	<li> you do not mind making your drawing simulation-specific
 	<li> sch-rnd does not run the simulator, merely exports the netlist; you
 	     will need to run the simulator using the netlist (from a shell, maybe
@@ -56,7 +56,7 @@
 	     sources or resistors (e.g. load) or capacitors or inductances; removing
 	     parts; disconnecting pins; changing attributes (e.g. value of
 	     components); 
-	<li> a setup includes outpout configuration that contains commands for
+	<li> a setup includes output configuration that contains commands for
 	     SPICE to run different analyses and also contains instructions to
 	     sch-rnd on how to present the output of those runs.
 </ul>
@@ -123,7 +123,7 @@
 <p>
 In the list of properties for presentation and in the positive and negative
 connection of an <i>add modification<i>, node addresses are used. A node
-address is either the name of an <i>abstract network</i> or apair of
+address is either the name of an <i>abstract network</i> or a pair of
 <i>abstract component</i> and <i>port name</i>, e.g. CN2-4 means "port 4
 of component CN2".
 
@@ -166,7 +166,7 @@
 Sheets and project created before 1.0.2 will typically lack this view. Adding
 the view is trivial either in the view GUI and in the project file. The
 most important aspects is to include target_sim_ngspice at the end of the
-engline list ad include std_forge before that.
+engine list ad include std_forge before that.
 <p>
 As of 1.0.2, the ordered engine list for the sim_ngspice view is:
 <ol>
@@ -210,7 +210,7 @@
 </ul>
 <p>
 The extra symbols drawn for spice simulation may interfere with other workflows,
-e.g. if the same project is used as a soruce for a PCB workflow. There are
+e.g. if the same project is used as a source for a PCB workflow. There are
 multiple mechanisms to deal with this:
 <ul>
 	<li> the classic approach: draw spice-related extras on separate sheet and do not include that sheet in workflows different than spice
@@ -221,7 +221,7 @@
 <H3 autotoc="yes" id="test_benching"> Test benching </H3>
 <p>
 The test bench mechanism is responsible for selecting parts of the circuit
-for simulation. Test benching operatos on project level. It is implemented
+for simulation. Test benching operates on project level. It is implemented
 using the test_bench project stance and
 <a href="../../../design/10_forge.html#des10.1">forge-if/test_bench attribute</a>
 in symbols and wirenets to conditionally omit objects that are not part of
@@ -257,7 +257,7 @@
 <H4 autotoc="yes" id="test_bench"> Test benching in the config </H3>
 <p>
 The project stance test_bench is part of the config tree: /stances/test_bench
-is a string containign the name of the currently activated test bench; 
+is a string containing the name of the currently activated test bench; 
 /stances/test_bench_values is an array of all known test bench names. These
 shall be set on the project role (so they are part of the project file). The
 GUI expects and edits them on the project role.