[DOCS] Fix typos in changelogs

Resolves: #104843
Releases: main
Change-Id: I38d9dd2bb2562af43866c57f10b245960a6670d0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85911


Tested-by: core-ci <typo3@b13.com>
Tested-by: Simon Praetorius <simon@praetorius.me>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Simon Praetorius <simon@praetorius.me>

typo3/sysext/core/Documentation/Changelog/13.1/Feature-103441-RequestIdAsPublicVisibleErrorReferenceInErrorHandlersOutput.rst

@@ -20,7 +20,7 @@ occurred!" followed by a timestamp and a hash. This is part of log messages.
 Whenever an error/exception is logged, the log message contains the request ID.
 
 With this the request ID is also shown in web output of error/exception handlers
- as public visible error reference.
+as public visible error reference.
 
 
 Impact

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

@@ -19,7 +19,7 @@ by adding the fields to be rendered as a comma-separated list.
 However, besides rendering only records form a single table, the edit form
 is also capable of rendering records of different tables in the same request.
 
-Therefore, the limit fields funcionality has been extended to allow
+Therefore, the limit fields functionality has been extended to allow
 set the fields to be rendered on a per-table basis. This means that
 passing just a comma-separated list of fields as value for `columnsOnly`
 has been deprecated.

typo3/sysext/core/Documentation/Changelog/13.2/Feature-104220-MakeParseFuncAllowTagsAndDenyTagsOptional.rst

@@ -63,7 +63,6 @@ The example above only allows :html:`<u>` and encodes any other tag.
     }
 
 The example above allows all tags, the new :typoscript:`allowTags = *`
-takes precendence over :typoscript:`denyTags = *`.
-
+takes precedence over :typoscript:`denyTags = *`.
 
 .. index:: Frontend, TypoScript, ext:core

typo3/sysext/core/Documentation/Changelog/13.3/Deprecation-104789-FluidVariablesTrueFalseNull.rst

@@ -34,7 +34,7 @@ This should rarely happen, as it would involve using :php:`$view->assign('true',
 Migration
 =========
 
-Template code using these variables should be adjusted to use diffferent variable names.
+Template code using these variables should be adjusted to use different variable names.
 In Fluid v4, the variables will contain their matching PHP counterparts.
 
 .. index:: Fluid, NotScanned, ext:fluid

typo3/sysext/core/Documentation/Changelog/13.3/Feature-104631-AddUNIONClauseSupportToTheQueryBuilder.rst

@@ -42,11 +42,11 @@ which introduces two new API method on the QueryBuilder:
 
 * :php:`union(string|QueryBuilder $part)` to create first UNION query part
 * :php:`addUnion(string|QueryBuilder $part, UnionType $type = UnionType::DISTINCT)`
-  to add addtional :sql:`UNION (ALL|DISTINCT)` query parts with the selected union
+  to add additional :sql:`UNION (ALL|DISTINCT)` query parts with the selected union
   query type.
 
 TYPO3 decorates the Doctrine DBAL QueryBuilder to provide for most API methods automatic
-quoting of identifiers and values **and**  to appliy database restrictions automatically
+quoting of identifiers and values **and**  to apply database restrictions automatically
 for :sql:`SELECT` queries.
 
 The Doctrine DBAL API has been adopted now to provide the same surface for the

typo3/sysext/core/Documentation/Changelog/13.3/Feature-104832-PSR-14EventToAlterTheResultsOfPageTreeRepository.rst

@@ -26,7 +26,7 @@ Example
 =======
 
 The event listener class, using the PHP attribute :php:`#[AsEventListener]` for
-registration, will rmoeve any children for displaying for the page with the
+registration, will remove any children for displaying for the page with the
 UID 123:
 
 ..  code-block:: php