diff --git a/core/MAINTAINERS.txt b/core/MAINTAINERS.txt
index 7c8e2c60f4..8c90c33241 100644
--- a/core/MAINTAINERS.txt
+++ b/core/MAINTAINERS.txt
@@ -56,7 +56,7 @@ subsystems. See https://www.drupal.org/contribute/core-maintainers for more
 information on their responsibilities, and to find out how to become a subsystem
 maintainer. Current subsystem maintainers:
 
-Actions
+Actions UI
 - ?
 
 Ajax
diff --git a/core/modules/action/action.info.yml b/core/modules/action/action.info.yml
index 05aaf35aeb..fc3e6c0526 100644
--- a/core/modules/action/action.info.yml
+++ b/core/modules/action/action.info.yml
@@ -1,4 +1,4 @@
-name: Actions
+name: Actions UI
 type: module
 description: 'Allows configuration of tasks to be executed in response to events.'
 package: Core
diff --git a/core/modules/action/action.module b/core/modules/action/action.module
index c37bd9230d..e4714bc75b 100644
--- a/core/modules/action/action.module
+++ b/core/modules/action/action.module
@@ -2,7 +2,7 @@
 
 /**
  * @file
- * This is the Actions module for executing stored actions.
+ * This is the Actions UI module for executing stored actions.
  */
 
 use Drupal\Core\Url;
