TYPO3-Documentation · linawolf · Nov 28, 2025 · Nov 27, 2025 · Nov 28, 2025
diff --git a/...mentation/Administration/PermissionsManagement/SettingUpBackendGroups/Index.rst b/...mentation/Administration/PermissionsManagement/SettingUpBackendGroups/Index.rst
@@ -45,12 +45,12 @@ for listing and editing, and specific fields in backend forms.
 
 Ensure ACL groups grant essential permissions for specific elements management.
 For example, users managing custom record types (e.g., Article, Product) should list,
-create, and access records, possibly via a custom backend module or the List module.
+create, and access records, possibly via a custom backend module or the :guilabel:`Content > Records` module.
 It's crucial to equip such a group with access to:
 
 * Listing and modifying the table of a records
 * Editing fields within the record that align with this group's purpose
-* Accessing the core List module or custom module for records management
+* Accessing the core :guilabel:`Content > Records` module or custom module for records management
 * If there are relations from this record, for example, to files, it should also permit uploading, selecting, and processing these files
 
 Therefore, a group can be seen as an independent unit that provides complete

diff --git a/Documentation/ApiOverview/Backend/BackendModules/BackendGUI.rst b/Documentation/ApiOverview/Backend/BackendModules/BackendGUI.rst
@@ -46,7 +46,7 @@ Navigation frame
   The current location (i.e. page or frame) is carried over between
   navigation frames when changing modules. This means, for example, that
   when you move from the :guilabel:`Content > Page` module to the
-  :guilabel:`Content > List` module, the same page stays selected in the page tree.
+  :guilabel:`Content > Records` module, the same page stays selected in the page tree.
 
 DocHeader
   This part is always located above the Content area. It will generally

diff --git a/Documentation/ApiOverview/Backend/BackendUserObject.rst b/Documentation/ApiOverview/Backend/BackendUserObject.rst
@@ -39,7 +39,7 @@ the access list by this function call:
 
    $GLOBALS['BE_USER']->check('modules', 'web_list');
 
-Here access to the module :guilabel:`Content > List` is checked.
+Here access to the module :guilabel:`Content > Records` is checked.
 
 
 .. index::

diff --git a/Documentation/ApiOverview/Database/DatabaseStructure/Index.rst b/Documentation/ApiOverview/Database/DatabaseStructure/Index.rst
@@ -38,7 +38,7 @@ Managed tables
 ==============
 
 Defined in the :ref:`TCA <t3tca:start>` and, by default, editable in the
-:guilabel:`Content > List` module. TYPO3 derives database schemas from the TCA
+:guilabel:`Content > Records` module. TYPO3 derives database schemas from the TCA
 configuration. Required fields such as :sql:`uid` and :sql:`pid` are generated
 automatically.
 

diff --git a/Documentation/ApiOverview/Database/DoctrineDbal/RestrictionBuilder/Index.rst b/Documentation/ApiOverview/Database/DoctrineDbal/RestrictionBuilder/Index.rst
@@ -16,7 +16,7 @@ should be handled and displayed by the framework.
 
 The `ctrl` section of a table's TCA array specifies optional framework-internal
 handling of soft deletes and language overlays: For instance, when a row is
-deleted in the backend using the page or list module, many tables are configured
+deleted in the backend using the page or :guilabel:`Content > Records` module, many tables are configured
 to not drop that row entirely from the table, but to set a field (often
 `deleted`) for that row from `0` to `1`. Similar mechanisms apply for start and
 end times, and to language and workspace overlays as well. See the

diff --git a/...ation/ApiOverview/Events/Events/Backend/BeforeRecordDownloadIsExecutedEvent.rst b/...ation/ApiOverview/Events/Events/Backend/BeforeRecordDownloadIsExecutedEvent.rst
@@ -15,7 +15,7 @@ BeforeRecordDownloadIsExecutedEvent
 
 The event :php:`TYPO3\CMS\Backend\RecordList\Event\BeforeRecordDownloadIsExecutedEvent`
 can be used to modify the result of a download / export initiated via
-the :guilabel:`Content > List` module.
+the :guilabel:`Content > Records` module.
 
 The event lets you change both the main part and the header of the data file.
 You can use it to edit data to follow GDPR rules, change or translate data,

diff --git a/...Overview/Events/Events/Backend/BeforeRecordDownloadPresetsAreDisplayedEvent.rst b/...Overview/Events/Events/Backend/BeforeRecordDownloadPresetsAreDisplayedEvent.rst
@@ -10,7 +10,7 @@ BeforeRecordDownloadPresetsAreDisplayedEvent
 
 The event :php:`TYPO3\CMS\Backend\RecordList\Event\BeforeRecordDownloadPresetsAreDisplayedEvent`
 can be used to manipulate the list of available download presets in
