diff --git a/docs/configuring-metabase/caching.md b/docs/configuring-metabase/caching.md
index cf7e5d506691da32335a217f8409e6194d3a9a1e..abdc6651e91e7d19184c936a528b2844d0d6d556 100644
--- a/docs/configuring-metabase/caching.md
+++ b/docs/configuring-metabase/caching.md
@@ -64,7 +64,7 @@ Use a query’s average execution time to determine how long to cache the query'
 
 Metabase will recalculate a query's average execution time whenever it runs the query against the database to refresh the cached results. So if the first time Metabase runs the query against the database, it takes 5 minutes to return results, the average execution time will be 5 minutes. If the next query against the database takes 7 minutes to return, Metabase will update the average to 6 minutes (the average of 5 and 7 is 6).
 
-On [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans, you can view querying and caching stats in the [Metabase analytics](../usage-and-performance-tools/usage-analytics.md) collection.
+On [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans, you can view querying and caching stats in the [Usage analytics](../usage-and-performance-tools/usage-analytics.md) collection.
 
 ### Don’t cache results
 
diff --git a/docs/configuring-metabase/environment-variables.md b/docs/configuring-metabase/environment-variables.md
index a5febb914a81c98eb5f517c60cbf457148582974..5032231059d7d0c5416d1441f25c3dd2a5081c22 100644
--- a/docs/configuring-metabase/environment-variables.md
+++ b/docs/configuring-metabase/environment-variables.md
@@ -1963,7 +1963,7 @@ Default page to show people when they log in.
 Type: Boolean<br>
 Default: True
 
-If you want to exclude the [Metabase analytics](../usage-and-performance-tools/usage-analytics.md) collection, you can set `MB_LOAD_ANALYTICS_CONTENT=false`. Setting this environment variable to false can also come in handy when migrating environments, as it can simplify the migration process.
+If you want to exclude the [Usage analytics](../usage-and-performance-tools/usage-analytics.md) collection, you can set `MB_LOAD_ANALYTICS_CONTENT=false`. Setting this environment variable to false can also come in handy when migrating environments, as it can simplify the migration process.
 
 ### `MB_NO_SURVEYS`
 
diff --git a/docs/dashboards/subscriptions.md b/docs/dashboards/subscriptions.md
index d7c59080f1c6f2aa884ad017d75aa699c6c4f71b..b2e69c2d4f20d48dc665fa8e8706e6973405bac0 100644
--- a/docs/dashboards/subscriptions.md
+++ b/docs/dashboards/subscriptions.md
@@ -110,7 +110,7 @@ To remove a subscription from a dashboard, select the subscription you'd like to
 
 {% include plans-blockquote.html feature="Usage analytics" %}
 
-You can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in **Metabase analytics** collection. See [Usage analytics](../usage-and-performance-tools/usage-analytics.md).
+You can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in **Usage analytics** collection. See [Usage analytics](../usage-and-performance-tools/usage-analytics.md).
 
 ## Customize filter values for each dashboard subscription
 
diff --git a/docs/people-and-groups/managing.md b/docs/people-and-groups/managing.md
index 5ef7c776172255741b38d88662624c895b9dbc16..f0b05c51b143754b6b0e81c159c2fe51d6ebe47e 100644
--- a/docs/people-and-groups/managing.md
+++ b/docs/people-and-groups/managing.md
@@ -143,7 +143,7 @@ Metabase uses this anonymous user account to identify anonymous views, for examp
 - Last name: Metabase
 - Email: internal@metabase.com
 
-Metabase uses this account to load content into Metabase (like the [Metabase analytics](../usage-and-performance-tools/usage-analytics.md) collection). You may see this `internal@metabase.com` account in the logs.
+Metabase uses this account to load content into Metabase (like the [Usage analytics](../usage-and-performance-tools/usage-analytics.md) collection). You may see this `internal@metabase.com` account in the logs.
 
 ## Groups
 
diff --git a/docs/permissions/collections.md b/docs/permissions/collections.md
index c86172288fa074d4c55ae494ec50e4139096362e..8a5fb4a1e8894c52aeec1eba978c478860bed76d 100644
--- a/docs/permissions/collections.md
+++ b/docs/permissions/collections.md
@@ -92,7 +92,7 @@ Note that collections themselves can't be pinned. If you're running on a [Pro or
 
 The "Our analytics" collection and individual personal collections are invincible; they cannot be archived, injured, or slain. They are eternal.
 
-### Metabase analytics
+### Usage analytics
 
 See [Usage analytics](../usage-and-performance-tools/usage-analytics.md).
 
diff --git a/docs/questions/sharing/alerts.md b/docs/questions/sharing/alerts.md
index 256b9d6945b9eacc8d4c72b96dbba4b0f2cc1976..818bcf37c6d72aa9f2b078099c8a7d8f521fd457 100644
--- a/docs/questions/sharing/alerts.md
+++ b/docs/questions/sharing/alerts.md
@@ -104,7 +104,7 @@ Alerts will continue to work even if the person who set up the alert no longer h
 
 {% include plans-blockquote.html feature="Usage analytics" %}
 
-Admins can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in the **Metabase analytics** collection. See [Usage analytics](../../usage-and-performance-tools/usage-analytics.md#alerts-model).
+Admins can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in the **Usage analytics** collection. See [Usage analytics](../../usage-and-performance-tools/usage-analytics.md#alerts-model).
 
 ## How permissions work with alerts
 
diff --git a/docs/usage-and-performance-tools/usage-analytics.md b/docs/usage-and-performance-tools/usage-analytics.md
index f6c3e42c8906fe248ef18691b42b84450e13327c..64c8abfa67989ff230a284e3c0ba094c02578795 100644
--- a/docs/usage-and-performance-tools/usage-analytics.md
+++ b/docs/usage-and-performance-tools/usage-analytics.md
@@ -4,11 +4,11 @@ title: Usage analytics
 
 # Usage analytics
 
-{% include plans-blockquote.html feature="Metabase analytics" %}
+{% include plans-blockquote.html feature="Usage analytics" %}
 
-The **Metabase Analytics** collection is a special collection that contains view-only questions, dashboards, and models that help you understand how people are using your Metabase.
+The **Usage analytics** collection is a special collection that contains view-only questions, dashboards, and models that help you understand how people are using your Metabase.
 
-![Metabase analytics collection](./images/metabase-analytics.png)
+![Usage analytics collection](./images/metabase-analytics.png)
 
 These resources are useful for:
 
@@ -16,24 +16,24 @@ These resources are useful for:
 - **Auditing activity**: Know who viewed or did what and when, including tracking dashboard and question views, queries, downloads, and other activity like changing settings or inviting people to your Metabase.
 - **Improving operations**: Know the slowest dashboards and questions, how your database's are performing, who's consuming the most resources, and so on.
 
-Some things to keep in mind with this special Metabase analytics collection:
+Some things to keep in mind with this special Usage analytics collection:
 
-- Metabase analytics is a view-only collection. Even admins can't curate it. It is eternal.
-- By default, only admins can view the Metabase analytics collection (though admins can grant other groups view access to it). If you're upgrading from a version older than 48, people in groups with [monitoring access](../usage-and-performance-tools/usage-analytics.md) will also get access to the Metabase analytics collection. But after that initial grandfathering in, the monitoring access privilege is unrelated to the Metabase analytics collection; you'll need to specifically grant groups access to the Metabase analytics collection.
-- You can duplicate any item in the Metabase analytics collection, modify the item to your liking, and save the item to another collection.
+- Usage analytics is a view-only collection. Even admins can't curate it. It is eternal.
+- By default, only admins can view the Usage analytics collection (though admins can grant other groups view access to it). If you're upgrading from a version older than 48, people in groups with [monitoring access](../usage-and-performance-tools/usage-analytics.md) will also get access to the Usage analytics collection. But after that initial grandfathering in, the monitoring access privilege is unrelated to the Usage analytics collection; you'll need to specifically grant groups access to the Usage analytics collection.
+- You can duplicate any item in the Usage analytics collection, modify the item to your liking, and save the item to another collection.
 - Metabase creates some default user accounts that you might see in your usage analytics, like `internal@metabase.com`. See [Default accounts](../people-and-groups/managing.md#default-user-accounts) for more information.
 
 ## Permissions
 
-By default, only admins can see the Metabase analytics collection. You can manage permissions for the collection in **Admin settings** > **Permissions** > **Collections**.
+By default, only admins can see the Usage analytics collection. You can manage permissions for the collection in **Admin settings** > **Permissions** > **Collections**.
 
-There are only two access types for the Metabase analytics collection: **View** and **No access**.
+There are only two access types for the Usage analytics collection: **View** and **No access**.
 
-Additionally, this Metabase analytics collection has a default sub-collection called "Custom reports" which you can use to save duplicated/modified questions, dashboards, and models. This sub-collection inherits the same permissions, but it's not view-only; admins have curate access by default, and can grant other groups view access.
+Additionally, this Usage analytics collection has a default sub-collection called "Custom reports" which you can use to save duplicated/modified questions, dashboards, and models. This sub-collection inherits the same permissions, but it's not view-only; admins have curate access by default, and can grant other groups view access.
 
 ## Viewing usage insights for a question, dashboard, or model
 
-> Only people in groups with view access to the Metabase analytics collection will see this Insights option.
+> Only people in groups with view access to the Usage analytics collection will see this Usage insights option.
 
 To view usage analytics for a question, dashboard, or model:
 
@@ -45,17 +45,17 @@ Metabase will take you to the relevant usage dashboard and plug in the item's ID
 
 ## Creating custom reports
 
-You can duplicate any of the questions, dashboards and models in the Metabase analytics collection and tweak them to your liking, but you'll need to save them to a different collection.
+You can duplicate any of the questions, dashboards and models in the Usage analytics collection and tweak them to your liking, but you'll need to save them to a different collection.
 
 ### Custom reports collection
 
-While you _can_ save custom questions, models, and dashboards wherever you like (except for the Metabase analytics collection), we recommend that you save your custom Metabase analytics reports in the conveniently named "Custom reports" sub-collection. That way these items inherit the same permissions as the parent Metabase analytics collection.
+While you _can_ save custom questions, models, and dashboards wherever you like (except for the Usage analytics collection), we recommend that you save your custom Usage analytics reports in the conveniently named "Custom reports" sub-collection. That way these items inherit the same permissions as the parent Usage analytics collection.
 
 There is one thing to know about the Custom reports collection: its metadata resets whenever Metabase restarts. While you are able to temporarily rename the Custom reports collection, or give it a description or an Official badge, Metabase will drop this collection's metadata when it restarts. But rest assured that Metabase will preserve any questions, models, events, or dashboards that you add to the Custom reports collection.
 
 ## Dashboards
 
-The Metabase Analytics collection includes a set of read-only dashboards.
+The Usage analytics collection includes a set of read-only dashboards.
 
 ### Metabase metrics dashboard
 
@@ -144,7 +144,7 @@ Dashboards and questions that you could consider archiving. Cards include:
 
 ## Models
 
-The Metabase analytics collection includes a bunch of useful models based on Metabase's application database.
+The Usage analytics collection includes a bunch of useful models based on Metabase's application database.
 
 ## Activity log model