spelling fixes to the documentation

[metalua.git] / doc / manual / match-ref.tex

diff --git a/doc/manual/match-ref.tex b/doc/manual/match-ref.tex
index 388887c635c89bd2504ea9369d2845bc23f7fce2..d11dedf2e18f13e6d624f8b79ee64e12560c2a5c 100644 (file)
--- a/doc/manual/match-ref.tex
+++ b/doc/manual/match-ref.tex
@@ -52,9 +52,9 @@ other patterns and blocks are ignored. If no pattern matches, an error
 {\tt"mismatch"} is raised. However, we'll see it's easy to add a catch-all
 pattern at the end of the match, when we want it to be failproof.
 
-\subsection{Patterns definition}
+\subsection{Pattern definitions}
 
-\paragraph{Atomic litterals}
+\paragraph{Atomic literals}
 Syntactically, a pattern is mostly identical to the values it matches: numbers,
 booleans and strings, when used as patterns, match identical values.
 
@@ -98,10 +98,10 @@ end
 \end{verbatim}
 
 When a variable appears several times in a single pattern, all the elements they
-match must be equal, in the sense of the "==" operator. Fore instance, pattern \{
+match must be equal, in the sense of the "==" operator. For instance, pattern \{
   x, x \} will match value \{ 1, 1 \}, but not \{ 1, 2 \}. Both values would be
 matched by pattern \{ x, y \}, though. A special identifier is "\_", which doesn't
-bind its content. Even if it appears more than once in the pattern, metched
+bind its content. Even if it appears more than once in the pattern, matched
 value parts aren't required to be equal. The pattern "\_" is therefore the
 simplest catch-all one, and a match statement with a "{\tt| \_ ->}" final
 statement will never throw a "mismatch" error.