Skip to content

Commit 7e69b3b

Browse files
committed
docs: update the SDoc markup chapter: [[NODE]]-related updates
1 parent 61df6db commit 7e69b3b

File tree

2 files changed

+525
-530
lines changed

2 files changed

+525
-530
lines changed

docs/sphinx/source/strictdoc_01_user_guide.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -680,7 +680,7 @@ The available options are: ``On`` / ``Off``. Default is ``On``.
680680

681681
In case of ``On``, the ``[SECTION].LEVEL`` fields must be absent or may only
682682
contain ``None`` to exclude that section from StrictDoc's automatic section
683-
numbering. See also :ref:`Section without a level <SECTION_WITHOUT_A_LEVEL>`.
683+
numbering. See also :ref:`Section without a level <UG_NODE_WITHOUT_A_LEVEL>`.
684684

685685
In case of ``Off``, all ``[SECTION].LEVEL`` fields must be populated.
686686

@@ -1159,7 +1159,7 @@ StrictDoc creates section numbers automatically. In the example above, the
11591159
sections will have their titles numbered accordingly: ``1 Chapter`` and
11601160
``1.1 Subchapter``.
11611161

1162-
.. _SECTION_WITHOUT_A_LEVEL:
1162+
.. _UG_NODE_WITHOUT_A_LEVEL:
11631163

11641164
Section without a level
11651165
^^^^^^^^^^^^^^^^^^^^^^^
@@ -2972,7 +2972,7 @@ The following is a list of features that are considered less portable when it co
29722972

29732973
- :ref:`Composing documents from other documents <UG_COMPOSABLE_DOCUMENTS>`. Composing documents from other documents is a useful feature but it may not be directly supported by other tools. When exporting to JSON or ReqIF, StrictDoc by default does not export included documents but only the including documents.
29742974
- :ref:`Composite requirement <UG_COMPOSITE_NODE>`. A Composite Requirement is a useful concept which is partially supported by StrictDoc but it may be supported less by other tools.
2975-
- :ref:`Section without a level <SECTION_WITHOUT_A_LEVEL>`. Table of contents hierarchy where some nodes do not have TOC levels (or have custom TOC levels) can cause problems when exporting/importing documentation content if an interfacing tool does not support custom TOC nodes.
2975+
- :ref:`Section without a level <UG_NODE_WITHOUT_A_LEVEL>`. Table of contents hierarchy where some nodes do not have TOC levels (or have custom TOC levels) can cause problems when exporting/importing documentation content if an interfacing tool does not support custom TOC nodes.
29762976

29772977
.. note::
29782978

0 commit comments

Comments
 (0)