summary refs log tree commit diff stats
diff options
context:
space:
mode:
authortersec <tersec@users.noreply.github.com>2022-02-18 15:06:11 +0000
committerGitHub <noreply@github.com>2022-02-18 16:06:11 +0100
commitf019e999d491ecf462421bd750aec0465d308094 (patch)
tree87addf1ca7069f17de81065f88e413fb282c8897
parent30e9f23ec04618616dcf2aaa7980794bad2135ed (diff)
downloadNim-f019e999d491ecf462421bd750aec0465d308094.tar.gz
keep casing of noinit and noreturn pragmas consistently documented (#19535)
-rw-r--r--doc/manual.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual.rst b/doc/manual.rst
index 2469a0525..e45133c38 100644
--- a/doc/manual.rst
+++ b/doc/manual.rst
@@ -2818,7 +2818,7 @@ The implicit initialization can be avoided for optimization reasons with the
 
 .. code-block:: nim
   var
-    a {.noInit.}: array[0..1023, char]
+    a {.noinit.}: array[0..1023, char]
 
 If a proc is annotated with the `noinit` pragma, this refers to its implicit
 `result` variable:
@@ -6636,7 +6636,7 @@ but accessed at runtime:
   doAssert nameToProc[2][1]() == "baz"
 
 
-noReturn pragma
+noreturn pragma
 ---------------
 The `noreturn` pragma is used to mark a proc that never returns.