-the :guilabel:`Content > List` module.
+the :guilabel:`Content > Records` module.
 
 See :confval:`mod.web_list.downloadPresets <t3tsref:mod-web-list-downloadpresets>`
 on how to configure download presets.

diff --git a/Documentation/ApiOverview/RequestLifeCycle/RequestAttributes/Target.rst b/Documentation/ApiOverview/RequestLifeCycle/RequestAttributes/Target.rst
@@ -9,7 +9,7 @@ Target
 ======
 
 The :php:`target` backend request attribute provides the target action of a
-backend route. For instance, the target of the :guilabel:`Content > List` module
+backend route. For instance, the target of the :guilabel:`Content > Records` module
 is set to :php:`TYPO3\CMS\Recordlist\Controller\RecordListController::mainAction`.
 
 Example:

diff --git a/Documentation/ApiOverview/SiteHandling/AddLanguages.rst b/Documentation/ApiOverview/SiteHandling/AddLanguages.rst
@@ -13,7 +13,7 @@ should behave. New languages for a site can also be configured in this module.
 When the backend shows the list of available languages, the list of languages is
 limited to the languages defined by the sites module. For instance, the
 languages are used in the page module language selector, when editing records
-or in the list module.
+or in the :guilabel:`Content > Records` module.
 
 The language management provides the ability to hide a language on the frontend
 while allowing it on the backend. This enables editors to start translating

diff --git a/...ntation/CodeSnippets/Events/Backend/BeforeRecordDownloadIsExecutedEvent.rst.txt b/...ntation/CodeSnippets/Events/Backend/BeforeRecordDownloadIsExecutedEvent.rst.txt
@@ -3,7 +3,7 @@
 
 ..  php:class:: BeforeRecordDownloadIsExecutedEvent
 
-    Listeners to this event are able to manipulate the download of records, usually triggered via Web > List.
+    Listeners to this event are able to manipulate the download of records, usually triggered via Content > Records.
 
     ..  php:method:: getHeaderRow()
         :returns: `array`

diff --git a/...on/CodeSnippets/Events/Backend/ModifyDatabaseQueryForRecordListingEvent.rst.txt b/...on/CodeSnippets/Events/Backend/ModifyDatabaseQueryForRecordListingEvent.rst.txt
@@ -3,7 +3,7 @@
 
 ..  php:class:: ModifyDatabaseQueryForRecordListingEvent
 
-    Use this Event to alter the database query when loading content for a page (usually in the records module)
+    Use this Event to alter the database query when loading content for a page (usually in the "Records" module)
     before it is executed.
 
     ..  php:method:: getQueryBuilder()

diff --git a/Documentation/ExtensionArchitecture/Extbase/Reference/FileUpload.rst b/Documentation/ExtensionArchitecture/Extbase/Reference/FileUpload.rst
@@ -34,7 +34,7 @@ and the TCA definition:
     :caption: EXT:my_extension/Configuration/TCA/tx_myextension_domain_model_blog.php
 
 Once this is set up, you can create/edit records through the TYPO3
-backend (for example via :guilabel:`Content > List`), attach a single or
+backend (for example via :guilabel:`Content > Records`), attach a single or
 multiple files in it. Then using a normal
 controller and Fluid template, you can display an image.
 

diff --git a/Documentation/Images/AutomaticScreenshots/AccessControl/BackendUserAdmin.rst.txt b/Documentation/Images/AutomaticScreenshots/AccessControl/BackendUserAdmin.rst.txt
@@ -3,4 +3,4 @@
 .. figure:: /Images/AutomaticScreenshots/AccessControl/BackendUserAdmin.png
    :class: with-shadow
 
-   In :guilabel:`Content > List` view, the different icon for admin users
+   In :guilabel:`Content > Records` view, the different icon for admin users
diff --git a/Documentation/PhpArchitecture/WorkingWithExceptions.rst b/Documentation/PhpArchitecture/WorkingWithExceptions.rst
@@ -49,7 +49,7 @@ Typical cases for exceptions that are designed to be caught
 
 *   Race conditions than can be created by editors in a normal workflow:
 
-    *   Editor 1 calls list module and a record is shown.
+    *   Editor 1 calls :guilabel:`Content > Records` module and a record is shown.
 
     *   Editor 2 deletes this record.
 

diff --git a/Documentation/Testing/AcceptanceTesting/_AcceptanceTests/_SomeCest.php b/Documentation/Testing/AcceptanceTesting/_AcceptanceTests/_SomeCest.php
@@ -12,7 +12,7 @@ class SomeCest
      * @param BackendTester $I
      */
     public function _before(BackendTester $I)
-    {   // Switch to "content frame", eg the "list module" content
+    {   // Switch to "content frame", eg the "Records module" content
         $I->switchToContentFrame();
 
         // Switch to "main frame", the frame with the main modules and top bar