[PLA] [PATCH] typo fixes for pla 6 .. 8

[Raphael Langerhorst]

Hi,

attached patch fixes typos found in pla00006.txt through pla00008.txt.

Please review the fixes. In particular pla00006.txt contained a bug in the squareClass constructor AFAICS. (from AK)

Regards,
Raphael
-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
-------------- next part --------------
Index: pla00006.txt
===================================================================
--- pla00006.txt	(revision 11)
+++ pla00006.txt	(working copy)
@@ -36,7 +36,7 @@
 A member variable within an object can either refer to data, or it can refer to
 code blocks. Their default values can be preset at the time of class definition.
 New instances will have these default values set. Afterwards, every code block
-with access to the object and/or the class will be able the declare additional
+with access to the object and/or the class will be able to declare additional
 member variables.
 
 Visibility
@@ -127,7 +127,7 @@
 
 	squareClass := # rectangleClass (
 		set_b := { set_a(%1) }; // we overwrite set_b
-		get_b := { get_b() };   // same here
+		get_b := { get_a() };   // same here
 
 		init := { ( ?? a ? '.init(a: %a, b: %a) ; };
 		// ' is the base class object, like "super" in other languages
@@ -141,7 +141,7 @@
 previously defined rectangleClass: a square is a special case of a rectangle,
 where both sides a and b have the same length. Thus, we redefine the methods
 set_b and get_b to access the set_a/get_a methods instead, and redefine the
-constructor method "init" the initialize the base object appropriately. All
+constructor method "init" to initialize the base object appropriately. All
 other functionality (computing area, circumference, etc.) is inherited from
 rectangleClass and left unchanged.
 
Index: pla00007.txt
===================================================================
--- pla00007.txt	(revision 11)
+++ pla00007.txt	(working copy)
@@ -12,8 +12,8 @@
 
 
 Cross-Side Scripting Vulnerabilities, SQL injections and other security
-problems related to missing quopting and encoding are the problably most
-dangerous class of security problems this days.
+problems related to missing quoting and encoding are problably the most
+dangerous class of security problems these days.
 
 Buffer Overflow are imo not that significant anymore because a great amount
 of new networking software is written already in scripting languages which
@@ -47,7 +47,7 @@
 
 	foobar := "$xx::foo$bar";
 
-Also note that a untyped string may never contain typed strings. So the
+Also note that an untyped string may never contain typed strings. So the
 following is also illegal:
 
 	foo := "this is a test: $hahaha::(1+2+3)";
@@ -61,10 +61,10 @@
 or quote the parts according to their types, throwing an exception if
 unsupported types are found or unsupported constructs are found.
 
-One such 'unsupported construct' would e.g. passing including typed strings in 
-SQL queryies using the string:: or integer:: type.
+One such 'unsupported construct' would be e.g. passing including typed strings
+in SQL queryies using the string:: or integer:: type.
 
-Most functions that are passed a string eighter only except typed or untyped
+Most functions that are passed a string eighter only expect typed or untyped
 strings.
 
 E.g. regualar expressions are only possible with untyped strings because they
@@ -73,7 +73,7 @@
 SQL queries on the other hand may only be allowed typed for security reasons.
 
 Since each SQL backend might have a different idea of how quoting should be
-done it makes sense to delegate to actual quoting to the SQL backend instead
+done it makes sense to delegate the actual quoting to the SQL backend instead
 of doing it premature in the application.
 
 
Index: pla00008.txt
===================================================================
--- pla00008.txt	(revision 11)
+++ pla00008.txt	(working copy)
@@ -11,7 +11,7 @@
            *****************************************************
 
 
-The examples is this document are based on the syntax from PLA #00004.
+The examples in this document are based on the syntax from PLA #00004.
 
 AK suggested on the PLA mailing list to use functions for controlling
 the program flow: