[DOCS] Fix typos and grammar in changelogs

Resolves: #104847
Releases: main
Change-Id: I018f359886bb98962646ab542da5cabb6851af43
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85915


Reviewed-by: Chris Müller <typo3@brotkrueml.dev>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Chris Müller <typo3@brotkrueml.dev>
Reviewed-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>
Tested-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102108-TCATypesbitmask_Settings.rst

@@ -2,9 +2,9 @@
 
 .. _breaking-102108-1696618684:
 
-===================================================
-Breaking: #102108 - TCA [types][bitmask_*] settings
-===================================================
+=====================================================
+Breaking: #102108 - TCA `[types][bitmask_*]` settings
+=====================================================
 
 See :issue:`102108`
 
@@ -14,8 +14,8 @@ Description
 Handling of two settings has been removed from the
 TYPO3 Core codebase:
 
-* `$GLOBALS['TCA']['someTable']['types']['bitmask_excludelist_bits']`
-* `$GLOBALS['TCA']['someTable']['types']['bitmask_value_field']`
+* :php:`$GLOBALS['TCA']['someTable']['types']['bitmask_excludelist_bits']`
+* :php:`$GLOBALS['TCA']['someTable']['types']['bitmask_value_field']`
 
 
 Impact

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102113-RemovedLegacySettingGFXgdlib.rst

@@ -32,7 +32,7 @@ Migration
 The configuration value has been removed without replacement.
 
 Custom code that relied on :php:`$GLOBALS['TYPO3_CONF_VARS']['GFX']['gdlib']`
-should instead also adopt to the simpler check
+should instead adopt the simpler check
 :php:`if (class_exists(\GdImage::class))`.
 
 .. index:: LocalConfiguration, FullyScanned, ext:core

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102146-RemovedLegacySettingBEflexformForceCDATA.rst

@@ -14,7 +14,7 @@ Description
 The TYPO3 configuration option :php:`$GLOBALS['TYPO3_CONF_VARS']['BE']['flexformForceCDATA']`
 has been removed without substitution.
 
-This setting was an ancient work around for an issue in libxml in old PHP versions that has
+This setting was an ancient workaround for an issue in libxml in old PHP versions that has
 been resolved long ago.
 
 This was the last usage of :php:`useCDATA` option in FlexForm-related XML methods in

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102229-RemovedFlexFormTools-traverseFlexFormXMLData.rst

@@ -41,7 +41,7 @@ Impact
 ======
 
 In general, these changes should have relatively low impact on extensions, if they
-don't built additional low level functionality on top of the general TYPO3 Core
+don't build additional low level functionality on top of the general TYPO3 Core
 FlexForm related features. Extensions like the TemplaVoila forks may need to have
 a look for required adaptions, though.
 

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102518-DatabaseEngineVersionRequirements.rst

@@ -21,7 +21,7 @@ TYPO3 v13 supports these database products and versions:
 Impact
 ======
 
-Environments with older MariaDB or MySQL database engines will reporting an unsupported
+Environments with older MariaDB or MySQL database engines will report an unsupported
 database version and stop working properly with the upcoming Doctrine DBAL v4 upgrade.
 
 Affected installations

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102900-MetaphoneSearchRemovedFromIndexed_search.rst

@@ -36,7 +36,7 @@ On a code level, the removal affects these areas:
 
 * Class :php:`\TYPO3\CMS\IndexedSearch\Utility\DoubleMetaPhoneUtility` has been
   removed.
-* The "hook" :php:`$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['indexed_search']['metaphone']
+* The "hook" :php:`$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['indexed_search']['metaphone']`
   to register an own "metaphone" solution has been removed.
 * The extension configuration option :php:`enableMetaphoneSearch` has been removed.
 * The database columns :sql:`index_fulltext.metaphonedata` and :sql:`index_words.metaphone`

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102902-SearchRulesRemovedFromIndexedSearch.rst

@@ -11,7 +11,7 @@ See :issue:`102902`
 Description
 ===========
 
-The "Rules" section in Indexed Search stems from a time where today's knowledge
+The "Rules" section in Indexed Search stems from a time when today's knowledge
 how a search works was considered "advanced". By today's standards, it can be
 considered common sense and therefore the rules and its related TypoScript
 configuration have been removed.

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102921-RemoveSeveralOutdatedIndexedSearchFeatures.rst

@@ -13,7 +13,7 @@ Description
 
 The internal search of TYPO3, Indexed Search exists since over 20 years. Some
 functionality that is shipped with the search form is not considered up-to-date
-anymore, in regards to templating, as Indexed Search has an Extbase and
+anymore, in regard to templating, as Indexed Search has an Extbase and
 Fluid-based plugin since TYPO3 v6.2 (10 years).
 
 Some functionality was never removed, which is now the case:

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-102924-SingleTableInheritanceFromFeGroupsRemoved.rst

@@ -18,8 +18,8 @@ specific value of a database field.
 TYPO3 has the functionality enabled for the database tables :sql:`fe_users` and
 :sql:`fe_groups`.
 
-The respective default models, which do not make a lot of sense, as models are
-depending on a specific domain, have been removed in previous TYPO3 versions.
+The respective default models, which do not make a lot of sense as models
+depend on a specific domain, have been removed in previous TYPO3 versions.
 
 For frontend user groups, the usage and the usefulness for TYPO3 to ship this out
 of the box, has shown little impact. For this reason, the functionality has been

typo3/sysext/core/Documentation/Changelog/13.0/Breaking-97664-FormPersistenceManagerInterfaceModifed.rst

@@ -2,9 +2,9 @@
 
 .. _breaking-97664-1688659987:
 
-==========================================================
-Breaking: #97664 - FormPersistenceManagerInterface modifed
-==========================================================
+===========================================================
+Breaking: #97664 - FormPersistenceManagerInterface modified
+===========================================================
 
 See :issue:`97664`
 

typo3/sysext/core/Documentation/Changelog/13.0/Deprecation-87889-TYPO3BackendEntrypointScriptDeprecated.rst

@@ -21,7 +21,7 @@ Note that the maintenance tool is still available via `/typo3/install.php`.
 Impact
 ======
 
-The TYPO3 backend route path is made configurable in order to protected against
+The TYPO3 backend route path is made configurable in order to protect against
 application admin interface infrastructure enumeration (`WSTG-CONF-05`_).
 Therefore, all requests are handled by the PHP script `/index.php` in order to
 allow for variable admin interface URLs.

typo3/sysext/core/Documentation/Changelog/13.0/Feature-102935-PSR-14EventForPackageInitializationFunctionality.rst

@@ -38,7 +38,7 @@ by the core listeners to store their result, which was previously passed
 to the :doc:`removed <../13.0/Breaking-102935-OverhauledExtensionInstallationInExtensionManager>`
 `EXT:extensionmanager` PSR-14 events.
 
-Listeners can access those information using corresponding :php:`getStorageEntry()`
+Listeners can access that information using corresponding :php:`getStorageEntry()`
 method. Those entries are a :php:`PackageInitializationResult` object, which
 features the following methods:
 

typo3/sysext/core/Documentation/Changelog/13.0/Feature-82855-UpdateMetadataOfOnlineMediaAssets.rst

@@ -17,7 +17,7 @@ in the :guilabel:`File > Filelist` module. Additionally, also the context menu o
 such files has been extended for the new action.
 
 The action allows to reload the corresponding information from the external
-service. Those information are, for example, the preview image, the author or the
+service. That information is, for example, the preview image, the author or the
 dimensions of the online media asset.
 
 Impact

typo3/sysext/core/Documentation/Changelog/13.0/Feature-99807-ImproveModifyUrlForCanonicalTagEvent.rst

@@ -13,7 +13,7 @@ Description
 
 The :php:`\TYPO3\CMS\Seo\Event\ModifyUrlForCanonicalTagEvent`, used by listeners
 to manipulate the URL of the `canonical` tag, has been improved. The event is
-is now being dispatched after the standard functionality, such as fetching the
+now being dispatched after the standard functionality, such as fetching the
 URL from the page properties, has been executed.
 
 Additionally, the event is now even dispatched, in case the canonical tag

typo3/sysext/core/Documentation/Changelog/13.1/Feature-103439-TypoScriptProviderForSitesAndSets.rst

@@ -69,7 +69,7 @@ Impact
 ======
 
 Sites and sets can ship TypoScript without the need for :sql:`sys_template`
-records in database, and dependencies can expressed via sets, allowing for
+records in database, and dependencies can be expressed via sets, allowing for
 automatic ordering and deduplication.
 
 .. index:: Backend, Frontend, PHP-API, TypoScript, YAML, ext:core

typo3/sysext/core/Documentation/Changelog/13.1/Feature-103578-AddDatabaseDefaultValueSupportForTEXTBLOBAndJSONFieldTypes.rst

@@ -52,7 +52,7 @@ Advanced example with value quoting
 
     CREATE TABLE a_textfield_test_table
     (
-        # JSON object default value containting single quote in json field
+        # JSON object default value containing single quote in json field
         field1 JSON NOT NULL DEFAULT '{"key1": "value1", "key2": 123, "key3": "value with a '' single quote"}',
 
         # JSON object default value containing double-quote in json field

typo3/sysext/core/Documentation/Changelog/13.2/Deprecation-103752-ObsoleteGLOBALSTYPO3_CONF_VARSFEaddRootLineFields.rst

@@ -2,9 +2,9 @@
 
 .. _deprecation-103752-1714304437:
 
-======================================================================================
-Deprecation: #103752 - Obsolete $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields']
-======================================================================================
+========================================================================================
+Deprecation: #103752 - Obsolete `$GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields']`
+========================================================================================
 
 See :issue:`103752`
 

