summary refs log tree commit diff stats
path: root/doc/effects.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/effects.txt')
-rw-r--r--doc/effects.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/effects.txt b/doc/effects.txt
index 4ed1d09f1..df624e8b0 100644
--- a/doc/effects.txt
+++ b/doc/effects.txt
@@ -11,13 +11,14 @@ Iff a proc is side effect free and all its argument are evaluable at
 compile time, it can be evaluated by the compiler. However, really
 difficult is the ``newString`` proc: If it is simply wrapped, it
 should not be evaluated at compile time! On other occasions it can
-and should be evaluted:
+and should be evaluated:
 
-.. code-block:: nim
+  ```nim
   proc toUpper(s: string): string =
     result = newString(len(s))
     for i in 0..len(s) - 1:
       result[i] = toUpper(s[i])
+  ```
 
 No, it really can always be evaluated. The code generator should transform
 ``s = "\0\0\0..."`` back into ``s = newString(...)``.