From 33464004c9e5785fa2db4ff941e57d89b4ffdd4a Mon Sep 17 00:00:00 2001
From: Anja Leichsenring <aleichsenring@ab-softlab.de>
Date: Fri, 19 Jul 2019 16:22:45 +0200
Subject: [PATCH] [TASK] Review v10.0 Changelog

Change-Id: Id4f981b3d6b62601ae4f3c7a56b3153d1884f669
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61328
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Susanne Moog <look@susi.dev>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Susanne Moog <look@susi.dev>
Reviewed-by: Benni Mack <benni@typo3.org>
---
 .../core/Documentation/Changelog-10.rst       |  14 +++
 .../Breaking-21638-LockIPPropertyRemoved.rst  |   7 +-
 ...verWorkspacesUnpublishingFunctionality.rst |   4 +-
 ...ntDoesNotUseSpacelessViewHelperAnymore.rst |   0
 ...ipleTranslationFilesByDefaultInEXTform.rst |   0
 ...g-87193-DeprecatedFunctionalityRemoved.rst |  12 +-
 ...05-UseConstructorInjectionInDataMapper.rst |  18 +--
 ...amespacesViewObjectNamePatternProperty.rst |   6 +-
 ...emoveViewFormatToObjectNameMapProperty.rst |   6 +-
 ...reaking-87558-ConsolidateExtbaseCaches.rst |   8 +-
 ...7567-GlobalVariableTBE_TEMPLATERemoved.rst |   6 +-
 ...eObsoleteAPCCacheBackendImplementation.rst |   9 +-
 .../Breaking-87594-HardenExtbase.rst          |   7 +-
 ...sistenceclassesTyposcriptConfiguration.rst |   8 +-
 ...pertyExtensionNameOfAbstractController.rst |   4 +-
 ...Breaking-87936-TCAForSysHistoryRemoved.rst |  10 +-
 ...7-TCAOption_selicon_field_path_removed.rst |  10 +-
 ...87957-DoNotMagicallyRegisterValidators.rst |   6 +-
 ...989-TCAOptionSetToDefaultOnCopyRemoved.rst |   2 +-
 ...king-88129-RenameFeloginFlexformFields.rst |   5 +-
 ...on-relatedDatabaseFieldT3ver_idRemoved.rst |   8 +-
 ...ing-88182-JsfuncInlineJsHasBeenDropped.rst |   6 +-
 ...ng-88366-RemovedCf_PrefixOfCacheTables.rst |  12 +-
 ...dObsoletePageNotFound_handlingSettings.rst |   8 +-
 ...aking-88411-TBE_EDITORtypo3formRemoved.rst |   2 +-
 ...-88427-JsfuncevalfieldjsHasBeenRemoved.rst |   4 +-
 ...movedFrontendTrackUserFtuFunctionality.rst |   7 +-
 ...tchableControllerActionsHasBeenRemoved.rst |   7 +-
 ...balDataForTimeTrackerStatisticsRemoved.rst |   4 +-
 ...0-RTEImageHandlingFunctionalityDropped.rst |  19 +--
 ...ctiveOfExtensionInstallationEm_confphp.rst |  14 +--
 ...mValuesInUserAuthenticationDerivatives.rst |  16 +--
 ...ngedRequestWorkflowForFrontendRequests.rst | 104 +++++++++++++++++
 ...ageTSconfigSettingTSFEconstantsRemoved.rst |  10 +-
 ...erOfPageRepository-enableFieldsRemoved.rst |   6 +-
 ...Sys_languagestatic_lang_isocodeRemoved.rst |   6 +-
 ...treamlinedSoftRefParserReferenceLookup.rst |  14 +--
 ...dTypoScriptSublevel-InheritanceRemoved.rst |  10 +-
 ...emovedSwiftmailerswiftmailerDependency.rst |   6 +-
 ...rviceFromAbstractAuthenticationService.rst |  17 +--
 ...-PopupConfigurationInFormEngineDropped.rst |   0
 .../Breaking-88660-GLOBALST3_VARRemoved.rst   |   6 +-
 ...ditionalJavaScriptSubmitFromFormEngine.rst |   2 +-
 ...neFormDataProviderParentPageTcaRemoved.rst |   6 +-
 ...rtOfPHPFilesInImportExportFilesRemoved.rst |   2 +-
 ...-ConfigureExtbaseRequestHandlersViaPHP.rst |   4 +-
 ...g-88706-StreamlineFeloginLocallangKeys.rst |   2 +-
 ...perfluousMethodsOfLocalizationRedirect.rst |   5 +-
 ...CHashCalculationInIndexedSearchRemoved.rst |   8 +-
 ...FieldsRelatedToCSSStyledContentRemoved.rst |  10 +-
 ...OptionFromTypolinkaddQueryStringmethod.rst |   0
 ...nOfCSSFilesInResourceCompressorRemoved.rst |   6 +-
 ...criptTagsOmitTypetextjavascriptInHTML5.rst |   6 +-
 ...aking-88779-RecordListRemoveUnusedCode.rst |   2 +-
 ...99-IntroducedPSR-3CompatibleLoggingAPI.rst |  27 +++--
 ...0420-EmailFinisherSingleAddressOptions.rst |   6 +-
 ...eamlineBackendRoutePathInconsistencies.rst |  12 +-
 ...cation-85895-DeprecateFile_getMetaData.rst |   7 +-
 ...tion-87200-EmailFinisherFormatContants.rst |  37 ++++++
 ...cation-87200-EmailFinisherFormatOption.rst |   6 +-
 ...05-UseConstructorInjectionInDataMapper.rst |   5 +-
 ...idRuntimeReflectionCallsInObjectAccess.rst |  14 ++-
 ...erClassesWhenRegisteringPluginsmodules.rst |  34 +++---
 ...tbaseUtilityTypeHandlingUtilityhex2bin.rst |   6 +-
 ...leRelatedControllersMovedToEXTfilelist.rst |   0
 ...ecation-87894-GeneralUtilityidnaEncode.rst |   4 +-
 ...faultCachingFrameworkCacheNamesChanged.rst |  24 ++--
 ...eHashOptionsInViewHelpersAndUriBuilder.rst |  48 ++++----
 ...88428-ToprawurlencodeAndTopstr_replace.rst |   0
 ...ion-88432-ReplacedMd5jsWithAnAMDModule.rst |   2 +-
 ...tion-88433-DeprecateTopopenUrlInWindow.rst |   0
 ...ScriptFrontendController-settingLocale.rst |   4 +-
 ...tion-88499-BackendUtilitygetViewDomain.rst |   8 +-
 ...eprecatedMethodsInVersionNumberUtility.rst |  10 +-
 ...cation-88559-TSFE-sys_language_isocode.rst |   8 +-
 .../Deprecation-88567-GLOBALS_LOCAL_LANG.rst  |   9 +-
 ...alizeInFavorOfRegularSingletonInstance.rst |  39 +++++++
 ...WithTYPO3CMSBackendDocumentSaveActions.rst |   0
 ...62-DeprecatedBackendRouteXMOD_tximpexp.rst |   2 +-
 ...PClassMovedFromFrontendToCoreExtension.rst |   6 +-
 ...mplateParsingInTSFEAndTemplateService.rst} |  16 ++-
 ...nitializableInterfaceHasBeenDeprecated.rst |   0
 ...ature-21638-IntroducedIpLockingForIpv6.rst |   2 +-
 ...llowSortingFilelistByFileMetadataTitle.rst |   6 +-
 ...78432-AddLogMessageForSwitchUserAction.rst |   0
 ...AllowMultipleRecipientsInEmailFinisher.rst |   0
 ...-AddSupportForCurrentPageInConfigcache.rst |   6 +-
 ...nyDependencyInjectionForCoreAndExtbase.rst |  18 +--
 ...DoubleClickInStructureTreeChangesLabel.rst |   0
 ...ormationsInTheSystemInformationToolbar.rst |  16 +--
 ...ilViewHelperToRenderThumbnailsDeferred.rst |   6 +-
 ...mplementLinkHandlerForTelephoneNumbers.rst |   0
 ...-AllowGettingClassPropertyDefaultValue.rst |  27 +++++
 ...ndPlaintextAndHTMLMailsInEmailFinisher.rst |   3 +-
 ...Feature-87433-AddChangefreqAndPriority.rst |  25 ++--
 ...operty-infoToGatherDocBlockInformation.rst |   0
 .../Feature-87665-IntroduceBitSetClass.rst    |   0
 ...dLoginControllerHookToValidatePassword.rst |  38 ++++++
 ...lAPIBasedOnSymfonymailerAndSymfonymime.rst |   8 +-
 ...-DefineTwitterCardTypeInPageProperties.rst |   6 +-
 ...ature-88770-PSR-14BasedEventDispatcher.rst |   6 +-
 ...-88791-IntroducePreviewAspectInContext.rst |   2 +-
 ...ndleTypoScriptRenderingContextSettings.rst |   0
 ...99-IntroducedPSR-3CompatibleLoggingAPI.rst |   2 +-
 ...uestEnricherInterfaceHasBeenIntroduced.rst |   0
 ...etersAreNowIncludedInCanonicalizedUrls.rst |   2 +-
 ...27-ClassSchemaConstantsMarkedAsPrivate.rst |   8 +-
 ...-RemoveCoreHTTPRequestHandlerInterface.rst |   0
 ...lassesUseStrictModeAndScarlarTypeHints.rst |   0
 ...PDependencyAlgo26-matthiasidna-convert.rst |   0
 ...eIsBeingGeneratedMessageHasBeenRemoved.rst |   2 +-
 ...peScriptSourcesMovedIntoBuildDirectory.rst |   3 +-
 .../Documentation/Changelog/10.0/Index.rst    |  51 +++++++++
 ...RemovedUnusedLocallangFilesFromEXTlang.rst |  31 +++--
 ...ngedRequestWorkflowForFrontendRequests.rst | 108 ------------------
 ...tion-87200-EmailFinisherFormatContants.rst |  32 ------
 ...alizeInFavorOfRegularSingletonInstance.rst |  39 -------
 ...-AllowGettingClassPropertyDefaultValue.rst |  27 -----
 ...dLoginControllerHookToValidatePassword.rst |  36 ------
 typo3/sysext/core/Documentation/Index.rst     |   1 +
 typo3/sysext/core/Documentation/Settings.cfg  |   4 +-
 .../Php/PropertyPublicMatcher.php             |   4 +-
 122 files changed, 726 insertions(+), 608 deletions(-)
 create mode 100644 typo3/sysext/core/Documentation/Changelog-10.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-21638-LockIPPropertyRemoved.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst (91%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-86862-DefaultLayoutOfExtfluid_styled_contentDoesNotUseSpacelessViewHelperAnymore.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87009-UseMultipleTranslationFilesByDefaultInEXTform.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87193-DeprecatedFunctionalityRemoved.rst (99%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87305-UseConstructorInjectionInDataMapper.rst (77%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87558-ConsolidateExtbaseCaches.rst (78%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst (82%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst (76%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87594-HardenExtbase.rst (93%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst (87%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst (92%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87936-TCAForSysHistoryRemoved.rst (61%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87937-TCAOption_selicon_field_path_removed.rst (51%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87957-DoNotMagicallyRegisterValidators.rst (93%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst (86%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88129-RenameFeloginFlexformFields.rst (90%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst (70%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst (85%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst (61%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst (77%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88411-TBE_EDITORtypo3formRemoved.rst (91%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst (78%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst (86%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst (84%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst (74%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst (69%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst (62%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst (64%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst (78%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst (80%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst (66%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst (50%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88657-PopupConfigurationInFormEngineDropped.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88660-GLOBALST3_VARRemoved.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst (96%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst (87%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst (94%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88706-StreamlineFeloginLocallangKeys.rst (97%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst (88%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst (75%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88755-RemovePOSTOptionFromTypolinkaddQueryStringmethod.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst (77%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst (82%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88779-RecordListRemoveUnusedCode.rst (87%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst (61%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-80420-EmailFinisherSingleAddressOptions.rst (89%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst (59%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-85895-DeprecateFile_getMetaData.rst (52%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatContants.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87200-EmailFinisherFormatOption.rst (67%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87305-UseConstructorInjectionInDataMapper.rst (77%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst (63%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst (70%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst (83%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87882-FileRelatedControllersMovedToEXTfilelist.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-87894-GeneralUtilityidnaEncode.rst (82%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst (63%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst (55%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88428-ToprawurlencodeAndTopstr_replace.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst (92%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88433-DeprecateTopopenUrlInWindow.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst (88%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88499-BackendUtilitygetViewDomain.rst (76%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88559-TSFE-sys_language_isocode.rst (73%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88567-GLOBALS_LOCAL_LANG.rst (75%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88651-ReplaceTYPO3CMSBackendSplitButtonsWithTYPO3CMSBackendDocumentSaveActions.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst (92%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst (86%)
 rename typo3/sysext/core/Documentation/Changelog/{master/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst => 10.0/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst} (50%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Deprecation-88807-AdminPanelInitializableInterfaceHasBeenDeprecated.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-21638-IntroducedIpLockingForIpv6.rst (97%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst (81%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-78432-AddLogMessageForSwitchUserAction.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-80420-AllowMultipleRecipientsInEmailFinisher.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-83734-AddSupportForCurrentPageInConfigcache.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst (92%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-84757-DoubleClickInStructureTreeChangesLabel.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst (68%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst (72%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-86629-ImplementLinkHandlerForTelephoneNumbers.rst (100%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst (80%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-87433-AddChangefreqAndPriority.rst (69%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-87457-UseSymfonyproperty-infoToGatherDocBlockInformation.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-87665-IntroduceBitSetClass.rst (100%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst (94%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88648-DefineTwitterCardTypeInPageProperties.rst (74%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88770-PSR-14BasedEventDispatcher.rst (95%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88791-IntroducePreviewAspectInContext.rst (89%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst (91%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Feature-88807-AdminPanelRequestEnricherInterfaceHasBeenIntroduced.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst (93%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst (65%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-87516-RemoveCoreHTTPRequestHandlerInterface.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-87603-ClassesUseStrictModeAndScarlarTypeHints.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-87894-RemovedPHPDependencyAlgo26-matthiasidna-convert.rst (100%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst (94%)
 rename typo3/sysext/core/Documentation/Changelog/{master => 10.0}/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst (89%)
 create mode 100644 typo3/sysext/core/Documentation/Changelog/10.0/Index.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatContants.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
 delete mode 100644 typo3/sysext/core/Documentation/Changelog/master/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst

diff --git a/typo3/sysext/core/Documentation/Changelog-10.rst b/typo3/sysext/core/Documentation/Changelog-10.rst
new file mode 100644
index 000000000000..3237314dc3ce
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog-10.rst
@@ -0,0 +1,14 @@
+:orphan:
+
+.. include:: Includes.txt
+
+=============
+ChangeLog v10
+=============
+
+Every change to the TYPO3 Core which might affect your site is documented here.
+
+.. toctree::
+   :titlesonly:
+
+   Changelog/10.0/Index
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-21638-LockIPPropertyRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-21638-LockIPPropertyRemoved.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-21638-LockIPPropertyRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-21638-LockIPPropertyRemoved.rst
index 50563c14d60b..967fe2f59afb 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-21638-LockIPPropertyRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-21638-LockIPPropertyRemoved.rst
@@ -11,14 +11,15 @@ Description
 
 The IP-locking-functionality is extended from IPv4 only to now also support IPv6. A separate IpLocker-functionality was added.
 
-The public property :php:`lockIP` in :php:`AbstractUserAuthentication` is now removed. It usually shouldn't have been accessed directly and supported IPv4 only.
+The public property :php:`lockIP` in :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication` is now removed.
+It usually shouldn't have been accessed directly and supported IPv4 only.
 
 
 Impact
 ======
 
 Extensions relying on :php:`lockIP` won't be able to perform their task anymore.
-This might for example be the case when "lockIP" was set dynamically, depending on the REMOTE_ADDR.
+This might for example be the case when :php:`lockIP` was set dynamically, depending on the REMOTE_ADDR.
 
 
 Affected Installations
@@ -30,7 +31,7 @@ Every 3rd party extension depending on the formerly public :php:`lockIP` propert
 Migration
 =========
 
-Set :php:`lockIP` and :php:`lockIPv6` in :php:`TYPO3_CONF_VARS` - for FE or BE depending on the usecase.
+Set :php:`lockIP` and :php:`lockIPv6` in :php:`TYPO3_CONF_VARS` - for FE or BE depending on the use case.
 Use the new :php:`\TYPO3\CMS\Core\Authentication\IpLocker` API.
 
 .. index:: Backend, Frontend, LocalConfiguration, NotScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst
index e785ca970214..3f4f7cbf5847 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-81950-RemoveLeftoverWorkspacesUnpublishingFunctionality.rst
@@ -17,7 +17,7 @@ time, but had side-effects if changes were made between publishing and unpublish
 However, this functionality was not visible to TYPO3 out of the box, but only available with a possible third-party integration
 since TYPO3 4.5. The feature was therefore removed from TYPO3 Core.
 
-The (hidden) database field `sys_workspace.unpublish_time` was removed.
+The (hidden) database field :sql:`sys_workspace.unpublish_time` was removed.
 
 
 Impact
@@ -38,4 +38,4 @@ Migration
 If this feature is required for an installation, the field should be re-added by the third-party extension in TCA (which was missing)
 and the database which was using the functionality. On top, a custom auto-unpublishing CLI command should be created.
 
-.. index:: Database, NotScanned, ext:workspaces
\ No newline at end of file
+.. index:: Database, NotScanned, ext:workspaces
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-86862-DefaultLayoutOfExtfluid_styled_contentDoesNotUseSpacelessViewHelperAnymore.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-86862-DefaultLayoutOfExtfluid_styled_contentDoesNotUseSpacelessViewHelperAnymore.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-86862-DefaultLayoutOfExtfluid_styled_contentDoesNotUseSpacelessViewHelperAnymore.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-86862-DefaultLayoutOfExtfluid_styled_contentDoesNotUseSpacelessViewHelperAnymore.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87009-UseMultipleTranslationFilesByDefaultInEXTform.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87009-UseMultipleTranslationFilesByDefaultInEXTform.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87009-UseMultipleTranslationFilesByDefaultInEXTform.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87009-UseMultipleTranslationFilesByDefaultInEXTform.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87193-DeprecatedFunctionalityRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
similarity index 99%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87193-DeprecatedFunctionalityRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
index 81ba8598e3d0..dd4fc418f40a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87193-DeprecatedFunctionalityRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87193-DeprecatedFunctionalityRemoved.rst
@@ -1438,9 +1438,9 @@ The following features have been removed:
 * TCA auto migration from core v6 to core v7 compatible TCA
 * TCA auto migration from core v7 to core v8 compatible TCA
 * TCA :php:`type='group'` with :php:`internal_type='file'` and :php:`internal_type='file_reference`
-* Cache creation using :php:`\TYPO3\CMS\Cache\CacheManger` during :php:`ext_localconf.php` loading
-* All install tool upgrade wizards upgrading from v7 to v8 have been removed
-* The array key :php:`uploadfolder` in extensions :php:`ext_emconf.php` files is obsolete and ignored.
+* Cache creation using :php:`\TYPO3\CMS\Cache\CacheManger` during :file:`ext_localconf.php` loading
+* All install tool upgrade wizards upgrading from v7 to v8
+* The array key :php:`uploadfolder` in extensions :file:`ext_emconf.php` files is obsolete and ignored.
 * Standalone install tool entry point :file:`typo3/install/index.php` has been dropped, use :file:`typo3/install.php` instead
 * INCLUDE_TYPOSCRIPT statements in typoscript using a `.txt` ending for a file that ends with `.typoscript` does not work any longer
 * These variables are no longer declared in :file:`ext_tables.php` and :file:`ext_localconf.php` files: :php:`$_EXTKEY`, :php:`$_EXTCONF`,
@@ -1454,10 +1454,10 @@ The following features have been removed:
 * The extension :php:`taskcenter` and its add-on extension :php:`sys_action` have been dropped from core
 * Translation :php:`locallang` references :php:`EXT:lang` to removed extension "lang" do not work any longer
 * EXT:form: type GridContainer
-* EXT:form: renderingOptions._isHiddenFormElement and renderingOptions._isReadOnlyFormElement are dropped
+* EXT:form: :yaml:`renderingOptions._isHiddenFormElement` and :yaml:`renderingOptions._isReadOnlyFormElement` are dropped
 * :php:`$TBE_MODULES`: configuring a module via a custom "configureModuleFunction" is dropped
 * CLI Command alias "lang:language:update" is dropped in favor of "language:update"
-* Accessing or modifying $_GET/$_POST parameters during any PSR-15 middleware will not reflect any change during the actual Request processing anymore as it is overridden by the incoming PSR-7 request object, but overriden again when the RequestHandler is accessed
+* Accessing or modifying :php:`$_GET`/:php:`$_POST` parameters during any PSR-15 middleware will not reflect any change during the actual Request processing anymore as it is overridden by the incoming PSR-7 request object, but overriden again when the RequestHandler is accessed
 * Parsing of the legacy `<link>` tags which were migrated to `<a>` tags in Frontend is dropped
 
 The following database tables have been removed:
@@ -1513,6 +1513,6 @@ The following global instances have been removed:
 Impact
 ======
 
-Instantiating or requiring the PHP classes, calling the PHP methods directly, will result in PHP fatal errors.
+Instantiating or requiring the PHP classes or calling the PHP methods directly will trigger PHP :php:`E_ERRER` errors.
 
 .. index:: Backend, CLI, FlexForm, Fluid, Frontend, JavaScript, LocalConfiguration, PHP-API, TCA, TSConfig, TypoScript, PartiallyScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87305-UseConstructorInjectionInDataMapper.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87305-UseConstructorInjectionInDataMapper.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
index 57f3cef29f53..de5bb71222cd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87305-UseConstructorInjectionInDataMapper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87305-UseConstructorInjectionInDataMapper.rst
@@ -33,19 +33,19 @@ If possible, do not create instances yourself. Avoid :php:`GeneralUtility::makeI
 
 .. code-block:: php
 
-	public function __constructor(\TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper $object)
-	{
-	    $this->property = $object;
-	}
+   public function __constructor(\TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper $object)
+   {
+       $this->property = $object;
+   }
 
 If dependency injection is not possible, check the dependencies and instantiate objects via the object manager:
 
 .. code-block:: php
 
-	$object = $objectManager->get(
-	    \TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::class,
-	    $objectManager->get(\TYPO3\CMS\Extbase\Reflection\ReflectionService::class),
-	    // ...
-	);
+   $object = $objectManager->get(
+       \TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::class,
+       $objectManager->get(\TYPO3\CMS\Extbase\Reflection\ReflectionService::class),
+       // ...
+   );
 
 .. index:: PHP-API, FullyScanned, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst
index bc8338e27fdc..e58647cc5edc 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveNamespacesViewObjectNamePatternProperty.rst
@@ -17,7 +17,7 @@ Impact
 ======
 
 Overriding the property :php:`$namespacesViewObjectNamePattern` in
-controllers that extend :php`ActionController` will no longer trigger
+controllers that extend :php:`ActionController` will no longer trigger
 the instantiation of another view object, derived from the pattern.
 
 Affected Installations
@@ -28,8 +28,8 @@ All extensions that override the property :php:`$namespacesViewObjectNamePattern
 Migration
 =========
 
-If an action needs another template object other than the default
+If an action needs a template object other than the default
 :php:`\TYPO3\CMS\Fluid\View\TemplateView`, the property :php:`$defaultViewObjectName`
-needs to be overridden instead.
+needs to be overridden.
 
 .. index:: PHP-API, FullyScanned, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst
index 7a06d886fa43..b747a123d6c3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87511-RemoveViewFormatToObjectNameMapProperty.rst
@@ -17,7 +17,7 @@ Impact
 ======
 
 Overriding the property :php:`$viewFormatToObjectNameMap` in
-controllers that extend :php`ActionController` will no longer trigger
+controllers that extend :php:`ActionController` will no longer trigger
 the instantiation of another view object, derived from the mapping.
 
 Affected Installations
@@ -28,8 +28,8 @@ All extensions that override the property :php:`$viewFormatToObjectNameMap`.
 Migration
 =========
 
-If an action needs another template object other than the default
+If an action needs a template object other than the default
 :php:`\TYPO3\CMS\Fluid\View\TemplateView`, the property :php:`$defaultViewObjectName`
-needs to be overridden instead.
+needs to be overridden.
 
 .. index:: PHP-API, FullyScanned, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87558-ConsolidateExtbaseCaches.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87558-ConsolidateExtbaseCaches.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87558-ConsolidateExtbaseCaches.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87558-ConsolidateExtbaseCaches.rst
index c29de331f979..3af1c09df055 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87558-ConsolidateExtbaseCaches.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87558-ConsolidateExtbaseCaches.rst
@@ -21,13 +21,13 @@ Impact
 Adjusting the cache configuration of either `extbase_reflection`
 or `extbase_datamapfactory_datamap` will no longer have any effect.
 
-The installation may throw an error as well depending on the php error level configuration , if the no longer existing
+The installation may throw an error depending on the php error level configuration, if the no longer existing
 cache keys are written to without initializing them first.
 
-The following entries do no longer exist:
+The following global settings do no longer exist:
 
-* `$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_reflection']`
-* `$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_datamapfactory_datamap']`
+* :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_reflection']`
+* :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_datamapfactory_datamap']`
 
 The following code code might throw an error depending on the php error level configuration:
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst
similarity index 82%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst
index b4907e9a607c..1c56ef622af5 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87567-GlobalVariableTBE_TEMPLATERemoved.rst
@@ -9,7 +9,7 @@ See :issue:`87567`
 Description
 ===========
 
-The global variable used in TYPO3 Backend :php:`$GLOBALS[TBE_TEMPLATE]` which was available
+The global variable :php:`$GLOBALS[TBE_TEMPLATE]` used in TYPO3 Backend which was available
 for legacy reasons for old backend modules as an instance of :php:`DocumentTemplate` a.k.a. `alt_doc`
 has been removed.
 
@@ -19,7 +19,7 @@ The according PSR-15 middleware, which was marked as internal, is also removed.
 Impact
 ======
 
-Calling any method or property on :php:`$GLOBALS[TBE_TEMPLATE]` will result in a fatal error.
+Calling any method or property on :php:`$GLOBALS[TBE_TEMPLATE]` will trigger a PHP :php:`E_ERROR` error.
 
 
 Affected Installations
@@ -34,4 +34,4 @@ Migration
 Instantiate the :php:`DocumentTemplate` class directly in the controller of the module, or migrate
 to :php:`ModuleTemplate` which is available since TYPO3 v7.
 
-.. index:: PHP-API, FullyScanned, ext:backend
\ No newline at end of file
+.. index:: PHP-API, FullyScanned, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst
index 9fccd25cf9b5..29e7cfe327f0 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87583-RemoveObsoleteAPCCacheBackendImplementation.rst
@@ -9,7 +9,7 @@ See :issue:`87583`
 Description
 ===========
 
-The Caching framework backend implementation :php:`\TYPO3\CMS\Core\Cache\Backend\ApcBackend` has
+The Caching framework backend implementation :php:`TYPO3\CMS\Core\Cache\Backend\ApcBackend` has
 been removed. The APCu PHP extension has superseded in PHP 7.x.
 
 Impact
@@ -22,14 +22,13 @@ Affected Installations
 ======================
 
 Any installation which has been updated, and any legacy APC cache backend is configured (see
-LocalConfiguration).
+:file:`LocalConfiguration.php`).
 
 Migration
 =========
 
-Use APCu implementation, which is implented via :php:`\TYPO3\CMS\Core\Cache\Backend\ApcuBackend`
-instead of :php:`\TYPO3\CMS\Core\Cache\Backend\ApcBackend` in your caching framework
-configuration.
+Use APCu implementation, which is implemented via :php:`TYPO3\CMS\Core\Cache\Backend\ApcuBackend`
+instead of :php:`TYPO3\CMS\Core\Cache\Backend\ApcBackend` in your caching framework configuration.
 
 Example before:
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87594-HardenExtbase.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87594-HardenExtbase.rst
similarity index 93%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87594-HardenExtbase.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87594-HardenExtbase.rst
index 7ece6d579902..6995f7195c2d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87594-HardenExtbase.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87594-HardenExtbase.rst
@@ -9,7 +9,8 @@ See :issue:`87594`
 Description
 ===========
 
-While hardening Extbase classes, method signatures changed due to an enforced strict type mode and introduced type hints for scalars. The change of signatures is considered breaking for the following methods of the following interfaces and their implementations and for the following classes and their derivatives:
+While hardening Extbase classes, method signatures changed due to an enforced strict type mode and introduced type hints for scalars.
+The change of signatures is considered breaking for the following methods of the following interfaces and their implementations and for the following classes and their derivatives:
 
 - :php:`\TYPO3\CMS\Extbase\DomainObject\DomainObjectInterface::getUid`
 - :php:`\TYPO3\CMS\Extbase\DomainObject\DomainObjectInterface::setPid`
@@ -86,8 +87,8 @@ PHP might throw a fatal error if the method signature(s) of your implementations
 Affected Installations
 ======================
 
-- All installations that use classes, that implement mentioned interfaces and their methods.
-- All installations that use classes, that inherit mentioned classes and overwrite their methods.
+- All installations that use classes that implement mentioned interfaces and their methods.
+- All installations that use classes that inherit mentioned classes and overwrite their methods.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
similarity index 87%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
index 06abf95795e1..b023840c3893 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87623-ReplaceConfigpersistenceclassesTyposcriptConfiguration.rst
@@ -11,7 +11,7 @@ Description
 
 The configuration of classes in the context of the Extbase persistence is no longer possible via typoscript.
 All typoscript concerning the configuration of classes in that context needs to be converted to php, residing
-in `EXT:Configuration/Extbase/Persistence/Classes.php`.
+in :file:`EXT:Configuration/Extbase/Persistence/Classes.php`.
 
 
 Impact
@@ -34,7 +34,7 @@ Migration
 =========
 
 Every extension that used typoscript for such configuration must provide a php configuration class called:
-`EXT:Configuration/Extbase/Persistence/Classes.php`
+:file:`EXT:Configuration/Extbase/Persistence/Classes.php`
 
 The migration is best described by an example:
 
@@ -83,9 +83,9 @@ This configuration will look like this, defined in php:
 
 A few things are noteworthy here:
 
-- The typoscript node `mapping` has been dropped and all sub nodes like `tableName` and `columns` are now located directly
+- The typoscript node :typoscript:`mapping` has been dropped and all sub nodes like :typoscript:`tableName` and :typoscript:`columns` are now located directly
   in the top node, i.e. the class name.
-- The mapping of columns changed due to the fact that `mapOnProperty` has been dropped and the mapping direction changed.
+- The mapping of columns changed due to the fact that :typoscript:`mapOnProperty` has been dropped and the mapping direction changed.
   With typoscript the top nodes were called like the class names which indicates the mapping direction model to table. But
   then, one had to define a mapping by columns instead of properties, which means, the mapping directions was reversed,
   forcing you to map database table fields on properties. This was quite confusing and the configuration is now eased as
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst
index a6f7b38e3cb1..2bc0bbd71576 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87627-RemovePropertyExtensionNameOfAbstractController.rst
@@ -24,13 +24,13 @@ Accessing the missing property :php:`$extensionName` will throw a fatal error.
 Affected Installations
 ======================
 
-All installations that read from :php:`\TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::$extensionName`
+All installations that read from :php:`\TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::$extensionName`.
 
 
 Migration
 =========
 
-The extension name is set in and available through the request object that is attached to the controller.
+The extension name is set in and available through the request object that is available in the controller.
 See :php:`\TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::$request` and :php:`\TYPO3\CMS\Extbase\Mvc\Request::getControllerExtensionName()`
 for more information.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87936-TCAForSysHistoryRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87936-TCAForSysHistoryRemoved.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87936-TCAForSysHistoryRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87936-TCAForSysHistoryRemoved.rst
index b8d049863e15..7bac75d65223 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87936-TCAForSysHistoryRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87936-TCAForSysHistoryRemoved.rst
@@ -9,17 +9,17 @@ See :issue:`87936`
 Description
 ===========
 
-The TCA definition for `sys_history` database table was removed. It was never shown in TYPO3 Backend,
+The TCA definition for :sql:`sys_history` database table was removed. It was never shown in TYPO3 Backend,
 and only in use for the BElog module as Extbase Domain Model. However, this relationship between
 logs and sys_history was decoupled in TYP3 v9.0.
 
-The database field "pid" which was "0" at all times, is now removed.
+The database field :sql:`pid` which was "0" at all times, is now removed.
 
 
 Impact
 ======
 
-Accessing :php:`$GLOBALS[TCA][sys_history]` will trigger a PHP warning, and the contents of the array
+Accessing :php:`$GLOBALS[TCA][sys_history]` will trigger a PHP :php:`E_WARNING`, and the contents of the array
 are not available anymore.
 
 
@@ -27,12 +27,12 @@ Affected Installations
 ======================
 
 Any TYPO3 installation with extensions accessing the global array by making use of
-`sys_history`.
+:sql:`sys_history`.
 
 
 Migration
 =========
 
-If still needed, an extension should deliver the full TCA definition of `sys_history`.
+If still needed, an extension should deliver the full TCA definition of :sql:`sys_history`.
 
 .. index:: Database, TCA, FullyScanned, ext:core
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87937-TCAOption_selicon_field_path_removed.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87937-TCAOption_selicon_field_path_removed.rst
similarity index 51%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87937-TCAOption_selicon_field_path_removed.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87937-TCAOption_selicon_field_path_removed.rst
index 9247ce13d85f..33b7de8f82bf 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87937-TCAOption_selicon_field_path_removed.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87937-TCAOption_selicon_field_path_removed.rst
@@ -12,25 +12,25 @@ Description
 The TCA option :php:`$GLOBALS['TCA'][$myTable]['ctrl']['selicon_field_path']` was removed.
 
 The option allowed to show icons in select items when using :php:`$myTable` as a foreign table
-in relations, and was bound to using `selicon_field` as a legacy file ("internal_type=file").
+in relations, and was bound to using :php:`selicon_field` as a legacy file (:php:`internal_type=file`).
 
 
 Impact
 ======
 
-It is now only possible to use `selicon_field` in inline relations towards `sys_file_reference`.
-Setting the `selicon_field_path` has no effect anymore and a deprecation warning will be triggered.
+It is now only possible to use :php:`selicon_field` in inline relations towards :php:`sys_file_reference`.
+Setting the :php:`selicon_field_path` has no effect anymore and a PHP :php:`E_USER_DEPRECATED` error will be triggered.
 
 
 Affected Installations
 ======================
 
-Any TYPO3 installation with an extension providing TCA with `selicon_field_path`.
+Any TYPO3 installation with an extension providing TCA with :php:`selicon_field_path`.
 
 
 Migration
 =========
 
-Remove the option `selicon_field_path` and use a inline relation to file references in `selicon_field` instead.
+Remove the option :php:`selicon_field_path` and use a inline relation to file references in :php:`selicon_field` instead.
 
 .. index:: TCA, PartiallyScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87957-DoNotMagicallyRegisterValidators.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87957-DoNotMagicallyRegisterValidators.rst
similarity index 93%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87957-DoNotMagicallyRegisterValidators.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87957-DoNotMagicallyRegisterValidators.rst
index b343cc56e008..e36dcc9f75a8 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87957-DoNotMagicallyRegisterValidators.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87957-DoNotMagicallyRegisterValidators.rst
@@ -9,12 +9,12 @@ See :issue:`87957`
 Description
 ===========
 
-There are several validators that Extbase automatically applies. One of these is domain validators that are registered
+There were several validators that Extbase applies automatically. One example are domain validators that are registered
 if created in a specific directory. Another one is the type validator which is created if a validator with a specific
 name exists.
 
-For this reason, the method :php:`\TYPO3\CMS\Extbase\Utility\ClassNamingUtility::translateModelNameToValidatorName` has
-been removed without substitution.
+The method :php:`TYPO3\CMS\Extbase\Utility\ClassNamingUtility::translateModelNameToValidatorName` has
+been removed without substitution. This leads to no automatically registered validators anymore.
 
 Domain Validators
 =================
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst
index e9b6925d2ff4..535cd52d6bec 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-87989-TCAOptionSetToDefaultOnCopyRemoved.rst
@@ -17,7 +17,7 @@ It allowed to reset a certain field to its default value when copying a record.
 Impact
 ======
 
-Having the setting set in TCA will trigger a deprecation warning when building TCA.
+Having the setting set in TCA will trigger a PHP :php:`E_USER_DEPRECATED` error when building TCA.
 
 Copying records with this TCA setting enabled, will now keep the copied state and avoid side-effects.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88129-RenameFeloginFlexformFields.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88129-RenameFeloginFlexformFields.rst
similarity index 90%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88129-RenameFeloginFlexformFields.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88129-RenameFeloginFlexformFields.rst
index 8720256cacef..33a5ff9b156b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88129-RenameFeloginFlexformFields.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88129-RenameFeloginFlexformFields.rst
@@ -25,7 +25,7 @@ Affected Installations
 ======================
 
 All installations with a felogin plugin need to migrate their flexform database values.
-PageTsConfig needs to be adjusted, that overrides the flexform.
+PageTsConfig that overrides the flexform needs to be adjusted.
 
 
 Migration
@@ -34,7 +34,8 @@ Migration
 An update wizard is provided to easily update all used felogin plugins. To migrate the flexform values, execute
 `Migrate felogin plugins to use prefixed flexform keys`.
 
-All PageTsConfig that overrides felogin flexform fields e.g. :typoscript:`TCEFORM.tt_content.pi_flexform.login.sDEF.showForgotPassword.disabled = 1` needs to add the `settings.` prefix to the keys.
+All PageTsConfig that overrides felogin flexform fields e.g. :typoscript:`TCEFORM.tt_content.pi_flexform.login.sDEF.showForgotPassword.disabled = 1`
+needs to add the `settings.` prefix to the keys.
 Note the escaping backslash! :typoscript:`TCEFORM.tt_content.pi_flexform.login.sDEF.settings\.showForgotPassword.disabled = 1`.
 
 .. index:: FlexForm, NotScanned, ext:felogin
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst
similarity index 70%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst
index fa93d53effab..f10aece6ecda 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88143-Version-relatedDatabaseFieldT3ver_idRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88143`
 Description
 ===========
 
-The database field for all workspace-enabled database tables `t3ver_id` is removed. It previously
+The database field for all workspace-enabled database tables :sql:`t3ver_id` is removed. It previously
 contained an incrementing numeric value when using incrementing versioning - the versioning concept
 which was in place before Workspaces were introduced in TYPO3 v4.0.
 
@@ -23,7 +23,7 @@ Impact
 Creating SQL statements in custom extensions explicitly selecting this field will result in SQL
 errors.
 
-In addition, when upgrading TYPO3 to v10.0. this field will be removed by the Database Analyzer
+In addition, when upgrading TYPO3 to v10.0 this field will be removed by the Database Analyzer
 Tool in the Install Tool for all TYPO3 core database tables and extensions using the automatic
 creation of database fields.
 
@@ -37,7 +37,7 @@ All installations with custom extensions explicitly requesting this field.
 Migration
 =========
 
-Search in any extension in `typo3conf/ext` for `t3ver_id` to see any usages, and remove the field
-from any queries, database definitions in `ext_tables.sql` files.
+Search in any extension in `typo3conf/ext` for :sql:`t3ver_id` to see any usages, and remove the field
+from any queries, database definitions in :file:`ext_tables.sql` files.
 
 .. index:: Database, NotScanned, ext:workspaces
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst
similarity index 85%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst
index fc5ec603cbef..810bdc8015bb 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88182-JsfuncInlineJsHasBeenDropped.rst
@@ -10,13 +10,13 @@ Description
 ===========
 
 The JavaScript file :file:`jsfunc.inline.js` which was responsible for FormEngine's subcomponent IRRE has been
-superseded by the rewritten `InlineControlContainer` component.
+superseded by the rewritten :php:`TYPO3\CMS\Backend\Form\Container\InlineControlContainer` component.
 
 
 Impact
 ======
 
-Requesting the file :file:`typo3/sysext/backend/Resources/Public/JavaScript/jsfunc.inline.js` will throw a 404 error.
+Requesting the file :file:`typo3/sysext/backend/Resources/Public/JavaScript/jsfunc.inline.js` will cause a 404 error.
 Calling any method of the global :javascript:`inline` object will throw an error since the object doesn't exist anymore.
 
 
@@ -29,7 +29,7 @@ All installations of TYPO3 are affected.
 Migration
 =========
 
-There is no migration available in most cases, since the `InlineControlContainer` component is now event-driven.
+There is no migration available in most cases, since the :php:`TYPO3\CMS\Backend\Form\Container\InlineControlContainer` component is now event-driven.
 
 One exception is the former :javascript:`inline.delayedImportElement()` method, since this part is now based on
 `postMessage`. For this approach, a small helper utility :javascript:`TYPO3/CMS/Backend/Utility/MessageUtility` has
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst
index 18bfd059971c..4a3179f44c21 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88366-RemovedCf_PrefixOfCacheTables.rst
@@ -1,23 +1,23 @@
 .. include:: ../../Includes.txt
 
-=======================================================
-Breaking: #88366 - Removed "cf_" prefix of cache tables
-=======================================================
+=================================================
+Breaking: #88366 - Removed prefix of cache tables
+=================================================
 
 See :issue:`88366`
 
 Description
 ===========
 
-In addition, when the Typo3DatabaseBackend now accesses and creates tables without the "cf_"
-prefix ("cf" = Caching Framework), so caches in the database are simply called "cache_rootline"
+In addition, when the Typo3DatabaseBackend now accesses and creates tables without the ``cf_``
+prefix ("cf" = Caching Framework), so caches in the database are simply called `cache_rootline`
 for instance.
 
 
 Impact
 ======
 
-Accessing the database tables directly with a "cf_" prefix will not work on the TYPO3 managed
+Accessing the database tables directly with a ``cf_`` prefix will not work on the TYPO3 managed
 cache tables.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst
index ad344087ad2c..190b0f934a19 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88376-RemovedObsoletePageNotFound_handlingSettings.rst
@@ -9,7 +9,7 @@ See :issue:`88376`
 Description
 ===========
 
-The following global TYPO3 settings usually set within `LocalConfiguration.php` have been removed:
+The following global TYPO3 settings, usually set within :file:`LocalConfiguration.php` have been removed:
 
 * :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['pageNotFound_handling']`
 * :php:`$GLOBALS['TYPO3_CONF_VARS']['FE']['pageNotFound_handling_statheader']`
@@ -32,18 +32,18 @@ will remove the settings automatically.
 Affected Installations
 ======================
 
-Any TYPO3 installations having these settings overridden in `LocalConfiguration.php`
+Any TYPO3 installations having these settings overridden in :file:`LocalConfiguration.php`
 file of an installation.
 
 
 Migration
 =========
 
-Access the install tool to automatically update the `LocalConfiguration.php` file and remove the
+Access the install tool to automatically update the :file:`LocalConfiguration.php` file and remove the
 settings.
 
 Ensure to set up Site Handling with proper error handlers. Avoid accessing these settings but
-rather use the available `ErrorController` PHP class, when trying to manually trigger a 404/500
+rather use the available :php:`TYPO3\CMS\Frontend\Controller\ErrorController` class, when trying to manually trigger a 404/500
 in the Frontend (e.g. custom plugin) instead.
 
 .. index:: Frontend, LocalConfiguration, PartiallyScanned, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88411-TBE_EDITORtypo3formRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88411-TBE_EDITORtypo3formRemoved.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88411-TBE_EDITORtypo3formRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88411-TBE_EDITORtypo3formRemoved.rst
index 6f75a8b9d8a2..01484caac2e0 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88411-TBE_EDITORtypo3formRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88411-TBE_EDITORtypo3formRemoved.rst
@@ -16,7 +16,7 @@ have been removed.
 Impact
 ======
 
-Any extension relying on this code will stop working.
+Any extension relying on this code will not work anymore.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst
index 1ec450f917e7..4f0332ee244e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88427-JsfuncevalfieldjsHasBeenRemoved.rst
@@ -9,14 +9,14 @@ See :issue:`88427`
 Description
 ===========
 
-The file :file:`jsfunc.evalfield.js` responsible for form value evaluation and validation has been removed. This job is
+The file :file:`jsfunc.evalfield.js`, responsible for form value evaluation and validation, has been removed. This job is
 now done by :js:`TYPO3/CMS/Backend/FormEngineValidation` since TYPO3 7.4.
 
 
 Impact
 ======
 
-Extensions still relying on this file and its API will stop working.
+Extensions still relying on this file and its API will not work anymore.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst
index 59a04d44e07a..d0c7f70a582d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88458-RemovedFrontendTrackUserFtuFunctionality.rst
@@ -12,14 +12,15 @@ Description
 The "ftu" feature, used to transfer sessions via GET parameter, has been removed.
 
 The implementation and the functionality exposed some security concerns, if enabled via TypoScript
-`config.ftu` as sessions could have been taken over by link sharing, although this was mitigated
+:typoscript:`config.ftu` as sessions could have been taken over by link sharing, although this was mitigated
 in the past by a security change.
 
 
 Impact
 ======
 
-The following public properties now trigger a PHP warning, when accessed:
+The following public properties now trigger PHP :php:`E_WARNING` when accessed:
+
 * :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->get_name`
 * :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getFallBack`
 * :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication->getMethodEnabled`
@@ -35,7 +36,7 @@ set anymore.
 Affected Installations
 ======================
 
-Any TYPO3 installation using the `config.ftu` functionality.
+Any TYPO3 installation using the :typoscript:`config.ftu` functionality.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst
index 7457c106c076..43d564fb1d6c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88496-MethodGetSwitchableControllerActionsHasBeenRemoved.rst
@@ -9,13 +9,16 @@ See :issue:`88496`
 Description
 ===========
 
-The abstract method :php:`\TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager::getSwitchableControllerActions` has been removed in favor of :php:`\TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager::getControllerConfiguration`. While the method name changes, the expected implemented functionality stays the same.
+The abstract method :php:`\TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager::getSwitchableControllerActions`
+has been removed in favor of :php:`\TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager::getControllerConfiguration`.
+While the method name changes, the expected implemented functionality stays the same.
 
 
 Impact
 ======
 
-Method :php:`getSwitchableControllerActions` will no longer be called. Instead :php:`getControllerConfiguration` is expected to be implemented by classes that extend :php:`TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager`.
+Method :php:`getSwitchableControllerActions` will no longer be called. Instead :php:`getControllerConfiguration` is expected
+to be implemented by classes that extend :php:`TYPO3\CMS\Extbase\Configuration\AbstractConfigurationManager`.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst
similarity index 84%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst
index 405ca3eab681..a7fa4d428af7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88498-GlobalDataForTimeTrackerStatisticsRemoved.rst
@@ -26,7 +26,7 @@ This also results in having :php:`$GLOBALS['TYPO3_MISC']` to not be set anymore.
 Impact
 ======
 
-Accessing the global variables will trigger a PHP warning, as they do not exist anymore.
+Accessing the global variables will trigger a PHP :php:`E_WARNING` error, as they do not exist anymore.
 
 
 Affected Installations
@@ -38,7 +38,7 @@ Any TYPO3 installation with an extension working with any of the global variable
 Migration
 =========
 
-Remove the usages and either use the newly introduced `TimeTracker->finish()` to calculate data, or set
+Remove the usages and either use the newly introduced :php:`TimeTracker->finish()` to calculate data, or set
 your own variables, if microtime is needed.
 
 .. index:: PHP-API, FullyScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst
similarity index 74%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst
index ecfe5e63b045..7e6f91231d56 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88500-RTEImageHandlingFunctionalityDropped.rst
@@ -16,12 +16,13 @@ It is still possible to use HTMLArea in further versions (if adopted), however t
 handling of images is removed.
 
 This includes:
-- RTE processing mode ("ts_images")
-- SoftReference Index for handling inline images
-- Removed public method `ImportExport->getRTEoriginalFilename()`
-- Removed public method `RteHtmlParser->TS_images_rte()`
-- Removed CLI command "cleanup:rteimages" and relevant command class
-- The configuration option `$GLOBALS['TYPO3_CONF_VARS']['BE']['RTE_imageStorageDir']`
+
+* RTE processing mode ("ts_images")
+* SoftReference Index for handling inline images
+* Removed public method :php:`ImportExport->getRTEoriginalFilename()`
+* Removed public method :php:`RteHtmlParser->TS_images_rte()`
+* Removed CLI command "cleanup:rteimages" and relevant command class
+* The configuration option :php:`$GLOBALS['TYPO3_CONF_VARS']['BE']['RTE_imageStorageDir']`
 
 
 Impact
@@ -30,10 +31,10 @@ Impact
 Images within an RTE field are not processed at all anymore, not part of the CLI.
 
 Calling the CLI script, using the PHP methods or the PHP CLI command class directly
-within PHP, will result in a fatal error.
+within PHP, will result in a PHP :php:`E_ERROR` error.
 
-Accessing the configuration option will trigger a PHP notice, as it is
-silently removed, if customly set in `LocalConfiguration.php`.
+Accessing the configuration option will trigger a PHP :php:`E_NOTICE` error, as it is
+silently removed, if customary set in :file:`LocalConfiguration.php`.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst
similarity index 69%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst
index db458f26e888..c69f1fe7c88a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88525-RemoveCreateDirsDirectiveOfExtensionInstallationEm_confphp.rst
@@ -9,15 +9,15 @@ See :issue:`88525`
 Description
 ===========
 
-Every TYPO3 extension has a file called `ext_emconf.php` where important information regarding
+Every TYPO3 extension has a file called :file`ext_emconf.php` where important information regarding
 dependencies, current version and loading order are stored.
 
-The directive `createDirs` that was responsible to create a list of folders in the file structure
+The directive :php:`createDirs` that was responsible to create a list of folders in the file structure
 during extension installation has been dropped.
 
-The option was available before any File Abstraction Layer, as the `uploads/` folder is not
-created by default by TYPO3 anymore, this directive is not supported as well, as TYPO3 strives
-to support unified file handling for content files, volatile files (file uploads within `typo3temp/var/`)
+The option was available before any File Abstraction Layer. As the :file:`uploads/` folder is not
+created by default by TYPO3 anymore, this directive is not supported anymore as well, as TYPO3 strives
+to support unified file handling for content files, volatile files (file uploads within :file:`typo3temp/var/`)
 or within Extensions directly. The Environment API, introduced in TYPO3 v9, should support for PHP-based
 APIs to choose / create a correct folder location.
 
@@ -33,7 +33,7 @@ when upgrading from previous TYPO3 versions, will continue to exist.
 Affected Installations
 ======================
 
-Any TYPO3 extension having this property within `ext_emconf.php` set.
+Any TYPO3 extension having this property within :file:`ext_emconf.php` set.
 
 
 Migration
@@ -42,6 +42,6 @@ Migration
 When an extension supports TYPO3 v10+ only, this directive can be removed.
 
 If an extension needs a special directory, this should be created via PHP when it is needed
-via e.g. `GeneralUtility::mkdir_deep()`.
+via e.g. :php:`GeneralUtility::mkdir_deep()`.
 
 .. index:: PHP-API, NotScanned, ext:extensionmanager
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst
similarity index 62%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst
index 484ecb016425..11d9e591138c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88527-OverridingCustomValuesInUserAuthenticationDerivatives.rst
@@ -9,26 +9,26 @@ See :issue:`88527`
 Description
 ===========
 
-Due to some restructuring of :php:`AbstractUserAuthentication` and its direct sub-classes
-:php:`BackendUserAuthentication` (a.k.a. :php:`$BE_USER`) and :php:`FrontendUserAuthentication`,
+Due to some restructuring of :php:`TYPO3\CMS\Core\Authentication\AbstractUserAuthentication` and its direct sub-classes
+:php:`TYPO3\CMS\Core\Authentication\BackendUserAuthentication` (a.k.a. :php:`$BE_USER`) and :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication`,
 various settings are now directly initiated and set in the respective constructor of each PHP class.
 
-Following this, the properties `sessionTimeout`, `gc_time` and `sessionDataLifetime` are set already
+Following this, the properties :php:`sessionTimeout`, :php:`gc_time` and :php:`sessionDataLifetime` are set already
 when the constructor is called. Before this was the case when :php:`start()` was called.
 
-In addition, the property `loginType` must be set for any subclass on instantiation. Previously
+In addition, the property :php:`loginType` must be set for any subclass on instantiation. Previously
 this was possible to be set just before :php:`start()` was called.
 
-The previous behavior allowed to override certain parameters to be evaluated just before `start()`.
+The previous behavior allowed to override certain parameters to be evaluated just before :php:`start()`.
 
 
 Impact
 ======
 
-Setting any global variables between the constructor method and `start()` will have no effect, as
+Setting any global variables between the constructor method and :php:`start()` will have no effect, as
 this is transferred and evaluated at the public properties already when the constructor is called.
 
-Subclassing :php:`AbstractUserAuthentication` without setting `loginType` will trigger an exception
+Subclassing :php:`AbstractUserAuthentication` without setting :php:`loginType` will trigger an exception
 on instantiation.
 
 
@@ -36,7 +36,7 @@ Affected Installations
 ======================
 
 Any TYPO3 installation where a custom UserAuthentication instantiation or sub-class is in place, and the setting
-order was changed between calling the constructor and the method `start()`, which is considered a very rare case.
+order was changed between calling the constructor and the method :php:`start()`, which is considered a very rare case.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
new file mode 100644
index 000000000000..ada259ff4206
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
@@ -0,0 +1,104 @@
+.. include:: ../../Includes.txt
+
+=================================================================
+Breaking: #88540 - Changed Request Workflow for Frontend Requests
+=================================================================
+
+See :issue:`88540`
+
+Description
+===========
+
+The "Frontend Request Workflow" is the PHP code responsible for
+setting up various functionality when the TYPO3 Frontend (= rendering of the website)
+is booted and the content is built. This includes Login/Permission Check, resolving
+the current site + language, and checking the page + rootline, then
+parsing TypoScript, which will then lead to building content (or taken from
+cache), until the actual output is returned.
+
+Since TYPO3 v9, this is all built via PSR-15 middlewares, the PSR-15 Request Handler,
+and the global TypoScriptFrontendController (TSFE).
+
+For TYPO3 v10.0, various changes were made in order to separate concerns / logic
+from each other, allowing to easily exchange certain components with
+other / extended functionality.
+
+The following changes have been made:
+
+Storing session data from a Frontend User Session / Anonymous session is now triggered within the Frontend User
+(`frontend-user-authenticator`) Middleware, at a later point - once the page was generated. Up until TYPO3 v9, this
+was part of the RequestHandler logic right after content was put together. This was due to legacy reasons of the
+previous hook execution order.
+
+Resolving the actual site - that is the site configuration plus the language - now happens before Frontend
+and Backend User Authentication. This is important to understand to be able to define further settings within
+Site Handling configuration in the future. Site and Site Language Resolving is now 100% independent of any permission
+settings. Evaluating if a language is active is evaluated separately.
+
+Backend User Authentication (:php:`$BE_USER`) is now started before Frontend User Authentication (`fe_user`), previously
+this was the other way around. Frontend Users are now stored in the request object via the `frontend.user` attribute,
+instead of :php:`$TSFE->fe_user`, until :php:`$TSFE` is instantiated.
+
+Once all site + permission/authentication functionality has been set up, Routing now tries to detect
+the target page ID and the URL parameters (`PageResolver` middleware) and evaluates the result, so-called
+"Page Arguments" directly afterwards (`PageArgumentValidator` middleware). This effectively validates the cHash
+logic.
+
+All of the mentioned parts above do not depend on :php:`TSFE` anymore. In fact, they are 100% independent of
+any TSFE-related code. :php:`TSFE` is instantiated after all site resolving, authentication, page resolving and argument
+validation is done.
+
+The new request workflow looks like this (simplified):
+
+#. Evaluation of Normalized Parameters (a.k.a. :php:`getIndpEnv`) & Evaluation of "Maintenance Mode" functionality
+#. Handling registered eID scripts depending on GET parameter `eID`
+#. Resolving Site configuration and Language from URL if possible
+#. Resolving logged-in Backend User Authentication for previewing hidden pages or languages
+#. Authentication of Website Users ("Frontend Users")
+#. Executing various static routes and redirect functionality
+#. Resolving Target Page ID and URL parameters based on Routing, Validation of Page Arguments based on "cHash"
+#. Setting up global :php:`$TSFE` object, injecting previously resolved settings into TSFE.
+#. Resolving the Rootline for the page
+#. Parsing and Evaluation of TypoScript Instructions to render the page content
+#. Build the content (cached / uncached)
+#. Return the Response (PSR-7) to the base application and output headers + content.
+
+In addition, :php:`TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController` now expects the following constructor arguments:
+
+#. Context API object (previously a copy of :php:`$TYPO3_CONF_VARS`, until TYPO3 v8, then, unused)
+#. :php:`TYPO3\CMS\Core\Site\Entity\SiteInterface` object (previously the Page ID)
+#. :php:`TYPO3\CMS\Core\Site\Entity\SiteLanguage` object (previously the Page Type)
+#. :php:`TYPO3\CMS\Core\Routing\PageArguments` object (previously the no_cache GET parameter)
+#. :php:`TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication` object (previously the cHash parameter)
+
+Impact
+======
+
+Hooks that depend on certain functionality being made before or after a hook is
+called will likely have a different behavior when a Frontend Session is used within Hooks.
+
+Anything related to regular plugins / content / TypoScript is not affected.
+
+
+Affected Installations
+======================
+
+Any hooks from third party extensions that run
+:php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_fe.php']['hook_eofe']`
+and depend on the frontend session data being written.
+
+Any TYPO3 extensions using middlewares in the frontend.
+
+Migration
+=========
+
+Consider using a PSR-15 middleware instead of using a hook, or explicitly call :php:`storeSessionData()` within
+the PHP hook if necessary.
+
+If an existing middleware was used, ensure that it's loaded in TYPO3 v10 at the proper location, as the
+`typo3-cms/frontend/tsfe` middleware is loaded at a very late point.
+
+Ensure to use proper objects for the constructor arguments on :php:`TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController` when instantiating
+the object on your own.
+
+.. index:: Frontend, PHP-API, NotScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst
similarity index 64%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst
index 739e955a8338..ea9b26f9380e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88564-PageTSconfigSettingTSFEconstantsRemoved.rst
@@ -9,13 +9,13 @@ See :issue:`88564`
 Description
 ===========
 
-The PageTSconfig / UserTSconfig `TSFE.constants`, which allowed to override settings constants
+The PageTSconfig / UserTSconfig :typoscript:`TSFE.constants`, which allowed to override settings constants
 on a per-tree level page was introduced in TYPO3 at the very beginning, long before TSconfig had conditions.
 
 It was used to share TypoScript-based configuration between frontend / backend, and on a per-page/tree level.
 
 However, this has been superseded for a long time by using proper configuration files which
-can be loaded at any time when `ext_localconf.php` of an extension is loaded, for example.
+can be loaded at any time, for example when :file:`ext_localconf.php` of an extension is loaded.
 
 Therefore, the option has been removed.
 
@@ -23,21 +23,21 @@ Therefore, the option has been removed.
 Impact
 ======
 
-Setting `TSFE.constants` in PageTSconfig or UserTSconfig has no effect anymore, as it is not evaluated
+Setting :typoscript:`TSFE.constants` in PageTSconfig or UserTSconfig has no effect, as it is not evaluated
 anymore.
 
 
 Affected Installations
 ======================
 
-Any TYPO3 installation using `TSFE.constants` in their PageTSconfig.
+Any TYPO3 installation using :typoscript:`TSFE.constants` in their PageTSconfig.
 
 
 Migration
 =========
 
 It is recommended to include TypoScript conditions in setup/constants, also since constants+setup
-are also evaluated in Backend context for Extbase modules, this option is not needed anymore and
+are evaluated in Backend context for Extbase modules. This option is not needed anymore and
 can be substituted by simple constants in `sys_template` or any Extension inclusion files as well.
 
 .. index:: TSConfig, NotScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst
similarity index 78%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst
index 06a8f6d5c09f..c315f7eccd9c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88574-4thParameterOfPageRepository-enableFieldsRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88574`
 Description
 ===========
 
-The fourth parameter of :php:`PageRepository->enableFields()` was meant to filter out versioned records
+The fourth parameter of :php:`TYPO3\CMS\Core\Domain\Repository\PageRepository->enableFields()` was meant to filter out versioned records
 which are in Live Workspace (versioning, not workspaces). Although the method has largely been superseded
 with Doctrine DBAL's Restrictions, it is still used in some places.
 
@@ -21,7 +21,7 @@ Impact
 ======
 
 Calling the method above with the fourth parameter set to true has no effect anymore, and will
-trigger a PHP Notice.
+trigger a PHP :PHP:`E_NOTICE` error.
 
 
 Affected Installations
@@ -35,6 +35,6 @@ Migration
 =========
 
 The fourth parameter on any method call can be removed (if set to "false"), or should be replaced with a
-separate instance of PageRepository with a custom Context.
+separate instance of :php:`TYPO3\CMS\Core\Domain\Repository\PageRepository` with a custom Context.
 
 .. index:: Frontend, PHP-API, FullyScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst
similarity index 80%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst
index 831185fa2c65..afe80fa814da 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88583-DatabaseFieldSys_languagestatic_lang_isocodeRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88583`
 Description
 ===========
 
-The database field `static_lang_isocode` is a reference to a language within the third-party
+The database field :sql:`static_lang_isocode` is a reference to a language within the third-party
 extension `static_info_tables`. This was tightly coupled to TYPO3 Core until Site Handling was
 introduced to add meaning and meta-data to a language on a per-site level.
 
@@ -19,7 +19,7 @@ The field is not in use by the TYPO3 Core anymore, so the database definition is
 Impact
 ======
 
-Migrating to TYPO3 v10.0 will remove the field in the Database Comparison View.
+Migrating to TYPO3 v10.0 will remove the field in the Database Analyzer.
 
 
 Affected Installations
@@ -32,7 +32,7 @@ database field, which is very unlikely.
 Migration
 =========
 
-The field can safely be removed in the Database Comparison View if it is not used by an extension.
+The field can safely be removed in the Database Analyzer if it is not used by an extension.
 
 If the field is still needed, it is recommended to install the extension `static_info_tables`.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst
similarity index 66%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst
index 7c514f25e184..5e6e4e9eb955 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88638-StreamlinedSoftRefParserReferenceLookup.rst
@@ -17,12 +17,12 @@ Parsers can be added or overridden via the hook registry
 :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['GLOBAL']['softRefParser'][$parserType]`.
 
 Previously, the API method for fetching the proper parsers
-:php:`BackendUtility::softRefParserObj()` kept a runtime cache of created objects
-per type within a global PHP array ("T3_VAR"). This allowed to create objects
+:php:`TYPO3\CMS\Backend\Utility\BackendUtility::softRefParserObj()` kept a runtime cache of created objects
+per type within a global PHP array (:php:`T3_VAR`). This allowed to create objects
 only once, even if there are multiple necessary parts required.
 
 TYPO3's Core SoftRefParser does not keep any state, but the class now has a
-SingletonInterface, which means that the object is now a re-used object
+:php:`SingletonInterface`, which means that the object is now a re-used object
 as before.
 
 
@@ -30,9 +30,9 @@ Impact
 ======
 
 Calling the SoftRefParser factory method does not keep state of the parser
-objects via `$GLOBALS['T3_VAR']['softRefParser']` anymore.
+objects via :php:`$GLOBALS['T3_VAR']['softRefParser']` anymore.
 
-Instead, SingletonInterface is recommended for re-using SoftRefParser objects
+Instead, :php:`SingletonInterface` is recommended for re-using SoftRefParser objects
 if they need to keep state.
 
 
@@ -46,10 +46,10 @@ or the global variable directly.
 Migration
 =========
 
-Replace the global variable access via the API call to BackendUtility, if this
+Replace the global variable access via the API call to :php:`TYPO3\CMS\Backend\Utility\BackendUtility`, if this
 is applicable.
 
 If a custom parser is in use, it is recommended to evaluate whether it contains
-re-usable data and switch to SingletonInterface instead.
+re-usable data and switch to :php:`SingletonInterface` instead.
 
 .. index:: Backend, FullyScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst
index f5e8f0c620fd..cc648a0183f6 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst
@@ -9,13 +9,13 @@ See :issue:`88640`
 Description
 ===========
 
-The database field `nextLevel` of the database table `sys_template` where TypoScript configuration
+The database field :sql:`nextLevel` of the database table :sql:`sys_template` where TypoScript configuration
 is stored, has been removed.
 
-The field `nextLevel` was introduced in TYPO3 v3.x before TypoScript could be imported from
+The field :sql:`nextLevel` was introduced in TYPO3 v3.x before TypoScript could be imported from
 external files.
 
-Nowadays, TypoScript conditions should be used much more instead of this `nextLevel` feature,
+Nowadays, TypoScript conditions should be used much more instead of this :sql:`nextLevel` feature,
 which is kind of a pseudo-condition.
 
 
@@ -30,14 +30,14 @@ Requesting the database field in custom database queries will result in an SQL e
 Affected Installations
 ======================
 
-TYPO3 installations that have `sys_template` records with this flag activated,
+TYPO3 installations that have :sql:`sys_template` records with this flag activated,
 or querying this database field in third-party extensions.
 
 
 Migration
 =========
 
-Check for existing `sys_template` records having this flag activated by executing
+Check for existing :sql:`sys_template` records having this flag activated by executing
 this SQL command:
 
 :sql:`SELECT * FROM sys_template WHERE nextLevel>0 AND deleted=0;`
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst
index bc83eb99762e..86892ea1884c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88643-RemovedSwiftmailerswiftmailerDependency.rst
@@ -19,10 +19,10 @@ Impact
 ======
 
 Custom SwiftMailer plugins or transports cannot be used without further
-migration anymore and will result in a fatal error.
+migration anymore and will result in a fatal :php:`E_ERROR`.
 
-Using SwiftMailer-specific API by using TYPO3's MailMessage class might result
-in fatal errors as well when sending out emails.
+Using SwiftMailer-specific API by using TYPO3's :php:`TYPO3\CMS\Core\Mail\MailMessage` class might result
+in fatal :php:`E_ERROR` when sending out emails.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst
similarity index 50%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst
index 1902a470b1e8..94a6fa3bac63 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88646-RemovedInheritanceOfAbstractServiceFromAbstractAuthenticationService.rst
@@ -9,24 +9,25 @@ See :issue:`88646`
 Description
 ===========
 
-The AbstractAuthenticationService PHP class is used for any kind of Authentication
+The PHP :php:`TYPO3\CMS\Core\Authentication\AbstractAuthenticationService` class is used for any kind of Authentication
 or Authorization towards Backend Users and Frontend Users.
 
-It was previously based on :php:`AbstractService` for any kind of Service API, which
+It was previously based on :php:`TYPO3\CMS\Core\Service\AbstractService` for any kind of Service API, which
 also includes manipulating files and execution of external applications, which is
 there for legacy reasons since TYPO3 3.x, where the Service API via :php:`GeneralUtility::makeInstanceService` was added.
 
-In order to refactor the Authentication API, the AbstractAuthenticationService
-class does not inherit from AbstractService anymore. Instead, the most required
+In order to refactor the Authentication API, the :php:`TYPO3\CMS\Core\Authentication\AbstractAuthenticationService`
+class does not inherit from :php:`TYPO3\CMS\Core\Service\AbstractService` anymore. Instead, the most required
 methods for executing a service is added to the Abstract class directly.
 
 
 Impact
 ======
 
-Any calls or checks on the AbstractAuthenticationService class or methods, properties or constants that reside within AbstractService will result in PHP errors or warnings.
+Any calls or checks on the :php:`TYPO3\CMS\Core\Authentication\AbstractAuthenticationService` class or methods, properties or constants that reside within
+:php:`TYPO3\CMS\Core\Service\AbstractService` will result in PHP :php:`E_ERROR` or :php:`E_WARNING`.
 
-Since AbstractAuthenticationService is used for most custom Authentication APIs,
+Since :php:`TYPO3\CMS\Core\Authentication\AbstractAuthenticationService` is used for most custom Authentication APIs,
 this could affect some of the hooks or custom authentication providers available.
 
 
@@ -40,8 +41,8 @@ users / groups - e.g. LDAP or Two-Factor-Authentication.
 Migration
 =========
 
-If your custom Authentication Service extends from AbstractAuthenticationService
-but requires methods or properties from AbstractService, ensure to copy over the
+If your custom Authentication Service extends from :php:`TYPO3\CMS\Core\Authentication\AbstractAuthenticationService`
+but requires methods or properties from :php:`TYPO3\CMS\Core\Service\AbstractService`, ensure to copy over the
 necessary methods/properties/constants into your custom Authentication provider.
 
 .. index:: PHP-API, NotScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88657-PopupConfigurationInFormEngineDropped.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88657-PopupConfigurationInFormEngineDropped.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88657-PopupConfigurationInFormEngineDropped.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88657-PopupConfigurationInFormEngineDropped.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88660-GLOBALST3_VARRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88660-GLOBALST3_VARRemoved.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88660-GLOBALST3_VARRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88660-GLOBALST3_VARRemoved.rst
index abafa7420747..b1888bd34d16 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88660-GLOBALST3_VARRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88660-GLOBALST3_VARRemoved.rst
@@ -14,10 +14,10 @@ use cases - previously used within Service API via :php:`GeneralUtility::makeIns
 and to magically inject special hard-coded local indexed search files, has been removed.
 
 The overall goal of TYPO3's application is to not keep any state within global variables, and
-the `T3_VAR` ("TYPO3 Various") has not been actively used for that anymore since TYPO3 6.0, and
+the :php:`T3_VAR` ("TYPO3 Various") has not been actively used for that anymore since TYPO3 6.0, and
 has been kept only for backwards-compatibility of the existing solutions.
 
-The initialization of the global variable during TYPO3 Bootstrap, any usages of `T3_VAR`,
+The initialization of the global variable during TYPO3 Bootstrap, any usages of :php:`T3_VAR`,
 especially within "indexed search" has been removed.
 
 
@@ -34,7 +34,7 @@ and has no effect.
 Affected Installations
 ======================
 
-TYPO3 installations with third-party extensions or code within `AdditionalConfiguration.php`
+TYPO3 installations with third-party extensions or code within :file:`AdditionalConfiguration.php`
 that actively set or read values from the global variable.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst
similarity index 96%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst
index 9c24ccd09e56..14a93c21239b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88667-RemovedAdditionalJavaScriptSubmitFromFormEngine.rst
@@ -31,7 +31,7 @@ All 3rd-party extensions using this option are affected.
 Migration
 =========
 
-It is possible to create and register a AMD module.
+It is possible to create and register an AMD module.
 
 .. code-block:: php
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst
index 20e31cf8d34b..d1dd254e6cad 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88669-FormEngineFormDataProviderParentPageTcaRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88669`
 Description
 ===========
 
-FormEngine added "parentPageTca" by default to the result object. It was added in TYPO3 v7 during
+FormEngine added :php:`parentPageTca` by default to the result object. It was added in TYPO3 v7 during
 refactoring, but already commented that it wasn't used at all in Core, and might not be necessary.
 
 It contained a copy of :php:`$GLOBALS['TCA']['pages']`, which can be obtained directly as well.
@@ -20,7 +20,7 @@ The DataProvider and the value within the result key has been removed.
 Impact
 ======
 
-When accessing the `parentPageTca` key within a FormDataProvider or Node (FormEngine-related only),
+When accessing the :php:`parentPageTca` key within a FormDataProvider or Node (FormEngine-related only),
 a PHP notice is given due to a non-existing array key.
 
 
@@ -34,7 +34,7 @@ DataProvider, which is highly unlikely.
 Migration
 =========
 
-Instead of accessing `$result['parentPageTca'] within a custom FormDataProvider or FormRenderNode,
+Instead of accessing :php:`$result['parentPageTca'] within a custom FormDataProvider or FormRenderNode,
 :php:`$GLOBALS['TCA']['pages']` can be accessed directly.
 
 .. index:: TCA, NotScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst
similarity index 87%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst
index f3a7db533c92..429976516ad7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88681-ImportOfPHPFilesInImportExportFilesRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88681`
 Description
 ===========
 
-Importing XML data via `EXT:impexp` previously allowed to import PHP files for Administrators
+Importing XML data via EXT:impexp previously allowed to import PHP files for Administrators
 in TYPO3 Backend. This by-pass functionality is removed, and the configured File Deny Pattern
 now applies for all imports in order to streamline import functionality with other file
 operations within TYPO3 Core.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst
index 0b4e8a0ad92a..70d785f09eb2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88687-ConfigureExtbaseRequestHandlersViaPHP.rst
@@ -11,7 +11,7 @@ Description
 
 The configuration of extbase request handlers is no longer possible via typoscript.
 All typoscript concerning the configuration of request handlers needs to be converted to php, residing
-in `EXT:Configuration/Extbase/RequestHandlers.php`.
+in :file:`EXT:Configuration/Extbase/RequestHandlers.php`.
 
 
 Impact
@@ -31,7 +31,7 @@ Migration
 =========
 
 Every extension that used typoscript for such configuration must provide a php configuration class called:
-`EXT:Configuration/Extbase/RequestHandlers.php`
+:file:`EXT:Configuration/Extbase/RequestHandlers.php`
 
 The migration is best described by an example:
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88706-StreamlineFeloginLocallangKeys.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88706-StreamlineFeloginLocallangKeys.rst
similarity index 97%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88706-StreamlineFeloginLocallangKeys.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88706-StreamlineFeloginLocallangKeys.rst
index b9cb964ddc20..c9ff02e370f5 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88706-StreamlineFeloginLocallangKeys.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88706-StreamlineFeloginLocallangKeys.rst
@@ -58,6 +58,6 @@ Keys:
 Migration
 =========
 
-Remove the corresponding `ll_` from the key.
+Remove the `ll_` prefix from the key.
 
 .. index:: Frontend, NotScanned, ext:felogin
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst
index 946e01adb8a4..864861be8555 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88724-RemoveSuperfluousMethodsOfLocalizationRedirect.rst
@@ -10,14 +10,15 @@ Description
 ===========
 
 The method :php:`localizationRedirect` in PageLayoutView, DatabaseRecordList and EditDocumentController were almost equal.
-So the usage has been streamlined and the methods in PageLayoutView and DatabaseRecordList has been removed.
+The usage has been streamlined and the methods in PageLayoutView and DatabaseRecordList have been removed.
 
 
 Impact
 ======
 
 Calling the routes `web_layout` or `web_list` with parameter `justLocalized` will not redirect to the translated record anymore.
-Calling :php:`TYPO3\CMS\Backend\View\PageLayoutView->localizationRedirect` or :php:`TYPO3\CMS\Recordlist\RecordList\DatabaseRecordList->localizationRedirect` will result in a fatal error.
+Calling :php:`TYPO3\CMS\Backend\View\PageLayoutView->localizationRedirect` or :php:`TYPO3\CMS\Recordlist\RecordList\DatabaseRecordList->localizationRedirect`
+will result in a fatal :php:`E_ERROR`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst
index e3438ba96084..ab11005a104d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88741-CHashCalculationInIndexedSearchRemoved.rst
@@ -23,10 +23,10 @@ has been removed.
 
 The following database fields are unused and have been removed:
 
-* index_config.chashcalc
-* index_phash.cHashParams
+* :sql:`index_config.chashcalc`
+* :sql:`index_phash.cHashParams`
 
-The database field `index_debug.debuginfo` now contains data stored in a JSON-formatted string
+The database field :sql:`index_debug.debuginfo` now contains data stored in a JSON-formatted string
 instead of a serialized PHP string.
 
 
@@ -49,7 +49,7 @@ of Indexed Search.
 Migration
 =========
 
-No migration needed, as everything works as before, as the data is now stored in
+No migration needed, as everything works as before. The data is now stored in
 the database field as JSON-encoded string `index_phash.static_page_arguments`.
 
 In case of using debug information for Indexed Search (index with enabled debug information),
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst
index 3b94db124a67..c479631f79c5 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88744-DatabaseFieldsRelatedToCSSStyledContentRemoved.rst
@@ -10,19 +10,19 @@ Description
 ===========
 
 CSS Styled Content was superseded with Fluid Styled Content in TYPO3 v7, and support was dropped
-with TYPO3 v9. However, TYPO3 Core still shipped with some database fields that were kept to easy
+with TYPO3 v9. TYPO3 Core still shipped with some database fields that were kept to easy
 manual migration for specific values in these fields.
 
-These database fields within the database table `tt_content` have been removed.
+These database fields within the database table :sql:`tt_content` have been removed.
 
-* tt_content.spaceBefore (now used via space_before_class)
-* tt_content.spaceAfter (now used via space_after_class)
+* :sql:`tt_content.spaceBefore` (now used via space_before_class)
+* :sql:`tt_content.spaceAfter` (now used via space_after_class)
 
 
 Impact
 ======
 
-Accessing the database fields with a custom SQL query will result in SQL errors, or empty values.
+Accessing the database fields with a custom SQL query will result in SQL errors or empty values.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88755-RemovePOSTOptionFromTypolinkaddQueryStringmethod.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88755-RemovePOSTOptionFromTypolinkaddQueryStringmethod.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88755-RemovePOSTOptionFromTypolinkaddQueryStringmethod.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88755-RemovePOSTOptionFromTypolinkaddQueryStringmethod.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst
index ab231a5a4e10..489d6edd1a0a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88758-SelectiveConcatenationOfCSSFilesInResourceCompressorRemoved.rst
@@ -9,7 +9,7 @@ See :issue:`88758`
 Description
 ===========
 
-ResourceCompressor, used to merge and compress CSS and JS files, has had an option to only
+:php:`TYPO3\CMS\Core\Resource\ResourceCompressor`, used to merge and compress CSS and JS files, has had an option to only
 merge CSS files from selected folders. This was used to limit CSS files of skins for TYPO3
 Backend files.
 
@@ -22,7 +22,7 @@ which should be concatenated, this change does not affect TYPO3 API of Frontend
 Impact
 ======
 
-Calling ResourceCompressor->concatenateCssFiles() with a second argument has no effect anymore.
+Calling :php:`TYPO3\CMS\Core\Resource\ResourceCompressor->concatenateCssFiles()` with a second argument has no effect anymore.
 
 Adding CSS files manually in TYPO3 Backend via custom extensions will now automatically be merged
 with the loaded CSS styles of :php:`$TBE_STYLES` skin.
@@ -32,7 +32,7 @@ Affected Installations
 ======================
 
 TYPO3 installations with extensions adding third-party CSS files in the TYPO3 Backend,
-or extensions using ResourceCompressor directly.
+or extensions using :php:`TYPO3\CMS\Core\Resource\ResourceCompressor` directly.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst
similarity index 82%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst
index 35e09b8a811b..198fa6ff3cab 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88772-JavaScriptScriptTagsOmitTypetextjavascriptInHTML5.rst
@@ -9,14 +9,14 @@ See :issue:`88772`
 Description
 ===========
 
-When rendering HTML5 output, `<script>` tags do not the additional attribute `type=text/javascript`
+When rendering HTML5 output, :html:`<script>` tags do not the additional attribute :html:`type=text/javascript`
 anymore as it is considered optional, and if none given, modern browsers fall back to this type
 already.
 
 See the official W3C definition here: https://www.w3.org/TR/html52/semantics-scripting.html#element-attrdef-script-type
 
 For this reason, all of TYPO3's Backend (which is rendering HTML5) and Installer do not include
-this optional attribute in `<script>` tags anymore.
+this optional attribute in :html:`<script>` tags anymore.
 
 For TYPO3 Frontend rendering, the attribute is omitted when having no doctype or HTML5 as doctype
 configured (via TypoScript :typoscript:`config.doctype = html5`). This leads to a minimal smaller
@@ -28,7 +28,7 @@ For any XHTML or HTML4-based website, the attribute is still added.
 Impact
 ======
 
-TYPO3's Frontend rendering does not render `type=text/javascript` anymore in `<script>` tags when
+TYPO3's Frontend rendering does not render :html:`type=text/javascript` anymore in :html:`<script>` tags when
 rendering a HTML5 output, unless explicitly specified.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88779-RecordListRemoveUnusedCode.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88779-RecordListRemoveUnusedCode.rst
similarity index 87%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88779-RecordListRemoveUnusedCode.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88779-RecordListRemoveUnusedCode.rst
index 394735ed744f..d7f490ccb9a3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88779-RecordListRemoveUnusedCode.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88779-RecordListRemoveUnusedCode.rst
@@ -30,7 +30,7 @@ The following public methods have been removed from :php:`TYPO3\CMS\Recordlist\R
 Impact
 ======
 
-Calling one of the mentioned methods will trigger a fatal php error.
+Calling one of the mentioned methods will trigger a fatal :php:`E_ERROR`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
similarity index 61%
rename from typo3/sysext/core/Documentation/Changelog/master/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
index 55f0e96790b9..a29ca9154234 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Breaking-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
@@ -13,21 +13,28 @@ With the adaption of the PSR-3 standard some PHP code had to be changed in order
 The key difference is that log levels are now represented by strings rather than numbers. Note that the order
 of log levels is not affected and stays the same.
 
-The breaking changes mostly affect internal functionality and usually does not affect third-party extensions.
+The breaking changes mostly affect internal functionality and should not apply to third-party extensions.
 
 
 Impact
 ======
 
-The class :php:`\TYPO3\CMS\Core\Log\LogLevel` now extends from the PSR-3 base class and therefore inherits the new definition of the log levels (EMERGENCY to DEBUG) based on string values.
+The class :php:`\TYPO3\CMS\Core\Log\LogLevel` now extends from the PSR-3 base class and therefore inherits the new definition
+of the log levels (`EMERGENCY` to `DEBUG`) based on string values.
 
-The signatures of these to methods has been adjusted to accept the new :php:`LogLevel::*` constants:
-- :php:`\TYPO3\CMS\Core\Log\Logger::addWriter`
-- :php:`\TYPO3\CMS\Core\Log\Logger::addProcessor`
+The signatures of following methods have been adjusted to accept the new :php:`LogLevel::*` constants:
 
-The internal storage of the log level inside :php:`\TYPO3\CMS\Core\Log\LogRecord` has been adjusted, consequently the methods :php:`setLevel()` and :php:`getLevel()` accept :php:`string` values now.
+* :php:`\TYPO3\CMS\Core\Log\Logger::addWriter`
+* :php:`\TYPO3\CMS\Core\Log\Logger::addProcessor`
 
-Also in case you have configured own logger or log targets, you have to adjust the integer level and use strings.
+The internal storage of the log level inside :php:`\TYPO3\CMS\Core\Log\LogRecord` has been adjusted, consequently the methods
+
+* :php:`setLevel()` and
+* :php:`getLevel()`
+
+respectively accept and return :php:`string` values now.
+
+In case you have configured own logger or log targets, you have to adjust the integer level and use strings.
 
 Example:
 
@@ -63,9 +70,9 @@ Any installation using third-party extensions interacting with the internals of
 Migration
 =========
 
-There are two easy ways to convert the number to the string representation and vice versa:
+There are two easy ways to convert the integer to the string representation and vice versa:
 
-- Convert from number to string: :php:`$logLevel = LogLevel::getInternalName($logLevelAsNumber)`
-- Convert from string to number: :php:`$logLevelAsNumber = LogLevel::normalizeLevel($logLevel)`
+- Convert from integer to string: :php:`$logLevel = LogLevel::getInternalName($logLevelAsNumber)`
+- Convert from string to integer: :php:`$logLevelAsNumber = LogLevel::normalizeLevel($logLevel)`
 
 .. index:: PHP-API, NotScanned, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-80420-EmailFinisherSingleAddressOptions.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-80420-EmailFinisherSingleAddressOptions.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-80420-EmailFinisherSingleAddressOptions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-80420-EmailFinisherSingleAddressOptions.rst
index 021748909477..80f8d27aae6b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-80420-EmailFinisherSingleAddressOptions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-80420-EmailFinisherSingleAddressOptions.rst
@@ -9,7 +9,11 @@ See :issue:`80420`
 Description
 ===========
 
-The :php:`EmailFinisher` of EXT:form has options to set multiple recipients for :code:`To`, :code:`CC` and :code:`BCC`. For this reason, the following options have been deprecated and will be removed in TYPO3 11.0:
+The :php:`EmailFinisher` of EXT:form has options to set multiple recipients for :code:`To`, :code:`CC` and :code:`BCC`.
+For consistency reasons and to limit the number of choices, resulting in easier configuration, the single value configuration options
+have will be removed in favour for their respective multi value variants.
+
+For this reason, the following options have been marked as deprecated and will be removed in TYPO3 11.0:
 
 * :yaml:`recipientAddress`
 * :yaml:`recipientName`
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst
similarity index 59%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst
index 0e0f8be053e8..0517bab49f12 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-82669-StreamlineBackendRoutePathInconsistencies.rst
@@ -9,11 +9,11 @@ See :issue:`82669`
 Description
 ===========
 
-When registering Backend modules, it is already possible to define a custom route path, via the `path`
-option in the module configuration section within `ext_tables.php`.
+When registering Backend modules, it is already possible to define a custom route path, via the :php:`path`
+option in the module configuration section within :file:`ext_tables.php`.
 
-Backend Routes to modules without path configurations are now named
-"/module/main-module-name/submodule-name" e.g. "/module/web/ts".
+Backend Routes to modules without path configurations are now named using the pattern
+"/module/<main-module-name>/<submodule-name>" e.g. `/module/web/ts`.
 
 Old route paths for modules are called "/web/ts/" will still work but are discouraged to use.
 
@@ -28,13 +28,13 @@ resolved, whereas the old path will be removed in TYPO3 v10.0.
 Affected Installations
 ======================
 
-Any installation using TYPO3 Backend Links via `buildUriFromRoutePath()` in custom extensions.
+Any installation using TYPO3 Backend Links via :php:`TYPO3\CMS\Backend\Routing\UriBuilder->buildUriFromRoutePath()` in custom extensions.
 
 
 Migration
 =========
 
-TYPO3 Backend Links via `buildUriFromRoutePath()` should be used with the new module name as
+TYPO3 Backend Links via :php:`TYPO3\CMS\Backend\Routing\UriBuilder->buildUriFromRoutePath()` should be used with the new module name as
 described above.
 
 .. index:: Backend, NotScanned, ext:backend
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-85895-DeprecateFile_getMetaData.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-85895-DeprecateFile_getMetaData.rst
similarity index 52%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-85895-DeprecateFile_getMetaData.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-85895-DeprecateFile_getMetaData.rst
index 61c102503eff..273cbd21092f 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-85895-DeprecateFile_getMetaData.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-85895-DeprecateFile_getMetaData.rst
@@ -9,19 +9,20 @@ See :issue:`85895`
 Description
 ===========
 
-The internal method :php:`File::_getMetaData()` which is used to fetch meta data of a file has been marked as deprecated. This method has been superseded by the :php:`MetaDataAspect`.
+The internal method :php:`TYPO3\CMS\Core\Resource\File::_getMetaData()` which is used to fetch meta data of a file
+has been marked as deprecated. This method has been superseded by the :php:`TYPO3\CMS\Core\Resource\MetaDataAspect`.
 
 
 Impact
 ======
 
-Using this method will trigger a deprecation entry.
+Using this method will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
 ======================
 
-Any 3rd party extension calling :php:`_getMetaData()` is affected.
+Any 3rd party extension calling :php:`:php:`TYPO3\CMS\Core\Resource\File::_getMetaData()` is affected.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatContants.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatContants.rst
new file mode 100644
index 000000000000..39dff031188c
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatContants.rst
@@ -0,0 +1,37 @@
+.. include:: ../../Includes.txt
+
+======================================================
+Deprecation: #87200 - EmailFinisher FORMAT_* constants
+======================================================
+
+See :issue:`87200`
+
+Description
+===========
+
+The constants
+
+* :php:`TYPO3\CMS\Form\Domain\Finishers\EmailFinisher::FORMAT_PLAINTEXT` and
+* :php:`TYPO3\CMS\Form\Domain\Finishers\EmailFinisher::FORMAT_HTML`
+
+have been marked as deprecated and will be removed in TYPO3 11.0.
+
+
+Impact
+======
+
+Accessing these constants will lead to a fatal :php:`E_ERROR` in TYPO3 11.0.
+
+
+Affected Installations
+======================
+
+All installations which use EXT:form and directly access these constants.
+
+
+Migration
+=========
+
+Do not use these constants anymore.
+
+.. index:: PHP-API, FullyScanned, ext:form
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatOption.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatOption.rst
similarity index 67%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatOption.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatOption.rst
index 8858af5a9151..f3441ecca0f1 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatOption.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87200-EmailFinisherFormatOption.rst
@@ -9,7 +9,9 @@ See :issue:`87200`
 Description
 ===========
 
-The :yaml:`format` option of the :php:`EmailFinisher` has been deprecated and will be removed in TYPO3 11.0. It is replaced by the new :yaml:`addHtmlPart` option which can be used to disable HTML and enforce plaintext-only mails. If set, mails will contain a plaintext and HTML part, otherwise only a plaintext part.
+The :yaml:`format` option of the :php:`TYPO3\CMS\Form\Domain\Finishers\EmailFinisher` has been marked as deprecated and
+will be removed in TYPO3 11.0. It is replaced by the new :yaml:`addHtmlPart` option which can be used to disable HTML
+and enforce plaintext-only mails. If set, mails will contain a plaintext and HTML part, otherwise only a plaintext part.
 
 If the :yaml:`format` option is used, its value will be automatically migrated to :yaml:`addHtmlPart`:
 
@@ -29,7 +31,7 @@ The :yaml:`format` option will no longer work in TYPO3 11.0.
 Affected Installations
 ======================
 
-All installations which use EXT:form and its :php:`EmailFinisher`.
+All installations which use EXT:form and its :php:`TYPO3\CMS\Form\Domain\Finishers\EmailFinisher`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87305-UseConstructorInjectionInDataMapper.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87305-UseConstructorInjectionInDataMapper.rst
similarity index 77%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87305-UseConstructorInjectionInDataMapper.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87305-UseConstructorInjectionInDataMapper.rst
index f98990199685..6182454e82b2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87305-UseConstructorInjectionInDataMapper.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87305-UseConstructorInjectionInDataMapper.rst
@@ -9,13 +9,14 @@ See :issue:`87305`
 Description
 ===========
 
-The 8th argument (:php:`\TYPO3\CMS\Extbase\Persistence\QueryInterface`) of method :php:`\TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper->__construct` has been marked deprecated.
+The 8th argument (:php:`\TYPO3\CMS\Extbase\Persistence\QueryInterface`) of method
+:php:`\TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper->__construct` has been marked as deprecated.
 
 
 Impact
 ======
 
-Instantiating objects along with that argument will trigger a deprecation warning.
+Instantiating objects along with that argument will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst
similarity index 63%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst
index 9b29faacec63..3644d8f51496 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87332-AvoidRuntimeReflectionCallsInObjectAccess.rst
@@ -9,9 +9,16 @@ See :issue:`87332`
 Description
 ===========
 
-1) Class :php:`\TYPO3\CMS\Extbase\Reflection\ObjectAccess` uses reflection to make non public properties gettable and settable. This behaviour is triggered by setting the argument :php:`$forceDirectAccess` of methods :php:`getProperty`, :php:`getPropertyInternal` or :php:`setProperty` to :php:`true`. Triggering this behaviour is deprecated and will be removed in TYPO3 11.0.
+Class :php:`\TYPO3\CMS\Extbase\Reflection\ObjectAccess` uses reflection to make non public properties gettable and settable.
+This behaviour is triggered by setting the argument :php:`$forceDirectAccess` of methods
 
-2) Method :php:`\TYPO3\CMS\Extbase\Reflection\ObjectAccess::buildSetterMethodName` has been deprecated and will be removed in TYPO3 11.0.
+* :php:`getProperty`
+* :php:`getPropertyInternal`
+* :php:`setProperty`
+
+to :php:`true`. Triggering this behaviour has been marked as deprecated and will be removed in TYPO3 11.0.
+
+Method :php:`\TYPO3\CMS\Extbase\Reflection\ObjectAccess::buildSetterMethodName` has been marked as deprecated and will be removed in TYPO3 11.0.
 
 
 Impact
@@ -33,7 +40,8 @@ Affected Installations
 Migration
 =========
 
-1) Make sure the affected property is accessible by either making it public or providing getters/hassers/issers or setters (:php:`getProperty()`, :php:`hasProperty()`, :php:`isProperty()`, :php:`setProperty()`).
+1) Make sure the affected property is accessible by either making it public or providing getters/hassers/issers or setters
+(:php:`getProperty()`, :php:`hasProperty()`, :php:`isProperty()`, :php:`setProperty()`).
 
 2) Build setter names manually: :php:`$setterMethodName = 'set' . ucfirst($propertyName);`
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst
similarity index 70%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst
index 2c005b40ba26..94085175f65a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87550-UseControllerClassesWhenRegisteringPluginsmodules.rst
@@ -11,19 +11,20 @@ Description
 
 Configuring plugins and modules via the following methods has changed in two important ways.
 
-- :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`
-- :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule`
+* :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`
+* :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule`
 
 Both methods expect you to provide the argument :php:`$extensionName` and :php:`$controllerActions`.
 :php:`configurePlugin` also allows the argument :php:`$nonCacheableControllerActions`.
 
 The first important change targets the :php:`$extensionName` argument.
-During the switch from underscore class names :php`Tx_Extbase_Foo_Bar` to actual namespaced classes
+During the switch from underscore class names :php:`Tx_Extbase_Foo_Bar` to actual namespaced classes
 :php:`TYPO3\CMS\Extbase\Foo\Bar`, a vendor `TYPO3\CMS` has been introduced which had to be respected
 during the configuration of plugins. To make that possible the argument :php:`$extensionName` has been
 prepended with the vendor name, concatenated with dots.
 
-::
+.. code-block:: php
+
    <?php
 
    \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
@@ -37,14 +38,15 @@ prepended with the vendor name, concatenated with dots.
 Setting the vendor name is now deprecated and must be omitted. Instead, the vendor name will be derived
 from the controller class namespace, which leads to the second important change.
 
-Both arguments :php:`$controllerActions` and `$nonCacheableControllerActions` used controller aliases as
-array keys. The alias was the controller class name without the namespace and without the `Controller`
-suffix. There were a lot of conventions and a quite stupid custom autoloader mechanism before the introduction
+Both arguments :php:`$controllerActions` and :php:`$nonCacheableControllerActions` used controller aliases as
+array keys. The alias was the controller class name without the namespace and without the :php:`Controller`
+suffix. There were a lot of conventions and a custom autoloader mechanism before the introduction
 of the composer autoloader, which made it necessary to put controllers in a specific directory and to name
 the controller accordingly. As this is no longer the case, there is no need to guess the controller class name
 any longer. Instead, the configuration/registration is now done with fully qualified controller class names.
 
-::
+.. code-block:: php
+
    <?php
 
    \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
@@ -58,16 +60,16 @@ any longer. Instead, the configuration/registration is now done with fully quali
 Conclusion
 ==========
 
-The following things are deprecated:
+The following things have been marked as deprecated:
 
-- Prepend the :php:`$extensionName` argument with a vendor name.
-- Using controller aliases as array keys in both arguments :php:`$controllerActions` and :php:`$nonCacheableControllerActions`.
+* Prepend the :php:`$extensionName` argument with a vendor name.
+* Using controller aliases as array keys in both arguments :php:`$controllerActions` and :php:`$nonCacheableControllerActions`.
 
 
 Impact
 ======
 
-Using the deprecated syntax will log deprecation warnings and will stop working in TYPO3 11.0.
+Using the deprecated syntax will trigger PHP :php:`E_USER_DEPRECATED` errors and will stop working in TYPO3 11.0.
 
 
 Affected Installations
@@ -75,14 +77,14 @@ Affected Installations
 
 All installations that use these methods:
 
-- :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`
-- :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule`
+* :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin`
+* :php:`\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule`
 
 
 Migration
 =========
 
-- Omit the vendor name in argument :php:`$extensionName`
-- Use fully qualified class names as array keys in arguments :php:`$controllerActions` and :php:`$nonCacheableControllerActions`
+* Omit the vendor name in argument :php:`$extensionName`
+* Use fully qualified class names as array keys in arguments :php:`$controllerActions` and :php:`$nonCacheableControllerActions`
 
 .. index:: PHP-API, PartiallyScanned, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst
similarity index 83%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst
index d100fdb28515..61af1cea65a7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87613-DeprecateTYPO3CMSExtbaseUtilityTypeHandlingUtilityhex2bin.rst
@@ -9,19 +9,19 @@ See :issue:`87613`
 Description
 ===========
 
-:php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin` has been deprecated and will be removed in TYPO3 11.0.
+:php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin` has been marked as deprecated and will be removed in TYPO3 11.0.
 
 
 Impact
 ======
 
-Calling :php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin` will trigger a deprecation log entry.
+Calling :php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin` will trigger PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
 ======================
 
-All installations that call :php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin`
+All installations that call :php:`\TYPO3\CMS\Extbase\Utility\TypeHandlingUtility::hex2bin`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87882-FileRelatedControllersMovedToEXTfilelist.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87882-FileRelatedControllersMovedToEXTfilelist.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87882-FileRelatedControllersMovedToEXTfilelist.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87882-FileRelatedControllersMovedToEXTfilelist.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87894-GeneralUtilityidnaEncode.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87894-GeneralUtilityidnaEncode.rst
similarity index 82%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-87894-GeneralUtilityidnaEncode.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87894-GeneralUtilityidnaEncode.rst
index 12c9b9e228ef..f602ffbcd84a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87894-GeneralUtilityidnaEncode.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-87894-GeneralUtilityidnaEncode.rst
@@ -18,7 +18,7 @@ For this reason the method :php:`GeneralUtility::idnaEncode()` has been marked a
 Impact
 ======
 
-Calling :php:`GeneralUtility::idnaEncode()` directly will trigger a deprecation message.
+Calling :php:`GeneralUtility::idnaEncode()` directly will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
@@ -32,7 +32,7 @@ Migration
 
 Use :php:`idn_to_ascii($domain, IDNA_DEFAULT, INTL_IDNA_VARIANT_UTS46);` instead.
 
-Please be aware that in contrary to :php:`GeneralUtility::idnaEncode()` the native PHP function only works on domain names, not email addresses or
+Please be aware that contrary to :php:`GeneralUtility::idnaEncode()` the native PHP function only works on domain names, not email addresses or
 similar. In order to encode email addresses split the address at the last :php:`'@'` and use :php:`idn_to_ascii()` on that last part.
 Also, if there is an error in converting a string, a bool :php:`false` is returned.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst
similarity index 63%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst
index 8b4c3233f941..c09e2cbb8ad7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88366-DefaultCachingFrameworkCacheNamesChanged.rst
@@ -17,37 +17,37 @@ Framework was introduced.
 
 The following caches have been renamed:
 
-- cache_core => core
-- cache_hash => hash
-- cache_pages => pages
-- cache_pagesection => pagesection
-- cache_runtime => runtime
-- cache_rootline => rootline
-- cache_imagesizes => imagesizes
+* `cache_core` => `core`
+* `cache_hash` => `hash`
+* `cache_pages` => `pages`
+* `cache_pagesection` => `pagesection`
+* `cache_runtime` => `runtime`
+* `cache_rootline` => `rootline`
+* `cache_imagesizes` => `imagesizes`
 
 The caches should now be accessed via :php:`$cacheManager->getCache('core')` instead of
-:php:`$cacheManager->getCache('cache_core')` - without the "cache_" prefix.
+:php:`$cacheManager->getCache('cache_core')` - without the ``cache_`` prefix.
 
-In addition, when the DatabaseBackend cache is used, the database tables do not have the `cf_`
+In addition, when the DatabaseBackend cache is used, the database tables do not have the :sql:`cf_`
 prefix anymore, making it clearer for integrators and developers what the caches mean.
 
 
 Impact
 ======
 
-When accessing the cache with a "cache" prefix, a deprecation message is thrown.
+When accessing the cache with a "cache" prefix, a PHP :php:`E_USER_DEPRECATED` error is triggered.
 
 
 Affected Installations
 ======================
 
-Any TYPO3 extension using the caching framework with the "cache_" prefix.
+Any TYPO3 extension using the caching framework with the ``cache_`` prefix.
 
 
 Migration
 =========
 
-Remove the "cache_" prefix from the callers code.
+Remove the ``cache_`` prefix from the callers code.
 
 In addition, run through the Database Table Analyzer of the Configuration module to
 re-create any database tables of the Caching Framework.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst
similarity index 55%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst
index 4c735cc2fcfc..1f10ab5d6e0e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88406-SetCacheHashnoCacheHashOptionsInViewHelpersAndUriBuilder.rst
@@ -9,35 +9,39 @@ See :issue:`88406`
 Description
 ===========
 
-Various Fluid ViewHelpers regarding linking have arguments similar to which are not evaluated anymore:
-- useCacheHash
-- noCacheHash
+Various Fluid ViewHelpers regarding linking have arguments similar to:
+
+* :php:`useCacheHash`
+* :php:`noCacheHash`
+
+which are not evaluated anymore.
 
 Extbase's UriBuilder has the following options that have no effect anymore since the Site
-Handling concept automatically detects when to a cHash argument is necessary.
+Handling concept automatically detects when to a cHash argument is necessary:
 
-- UriBuilder->setUseCacheHash()
-- UriBuilder->getUseCacheHash()
+* :php:`TYPO3\CMS\Extbase\Mvc\Web\Routing\UriBuilder->setUseCacheHash()`
+* :php:`TYPO3\CMS\Extbase\Mvc\Web\Routing\UriBuilder->getUseCacheHash()`
 
 Impact
 ======
 
-Calling the UriBuilder methods will trigger a deprecation message.
-
-Using the arguments noCacheHash/useCacheHash in the following ViewHelpers will
-trigger a deprecation message:
-- f:form
-- f:link.action
-- f:link.page
-- f:link.typolink
-- f:uri.action
-- f:uri.page
-- f:uri.typolink
-- f:widget.link
-- f:widget.uri
-
-If the underlying TypoLink logic is accessed directly, it will trigger a deprecation message
-if `.useCacheHash` is set - without any effect either.
+Calling the UriBuilder methods will trigger a PHP :php:`E_USER_DEPRECATED` error.
+
+Using the arguments :php:`noCacheHash`/:php:`useCacheHash` in the following ViewHelpers will
+trigger a PHP :php:`E_USER_DEPRECATED` error:
+
+* :html:`f:form`
+* :html:`f:link.action`
+* :html:`f:link.page`
+* :html:`f:link.typolink`
+* :html:`f:uri.action`
+* :html:`f:uri.page`
+* :html:`f:uri.typolink`
+* :html:`f:widget.link`
+* :html:`f:widget.uri`
+
+If the underlying TypoLink logic is accessed directly, it will trigger a PHP :php:`E_USER_DEPRECATED` error
+if :typoscript:`.useCacheHash` is set - without any effect either.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88428-ToprawurlencodeAndTopstr_replace.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88428-ToprawurlencodeAndTopstr_replace.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88428-ToprawurlencodeAndTopstr_replace.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88428-ToprawurlencodeAndTopstr_replace.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst
index b2b2f169e2e2..41d3ccd073b7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88432-ReplacedMd5jsWithAnAMDModule.rst
@@ -9,7 +9,7 @@ See :issue:`88432`
 Description
 ===========
 
-The file :file:`md5.js` used to generate a MD5 hash in JavaScript is deprecated and replaced by an AMD module
+The file :file:`md5.js` used to generate a MD5 hash in JavaScript has been marked as deprecated and replaced by an AMD module
 :js:`TYPO3/CMS/Backend/Hashing/Md5`.
 
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88433-DeprecateTopopenUrlInWindow.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88433-DeprecateTopopenUrlInWindow.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88433-DeprecateTopopenUrlInWindow.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88433-DeprecateTopopenUrlInWindow.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst
similarity index 88%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst
index b94c28beab2d..9c71c43d8e00 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88473-TypoScriptFrontendController-settingLocale.rst
@@ -10,7 +10,7 @@ Description
 ===========
 
 Due to Site Handling, setting the locale information (:php:`setlocale`) can be handled
-much earlier without any dependencies on the global TSFE object.
+much earlier without any dependencies on the global :php:`TSFE` object.
 
 The functionality of the method :php:`TypoScriptFrontendController->settingLocale()` has
 been moved into :php:`Locales::setSystemLocaleFromSiteLanguage()`. The former method
@@ -27,7 +27,7 @@ Affected Installations
 ======================
 
 Any TYPO3 installation with a third party extension booting up a custom Frontend system and
-explicitly call the method above.
+explicitly calling the method.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88499-BackendUtilitygetViewDomain.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88499-BackendUtilitygetViewDomain.rst
similarity index 76%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88499-BackendUtilitygetViewDomain.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88499-BackendUtilitygetViewDomain.rst
index 25beafa7a2b0..08a85588cc2d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88499-BackendUtilitygetViewDomain.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88499-BackendUtilitygetViewDomain.rst
@@ -13,14 +13,14 @@ The static method :php:`TYPO3\CMS\Backend\Utility\BackendUtility::getViewDomain(
 as deprecated, as it has been superseded by directly using the PageRouter of Site Handling.
 
 Site Handling allows to generate proper frontend preview URLs the same way as TYPO3 Core does in
-all other places,by calling the PageRouter of a Site object directly, so the workarounds are not
+all other places, by calling the PageRouter of a Site object directly, so the workarounds are not
 necessary anymore, making this method obsolete.
 
 
 Impact
 ======
 
-Calling :php:`BackendUtility::getViewDomain()` will trigger a deprecation warning.
+Calling :php:`BackendUtility::getViewDomain()` will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
@@ -33,11 +33,11 @@ Migration
 =========
 
 Substitute the method by directly detecting a site based on a given Page ID in the TYPO3 Backend.
-Call the `getRouter()` method on this Site object to create proper links to pages in TYPO3 Frontend.
+Call the :php:`getRouter()` method on this Site object to create proper links to pages in TYPO3 Frontend.
 
 Example with additional GET parameters:
 
-:php:
+.. code-block:: php
 
     $site = GeneralUtility::makeInstance(SiteFinder::class)->getSiteByPageId($pageId);
     $url = $site->getRouter()->generateUri($pageId, ['type' => 13]);
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst
index a4e263035759..771da62fd20e 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88554-DeprecatedMethodsInVersionNumberUtility.rst
@@ -9,19 +9,19 @@ See :issue:`88554`
 Description
 ===========
 
-The following methods of :php:\TYPO3\CMS\Core\Utility\VersionNumberUtility` have been deprecated and will be removed in
+The following methods of :php:`\TYPO3\CMS\Core\Utility\VersionNumberUtility` have been marked as deprecated and will be removed in
 TYPO3 11.0:
 
-- :php:`convertIntegerToVersionNumber`
-- :php:`splitVersionRange`
-- :php:`raiseVersionNumber`
+* :php:`convertIntegerToVersionNumber`
+* :php:`splitVersionRange`
+* :php:`raiseVersionNumber`
 
 
 Impact
 ======
 
 Calling the methods :php:`convertIntegerToVersionNumber`, :php:`splitVersionRange` or :php:`raiseVersionNumber` of
-:php:\TYPO3\CMS\Core\Utility\VersionNumberUtility` will trigger a deprecation message.
+:php:\TYPO3\CMS\Core\Utility\VersionNumberUtility` will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88559-TSFE-sys_language_isocode.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88559-TSFE-sys_language_isocode.rst
similarity index 73%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88559-TSFE-sys_language_isocode.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88559-TSFE-sys_language_isocode.rst
index 809dfcdf94e3..ede77c839bc2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88559-TSFE-sys_language_isocode.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88559-TSFE-sys_language_isocode.rst
@@ -10,26 +10,26 @@ Description
 ===========
 
 The public property :php:`TypoScriptFrontendController->sys_language_isocode`
-has set the equivalent of `SiteLanguage->getTwoLetterIsoCode()` since the introduction
+has set the equivalent of :php:`TYPO3\CMS\Core\Site\Entity\SiteLanguage->getTwoLetterIsoCode()` since the introduction
 of Site Handling in TYPO3 v9.
 
 As all code should switch to Site Handling, this property can be accessed via
 the current site language as well, making this property obsolete.
 
-The property has been deprecated.
+The property has been marked as deprecated.
 
 
 Impact
 ======
 
-Setting or fetching this property will trigger a PHP deprecation warning.
+Setting or fetching this property will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
 ======================
 
 Any TYPO3 installation with a third party extension accessing this property,
-or via TypoScript getData() :ts:`TSFE:sys_language_isocode`.
+or via TypoScript :ts:`TSFE:sys_language_isocode`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88567-GLOBALS_LOCAL_LANG.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88567-GLOBALS_LOCAL_LANG.rst
similarity index 75%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88567-GLOBALS_LOCAL_LANG.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88567-GLOBALS_LOCAL_LANG.rst
index c881c8d86061..ca8d94f6d0c7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88567-GLOBALS_LOCAL_LANG.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88567-GLOBALS_LOCAL_LANG.rst
@@ -15,22 +15,21 @@ scope, it is more feasible to have it scoped to the actual :php:`LanguageService
 that loaded this data, in order to allow various language functionality in the
 same PHP process without having to deal with global variables.
 
-For this reason, it is discouraged to use the :php:`$GLOBALS['LOCAL_LANG']`
+For this reason, it is discouraged to use :php:`$GLOBALS['LOCAL_LANG']`
 but instead rely on :php:`LanguageService->includeLLfile()` which returns
 the actual values as well, but only the ones loaded from this instance.
 
-Since LanguageService is usually available via `$GLOBALS['LANG']` the
+Since an instance of :php:`TYPO3\CMS\Core\Localization\LanguageService` is usually available via `$GLOBALS['LANG']` the
 labels are accessible within PHP anyways.
 
-Due to this change, the second and third arguments of
-:php:`LanguageService->includeLLFile()` have been deprecated.
+Due to this change, the second and third arguments of :php:`LanguageService->includeLLFile()` have been marked as deprecated.
 
 
 Impact
 ======
 
 Calling the method above with an explicit second and/or third argument will
-trigger a PHP deprecation warning.
+trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
new file mode 100644
index 000000000000..0392feaadae0
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
@@ -0,0 +1,39 @@
+.. include:: ../../Includes.txt
+
+==================================================================================
+Deprecation: #88569 - Locales::initialize() in favor of regular singleton instance
+==================================================================================
+
+See :issue:`88569`
+
+Description
+===========
+
+The method :php:`TYPO3\CMS\Core\Localization\Locales::initialize()` has been marked as deprecated.
+It was a workaround to re-initialize the Singleton Instance of the PHP class :php:`Locales` for user-defined locales, which were
+loaded by an extensions' :file:`ext_localconf.php`.
+
+:php:`Locales` is now initialized only when needed, and not during the early bootstrap process,
+making this functionality obsolete, as this is taken care of within the regular constructor.
+
+
+Impact
+======
+
+Calling :php:`TYPO3\CMS\Core\Localization\Locales::initialize()` will trigger a PHP :php:`E_USER_DEPRECATED` error.
+
+
+Affected Installations
+======================
+
+Any TYPO3 installation with a third-party extension calling :php:`Locales::initialize()` directly.
+
+
+Migration
+=========
+
+Replace the function call by a regular :php:`GeneralUtility::makeInstance(Locales::class);`
+or use Dependency Injection (Constructor Injection or ObjectManager) to fetch an instance of
+the :php:`Locales` class.
+
+.. index:: PHP-API, FullyScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88651-ReplaceTYPO3CMSBackendSplitButtonsWithTYPO3CMSBackendDocumentSaveActions.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88651-ReplaceTYPO3CMSBackendSplitButtonsWithTYPO3CMSBackendDocumentSaveActions.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88651-ReplaceTYPO3CMSBackendSplitButtonsWithTYPO3CMSBackendDocumentSaveActions.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88651-ReplaceTYPO3CMSBackendSplitButtonsWithTYPO3CMSBackendDocumentSaveActions.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst
index 409f13e18b52..836c7aac5a9c 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88662-DeprecatedBackendRouteXMOD_tximpexp.rst
@@ -17,7 +17,7 @@ either the export or the import process, controlled by a query parameter.
 Impact
 ======
 
-Calling the route will render a deprecation notice.
+Calling the route will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst
similarity index 86%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst
index 6aab7f61f75c..d9123459c831 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88746-PageRepositoryPHPClassMovedFromFrontendToCoreExtension.rst
@@ -16,12 +16,12 @@ at all.
 
 In addition, various places of the backend also used PageRepository already, which violated the
 separation of packages, as TYPO3 Core aims to strictly separate Frontend and Backend application
-coe.
+code.
 
 In the case of PageRepository, the code is used by both applications, and is therefore moved
-to Core system extension (EXT:core), and renamed to `TYPO3\CMS\Core\Domain\Repository\PageRepository`.
+to Core system extension (EXT:core), and renamed to :php:`TYPO3\CMS\Core\Domain\Repository\PageRepository`.
 
-Until TYPO3 v9, it was placed in `TYPO3\CMS\Frontend\Page\PageRepository`.
+Until TYPO3 v9, it was placed in :php:`TYPO3\CMS\Frontend\Page\PageRepository`.
 
 In addition, all interface'd hooks are moved to EXT:core as well with the same PHP namespace.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst
similarity index 50%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst
index 9b937f27ac86..63e0545b44f9 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst
@@ -1,27 +1,31 @@
 .. include:: ../../Includes.txt
 
-==========================================================================================
-Deprecation: #88792 - forceTemplateParsing in TSFE and TemplateService has been deprecated
-==========================================================================================
+======================================================================
+Deprecation: #88792 - forceTemplateParsing in TSFE and TemplateService
+======================================================================
 
 See :issue:`88792`
 
 Description
 ===========
 
-The setting `forceTemplateParsing` in `TypoScriptFrontendController` as well as an `TemplateService` has been deprecated and replaced by Context API.
+* :php:`TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::forceTemplateParsing` and
+* :php:`TYPO3\CMS\Core\TypoScript\TemplateService::forceTemplateParsing`
+
+have been marked as deprecated and replaced by Context API.
 
 
 Impact
 ======
 
-Setting either `forceTemplateParsing` of `TypoScriptFrontendController` or `TemplateService` will result in a deprecation notice.
+Setting either :php:`forceTemplateParsing` of :php:`TypoScriptFrontendController` or :php:`TemplateService`
+will trigger a PHP :php:`E_USER_DEPRECATED` error.
 
 
 Affected Installations
 ======================
 
-All installations setting or reading `$TSFE->forceTemplateParsing` or `TemplateService->forceTemplateParsing`.
+All installations setting or reading :php:`$TSFE->forceTemplateParsing` or :php:`TemplateService->forceTemplateParsing`.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88807-AdminPanelInitializableInterfaceHasBeenDeprecated.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88807-AdminPanelInitializableInterfaceHasBeenDeprecated.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Deprecation-88807-AdminPanelInitializableInterfaceHasBeenDeprecated.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Deprecation-88807-AdminPanelInitializableInterfaceHasBeenDeprecated.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-21638-IntroducedIpLockingForIpv6.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-21638-IntroducedIpLockingForIpv6.rst
similarity index 97%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-21638-IntroducedIpLockingForIpv6.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-21638-IntroducedIpLockingForIpv6.rst
index e1a53b45eb8e..cdcb6230d264 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-21638-IntroducedIpLockingForIpv6.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-21638-IntroducedIpLockingForIpv6.rst
@@ -14,7 +14,7 @@ This security feature enables binding of a user session (Backend or Frontend) to
 
 The available configuration options with their default values for IP-locking are:
 
-.. code-block:: typoscript
+.. code-block:: php
 
    $GLOBALS['TYPO3_CONF_VARS']['FE']['lockIP'] = 2;
    $GLOBALS['TYPO3_CONF_VARS']['FE']['lockIPv6'] = 2;
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst
similarity index 81%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst
index b2343aa7ae81..730bd1efb1dd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-56213-AllowSortingFilelistByFileMetadataTitle.rst
@@ -12,14 +12,14 @@ Description
 The possibility to sort files by their meta data title in the "File Links" content element has been introduced.
 The title attribute is part of the base metadata table and therefor available in all TYPO3 installations.
 
-If you need further FAL fields to sort by, extend the TCA of tt_content field `filelink_sorting` and add
+If you need further FAL fields to sort by, extend the TCA of tt_content field :php:`filelink_sorting` and add
 metadata fields as options to choose from.
 
 For example add the following in :file:`TCA/Overrides/tt_content.php`::
 
    $GLOBALS['TCA']['tt_content']['columns']['filelink_sorting']['config']['items'][] = ['Sort by alternative Text', 'alternative'];
 
-Or use Page TSConfig `TCEFORM.tt_content.filelink_sorting.addItems.alternative = sort by "Alternative" metadata field`.
+Or use Page TSConfig :typoscript:`TCEFORM.tt_content.filelink_sorting.addItems.alternative = sort by "Alternative" metadata field`.
 
 
 Impact
@@ -28,4 +28,4 @@ Impact
 The filelinks content element has a new option for sorting "by file metadata title" which can be chosen in
 the drop down when creating the element.
 
-.. index:: Frontend, ext:frontend
+.. index:: Backend, TCA, ext:frontend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-78432-AddLogMessageForSwitchUserAction.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-78432-AddLogMessageForSwitchUserAction.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-78432-AddLogMessageForSwitchUserAction.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-78432-AddLogMessageForSwitchUserAction.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-80420-AllowMultipleRecipientsInEmailFinisher.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-80420-AllowMultipleRecipientsInEmailFinisher.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-80420-AllowMultipleRecipientsInEmailFinisher.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-80420-AllowMultipleRecipientsInEmailFinisher.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-83734-AddSupportForCurrentPageInConfigcache.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-83734-AddSupportForCurrentPageInConfigcache.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-83734-AddSupportForCurrentPageInConfigcache.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-83734-AddSupportForCurrentPageInConfigcache.rst
index d7f4223a5335..f7045f6fdedd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-83734-AddSupportForCurrentPageInConfigcache.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-83734-AddSupportForCurrentPageInConfigcache.rst
@@ -9,7 +9,7 @@ See :issue:`83734`
 Description
 ===========
 
-When using the TypoScript property `config.cache`, it is possible to define a configuration that
+When using the TypoScript property :ts:`config.cache`, it is possible to define a configuration that
 affects all pages via:
 
 .. code-block:: typoscript
@@ -24,13 +24,13 @@ Thus, the syntax with the keyword "current" is now possible:
 
    config.cache.all = fe_users:current
 
-where `current` is dynamically replaced by the current Page ID.
+where :ts:`current` is dynamically replaced by the current Page ID.
 
 
 Impact
 ======
 
-When using `current` inside the :php:`config.cache` TypoScript property, it is now replaced with
+When using :ts:`current` inside the :ts:`config.cache` TypoScript property, it is now replaced with
 the current Page ID.
 
 .. index:: TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst
similarity index 92%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst
index 6f8fcbe32913..f36ecc7470b7 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-84112-SymfonyDependencyInjectionForCoreAndExtbase.rst
@@ -14,7 +14,7 @@ to manage system wide dependency management and injection for classes.
 With the integration provided in TYPO3 the symfony dependency injection container
 features support for Extbase and non-Extbase classes and is thus intended to
 replace the Extbase dependency injection container and object manager.
-The symfony container implements :php:`\Psr\Conteiner\ContainerInterface`
+The symfony container implements :php:`\Psr\Container\ContainerInterface`
 as specified by PSR-11. This interface should be used when requiring access
 to the container.
 Therefore :php:`\TYPO3\CMS\Extbase\Object\ObjectManager` now resorts to this
@@ -25,7 +25,7 @@ to retrieve instances from the container, if possible.
 
 Classes should be adapted to avoid both, :php:`ObjectManager` and
 :php:`GeneralUtility::makeInstance()` whenever possible.
-Service dependencies should be injected via custructor injection or
+Service dependencies should be injected via constructor injection or
 setter methods (inject methods as in Extbase are supported).
 
 Configuration
@@ -63,27 +63,27 @@ reflects the current feature set of Extbase DI. The configuration looks like:
         resource: '../Classes/*'
 
 Extensions which have used Extbase dependency injection in the past, will want
-to enable `autowire` for a smooth migration. `autowire: true` instructs symfony
+to enable :yaml:`autowire` for a smooth migration. :yaml:`autowire: true` instructs symfony
 to calculate the required dependencies from type declarations of the constructor
 and inject methods. This calculation yields to a service initialization recipe
 which is cached in php code (in TYPO3 core cache).
 Note: An extension doesn't need to use autowiring, it is free to manually
 wire dependencies in the service configuration file.
 
-It is suggested to enable `autoconfigure: true` as this will automatically
+It is suggested to enable :yaml:`autoconfigure: true` as this will automatically
 add symfony service tags based on implemented interfaces or base classes.
 An Example: autoconfiguration ensured that classes which implement
 :php:`\TYPO3\CMS\Core\SingletonInterface` will be publicly available from the
 symfony container (which is required for legacy singleton lookups through
 :php:`\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance()`).
 
-`public: false` is a performance optimization and is therefore suggested to be
+:yaml:`public: false` is a performance optimization and is therefore suggested to be
 enabled in extensions (symfony does not enable this by default for backwards
 compatibility reasons only). This settings controls which services are available
-through `\Psr\Container\ContainerInterface->get()`. Services that need to be public
+through :php:`\Psr\Container\ContainerInterface->get()`. Services that need to be public
 (e.g. Singletons, because they need to be shared with legacy code that uses
 :php:`\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance()`, or Extbase controllers)
-will be marked public automatically due to `autoconfigure: true` by custom
+will be marked public automatically due to :yaml:`autoconfigure: true` by custom
 TYPO3 provided symfony compiler passes.
 
 
@@ -200,8 +200,8 @@ Impact
    suffix (which is the default for Extbase).
 
  * Dependency Injection can be added to constructors of existing services
-   without being breaking. `GeneralUtility::makeInstance(ServiceName::class)`
-   will keep working,  as `makeInstance` has been adapted to resort to the
+   without being breaking. :php:`GeneralUtility::makeInstance(ServiceName::class)`
+   will keep working,  as :php:`makeInstance` has been adapted to resort to the
    symfony container.
 
  * Cyclic dependencies are not supported with Symfony DI (Extbase DI did so).
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-84757-DoubleClickInStructureTreeChangesLabel.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-84757-DoubleClickInStructureTreeChangesLabel.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-84757-DoubleClickInStructureTreeChangesLabel.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-84757-DoubleClickInStructureTreeChangesLabel.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst
similarity index 68%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst
index 1c46860708b3..b54d6afe6e92 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-85569-ShowSchedulerInformationsInTheSystemInformationToolbar.rst
@@ -12,13 +12,15 @@ Description
 The system information toolbar now shows useful information about the TYPO3 scheduler system extension.
 
 The following information can be gathered quickly via the toolbar:
-- Warning if the scheduler execution seems not to be configured correctly
-- Important information about the last successfully executed scheduler run
-  - the start date
-  - the start time
-  - the duration (in minutes)
-  - the execution type (automatically/CLI or manually/via backend)
-    - a manual execution highlights the text
+
+Warning if the scheduler execution seems not to be configured correctly
+
+Important information about the last successfully executed scheduler run
+
+* the start date
+* the start time
+* the duration (in minutes)
+* the execution type (automatically/CLI or manually/via backend), a manual execution highlights the text
 
 Impact
 ======
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst
similarity index 72%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst
index 7efc03508cec..f4d944e989ef 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-85607-NewThumbnailViewHelperToRenderThumbnailsDeferred.rst
@@ -11,16 +11,16 @@ Description
 
 A new ViewHelper for the backend to render thumbnails deferred was introduced.
 
-The :php:`\TYPO3\CMS\Backend\ViewHelpers\ThumbnailViewHelper` extends the :php:`ImageViewHelper` and generate the image tag with the special URI.
+The :php:`\TYPO3\CMS\Backend\ViewHelpers\ThumbnailViewHelper` extends the :php:`ImageViewHelper` and generates the image tag with the special URI.
 
 .. code-block:: HTML
 
-	<be:thumbnail image="{file.resource}" maxWidth="{thumbnail.width}" maxHeight="{thumbnail.height}" />
+    <be:thumbnail image="{file.resource}" maxWidth="{thumbnail.width}" maxHeight="{thumbnail.height}" />
 
 
 Impact
 ======
 
-Thumbnails do not block the rendering of a page, because the processing runs an extra http process.
+Thumbnails do not block the rendering of a page, because the processing runs an extra http request.
 
 .. index:: Backend, Fluid, ext:backend
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-86629-ImplementLinkHandlerForTelephoneNumbers.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-86629-ImplementLinkHandlerForTelephoneNumbers.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-86629-ImplementLinkHandlerForTelephoneNumbers.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-86629-ImplementLinkHandlerForTelephoneNumbers.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Feature-86964-AllowGettingClassPropertyDefaultValue.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
new file mode 100644
index 000000000000..0c3130bb3064
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
@@ -0,0 +1,27 @@
+.. include:: ../../Includes.txt
+
+============================================================
+Feature: #86964 - Allow getting class property default value
+============================================================
+
+See :issue:`86964`
+
+Description
+===========
+
+It is now possible to get the default value of a class property when using the :php:`TYPO3\CMS\Extbase\Reflection\ReflectionService`.
+
+.. code-block:: php
+
+    class MyClass
+    {
+        public $myProperty = 'foo';
+    }
+
+    $property = GeneralUtility::makeInstance(\TYPO3\CMS\Extbase\Reflection\ReflectionService::class)
+        ->getClassSchema(MyClass::class)
+        ->getProperty('myProperty');
+
+    $defaultValue = $property->getDefaultValue(); // "foo"
+
+.. index:: PHP-API, ext:extbase
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst
similarity index 80%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst
index 47c6b6a516df..b5f45733360d 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87200-SendPlaintextAndHTMLMailsInEmailFinisher.rst
@@ -9,7 +9,8 @@ See :issue:`87200`
 Description
 ===========
 
-The :php:`EmailFinisher` of EXT:form now sends mails with a plaintext and an HTML part. A new option :yaml:`addHtmlPart` has been added to configure if a HTML part should be added to mails.
+The :php:`EmailFinisher` of EXT:form now sends mails with a plaintext and an HTML part.
+A new option :yaml:`addHtmlPart` has been added to configure if a HTML part should be added to mails.
 
 
 Impact
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87433-AddChangefreqAndPriority.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87433-AddChangefreqAndPriority.rst
similarity index 69%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-87433-AddChangefreqAndPriority.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-87433-AddChangefreqAndPriority.rst
index 5305c28a4d2a..d559211678cd 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-87433-AddChangefreqAndPriority.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87433-AddChangefreqAndPriority.rst
@@ -1,8 +1,8 @@
 .. include:: ../../Includes.txt
 
-=============================================
-Feature: #87433 - Add changefreq and priority
-=============================================
+=============================================================
+Feature: #87433 - Add changefreq and priority for XML sitemap
+=============================================================
 
 See :issue:`87433`
 
@@ -16,14 +16,14 @@ revisited (for example: News in an archive are "never" updated, while your home
 
 Priority allows you to define how important the page is compared to other pages on your site. The priority is stated
 in a value from 0 to 1. Your most important pages can get an higher priority as other pages. This value does not
-affect how your pages are compared to pages of other websites.
+affect how important your pages are compared to pages of other websites.
 
-This feature allows to define the properties `changefreq` and `priority` for sitemap entries in TYPO3.
+This feature allows to define the properties :ts:`changefreq` and :ts:`priority` for sitemap entries in TYPO3.
 
-The properties `changefreq` and `priority` of pages can be controlled via page properties.
+The properties :ts:`changefreq` and :ts:`priority` of pages can be controlled via page properties.
 For records, the settings can be defined in TypoScript by mapping the properties to fields of the record by
-using the options `changeFreqField` and `priorityField`. `changeFreqField` needs to point to a field containing
-string values (see `pages` definition of field `sitemap_changefreq`), `priorityField` needs to point to a field with
+using the options :ts:`changeFreqField` and :ts:`priorityField`. :ts:`changeFreqField` needs to point to a field containing
+string values (see :ts:`pages` definition of field :ts:`sitemap_changefreq`), :ts:`priorityField` needs to point to a field with
 a decimal value between 0 and 1.
 
 
@@ -66,13 +66,14 @@ Impact
 
 Two new fields are available in the page properties: `sitemap_priority` (decimal) and `sitemap_changefreq` (list of values, for example "weekly", "daily", "never").
 
-Two new TypoScript options for the `RecordsXmlSitemapDataProvider` have been introduced:
-`changeFreqField` and `priorityField`.
+Two new TypoScript options for the :ts:`RecordsXmlSitemapDataProvider` have been introduced:
+:ts:`changeFreqField` and :ts:`priorityField`.
 
 All pages and records get a priority of 0.5 by default.
 
 .. attention::
+
    Both priority and change frequency does have no impact on your rankings. These options only gives hints to search engines
-   in which order and how often you would like a crawler to crawl your pages.
+   in which order and how often you would like a crawler to visit your pages.
 
-.. index:: ext:seo
+.. index:: ext:seo, Frontend, TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87457-UseSymfonyproperty-infoToGatherDocBlockInformation.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87457-UseSymfonyproperty-infoToGatherDocBlockInformation.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-87457-UseSymfonyproperty-infoToGatherDocBlockInformation.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-87457-UseSymfonyproperty-infoToGatherDocBlockInformation.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87665-IntroduceBitSetClass.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87665-IntroduceBitSetClass.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-87665-IntroduceBitSetClass.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-87665-IntroduceBitSetClass.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst
new file mode 100644
index 000000000000..987227e84415
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst
@@ -0,0 +1,38 @@
+.. include:: ../../Includes.txt
+
+==========================================================================
+Feature: #87726 - Extend FrontendLoginController Hook to validate password
+==========================================================================
+
+See :issue:`87726`
+
+Description
+===========
+
+The Hook :php:`$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['felogin']['password_changed']` is extended to validate the given password.
+In the Hook you can set a custom validation message.
+
+
+Impact
+======
+
+You can now use the hook via:
+
+.. code-block:: php
+
+    $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['felogin']['password_changed'][] = \Your\Namespace\Hooks\MyBeautifulHook::class . '->passwordChanged';
+
+Example implementation:
+-----------------------
+
+.. code-block:: php
+
+    public function passwordChanged(array &$params)
+    {
+        if($params['newPasswordUnencrypted']==='password'){
+            $params['passwordValid']=FALSE;
+            $params['passwordInvalidMessage']='<p class="text-danger">Do not use password as password</p>';
+        }
+    }
+
+.. index:: Frontend, ext:felogin, PHP-API
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst
index 416f92d35c6e..a8e7615c4d25 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88643-NewMailAPIBasedOnSymfonymailerAndSymfonymime.rst
@@ -17,12 +17,12 @@ messages.
 
 TYPO3 has replaced swiftmailer with the symfony components.
 
-The new component does not handle the regular PHP function :php:`mail()` which
-has been declared unsafe in various scenarios anymore. Instead, it is recommended
+The new component does not handle the regular PHP function :php:`mail()`, which
+has been declared unsafe in various scenarios, anymore. Instead it is recommended
 to switch to `sendmail` or `smtp`, which can be configured within the TYPO3
 Install Tool or the Settings module for System Maintainers under "Presets" => "Mail".
 
-All existing installations which still have "mail" are migrated to "sendmail"
+All existing installations which still configure ``mail`` are migrated to ``sendmail``
 by automatically detecting the sendmail path by checking PHP.ini settings, but
 should be reviewed on update.
 
@@ -32,7 +32,7 @@ and more flexibility, but is also stricter in validation.
 
 Especially custom extensions using the MailMessage API need to be evaluated,
 as it is not possible anymore to add multiple email addresses as a simple associative
-array but rather a NamedAddress object or a simple Address object from "symfony/mime".
+array but rather a NamedAddress object or a simple Address object from "symfony/mime" is required.
 
 All existing Swiftmailer-based transports which TYPO3 supports natively have been
 replaced by Symfony-based transport APIs.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88648-DefineTwitterCardTypeInPageProperties.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88648-DefineTwitterCardTypeInPageProperties.rst
similarity index 74%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88648-DefineTwitterCardTypeInPageProperties.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88648-DefineTwitterCardTypeInPageProperties.rst
index 83535e946aef..12a1ff6f2875 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88648-DefineTwitterCardTypeInPageProperties.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88648-DefineTwitterCardTypeInPageProperties.rst
@@ -10,12 +10,12 @@ Description
 ===========
 
 It is now possible to select the type of Twitter Card to be shown when a page is shared
-on Twitter. This option will render the `twitter:card` meta tag in frontend.
+on Twitter. This option will render the :html:`twitter:card` meta tag in frontend.
 
 Impact
 ======
 
-If you manually changed the value of the `twitter:card` by for example TypoScript and you
+If you manually changed the value of the :html:`twitter:card` by for example TypoScript and you
 want to override the value of the page properties, you have to use the replace option to
 override this value from the page properties.
 
@@ -31,4 +31,4 @@ Example:
   }
 
 
-.. index:: ext:seo
+.. index:: ext:seo, Frontend, TypoScript
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88770-PSR-14BasedEventDispatcher.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88770-PSR-14BasedEventDispatcher.rst
similarity index 95%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88770-PSR-14BasedEventDispatcher.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88770-PSR-14BasedEventDispatcher.rst
index 5afa9725c232..740017b2bdb3 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88770-PSR-14BasedEventDispatcher.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88770-PSR-14BasedEventDispatcher.rst
@@ -54,7 +54,7 @@ Impact
 
 TYPO3's EventDispatcher serves as the basis to replace all Signal/Slots and hooks in the future,
 however for the time being, hooks and registered Slots work the same way as before, unless migrated
-to an EventDispatcher-like code, whereas a deprecation message can be triggered.
+to an EventDispatcher-like code, whereas a PHP :php:`E_USER_DEPRECATED` error can be triggered.
 
 Some hooks / signal/slots might not be replaced 1:1 to EventDispatcher, but rather superseded with
 a more robust or future-proof API.
@@ -79,7 +79,7 @@ Example:
 
 The tag name `event.listener` identifies that a listener should be registered.
 
-The custom PHP class `MyCompany\MyPackage\EventListener\NullMailer` serves as the listener,
+The custom PHP class :php:`MyCompany\MyPackage\EventListener\NullMailer` serves as the listener,
 whereas the `identifier` is a common name so orderings can be built upon the identifier,
 the optional `before` and `after` attributes allow for custom sorting against `identifier`.
 
@@ -119,7 +119,7 @@ Events provided by a package. Be careful about the context that should be expose
 
 3. Emitters (TYPO3 Core or Extension Authors) should always use Dependency Injection to receive the
 EventDispatcher object as a constructor argument, where possible, by adding a type declaration
-for `Psr\EventDispatcher\EventDispatcherInterface`.
+for :php:`Psr\EventDispatcher\EventDispatcherInterface`.
 
 Any kind of Event provided by TYPO3 Core falls under TYPO3's Core API deprecation policy, except
 for its constructor arguments, which may vary. Events that should only be used within TYPO3 Core,
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88791-IntroducePreviewAspectInContext.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88791-IntroducePreviewAspectInContext.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88791-IntroducePreviewAspectInContext.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88791-IntroducePreviewAspectInContext.rst
index 6fe79d8189fb..c68a06cf6458 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88791-IntroducePreviewAspectInContext.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88791-IntroducePreviewAspectInContext.rst
@@ -22,6 +22,6 @@ The Context API has a new Aspect called "frontend.preview". It can be used to de
    GeneralUtility::makeInstance(Context::class)->getPropertyFromAspect('frontend.preview', 'isPreview');
 
 This Aspect replaces the now deprecated property :php:`TypoScriptFrontendController->fePreview`. Accessing this property
-triggers a PHP deprecation message, and fetches the information from the new Context Aspect instead.
+triggers a PHP :php:`E_USER_DEPRECATED` error, and fetches the information from the new Context Aspect instead.
 
 .. index:: Frontend, PHP-API, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
similarity index 91%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
index 10909cfe3d33..75ea31392140 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88799-IntroducedPSR-3CompatibleLoggingAPI.rst
@@ -20,7 +20,7 @@ also following the standard.
 Impact
 ======
 
-The adaption was not possible with a few breaking changes to the code base.
+The adaption was not possible without a few breaking changes to the code base.
 Luckily no configuration changes are necessary, hence integrators are not affected by those.
 
 .. index:: PHP-API, ext:core
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88807-AdminPanelRequestEnricherInterfaceHasBeenIntroduced.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Feature-88807-AdminPanelRequestEnricherInterfaceHasBeenIntroduced.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Feature-88807-AdminPanelRequestEnricherInterfaceHasBeenIntroduced.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Feature-88807-AdminPanelRequestEnricherInterfaceHasBeenIntroduced.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst
similarity index 93%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst
index 59f962e1cd96..81711e0dd363 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Important-86577-QueryParametersAreNowIncludedInCanonicalizedUrls.rst
@@ -32,7 +32,7 @@ An example:
        'queryParam2',
    ]
 
-This example will add query parameters `queryParam1` and `queryParam2` to the canonicalized
+This example will add query parameters :html:`queryParam1` and :html:`queryParam2` to the canonicalized
 URLs if they are provided.
 
 .. important::
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst
similarity index 65%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst
index 44e51b8e0f22..416dc3fb28c2 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87427-ClassSchemaConstantsMarkedAsPrivate.rst
@@ -9,8 +9,12 @@ See :issue:`87427`
 Description
 ===========
 
-The constants :php:`ClassSchema::MODELTYPE_ENTITY` and :php:`ClassSchema::MODELTYPE_VALUEOBJECT` have been marked as
-private, as they are used in :php:`\TYPO3\CMS\Extbase\Reflection\ClassSchema` only.
+The constants
+
+* :php:`ClassSchema::MODELTYPE_ENTITY` and
+* :php:`ClassSchema::MODELTYPE_VALUEOBJECT`
+
+have been marked as private, as they are used in :php:`\TYPO3\CMS\Extbase\Reflection\ClassSchema` only.
 
 Since this class is marked as internal explicitly, nobody should be affected by this change.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-87516-RemoveCoreHTTPRequestHandlerInterface.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87516-RemoveCoreHTTPRequestHandlerInterface.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-87516-RemoveCoreHTTPRequestHandlerInterface.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-87516-RemoveCoreHTTPRequestHandlerInterface.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-87603-ClassesUseStrictModeAndScarlarTypeHints.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87603-ClassesUseStrictModeAndScarlarTypeHints.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-87603-ClassesUseStrictModeAndScarlarTypeHints.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-87603-ClassesUseStrictModeAndScarlarTypeHints.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-87894-RemovedPHPDependencyAlgo26-matthiasidna-convert.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87894-RemovedPHPDependencyAlgo26-matthiasidna-convert.rst
similarity index 100%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-87894-RemovedPHPDependencyAlgo26-matthiasidna-convert.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-87894-RemovedPHPDependencyAlgo26-matthiasidna-convert.rst
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst
similarity index 94%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst
index 3e1f2ba63625..714c1baf4a8b 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Important-87980-PageIsBeingGeneratedMessageHasBeenRemoved.rst
@@ -27,7 +27,7 @@ or how low the current traffic is.
 The requests only need to (nearly) arrive at the same time.
 
 Note: In case the increased number of waiting requests has a negative
-impact on highly frequented servers, a additional proxy cache should be
+impact on highly frequented servers, an additional proxy cache should be
 considered in front of the server to make sure clients are served a valid
 response without waiting until new content is ready.
 
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst
similarity index 89%
rename from typo3/sysext/core/Documentation/Changelog/master/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst
rename to typo3/sysext/core/Documentation/Changelog/10.0/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst
index 53e23ea5d709..0032d1786d0a 100644
--- a/typo3/sysext/core/Documentation/Changelog/master/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Important-88043-TypeScriptSourcesMovedIntoBuildDirectory.rst
@@ -11,9 +11,10 @@ Description
 
 The TypeScript sources of all system extensions have been moved into the :file:`Build` directory. The former directory
 structure :file:`typo3/sysext/foobar/Resources/Private/TypeScript` has been superseded by the new structure
-`Build/Sources/TypeScript/foobar/Resources/Public/TypeScript`.
+:file:`Build/Sources/TypeScript/foobar/Resources/Public/TypeScript`.
 
 .. note::
+
    Mind that :file:`Public` is now the parent directory of :file:`TypoScript`.
 
 .. index:: JavaScript
diff --git a/typo3/sysext/core/Documentation/Changelog/10.0/Index.rst b/typo3/sysext/core/Documentation/Changelog/10.0/Index.rst
new file mode 100644
index 000000000000..e46216c18fd5
--- /dev/null
+++ b/typo3/sysext/core/Documentation/Changelog/10.0/Index.rst
@@ -0,0 +1,51 @@
+.. include:: ../../Includes.txt
+
+10.0 Changes
+=============
+
+**Table of contents**
+
+.. contents::
+   :local:
+   :depth: 1
+
+
+Breaking Changes
+^^^^^^^^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Breaking-*
+
+Features
+^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Feature-*
+
+Deprecation
+^^^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Deprecation-*
+
+Important
+^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Important-*
diff --git a/typo3/sysext/core/Documentation/Changelog/9.3/Breaking-84680-RemovedUnusedLocallangFilesFromEXTlang.rst b/typo3/sysext/core/Documentation/Changelog/9.3/Breaking-84680-RemovedUnusedLocallangFilesFromEXTlang.rst
index a3441d25569b..ac767c63af37 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.3/Breaking-84680-RemovedUnusedLocallangFilesFromEXTlang.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.3/Breaking-84680-RemovedUnusedLocallangFilesFromEXTlang.rst
@@ -15,29 +15,28 @@ Removed the last unused locallang files from EXT:lang.
 Impact
 ======
 
-Extensions or configuration that uses one of the following locallang files will not show a translation anymore.
+Extensions or configuration that use one of the following locallang files will not show a translation anymore.
 
-.. code-block:: php
 
-    'lang/Resources/Private/Language/locallang_alt_intro.xlf'
-    'lang/Resources/Private/Language/locallang_alt_doc.xlf'
-    'lang/Resources/Private/Language/locallang_login.xlf'
-    'lang/Resources/Private/Language/locallang_common.xlf'
-    'lang/Resources/Private/Language/locallang_core.xlf'
-    'lang/Resources/Private/Language/locallang_general.xlf'
-    'lang/Resources/Private/Language/locallang_misc.xlf'
-    'lang/Resources/Private/Language/locallang_mod_web_list.xlf'
-    'lang/Resources/Private/Language/locallang_tca.xlf'
-    'lang/Resources/Private/Language/locallang_tsfe.xlf'
-    'lang/Resources/Private/Language/locallang_wizards.xlf'
-    'lang/Resources/Private/Language/locallang_browse_links.xlf'
-    'lang/Resources/Private/Language/locallang_tcemain.xlf'
+* :file:`lang/Resources/Private/Language/locallang_alt_intro.xlf`
+* :file:`lang/Resources/Private/Language/locallang_alt_doc.xlf`
+* :file:`lang/Resources/Private/Language/locallang_login.xlf`
+* :file:`lang/Resources/Private/Language/locallang_common.xlf`
+* :file:`lang/Resources/Private/Language/locallang_core.xlf`
+* :file:`lang/Resources/Private/Language/locallang_general.xlf`
+* :file:`lang/Resources/Private/Language/locallang_misc.xlf`
+* :file:`lang/Resources/Private/Language/locallang_mod_web_list.xlf`
+* :file:`lang/Resources/Private/Language/locallang_tca.xlf`
+* :file:`lang/Resources/Private/Language/locallang_tsfe.xlf`
+* :file:`lang/Resources/Private/Language/locallang_wizards.xlf`
+* :file:`lang/Resources/Private/Language/locallang_browse_links.xlf`
+* :file:`lang/Resources/Private/Language/locallang_tcemain.xlf`
 
 
 Affected Installations
 ======================
 
-All extensions or configuration that still uses one of the mentioned locallang files.
+All extensions or configuration that still use any of the mentioned locallang files.
 
 
 Migration
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst b/typo3/sysext/core/Documentation/Changelog/master/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
deleted file mode 100644
index 111d1f15caec..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Breaking-88540-ChangedRequestWorkflowForFrontendRequests.rst
+++ /dev/null
@@ -1,108 +0,0 @@
-.. include:: ../../Includes.txt
-
-=================================================================
-Breaking: #88540 - Changed Request Workflow for Frontend Requests
-=================================================================
-
-See :issue:`88540`
-
-Description
-===========
-
-The "Frontend Request Workflow" is the PHP code responsible for
-setting up various functionality when the TYPO3 Frontend (= rendering of the website)
-is booted and the content is built. This includes Login/Permission Check, resolving
-the current site + language, and checking the page + rootline, then
-parsing TypoScript, which will then lead to building content (or taken from
-cache), until the actual output is returned.
-
-Since TYPO3 v9, this is all built via PSR-15 middlewares, the PSR-15 Request Handler,
-and the global TypoScriptFrontendController (TSFE).
-
-For TYPO3 v10.0, various changes were made in order to separate concerns / logic
-from each other, allowing to easily exchange certain components with
-other / extended functionality.
-
-The following changes have been made:
-
-- Storing session data from a Frontend User Session / Anonymous session is now triggered within the Frontend User
-("frontend-user-authenticator") Middleware, at a later point - once the page was generated. Up until TYPO3 v9, this
-was part of the RequestHandler logic right after content was put together. This was due to legacy reasons of the
-previous hook execution order.
-
-- Resolving the actual site - that is the site configuration plus the language - now happens before Frontend
-and Backend User Authentication. This is important to understand to be able to define further settings within
-Site Handling configuration in the future. Site and Site Language Resolving is now 100% independent of any permission
-settings. Evaluating if a language is active is evaluated separately.
-
-- Backend User Authentication ("$BE_USER") is now started before Frontend User Authentication ("fe_user"), previously
-this was the other way around. Frontend Users are now stored in the request object via the "frontend.user" attribute,
-instead of `$TSFE->fe_user`, until `$TSFE` is instantiated.
-
-- Once all site + permission/authentication functionality has been set up, Routing now tries to detect
-the target page ID and the URL parameters ("PageResolver" middleware) and evaluates the result, so-called
-"Page Arguments" directly afterwards ("PageArgumentValidator" middleware). This effectively validates the cHash
-logic.
-
-- All of the mentioned parts above do not depend on TSFE anymore. In fact, they are 100% independent of
-any TSFE-related code. TSFE is instantiated after all site resolving, authentication, page resolving and argument
-validation is done.
-
-The new request workflow looks like this (simplified):
-
-1. Evaluation of Normalized Parameters (a.k.a. getIndpEnv) & Evaluation of "Maintenance Mode" functionality
-2. Handling registered eID scripts depending on GET parameter `eID`
-3. Resolving Site configuration and Language from URL if possible
-4. Resolving logged-in Backend User Authentication for previewing hidden pages or languages
-5. Authentication of Website Users ("Frontend Users")
-6. Executing various static routes and redirect functionality
-7. Resolving Target Page ID and URL parameters based on Routing, Validation of Page Arguments based on "cHash"
-8. Setting up global $TSFE object, injecting previously resolved settings into TSFE.
-9. Resolving the Rootline for the page
-10. Parsing and Evaluation of TypoScript Instructions to render the page content
-11. Build the content (cached / uncached)
-12. Return the Response (PSR-7) to the base application and output headers + content.
-
-In addition, TypoScriptFrontendController now expects the following constructor arguments:
-
-1. Context API object (previously a copy of $TYPO3_CONF_VARS, until TYPO3 v8, then, unused)
-2. SiteInterface object (previously the Page ID)
-3. SiteLanguage object (previously the Page Type)
-4. PageArguments object (previously the no_cache GET parameter)
-5. FrontendUserAuthentication object (previously the cHash parameter)
-
-Impact
-======
-
-Hooks that depend on certain functionality being made before or after a hook is
-called will likely have a different behavior when:
-
-- A Frontend Session is used within Hooks.
-
-Anything related to regular plugins / content / TypoScript is not affected.
-
-
-Affected Installations
-======================
-
-Any hooks from third party extensions that run
-
-- :php:`$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_fe.php']['hook_eofe']`
-
-and depend on the frontend session data being written.
-
-Any TYPO3 extensions using middlewares in the frontend.
-
-Migration
-=========
-
-Consider using a PSR-15 middleware instead of using a hook, or explicitly call "storeSessionData" within
-the PHP hook if necessary.
-
-If an existing middleware was used, ensure that it's loaded in TYPO3 v10 at the proper location, as the
-`typo3-cms/frontend/tsfe` middleware is loaded at a very late point.
-
-Ensure to use proper objects for the constructor arguments on `TypoScriptFrontendController` when instantiating
-the object on your own.
-
-.. index:: Frontend, PHP-API, NotScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatContants.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatContants.rst
deleted file mode 100644
index e5df1348a6d3..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-87200-EmailFinisherFormatContants.rst
+++ /dev/null
@@ -1,32 +0,0 @@
-.. include:: ../../Includes.txt
-
-=====================================================
-Deprecation: #87200 - EmailFinisher FORMAT_* constants
-=====================================================
-
-See :issue:`87200`
-
-Description
-===========
-
-The constants :php:`EmailFinisher::FORMAT_PLAINTEXT` and :php:`EmailFinisher::FORMAT_HTML` have been deprecated and will be removed in TYPO3 11.0.
-
-
-Impact
-======
-
-Accessing these constants will lead to a fatal error in TYPO3 11.0.
-
-
-Affected Installations
-======================
-
-All installations which use EXT:form and directly access these constants.
-
-
-Migration
-=========
-
-Do not use these constants anymore.
-
-.. index:: PHP-API, FullyScanned, ext:form
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst b/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
deleted file mode 100644
index 998890a27ad7..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Deprecation-88569-LocalesinitializeInFavorOfRegularSingletonInstance.rst
+++ /dev/null
@@ -1,39 +0,0 @@
-.. include:: ../../Includes.txt
-
-==================================================================================
-Deprecation: #88569 - Locales::initialize() in favor of regular singleton instance
-==================================================================================
-
-See :issue:`88569`
-
-Description
-===========
-
-The method :php:`Locales::initialize()` has been deprecated. It was a workaround to re-initialize
-the Singleton Instance of the PHP class `Locales` for user-defined locales, which were
-loaded by an extensions' `ext_localconf.php`.
-
-Locales is now initialized only when needed, and not during the early bootstrap process,
-making this functionality obsolete, as this is taken care of within the regular constructor.
-
-
-Impact
-======
-
-Calling :php:`Locales::initialize()` will trigger a deprecation notice.
-
-
-Affected Installations
-======================
-
-Any TYPO3 installation with a third-party extension calling `Locales::initialize()` directly.
-
-
-Migration
-=========
-
-Replace the function call by a regular :php:`GeneralUtility::makeInstance(Locales::class);` call
-or use Dependency Injection (Constructor Injection or ObjectManager) to fetch an instance of
-the Locales class.
-
-.. index:: PHP-API, FullyScanned
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-86964-AllowGettingClassPropertyDefaultValue.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
deleted file mode 100644
index 16a117caf78a..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-86964-AllowGettingClassPropertyDefaultValue.rst
+++ /dev/null
@@ -1,27 +0,0 @@
-.. include:: ../../Includes.txt
-
-============================================================
-Feature: #86964 - Allow getting class property default value
-============================================================
-
-See :issue:`86964`
-
-Description
-===========
-
-It is now possible to get the default value of a class property when using the ``ReflectionService``.
-
-.. code-block:: php
-
-	class MyClass
-	{
-	    public $myProperty = 'foo';
-	}
-
-	$property = GeneralUtility::makeInstance(\TYPO3\CMS\Extbase\Reflection\ReflectionService::class)
-	    ->getClassSchema(MyClass::class)
-	    ->getProperty('myProperty');
-
-	$defaultValue = $property->getDefaultValue(); // "foo"
-
-.. index:: PHP-API, ext:extbase, NotScanned
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst
deleted file mode 100644
index 0a0f1d9f9a2b..000000000000
--- a/typo3/sysext/core/Documentation/Changelog/master/Feature-87726-ExtendFrontendLoginControllerHookToValidatePassword.rst
+++ /dev/null
@@ -1,36 +0,0 @@
-.. include:: ../../Includes.txt
-
-==========================================================================
-Feature: #87726 - Extend FrontendLoginController Hook to validate password
-==========================================================================
-
-See :issue:`87726`
-
-Description
-===========
-
-The Hook `$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['felogin']['password_changed']` is extended to validate the given password.
-In the Hook you can set a custom validation Message.
-
-
-Impact
-======
-
-You can now use the hook via:
-
-.. code-block:: php
-
-	$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['felogin']['password_changed'][] = \Your\Namespace\Hooks\MyBeautifulHook::class . '->passwordChanged';
-
-Example implementation:
------------------------
-.. code-block:: php
-	public function passwordChanged(array &$params)
-	{
-		if($params['newPasswordUnencrypted']==='password'){
-			$params['passwordValid']=FALSE;
-			$params['passwordInvalidMessage']='<p class="text-danger">Do not use password as password</p>';
-		}
-	}
-
-.. index:: Frontend, ext:felogin, PHP-API
diff --git a/typo3/sysext/core/Documentation/Index.rst b/typo3/sysext/core/Documentation/Index.rst
index 1351baef22f5..caa875974108 100644
--- a/typo3/sysext/core/Documentation/Index.rst
+++ b/typo3/sysext/core/Documentation/Index.rst
@@ -14,6 +14,7 @@ Every change to the TYPO3 Core which might affect your site is documented here.
 
    Sitemap/Index
    Master
+   Changelog-10
    Changelog-9
    Changelog-8
    Changelog-7
diff --git a/typo3/sysext/core/Documentation/Settings.cfg b/typo3/sysext/core/Documentation/Settings.cfg
index 70f35c78d612..9e2ac2c7462f 100644
--- a/typo3/sysext/core/Documentation/Settings.cfg
+++ b/typo3/sysext/core/Documentation/Settings.cfg
@@ -1,8 +1,8 @@
 [general]
 
 project     = TYPO3 CMS Core ChangeLog
-version     = latest (9-dev)
-release     = latest (9-dev)
+version     = latest (10-dev)
+release     = latest (10-dev)
 t3author    = TYPO3 CMS Core Team
 copyright   = 1997-2019
 
diff --git a/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php b/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
index 2a6310e1fcfc..43b81a467ae8 100644
--- a/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
+++ b/typo3/sysext/install/Configuration/ExtensionScanner/Php/PropertyPublicMatcher.php
@@ -596,13 +596,13 @@
     ],
     'TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->forceTemplateParsing' => [
         'restFiles' => [
-            'Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst',
+            'Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst',
             'Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst',
         ],
     ],
     'TYPO3\CMS\Core\TypoScript\TemplateService->forceTemplateParsing' => [
         'restFiles' => [
-            'Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateServiceHasBeenDeprecated.rst',
+            'Deprecation-88792-ForceTemplateParsingInTSFEAndTemplateService.rst',
             'Feature-88792-AddTypoScriptAspectToHandleTypoScriptRenderingContextSettings.rst',
         ],
     ],