summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorSimon Hafner <hafnersimon@gmail.com>2014-06-25 13:50:20 -0500
committerSimon Hafner <hafnersimon@gmail.com>2014-06-25 13:50:20 -0500
commitf793523ade7aa48dcf13ede123a0a434e39e54e0 (patch)
tree7c9d319007954673bb29b932f8c985dd028817a8
parent7a5be93ac4627e66298d66d2741cb4ea02ad6e2a (diff)
parent3c89ad78eb3158a49509ac86152195fb1f6ea8e5 (diff)
downloadNim-f793523ade7aa48dcf13ede123a0a434e39e54e0.tar.gz
Merge pull request #1294 from def-/tut-fix
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``