summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKazuki Tsujimoto <kazuki@callcc.net>2020-04-05 12:15:18 +0900
committerKazuki Tsujimoto <kazuki@callcc.net>2020-04-05 12:15:18 +0900
commitcab9788e0ca2c41a13e482a4a9924b5a968284fe (patch)
tree0a530097e0b40d1911693df0a160fb9b9fd507e3 /doc
parentec03d137428f83f7d8819e13cb788fbd7d4e75c7 (diff)
Fix typos
Diffstat (limited to 'doc')
-rw-r--r--doc/syntax/pattern_matching.rdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/syntax/pattern_matching.rdoc b/doc/syntax/pattern_matching.rdoc
index 3bb93093b2..9d3101c86b 100644
--- a/doc/syntax/pattern_matching.rdoc
+++ b/doc/syntax/pattern_matching.rdoc
@@ -35,7 +35,7 @@ Therefore, +case+ statement might be used for conditional matching and unpacking
else
puts "Unrecognized structure of config"
end
- # Prints: "connect with user 'admin'"
+ # Prints: "Connect with user 'admin'"
whilst standalone +in+ statement is most useful when expected data structure is known beforehand, to just unpack parts of it:
@@ -44,7 +44,7 @@ whilst standalone +in+ statement is most useful when expected data structure is
config in {db: {user:}} # will raise if the config's structure is unexpected
puts "Connect with user '#{user}'"
- # Prints: "connect with user 'admin'"
+ # Prints: "Connect with user 'admin'"
See below for more examples and explanations of the syntax.