summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
authorAndrey Makarov <ph.makarov@gmail.com>2021-02-20 20:01:45 +0300
committerGitHub <noreply@github.com>2021-02-20 18:01:45 +0100
commitd1fec552d04a000efd7504a3f3d621ea6f57b663 (patch)
treea4e3225b4aeda052b9d22bca1a0b88a6be8da10f /doc
parent0fcf1af7654aa4ac9934168ec84113a95c57a608 (diff)
downloadNim-d1fec552d04a000efd7504a3f3d621ea6f57b663.tar.gz
stricter checks for RST headlines (#17089)
Diffstat (limited to 'doc')
-rw-r--r--doc/gc.rst2
-rw-r--r--doc/manual_experimental_strictnotnil.rst2
-rw-r--r--doc/tut3.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/gc.rst b/doc/gc.rst
index a19ad0671..29b9a4131 100644
--- a/doc/gc.rst
+++ b/doc/gc.rst
@@ -77,7 +77,7 @@ the garbage collector with ``GC_enableMarkAndSweep`` and ``GC_disableMarkAndSwee
 
 
 Soft real-time support
----------------------
+----------------------
 
 To enable real-time support, the symbol `useRealtimeGC`:idx: needs to be
 defined via ``--define:useRealtimeGC`` (you can put this into your config
diff --git a/doc/manual_experimental_strictnotnil.rst b/doc/manual_experimental_strictnotnil.rst
index d779162f4..10b59a74e 100644
--- a/doc/manual_experimental_strictnotnil.rst
+++ b/doc/manual_experimental_strictnotnil.rst
@@ -183,7 +183,7 @@ Usually we just track the result of an expression: probably this should apply fo
 Also related to tracking initialization of expressions/fields.
 
 unstructured control flow rules
--------------------------
+-------------------------------
 
 Unstructured control flow keywords as ``return``, ``break``, ``continue``, ``raise`` mean that we jump from a branch out.
 This means that if there is code after the finishing of the branch, it would be ran if one hasn't hit the direct parent branch of those: so it is similar to an ``else``. In those cases we should use the reverse nilabilities for the local to the condition expressions. E.g.
diff --git a/doc/tut3.rst b/doc/tut3.rst
index a159f0d82..40ea2ae90 100644
--- a/doc/tut3.rst
+++ b/doc/tut3.rst
@@ -154,7 +154,7 @@ but does nothing else. Here is an example of such a tree representation:
 
 
 Custom Semantic Checking
------------------------
+------------------------
 
 The first thing that a macro should do with its arguments is to check
 if the argument is in the correct form. Not every type of wrong input