Index: examples1.txt
===================================================================
--- examples1.txt	(revision 2790)
+++ examples1.txt	(revision 2791)
@@ -20,7 +20,7 @@
 	let e2 e1
 	assert abs(netlen(e1) - netlen(e2)) < 2 mm
 
-# Example 3: check if isolation gap is mantained between any HV and LV nets
+# Example 3: check if isolation gap is maintained between any HV and LV nets
 # (Lazy: assume any copper is part of a network, compare net-to-net only)
 #
 # hv  is the list of high voltage nets
@@ -31,7 +31,7 @@
 	let lv  (@.p.type == type(net)) && !(@.a.high_voltage)
 	assert !is_closer(lv, hv, 4 mm) 
 
-# Example 4: check if isolation gap is mantained between any HV and LV nets
+# Example 4: check if isolation gap is maintained between any HV and LV nets
 # (Proper way: do not forget about copper not part of any network!)
 #
 # hv  is the list of high voltage nets
Index: proposal1.txt
===================================================================
--- proposal1.txt	(revision 2790)
+++ proposal1.txt	(revision 2791)
@@ -35,8 +35,8 @@
 
 P15 Note: the language is case sensitive with keywords and builtins using
     lowercase only. For better readability, in syntax description in this
-    document uppercase words are user choosen identifiers or fields. Whitepace
-    character sequences are usually threated as a single whitespace. (This
+    document uppercase words are user chosen identifiers or fields. Whitespace
+    character sequences are usually treated as a single whitespace. (This
     does not mean identifiers have to be uppercase in a program.)
 
     The syntax of a search statement is:
@@ -91,7 +91,7 @@
 P42 If the EXPR in an assert evaluates to false, a DRC violation is generated.
 
 P43 If an assert EXPR is a list anywhere else than in a function argument, it is
-    evaluated for all valid memebers of the list (see P45, P46). For example
+    evaluated for all valid members of the list (see P45, P46). For example
     if there is a variable called FOO, which is a list of objects
     (built using a search statement), expression
 
@@ -116,8 +116,8 @@
     is smaller than 10 mil, the right size is not evaluated. See also: P45, P46.
 
 P45 A field reference is valid if the field exists. For example a line object
-    has a thicnkess attribute, thus the .p.thickness is valid, but a polygon
-    object does not have a thickness and .p.thicnkess on a polygon is invalid.
+    has a thickness attribute, thus the .p.thickness is valid, but a polygon
+    object does not have a thickness and .p.thickness on a polygon is invalid.
     An user attribute reference (e.g. field .a.baz) is valid if the attribute
     key exists in the given object.
 
Index: requirements.txt
===================================================================
--- requirements.txt	(revision 2790)
+++ requirements.txt	(revision 2791)
@@ -1,7 +1,7 @@
 The Dynamic DRC should be able to solve at least these tasks:
 	- check start grounding
 	- require element placement:
-		- specific elements to be close to eachother
+		- specific elements to be close to each other
 		- element close to the edge
 		- element close to a network or other copper feature
 	- perform copper vs. copper checks