summary refs log tree commit diff stats
diff options
context:
space:
mode:
authordef <dennis@felsin9.de>2014-06-21 13:42:29 +0200
committerdef <dennis@felsin9.de>2014-06-21 13:42:29 +0200
commit3c89ad78eb3158a49509ac86152195fb1f6ea8e5 (patch)
tree6288452b598328045a252d30994b4ecfaf0db83b
parentbe534279da5021aa5e6621430a52ee1573f1a01f (diff)
downloadNim-3c89ad78eb3158a49509ac86152195fb1f6ea8e5.tar.gz
Rename {.effect.} to {.effects.} in Tut 2
-rw-r--r--doc/tut2.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tut2.txt b/doc/tut2.txt
index 11b485f50..1e23618e0 100644
--- a/doc/tut2.txt
+++ b/doc/tut2.txt
@@ -501,7 +501,7 @@ with the file and line where the uncaught exception is being raised, which may
 help you locate the offending code which has changed.
 
 If you want to add the ``{.raises.}`` pragma to existing code, the compiler can
-also help you. You can add the ``{.effect.}`` pragma statement to your proc and
+also help you. You can add the ``{.effects.}`` pragma statement to your proc and
 the compiler will output all inferred effects up to that point (exception
 tracking is part of Nimrod's effect system). Another more roundabout way to
 find out the list of exceptions raised by a proc is to use the Nimrod ``doc2``