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 67a8cebf8eb95f0ae6e6a1e19b0cbd88e54dcd37..1453ce6676c8e0f3ada6e90e4fbc48b6f01b004a 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 @@ -61,8 +61,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 567aa43b3b8202546a32f4aec77e4d6a9883c1ee..faf1adac4c3a7477bd182d485e4038b1e48e8566 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 @@ -10,8 +10,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 d482b4616845b8edacbbeff1d2666d5d8d2e8871..3624417855a9d1fda03da62a3ac3bb88fbedfa4f 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 @@ -71,8 +71,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/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