@@ -18,13 +18,13 @@ function action_help($route_name, RouteMatchInterface $route_match) {
     case 'help.page.action':
       $output = '';
       $output .= '<h3>' . t('About') . '</h3>';
-      $output .= '<p>' . t('The Actions module provides tasks that can be executed by the site such as unpublishing content, sending email messages, or blocking a user. Other modules can trigger these actions when specific system events happen; for example, when new content is posted or when a user logs in. Modules can also provide additional actions. For more information, see the <a href=":documentation">online documentation for the Actions module</a>.', [':documentation' => 'https://www.drupal.org/documentation/modules/action']) . '</p>';
+      $output .= '<p>' . t('The Actions UI module provides tasks that can be executed by the site such as unpublishing content, sending email messages, or blocking a user. Other modules can trigger these actions when specific system events happen; for example, when new content is posted or when a user logs in. Modules can also provide additional actions. For more information, see the <a href=":documentation">online documentation for the Actions UI module</a>.', [':documentation' => 'https://www.drupal.org/documentation/modules/action']) . '</p>';
       $output .= '<h3>' . t('Uses') . '</h3>';
       $output .= '<dl>';
       $output .= '<dt>' . t('Using simple actions') . '</dt>';
-      $output .= '<dd>' . t('<em>Simple actions</em> do not require configuration and are listed automatically as available on the <a href=":actions">Actions page</a>.', [':actions' => Url::fromRoute('entity.action.collection')->toString()]) . '</dd>';
+      $output .= '<dd>' . t('<em>Simple actions</em> do not require configuration and are listed automatically as available on the <a href=":actions">Actions administration page</a>.', [':actions' => Url::fromRoute('entity.action.collection')->toString()]) . '</dd>';
       $output .= '<dt>' . t('Creating and configuring advanced actions') . '</dt>';
-      $output .= '<dd>' . t('<em>Advanced actions</em> are user-created and have to be configured individually. Create an advanced action on the <a href=":actions">Actions page</a> by selecting an action type from the drop-down list. Then configure your action, for example by specifying the recipient of an automated email message.', [':actions' => Url::fromRoute('entity.action.collection')->toString()]) . '</dd>';
+      $output .= '<dd>' . t('<em>Advanced actions</em> are user-created and have to be configured individually. Create an advanced action on the <a href=":actions">Actions administration page</a> by selecting an action type from the drop-down list. Then configure your action, for example by specifying the recipient of an automated email message.', [':actions' => Url::fromRoute('entity.action.collection')->toString()]) . '</dd>';
       $output .= '</dl>';
       return $output;
 
diff --git a/core/modules/action/action.post_update.php b/core/modules/action/action.post_update.php
index 0de13395fa..6c237c4ca5 100644
--- a/core/modules/action/action.post_update.php
+++ b/core/modules/action/action.post_update.php
@@ -2,7 +2,7 @@
 
 /**
  * @file
- * Post update functions for Action module.
+ * Post update functions for Actions UI module.
  */
 
 /**
diff --git a/core/modules/action/tests/src/Functional/ActionUninstallTest.php b/core/modules/action/tests/src/Functional/ActionUninstallTest.php
index 1d718f0c53..f5d17379f8 100644
--- a/core/modules/action/tests/src/Functional/ActionUninstallTest.php
+++ b/core/modules/action/tests/src/Functional/ActionUninstallTest.php
@@ -5,7 +5,7 @@
 use Drupal\Tests\BrowserTestBase;
 
 /**
- * Tests that uninstalling Actions does not remove other modules' actions.
+ * Tests that uninstalling Actions UI does not remove other modules' actions.
  *
  * @group action
  * @see \Drupal\views\Plugin\views\field\BulkForm
@@ -26,7 +26,7 @@ class ActionUninstallTest extends BrowserTestBase {
   protected $defaultTheme = 'stark';
 
   /**
-   * Tests Action uninstall.
+   * Tests Actions UI uninstall.
    */
   public function testActionUninstall() {
     \Drupal::service('module_installer')->uninstall(['action']);
diff --git a/core/modules/help_topics/help_topics/action.overview.html.twig b/core/modules/help_topics/help_topics/action.overview.html.twig
index d3c5642ba3..90782e9ab8 100644
--- a/core/modules/help_topics/help_topics/action.overview.html.twig
+++ b/core/modules/help_topics/help_topics/action.overview.html.twig
@@ -6,7 +6,7 @@ related:
   - views_ui.bulk_operations
 ---
 {% set actions_link_text %}
-  {% trans %}Actions page{% endtrans %}
+  {% trans %}Actions administration page{% endtrans %}
 {% endset %}
 {% set actions_page = render_var(help_route_link(actions_link_text, 'entity.action.collection')) %}
 <h2>{% trans %}What are actions?{% endtrans %}</h2>
@@ -18,8 +18,8 @@ related:
 <h2>{% trans %}How are actions executed?{% endtrans %}</h2>
 <p>{% trans %}In the core software, actions can be executed through a <em>bulk operations form</em> added to a view; if you have the core Views module installed, see the related topic "Managing content listings (views)" for more information about views and bulk operations.{% endtrans %}</p>
 <h2>{% trans %}Configuring actions overview{% endtrans %}</h2>
-<p>{% trans %}The core Actions module provides a user interface for listing and configuring actions. The core Views UI module provides a user interface for creating views, which may include bulk operations forms for executing actions. See the related topics listed below for specific tasks.{% endtrans %}</p>
+<p>{% trans %}The core Actions UI module provides a user interface for listing and configuring actions. The core Views UI module provides a user interface for creating views, which may include bulk operations forms for executing actions. See the related topics listed below for specific tasks.{% endtrans %}</p>
 <h2>{% trans %}Additional resources{% endtrans %}</h2>
 <ul>
-  <li><a href="https://www.drupal.org/documentation/modules/action">{% trans %}Online documentation for the Action module{% endtrans %}</a></li>
+  <li><a href="https://www.drupal.org/documentation/modules/action">{% trans %}Online documentation for the Actions UI module{% endtrans %}</a></li>
 </ul>
diff --git a/core/modules/help_topics/help_topics/views.overview.html.twig b/core/modules/help_topics/help_topics/views.overview.html.twig
index 0e93040e45..55ff85d9e2 100644
--- a/core/modules/help_topics/help_topics/views.overview.html.twig
+++ b/core/modules/help_topics/help_topics/views.overview.html.twig
@@ -26,7 +26,7 @@ related:
   <li>{% trans %}<em>Advanced</em> &gt; <em>Exposed form</em>: if you have exposed filters or sorts, how to display the form to the user.{% endtrans %}</li>
 </ul>
 <h2>{% trans %}What are bulk operations?{% endtrans %}</h2>
-<p>{% trans %}Views using a table display format can include a bulk operations form, which allows users with sufficient permission to select one or more items from the view and apply an administrative action to them. The bulk actions available are specific to the base data type of the view; for example, a view of content items could support bulk publishing and unpublishing actions. If you have the core Actions module installed, see the related topic "Configuring actions" for more about actions.{% endtrans %}</p>
+<p>{% trans %}Views using a table display format can include a bulk operations form, which allows users with sufficient permission to select one or more items from the view and apply an administrative action to them. The bulk actions available are specific to the base data type of the view; for example, a view of content items could support bulk publishing and unpublishing actions. If you have the core Actions UI module installed, see the related topic "Configuring actions" for more about actions.{% endtrans %}</p>
 <h2>{% trans %}Managing views overview{% endtrans %}</h2>
 <p>{% trans %}The core Views module handles the display of views, and the core Views UI module allows you to create, edit, and delete views in the administrative interface. See the related topics listed below for specific tasks (if the Views UI module is installed).{% endtrans %}</p>
 <h2>{% trans %}Additional resources{% endtrans %}</h2>
diff --git a/core/modules/help_topics/help_topics/views_ui.bulk_operations.html.twig b/core/modules/help_topics/help_topics/views_ui.bulk_operations.html.twig
index 9f4cd2ac9c..2ce8d4bcce 100644
--- a/core/modules/help_topics/help_topics/views_ui.bulk_operations.html.twig
+++ b/core/modules/help_topics/help_topics/views_ui.bulk_operations.html.twig
@@ -16,7 +16,7 @@ related:
 {% endset %}
 {% set views_permissions = render_var(help_route_link(views_permissions_link_text, 'user.admin_permissions.module', {'modules': 'views_ui'})) %}
 <h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Add one or more existing actions as bulk operations to an existing table-style view. If you have the core Actions module installed, see the related topic "Configuring actions" for more information about actions.{% endtrans %}</p>
+<p>{% trans %}Add one or more existing actions as bulk operations to an existing table-style view. If you have the core Actions UI module installed, see the related topic "Configuring actions" for more information about actions.{% endtrans %}</p>
 <h2>{% trans %}Who can edit views?{% endtrans %}</h2>
 <p>{% trans %}The core Views UI module will need to be installed and you will need <em>{{ views_permissions }}</em> permission in order to edit a view.{% endtrans %}</p>
 <h2>{% trans %}Steps{% endtrans %}</h2>
diff --git a/core/modules/system/tests/src/Functional/Form/ModulesListFormWebTest.php b/core/modules/system/tests/src/Functional/Form/ModulesListFormWebTest.php
index 1e4678c60d..ab8b18e4d0 100644
--- a/core/modules/system/tests/src/Functional/Form/ModulesListFormWebTest.php
+++ b/core/modules/system/tests/src/Functional/Form/ModulesListFormWebTest.php
@@ -77,7 +77,7 @@ public function testModulesListFormStatusMessage() {
     // Enable a module that defines permissions.
     $edit = ['modules[action][enable]' => 'action'];
     $this->submitForm($edit, 'Install');
-    $this->assertSession()->elementTextContains('xpath', "//div[@role='contentinfo' and h2[text()='Status message']]", 'Module Actions has been enabled.');
+    $this->assertSession()->elementTextContains('xpath', "//div[@role='contentinfo' and h2[text()='Status message']]", 'Module Actions UI has been enabled.');
     $this->assertSession()->elementExists('xpath', "//div[@role='contentinfo' and h2[text()='Status message']]//a[contains(@href, '/admin/people/permissions/module/action')]");
 
     // Enable a module that has dependencies and both define permissions.