typo3/sysext/core/Documentation/Changelog/13.2/Deprecation-104108-TableDependantDefinitionOfColumnsOnly.rst

@@ -45,7 +45,7 @@ Migration
 The field to be rendered have to be passed as :php:`array` under the
 corresponding table name.
 
-An example, buidling such link using the `UriBuilder`:
+An example, building such link using the `UriBuilder`:
 
 .. code-block:: php
 

typo3/sysext/core/Documentation/Changelog/13.2/Feature-102337-IntroducePSR14EventModifyRecordListDownloadData.rst

@@ -22,7 +22,7 @@ and
 hooks, which have been :ref:`deprecated <deprecation-102337-1715591179>`.
 
 The event allows to modify both body and header section of the data
-dump, so it can e.g. be use to redact sepcific data for GDPR compliance,
+dump, so it can e.g. be used to redact specific data for GDPR compliance,
 transform / translate specific data, trigger creation of archives or web hooks,
 log export access and more.
 
@@ -34,7 +34,7 @@ The event offers the following methods:
 - :php:`setRecords()`: Sets the modified body rows of the dataset.
 - :php:`getRequest()`: Returns the PSR request context.
 - :php:`getTable()`: Returns the name of the database table of the dataset.
-- :php:`getFormat()`: Returns the the format of the download action (CSV/JSON).
+- :php:`getFormat()`: Returns the format of the download action (CSV/JSON).
 - :php:`getFilename()`: Returns the name of the download filename (for browser output).
 - :php:`getId()`: Returns the page UID of the download origin.
 - :php:`getModTSconfig()`: Returns the active module TSconfig of the download origin.

typo3/sysext/core/Documentation/Changelog/13.2/Feature-103493-EditFullRecordInCheckLinksModule.rst

@@ -16,7 +16,7 @@ provided the possibility to edit the field of a record, a broken link has
 been identified for. However, in some cases relevant context might be missing,
 e.g. when editing redirect records.
 
-Therefore, a new button has been introdcued, which allows to edit the
+Therefore, a new button has been introduced, which allows to edit the
 full record of the broken link. The new button is placed next to the
 existing - single field - edit button.