the other fixes by decasm++

docs/appendix-a-index.txt

@@ -7,7 +7,7 @@ It is sorted (almost as decided by [**leg**](#leg-op)) without prefixes like
 colon, dot, backslash, [*sigil*](appendix-g-glossary.html#sigil) or
 [*twigil*](appendix-g-glossary.html#twigil)
 and everything that contains punctuation or number comes first.
-Sometimes are added green placeholder:
+Sometimes a green placeholder is added:
 <span class="you-provide">n</span> stands for a [integer number](#Int-type),
 <span class="you-provide">f</span> is a floating [point number](#Num-type),
 <span class="you-provide">c</span> a single character,
@@ -23,13 +23,13 @@ After each method is its [*signature*](appendix-g-glossary.html#signature)
 (in round brackets), 
 telling you the value type (same as in placeholders) of the 
 [*parameters*](appendix-g-glossary.html#parameters) and the return value.
-The items itself are linked to a more detailed explanation inside of a tablet.
+Each item is linked to a more detailed explanation inside of a tablet.
 Each term is followed by a link «in french brackets» to a condensed summary
-listing of its category in [Appendix B](appendix-b-grouped.html)
-or to the according category in the tablets. Most links in the short description
+of its category in [Appendix B](appendix-b-grouped.html)
+or to the relevant category in the tablets. Most links in the short description
 lead to another item in A (when **bold**) or to the glossary (when *italic*).
 The chapter headlines serve as anchor and links to the navigation menu.
-Thatswhy large chapter like C are split into "C" (second letter a-m)
+Thats why large chapter like C are split into "C" (second letter a-m)
 and a following "n" (second letter n-z).
 
 

docs/tablet-0-history.txt

@@ -11,40 +11,41 @@ Back in the year 2000, things didn't look so good. The buzz around
 Perl was gone, because everybody had decent Regexes, even if theirs
 were not as tightly integrated as in Perl. And many of the other Perl
 5 features could be also found in Python or Ruby. Naturally, also, new
-shiny things appeared in mainstream languages, that couldn't so easily
+shiny things appeared in mainstream languages that couldn't so easily
 be pasted into Perl. The Perl syntax, especially for Regexes, is very
 rich, therefore you could hardly add something in a meaningful manner
 without changing a handful of others. Some features like "do {}
 while"-loops were just bolted on and other feature could not even be
 plugged in. A complete revamp was also more and more necessary because
-things like the OOP and missing signatures made problems to the Perl
+things like OOP and missing signatures made problems for Perl
 beginners. Other things like formats just had to move out of the
-interpreter into a module because they weren't that important as in
-the early days. And finally a lot of cruft had also to go, that was
-deprecated since Perl 5.0 like the ol' package'sub syntax.
-
-Much of these issues could be dealt within the perl 5 arena, and is
-recently done by the way, but if you would look into the perl
-internals, you would see a speed racer, highly tuned but with a lot of
-dirty tricks your cs-prof would't tell. In that magic world, were many
-things are mingled together merely invisibly, it is really hard, to
-bring in some cascades of changes. And even that would have some
+interpreter into a module because they weren't as important as in
+the early days. And finally a lot of cruft had also to go, syntax that
+was deprecated since Perl 5.0 like the ol' package'sub syntax.
+
+
+Many of these issues could be dealt with in the Perl 5 arena, and are
+recently done by the way. But if you look at the perl
+internals, you see a speed racer - highly tuned but with a lot of
+dirty tricks your CS-prof would't like. In that magic world were many
+things mingled together invisibly, making it really hard to
+bring in some changes. And even that would have some
 natural limits. Some nice features like lispish macros, which are
-really powerful and a way cleaner and faster in execution than perl 5
+powerful and much cleaner and faster in execution than Perl 5
 sourcefilters and a nice XS replacement, which would largely ease
 Perl's extensibility, are impossible to achieve with that codebase. It
 would be a complete rewrite anyway.
 
-But it was not only the language and his interpreter, also perl people
+But it was not only the language and his interpreter, but also perl people
 themself needed some new toy. Something to brim over with enthusiasm
 for. Perl 5 just worked, which is good, but sometimes boring if there
-i not much you expect to happen. Especially if there are problem like
+is not much you expect to happen. Especially if there are problem like
 described above. And Larry had the strong feeling that the Perl
 community had to open up anyway.
 
 So it had to be a complete new language with a brand new interpreter
 and Perl would be again the most cuddlesome thing around. As the Perl
-1 manpage tells you: Perl was always about to have all the cool
+1 manpage tells you: Perl was always about having all the cool
 features of other languages in one place. That isn't for the purpose
 of bling-bling. (You couldn't brag with lazy evaluated arrays in a hip
 hop video anyway) But it's about getting the task done the way you
@@ -84,7 +85,7 @@ Parrot
   * niecza
 
 Even the brave and higly skilled pumping nicholas the first wrote in
-the p5p list that in the regex engins were dragons he was afraid to
+the p5p list that in the regex engine were dragons he was afraid to
 wake up.
 
 ***

docs/tablet-1-language-design.txt

@@ -20,7 +20,7 @@ Strategy
 ========
 
 Every style and level of expertise has to be supported. And even more
-difficult: all of them have to play together well. The default often
+difficult: all of them have to play well together. The default often
 imitates a natural language (e.g., English). The following
 oft-repeated terms encapsulate strategies and concepts for this.
 
@@ -47,7 +47,7 @@ names and operators should be distinctive, similar things should look
 similar, different things different. Larry likes to add: weird things
 should also look weird. And sometimes even characters can be
 ideograms; like the Z meta-operator, which shows visually how it works
-(first left then right, then next left, etc.).
+(first left, then right, then next left, etc.).
 
 
 
@@ -78,7 +78,7 @@ the problems of that domain.
 Maximum reuse
 -------------
 
-Not only is syntax reused, to minimize the stuff you have to remember,
+Not only is syntax reused to minimize the stuff you have to remember,
 but concepts are reused also, wherever possible. For example, Pairs
 are used to build hashes or named parameters in routines calls. There
 are plenty more examples. Maybe the biggest one: the regex engine that
@@ -116,8 +116,8 @@ newline (`say $var`), or reading a file without a file handle
 (`slurp("filename").lines`). Rule of thumb: if you can think of a
 concept as trivial, then it should be. On the other hand, if you can
 think of a computable solution, it should at least be doable in Perl
-(no artificial walls). Huffman coding This is a refinement of the last
-rule: common, often used things have short, straightforward
+(no artificial walls). Huffman coding: This is a refinement of the last
+rule - common, often used things have short, straightforward
 names. More verbose names indicate more rare, harder to grasp
 concepts, or things that overwrite the default rules ("weird things
 should look weird"). It also implies that the defaults lean toward
@@ -134,7 +134,7 @@ should reflect logical units which can be freely combined. Making it
 more complicated than necessary is obviously not desirable. But
 oversimplification will create artificial complexity somewhere
 else. Like a water bed, where you can press down in one place but the
-water will go up in another.  All your paradigms are belong to us We
+water will go up in another.  All your paradigms are belong to us. We
 learn, take and adapt from every source possible to offer the best of
 all breeds. You should be able to keep your style when switching to
 Perl. Perl 6 supports the structured, object oriented, aspect
@@ -154,7 +154,7 @@ paradigm, but also every technique or neat trick loudly marketed out
 there as "must have" "in the \[%DATE%\]", should be available in Perl 6
 (or at least be possible), as long there is expressive value in it. A
 few examples include "named parameters", "lvalue subroutines",
-"parametizable subclasses" or "hygienic macros".
+"parametizable subclasses", or "hygienic macros".
 
 
 
@@ -168,7 +168,7 @@ fact, this happens so often that the term "second system syndrome" was
 coined. We chose this path for Perl 6 anyways, because we believe it's
 the only way to get a significantly better language.
 (Gradual improvements are flowing into Perl 5 all the time,
-sometimes inspired from Perl 6.) That's why the unofficial motto of
+sometimes inspired by Perl 6.) That's why the unofficial motto of
 Perl 6 is "Second system syndrome done right".
 
 
@@ -184,11 +184,11 @@ observed](appendix-d-delta.html#trends).
 Design Process
 ==============
 
-The initial source of the Perl 6 design came from 361 RFC (request for
-comments) submissions by people from all over the world. Larry Wall
+The initial source of the Perl 6 design came from 361 RFC (Requests For
+Comments) submissions by people from all over the world. Larry Wall
 sorted and commented on them in several documents called the
 Apocalypses (meaning "revelations"). Damian Conway wrote, for each
-Apocalypse, an Exegesis ("explanation"), that expounded Larry's
+Apocalypse, an Exegesis ("explanation"), that expounded on Larry's
 ideas. These are now all historic documents that not have changed
 since, because they were much harder to maintain than the Synopses
 ("abstracts" or "comparisons" (with Perl 5)). The Synopsis documents,

docs/tablet-4-operators.txt

@@ -22,9 +22,8 @@ teacher.
 
 Behind that link is a table which also tells you also the
 [associativity](appendix-b-grouped#operator-associativity) of
-every operator. This tells you after which rule to resolve precedence
-if one operator is used several times like in 2 * 3 * 7.
-
+every operator. This tells you the order in which an operator
+is resolved when used several times, like in 2 * 3 * 7.
 
 
 Comparison
@@ -37,7 +36,7 @@ Smartmatch
 
 This is the most mighty (much more mighty than its backported Perl 5
 twin) of all Perl 6 operators. It can be called the
-"compare-this-with-that-operator". If the left side of that infix op
+"compare-this-with-that-operator". If the left side of that infix operator
 matches somehow the content of the right side, it returns Bool::True,
 otherwise Bool::False. The negated form !~~ naturally works the other
 way around. The exact comparison operation depends on the [data
@@ -295,8 +294,8 @@ xxx
 Selfmade Operators
 ==================
 
-How to make your own is subject [this chapter](tablet-10-metaprogramming.html)
-in the metaprogramming tablet.
+How to make your own is subject [this chapter](tablet-10-metaprogramming.html#operators)
+at the metaprogramming tablet.
 
 
 ***

docs/tablet-5-io.txt

@@ -27,7 +27,7 @@ Writes text to the standard output (`$*OUT`, called `STDOUT` in Perl 5).
 This example just prints a [string literal](tablet-2-basic-syntax.html#quoting),
 but any type of value is allowed. **say** appends a line ending,
 according to the operating system convention.
-So every time you "say" something, it will later output will start on a fresh line.
+So every time you "say" something, later output will start on a fresh line.
 
 You can also give `say` a list of values. Each item will be taken as
 an expression to print. The results will be combined,
@@ -38,8 +38,7 @@ line ending will be added.
         which is ', compute_distance($earth, $our_home_planet),
         ' parsecs away.';
 
-That could also be written using [double-quoted
-strings](tablet-2-basic-syntax.html#double-quotes):
+That could also be written using [double-quoted strings](tablet-2-basic-syntax.html#double-quotes):
 
     say "Dear Earthlings, we come from $our_home_planet, which is { compute_distance($earth, $our_home_planet) } parsecs away.";
 

docs/tablet-9-regexes.txt

@@ -3,7 +3,8 @@
 > "We put the 'Regular' back into 'Expression'." — Larry Wall
 
 Similar to [quotes](tablet-2-basic-syntax.html#quoting),
-Regular Expressions are now a sublanguage, a language inside the language,
+Regular Expressions are now a sublanguage, a language inside the language
+([*slang*](apendix-g-glossary.html#slang) ),
 instead of just being funny strings.
 They are parsed by a completely different set of rules,
 which are stored in the special variable \$\~Regex (\$\~Trans for