Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Documentation/Advanced/CodingGuidelines.rst
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ However, adhering to the standard for TYPO3 documentation makes it easier for
other contributors to find their way around a file and pick the correct underlining
for the header level.

Use the :ref:`conventions for headlines <Headlines-and-sections>`.
Use the :ref:`conventions for headlines <headlines-and-sections>`.

This underlining is used **per (.rst) file**. It does not matter where in the toctree
the file is. You always start with underlining for level 1 (title) in each
Expand Down
2 changes: 1 addition & 1 deletion Documentation/Advanced/ContentStyleGuide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ Examples:
This applies to **all headers** on a page, not just the top level header (title).

In reST, headers are created by underlining / overlining with (`====`, `----`, etc.)
as described in :ref:`headlines and sections <Headlines-and-sections>`:
as described in :ref:`headlines and sections <headlines-and-sections>`:

.. code-block:: rst

Expand Down
2 changes: 1 addition & 1 deletion Documentation/Basics/RstCheatSheet.rst
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
:navigation-title: ReST Cheat Sheet
.. include:: /Includes.rst.txt
.. _writing-rest-introduction:
.. _Formatting-with-reST:
.. _formatting-with-rest:
.. _rest-quick-start:
.. _rest-cheat-sheet:

Expand Down
2 changes: 1 addition & 1 deletion Documentation/Howto/Contribute/HowYouCanHelp.rst
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ Here are some examples:

Example of a sequence diagram about request handling

* :ref:`Get started with PlantUML diagrams <PlantUML-diagrams>`
* :ref:`Get started with PlantUML diagrams <plantuml-diagrams>`


.. _docs-official-how-you-can-help-replace-outdated-images:
Expand Down
2 changes: 1 addition & 1 deletion Documentation/Howto/EditLocal.rst
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ More information

For more information in this guide:

* :ref:`reST cheat sheet <Formatting-with-reST>`
* :ref:`reST cheat sheet <formatting-with-rest>`
* `Rendering Documentation With Docker <https://github.com/t3docs/docker-render-documentation/blob/master/README.rst>`__
* :ref:`Review policy <review-policy>`

Expand Down
2 changes: 1 addition & 1 deletion Documentation/Howto/Migration/Index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ In the transition period the GitHub action of the official rendering process det
:file:`Documentation/guides.xml` is present and then automatically switches to the
PHP-based rendering.

.. _migrate_guides_xml:
.. _migrate-guides-xml:

Create the settings file :file:`Documentation/guides.xml`
=========================================================
Expand Down
2 changes: 1 addition & 1 deletion Documentation/Reference/FileStructure.rst
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ Read more about :ref:`configuring the rendering in guides.xml <guides-xml>`.
.. hint::
If you are migrating from the legacy Sphinx-based rendering and still have
a :file:`Documentation/Settings.cfg` you can use an automatic migration
tool to :ref:`migrate the settings.cfg into a guides.xml <migrate_guides_xml>`.
tool to :ref:`migrate the settings.cfg into a guides.xml <migrate-guides-xml>`.

Example:

Expand Down
4 changes: 2 additions & 2 deletions Documentation/Reference/GuidesXml.rst
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ And follow the interactive question.
.. hint::
If you are migrating from the legacy Sphinx-based rendering and still have
a :file:`Documentation/Settings.cfg` you can use an automatic migration
tool to :ref:`migrate the Settings.cfg into a guides.xml <migrate_guides_xml>`
tool to :ref:`migrate the Settings.cfg into a guides.xml <migrate-guides-xml>`

.. _guides-xml-api:

Expand Down Expand Up @@ -546,7 +546,7 @@ And follow the interactive question.
a private Gitlab or another issue tool, Make an internal page and
link it like `/SomePath/MyIssueReport`.

.. _settings-guides-preferred_typo3_version:
.. _settings-guides-preferred-typo3-version:

.. confval:: typo3-core-preferred
:name: guides-extension-typo3-core-preferred
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
.. index::
! Diagrams
Diagrams; PlantUML
.. _PlantUML-diagrams:
.. _plantuml-diagrams:

=================
PlantUML diagrams
Expand All @@ -28,7 +28,7 @@ This will be rendered as:

class -> otherClass : message

.. _PlantUML-diagrams-included:
.. _plantuml-diagrams-included:

Include a PlantUML file
=======================
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
.. include:: /Includes.rst.txt
.. index:: reST; Definition lists
.. _Styled-Definition-Lists:
.. _styled-definition-lists:

================
Definition lists
Expand Down Expand Up @@ -146,7 +146,7 @@ Source:

.. code-block:: rst

.. _label-parameterAbc:
.. _label-parameterabc:
.. rst-class:: dl-parameters

parameterAbc
Expand All @@ -157,7 +157,7 @@ Source:

Text describing parameterAbc ...

.. _label-parameterBcd:
.. _label-parameterbcd:
.. rst-class:: dl-parameters

parameterBcd
Expand All @@ -171,7 +171,7 @@ Source:

Rendering result:

.. _label-parameterAbc:
.. _label-parameterabc:
.. rst-class:: dl-parameters

parameterAbc
Expand All @@ -182,7 +182,7 @@ parameterAbc

Text describing parameterAbc ...

.. _label-parameterBcd:
.. _label-parameterbcd:
.. rst-class:: dl-parameters

parameterBcd
Expand All @@ -199,12 +199,12 @@ Source:

.. code-block:: rst

Here we link to :ref:`A link text for parameterAbc <label-parameterAbc>`.
Here we link to :ref:`A link text for parameterAbc <label-parameterabc>`.

Here we link to :ref:`A link text for parameterBcd <label-parameterAbc>`.
Here we link to :ref:`A link text for parameterBcd <label-parameterabc>`.

Result:

Here we link to :ref:`A link text for parameterAbc <label-parameterAbc>`.
Here we link to :ref:`A link text for parameterAbc <label-parameterabc>`.

Here we link to :ref:`A link text for parameterBcd <label-parameterAbc>`.
Here we link to :ref:`A link text for parameterBcd <label-parameterabc>`.
Loading