diff --git a/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-92655-MakeRequestTimeoutConfigurableForLinkvalidator.rst b/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-92655-MakeRequestTimeoutConfigurableForLinkvalidator.rst
index 09910f265c5bdc3537e3df2d3a956e9170adcca4..1149ab52a72ab653e934d2c25ed0161d4a50c0a2 100644
--- a/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-92655-MakeRequestTimeoutConfigurableForLinkvalidator.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.4.x/Important-92655-MakeRequestTimeoutConfigurableForLinkvalidator.rst
@@ -63,8 +63,8 @@ Depending on the library used and the tool, you can usually set:
* read timeout
* general timeout
-Libraries and utilities often have these options separately, including
-- for example - the curl command line tool or Guzzle.
+Libraries and utilities often have these options separately, including - for
+example - the curl command line tool or Guzzle.
TYPO3 uses Guzzle under the hood.
diff --git a/typo3/sysext/core/Documentation/Changelog/11.3/Deprecation-94377-ExtbaseObjectManager-getEmptyObject.rst b/typo3/sysext/core/Documentation/Changelog/11.3/Deprecation-94377-ExtbaseObjectManager-getEmptyObject.rst
index 23bc37f70bafb1df3cf41648003d14bce877c707..feffbf245600f36053b5f60ef3487d6787d05047 100644
--- a/typo3/sysext/core/Documentation/Changelog/11.3/Deprecation-94377-ExtbaseObjectManager-getEmptyObject.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.3/Deprecation-94377-ExtbaseObjectManager-getEmptyObject.rst
@@ -12,8 +12,8 @@ Description
===========
Extbase has the odd behavior that
-:php:`\TYPO3\CMS\Extbase\DomainObject\DomainObjectInterface` objects
-- typically classes in :file:`Classes/Domain/Model` of Extbase enabled
+:php:`\TYPO3\CMS\Extbase\DomainObject\DomainObjectInterface` objects -
+typically classes in :file:`Classes/Domain/Model` of Extbase enabled
extensions - don't call :php:`__construct` when the persistence layer
"thaws" a model from database - typically when a Extbase
:php:`Domain/Repository` uses a :php:`->findBy*` method.
diff --git a/typo3/sysext/core/Documentation/Changelog/11.4/Feature-94622-NewTCATypeCategory.rst b/typo3/sysext/core/Documentation/Changelog/11.4/Feature-94622-NewTCATypeCategory.rst
index 7c9d51766766cfdb4058cc257e0fc782387baf77..c53601390572494b3582927a4ecc3ed8cec63ff3 100644
--- a/typo3/sysext/core/Documentation/Changelog/11.4/Feature-94622-NewTCATypeCategory.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.4/Feature-94622-NewTCATypeCategory.rst
@@ -73,8 +73,8 @@ It's possible to use TSconfig options, such as
implemented for this type. For such special cases, please continue using TCA
type :php:`select`.
-The Override matrix - specifying the options which can be overridden in TSconfig
-- is extended for the new type. Following options can be overridden:
+The Override matrix - specifying the options which can be overridden in
+TSconfig - is extended for the new type. Following options can be overridden:
* :php:`size`
* :php:`maxitems`
diff --git a/typo3/sysext/core/Documentation/Changelog/11.5.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst b/typo3/sysext/core/Documentation/Changelog/11.5.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
index ff5f1217f763ffe1faefb716c00cf31b4ec5b9e4..aa47a3ccea4b70a6ea7672e8b3ed57c9083eb20c 100644
--- a/typo3/sysext/core/Documentation/Changelog/11.5.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
+++ b/typo3/sysext/core/Documentation/Changelog/11.5.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
@@ -20,9 +20,9 @@ default. However, it is still allowed to resolve a particular page by, for
example, "example.org" - as long as the page ID `123` is in the scope of the
site configured for the base URL "example.org".
-The new feature flag `security.frontend.allowInsecureSiteResolutionByQueryParameters`
-- which is disabled per default - can be used to reactivate the previous
-behavior:
+The new feature flag
+`security.frontend.allowInsecureSiteResolutionByQueryParameters` - which is
+disabled per default - can be used to reactivate the previous behavior:
.. code-block:: php
diff --git a/typo3/sysext/core/Documentation/Changelog/12.0/Breaking-98375-RemovedHooksInPageModule.rst b/typo3/sysext/core/Documentation/Changelog/12.0/Breaking-98375-RemovedHooksInPageModule.rst
index f7dd074e1fee4e5ef55eccb80f93ebf749a5e884..2c37baa68368a62c87118c43d05fd00b72736457 100644
--- a/typo3/sysext/core/Documentation/Changelog/12.0/Breaking-98375-RemovedHooksInPageModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/12.0/Breaking-98375-RemovedHooksInPageModule.rst
@@ -22,6 +22,7 @@ The following hooks are removed with a PSR-14 equivalent:
* :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/layout/class.tx_cms_layout.php']['tt_content_drawItem']`
The following hooks have been removed without substitution:
+
* :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/layout/class.tx_cms_layout.php']['list_type_Info']`
* :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/layout/class.tx_cms_layout.php']['tt_content_drawFooter']`
diff --git a/typo3/sysext/core/Documentation/Changelog/12.4.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst b/typo3/sysext/core/Documentation/Changelog/12.4.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
index 73731709c9d253b49e9943d11f5ef327cc72c06b..33c835393fcbde9354718ec517fb8983a5411a80 100644
--- a/typo3/sysext/core/Documentation/Changelog/12.4.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
+++ b/typo3/sysext/core/Documentation/Changelog/12.4.x/Important-100889-AllowInsecureSiteResolutionByQueryParameters.rst
@@ -20,9 +20,9 @@ default. However, it is still allowed to resolve a particular page by, for
example, "example.org" - as long as the page ID `123` is in the scope of the
site configured for the base URL "example.org".
-The new feature flag `security.frontend.allowInsecureSiteResolutionByQueryParameters`
-- which is disabled per default - can be used to reactivate the previous
-behavior:
+The new feature flag
+`security.frontend.allowInsecureSiteResolutionByQueryParameters` - which is
+disabled per default - can be used to reactivate the previous behavior:
.. code-block:: php
diff --git a/typo3/sysext/indexed_search/Documentation/AnalysingIndexedData/Index.rst b/typo3/sysext/indexed_search/Documentation/AnalysingIndexedData/Index.rst
index 94177c287d996a74bb96e649834ba4a533c7c2bf..074b079ae548ae662aa69d14c7810de5b262ef4a 100644
--- a/typo3/sysext/indexed_search/Documentation/AnalysingIndexedData/Index.rst
+++ b/typo3/sysext/indexed_search/Documentation/AnalysingIndexedData/Index.rst
@@ -184,8 +184,8 @@ As you see the main board page showing the list of messages/threads
("Sourcream and Oni...") is indexed without any values for the
parameter tt\_board\_uid (static_page_arguments). Then it has
also been indexed one time for each display of a message. In a search
-result any of these five rows may appear as an independent result row
-- after all they are to be regarded as a single page with unique
+result any of these five rows may appear as an independent result row - after
+all they are to be regarded as a single page with unique
content, despite sharing the same page-id!
Another interesting thing is that while the main page has inherited