From 59eca08ad0d77ce8837c7e22241e9f2d3a2925c3 Mon Sep 17 00:00:00 2001
From: Carl Masak <cmasak@gmail.com>
Date: Thu, 25 Mar 2010 13:25:13 +0100
Subject: [PATCH] [operators] minor typo/punctuation fixes

---
 src/operators.pod | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/operators.pod b/src/operators.pod
index 23f2b21..04cf377 100644
--- a/src/operators.pod
+++ b/src/operators.pod
@@ -246,7 +246,7 @@ and thus stores only one item in the variable C<@scores>, the rest is
 parsed as a list  N<and discarded, because it is not stored in any variable>.
 
 The ways in which this statement is parsed in Perl 6 is governed by
-I<precedence rules>. For example they state that the infix C<< => >> operator
+I<precedence rules>. For example, they state that the infix C<< => >> operator
 binds its arguments tighter than the infix C<,> operator, which in turn binds
 tighter than the C<=> assignment operator N<there are actually two assignment
 operators with different precedence. When the right-hand side appears to be a
@@ -257,8 +257,8 @@ and assignment of a two-item list to a single variable>.
 
 
 The precedence rules for Perl 6 allow very natural expression of many commonly
-used idioms without any parenthesis, or even without thinking about
-precedence. If you want to force a different way of parsing, parenthesis can
+used idioms without any parentheses, or even without thinking about
+precedence. If you want to force a different way of parsing, parentheses can
 be used around an expression. Then this parenthesis group has the tightest
 possible precedence.