[PLA] [PATCH] typos - separate and strategies

Raphael Langerhorst raphael-langerhorst at gmx.at
Sat Dec 22 15:20:30 CET 2007


Hi,

attached patch fixes various separate* and strategy typos.

Regards,
Raphael
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger?did=10
-------------- next part --------------
Index: pla00009.txt
===================================================================
--- pla00009.txt	(revision 13)
+++ pla00009.txt	(working copy)
@@ -50,7 +50,7 @@
 [ expression-list ]
 
 	Associativity: Nesting
-	List of elements seperated by ',' operator.
+	List of elements separated by ',' operator.
 	Each element may begin with 'id :' or 'expression =>' for
 	non-positional list elements.
 
@@ -221,7 +221,7 @@
 
 Macros definitions may only contain macro identifiers, round brackets,
 curly brackets and expressions. This elements must be specified whitespace
-seperated in the macro declaration.
+separated in the macro declaration.
 
 Expressions are written in the macro declaration as $foobar and _every_
 matching $foobar in the macro body is substituted (regardless of the context).
Index: pla00002.txt
===================================================================
--- pla00002.txt	(revision 13)
+++ pla00002.txt	(working copy)
@@ -187,7 +187,7 @@
 	Push a constant value on the stack.
 	In fact this is just a bogus placeholder for something smart. But without scalar
 	variables the concept of scalars is rather tricky. I already have some ideas
-	for these issues, which I will discuss in a seperate document.
+	for these issues, which I will discuss in a separate document.
 	Return the current context with next instruction pointer
 
   - OPERATOR "*"
@@ -203,6 +203,6 @@
 
 So long the basic idea. The details of the implementation of the context and
 instruction pointer objects are postponed to a later document because I have
-various possible implementation stretegies in mind that I'd like to discuss
-seperately.
+various possible implementation strategies in mind that I'd like to discuss
+separately.
 


More information about the PLA mailing list