summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authordrbrain <drbrain@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2012-07-24 21:54:50 +0000
committerdrbrain <drbrain@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2012-07-24 21:54:50 +0000
commitb8903f88f43b8dfa6e6bc0194182fffb83c07eb2 (patch)
tree26a44aef74677c9f69894691aebcf1f1985f4ad0 /doc
parenta10f6137cc11598bab093ee694224cf4b5b15eb7 (diff)
* doc/re.rdoc: Fix spelling
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@36527 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'doc')
-rw-r--r--doc/re.rdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/re.rdoc b/doc/re.rdoc
index b912ca1d32..1c68533a8d 100644
--- a/doc/re.rdoc
+++ b/doc/re.rdoc
@@ -250,7 +250,7 @@ quantified as one <i>atomic</i> whole.
The <tt>(?:</tt>...<tt>)</tt> construct provides grouping without
capturing. That is, it combines the terms it contains into an atomic whole
without creating a backreference. This benefits performance at the slight
-expense of readabilty.
+expense of readability.
# The group of parentheses captures 'n' and the second 'ti'. The
# second group is referred to later with the backreference \2
@@ -271,7 +271,7 @@ it matches becomes fixed for the remainder of the match, unless the entire
subexpression must be abandoned and subsequently revisited. In this
way <i>pat</i> is treated as a non-divisible whole. Atomic grouping is
typically used to optimise patterns so as to prevent the regular
-expression engine from backtracking needlesly.
+expression engine from backtracking needlessly.
# The <tt>"</tt> in the pattern below matches the first character of
# the string, then <tt>.*</tt> matches <i>Quote"</i>. This causes the
@@ -594,7 +594,7 @@ Example:
$+ #=> "c"
# same as m[-1]
-These global variables are thread-local and method-local varaibles.
+These global variables are thread-local and method-local variables.
== Performance