[TASK] Apply module renaming (#6234)

* [TASK] Apply module renaming

See https://docs.typo3.org/permalink/changelog:feature-107628-1729026000

Releases: main

* [TASK] Apply module renaming

See https://docs.typo3.org/permalink/changelog:feature-107628-1729026000

Releases: main

* [TASK] Apply module renaming

See https://docs.typo3.org/permalink/changelog:feature-107628-1729026000

Releases: main

* Apply suggestions from code review

Author: linawolf

Documentation/Administration/Deployment/InitialDeployment/Index.rst

@@ -109,7 +109,7 @@ Flush TYPO3 caches:
 
 ..  note::
 
-    You can use the `Admin Tools <https://docs.typo3.org/permalink/t3start:admin-tools>`_
+    You can use the `Install Tools <https://docs.typo3.org/permalink/t3start:admin-tools>`_
     to verify folder permissions and environment compatibility.
     Open: `https://example.org/typo3/install.php` and go to
-    the **System Environment** section.
+    the :guilabel:`System > Environment` module.

Documentation/Administration/DirectoryStructure/ClassicInstallations.rst

@@ -181,7 +181,7 @@ The folder :path:`typo3conf/system/` contains the installation-wide
 :ref:`configuration files <configuration-files>`:
 
 *   :file:`settings.php`: :ref:`Configuration <typo3ConfVars-settings>` written
-    by the :guilabel:`Admin Tools > Settings` backend module
+    by the :guilabel:`System > Settings` backend module
 *   :file:`additional.php`: :ref:`Manually created file <typo3ConfVars-additional>`
     which can override settings from :file:`settings.php` file
 

Documentation/Administration/DirectoryStructure/Index.rst

@@ -85,7 +85,7 @@ The folder :path:`config/system/` contains the installation-wide
 :ref:`configuration files <configuration-files>`:
 
 *   :path:`settings.php`: :ref:`Configuration <typo3ConfVars-settings>` written
-    by the :guilabel:`Admin Tools > Settings` backend module
+    by the :guilabel:`System > Settings` backend module
 *   :file:`additional.php`: :ref:`Manually created file <typo3ConfVars-additional>`
     which can override settings from :file:`settings.php` file
 
@@ -364,10 +364,14 @@ Run the following command to recreate missing directories:
 
 ..  _typo3temp-regeneration-guide-gui:
 
-Admin tools: Directory Status
------------------------------
+Module "Directory Status" in the "Environment" module
+-----------------------------------------------------
 
-Alternatively, a system maintainer can go to :guilabel:`Admin Tools > Environment > Directory Status`
+..  versionchanged:: 14.0
+    This module has been moved from :guilabel:`Admin tools` to :guilabel:`Settings`
+	<https://docs.typo3.org/permalink/changelog:feature-107628-1729026000>`_.
+
+Alternatively, a system maintainer can go to :guilabel:`System > Environment > Directory Status`
 and recreate the missing folders with the necessary permissions
 
 ..  toctree::

Documentation/Administration/DirectoryStructure/SiteFolder.rst

@@ -24,7 +24,7 @@ following file:
     for details.
 
     The file is automatically created if you use the
-    :guilabel:`Site Management > Sites` module to
+    :guilabel:`Sites > Setup` module to
     `create a new site configuration <https://docs.typo3.org/permalink/t3coreapi:sitehandling-create-new>`_.
 
     The name of the folder is editable as **Site Identifier** in the site
@@ -46,13 +46,13 @@ Site settings `settings.yaml` in the site folder
     :shortDescription: Site specific settings
 
     This file stores all changes that where made to the site settings using the
-    backend module :guilabel:`Site Management > Settings`. It overrides the
+    backend module :guilabel:`Sites > Setup > Settings`. It overrides the
     settings from all included site sets, including the set of the site package.
 
     ..  seealso::
 
         *   `Site settings <https://docs.typo3.org/permalink/t3coreapi:sitehandling-settings>`_.
-        *   `Module Site Management > Settings <https://docs.typo3.org/permalink/t3coreapi:site-settings-editor>`_
+        *   `Module Sites > Setup > Settings <https://docs.typo3.org/permalink/t3coreapi:site-settings-editor>`_
 
 
     ..  versionchanged:: 13.4.15

Documentation/Administration/Docker/Production/Ports/Index.rst

@@ -62,4 +62,4 @@ For details, see: :ref:`reverse-proxy-container`
 After installation, **check your site configuration** in TYPO3. If it was
 automatically created with a `http://` base URL but you're accessing the site
 via `https://`, you must adjust the base URL manually in the backend:
-:guilabel:`Site Management > Sites`.
+:guilabel:`Sites > Setup`.

Documentation/Administration/ExtensionManagement/ClassicMode/Index.rst

@@ -18,7 +18,7 @@ In the backend:
 
 ..  rst-class:: bignums
 
-1.  Go to :guilabel:`Admin Tools > Extensions`
+1.  Go to :guilabel:`System > Extensions`
 2.  In the Docheader, select :guilabel:`Get Extensions`
 3.  Click :guilabel:`Update now`
 
@@ -83,7 +83,7 @@ Uninstall / Deactivate Extension via TYPO3 Backend
 
 
 Log into the TYPO3 Backend and open the module
-:guilabel:`Admin tools > Extensions`. From the menu choose
+:guilabel:`System > Extensions`. From the menu choose
 :guilabel:`Install extensions`. You get an overview about installed extensions.
 
 On the left side you see an icon, which shows the status of each extension,
@@ -143,4 +143,4 @@ as a last resort. You should only remove an extension that you uninstalled
 successfully. Make a backup first. Then you can permanently remove an extension
 by removing its folder at :file:`typo3conf/ext/[extensionname]`. The
 corresponding database tables can be removed in the
-:guilabel:`Admin Tools > Maintenance > Analyze Database Structure`.
+:guilabel:`System > Maintenance > Analyze Database Structure`.

Documentation/Administration/Installation/SystemRequirements/Index.rst

@@ -152,7 +152,7 @@ for new directives and merge them if needed.
 
 You can check the `.htaccess` status under:
 
-:guilabel:`Admin Tools > Environment > Check Directory Status`
+:guilabel:`System > Environment > Check Directory Status`
 
 ..  _vhost-records:
 

Documentation/Administration/SystemSettings/BackendEntryPoint/Index.rst

@@ -47,7 +47,7 @@ Configuration
 =============
 
 The configuration can be done in the backend via
-:guilabel:`Admin Tools > Settings > Configure Installation-Wide Options`:
+:guilabel:`System > Settings > Configure Installation-Wide Options`:
 
 ..  figure:: /Images/ManualScreenshots/AdminTools/ConfigureEntryPoint.png
     :alt: Configure the entry point via GUI

Documentation/Administration/SystemSettings/MaintenanceMode/Index.rst

@@ -27,7 +27,7 @@ Total shutdown for maintenance purposes
 
 A system maintainer can achieve total TYPO3 backend shutdown for maintenance
 purposes in module
-:guilabel:`Admin Tools > Settings > Configure Installation-Wide Options`
+:guilabel:`System > Settings > Configure Installation-Wide Options`
 by setting :ref:`[BE][adminOnly] <t3coreapi:confval-globals-typo3-conf-vars-be-adminonly>`
 to `-1`.
 
@@ -73,7 +73,7 @@ Lock the TYPO3 backend for editors
 
 To prevent an installation's editors from logging into the TYPO3 backend during
 maintenance, go to module
-:guilabel:`Admin Tools > Settings > Configure Installation-Wide Options`
+:guilabel:`System > Settings > Configure Installation-Wide Options`
 and set :ref:`[BE][adminOnly] <t3coreapi:confval-globals-typo3-conf-vars-be-adminonly>`
 to `2` if you additionally want to block console commands including scheduler
 tasks, set it to `1`.

Documentation/Administration/SystemSettings/ProductionSettings/Index.rst

@@ -10,7 +10,7 @@ Production Settings
 
 To ensure a secure installation of TYPO3 on a production server, the following settings need to be set:
 
-- :guilabel:`Admin Tools > Settings > Configuration Presets` The "Live" preset has to be chosen to make sure no debug output is displayed.
+- :guilabel:`System > Settings > Configuration Presets` The "Live" preset has to be chosen to make sure no debug output is displayed.
   When using environment specific configurations, the recommended way is to specifically set the values for
   error/debugging configuration values instead of presets, like: