Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs - various edits (#65422)

Jeff Bruemmer5884bfe5477c
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index ebde6c0fc69..9421b1a1209 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -37,7 +37,7 @@ The core team runs a pretty well defined product process. It is actively being t
### A) Identify product needs from the community
-We actively look for new feature ideas from our community, user base and our own use of Metabase internally. We concentrate on the underlying _problem_ or _need_ as opposed to requests for specific features. While sometimes suggested features are built as requested, often we find that they involve changes to existing features, and perhaps an entirely different solution to the underlying problem. These will typically be collected in a number of issues, and tagged [Proposal](https://github.com/metabase/metabase/labels/.Proposal)
+We actively look for new feature ideas from our community, user base and our own use of Metabase internally. We concentrate on the underlying _problem_ or _need_ as opposed to requests for specific features. While sometimes suggested features are built as requested, often we find that they involve changes to existing features, and potentially an entirely different solution to the underlying problem. These will typically be collected in a number of issues, and tagged [Proposal](https://github.com/metabase/metabase/labels/.Proposal)
### B) Synthesize these needs into a concrete feature
@@ -107,4 +107,4 @@ Generally speaking, any issue in [Help Wanted](https://github.com/metabase/metab
### #YOLO JUST SUBMIT A PR
-If you come up with something really cool, and want to share it with us, just submit a PR. If it hasn't gone through the above process, we probably won't merge it as is, but if it's compelling, we're more than willing to help you via code review, design review and generally OCD nitpicking so that it fits into the rest of our codebase.
+If you come up with something cool, and want to share it with us, just submit a PR. If it hasn't gone through the above process, we probably won't merge it as is, but if it's compelling, we're more than willing to help you via code review, design review and generally OCD nitpicking so that it fits into the rest of our codebase.
diff --git a/docs/actions/introduction.md b/docs/actions/introduction.md
index 08e33941634..91ba3f5bc34 100644
--- a/docs/actions/introduction.md
+++ b/docs/actions/introduction.md
@@ -55,7 +55,7 @@ There are multiple ways to run actions:
Just something to clarify here: actions, even though they are added to models, make their changes to the underlying table that a model queries. Which means that anyone who has access to the underlying table, or to questions or other models based on that table, will be able to see the effects of an action. Tools other than Metabase that are connected to that database will also pick up these changes.
-In this sense, models are containers for actions; models are a way to organize actions. In fact, you could (in theory) add a [custom action](./custom.md) to a model that performs some update unrelated to its model's data. For example, you could write a custom action that updates the `Accounts` table, and add that action to a model that only queries an unrelated table (e.g., the `Orders` table). But, you know, maybe don't do that (unless you have a really good reason). [Basic actions](./basic.md), however, are only be available for models that wrap a single raw table.
+In this sense, models are containers for actions; models are a way to organize actions. In fact, you could (in theory) add a [custom action](./custom.md) to a model that performs some update unrelated to its model's data. For example, you could write a custom action that updates the `Accounts` table, and add that action to a model that only queries an unrelated table (e.g., the `Orders` table). But, you know, maybe don't do that (unless you have a good reason). [Basic actions](./basic.md), however, are only be available for models that wrap a single raw table.
Before using actions in production, consider playing around with actions on some sample data (like the Sample Database included with Metabase) to get a feel for how they work.
diff --git a/docs/cloud/google-sheets.md b/docs/cloud/google-sheets.md
index fde84c1deaa..3feff130f04 100644
--- a/docs/cloud/google-sheets.md
+++ b/docs/cloud/google-sheets.md
@@ -34,7 +34,7 @@ Here's how to set it up:
5. Give the service account **Viewer** permissions. Metabase will only have access to this folder or sheet; it won't have access to any other files in your Google Drive. If you select folder, Metabase will also sync any sheets it finds in any subfolders.
6. Click **Send** to share the folder with the Metabase service account.
7. Copy the sharing link for the folder or sheet.
-8. Return to Metabase and paste the sharing link into the field that asks for "the sharing link for this folder/file".
+8. Return to Metabase and paste the sharing link into "the sharing link for this folder/file" field.
**If you synced a Google Drive folder**, Metabase will sync with the Google Drive folder (and its subfolders) and import all Google Sheets, creating a new table in your Metabase Cloud Storage database for each sheet. For sheets with multiple tabs, Metabase will create a table for each tab. Metabase will only sync Google Sheets; it'll ignore other file types in the folder. After the initial sync, Metabase will sync every 15 minutes.
diff --git a/docs/cloud/migrate/heroku.md b/docs/cloud/migrate/heroku.md
index b1286eb2dcd..becc96e87f1 100644
--- a/docs/cloud/migrate/heroku.md
+++ b/docs/cloud/migrate/heroku.md
@@ -16,7 +16,7 @@ There are some additional steps you'll need to take to migrate from Heroku to Me
## Follow the migration guide to get the migration script
-You should follow along with the [migration guide](./guide.md). Once you download the migration script you'll need to get shell access to your Heroku server in order to execute the migration script.
+You should follow along with the [migration guide](./guide.md). Once you download the migration script you'll need to get shell access to your Heroku server to execute the migration script.
## Install Heroku CLI for your OS
diff --git a/docs/cloud/storage.md b/docs/cloud/storage.md
index f16580d1f3a..2ea5b32f67f 100644
--- a/docs/cloud/storage.md
+++ b/docs/cloud/storage.md
@@ -79,7 +79,7 @@ To remove Metabase Cloud Storage (which will _permanently_ erase all its data):
3. Click **Manage storage**.
4. Click **Edit**.
5. Click **Disable storage**.
-6. Click **Erase all data**, which---**WARNING**--will erase _all of its data_. We won't be able to recover the data, so only do this if you're absolutely sure you no need the storage and its data.
+6. Click **Erase all data**, which---**WARNING**--will erase _all of its data_. We won't be able to recover the data, so only do this if you're certain you no longer need the storage and its data.
## Syncing Google Sheets with Metabase
diff --git a/docs/configuring-metabase/appearance.md b/docs/configuring-metabase/appearance.md
index f6d034f8b28..f9210ea47b2 100644
--- a/docs/configuring-metabase/appearance.md
+++ b/docs/configuring-metabase/appearance.md
@@ -80,7 +80,7 @@ Custom colors are unavailable for:
## Logo
-You can replace Metabase’s familiar, tasteful, inspired-yet-not-threateningly-avant-garde dotted M logo with your very own logo. For things to work best, the logo you upload should be an SVG file that looks good when it’s around 60px tall. (In other words, ask the nearest designer for help.)
+You can replace Metabase's familiar, tasteful, inspired-yet-not-threateningly-avant-garde dotted M logo with your very own logo. For things to work best, the logo you upload should be an SVG file that looks good when it's around 60px tall. (In other words, ask the nearest designer for help.)
## Font
diff --git a/docs/configuring-metabase/environment-variables.md b/docs/configuring-metabase/environment-variables.md
index 838e054312a..4dab0bfda17 100644
--- a/docs/configuring-metabase/environment-variables.md
+++ b/docs/configuring-metabase/environment-variables.md
@@ -107,7 +107,7 @@ Allowed iframe hosts.
- Default: `true`
- [Configuration file name](./config-file.md): `anon-tracking-enabled`
-Enable the collection of anonymous usage data in order to help Metabase improve.
+Enable the collection of anonymous usage data to help Metabase improve.
### `MB_API_KEY`
@@ -365,7 +365,7 @@ Whether dashboards should default to a user's last used parameters on load.
- Type: integer
- Default: `10000`
-Consider metabase.driver/can-connect? / can-connect-with-details? to have failed if they were not able to
+Consider metabase.driver/can-connect? / can-connect-with-details? to have failed if they were unable to
successfully connect after this many milliseconds. By default, this is 10 seconds.
Timeout in milliseconds for connecting to databases, both Metabase application database and data connections.
@@ -444,7 +444,7 @@ The name you want to use for the sender of emails.
- [Configuration file name](./config-file.md): `email-max-recipients-per-second`
The maximum number of recipients, summed across emails, that can be sent per second.
- Note that the final email sent before reaching the limit is able to exceed it, if it has multiple recipients.
+ Note that the final email sent before reaching the limit can exceed it, if it has multiple recipients.
### `MB_EMAIL_REPLY_TO`
@@ -1237,7 +1237,7 @@ Indicates whether Metabase is running behind a proxy that sets the source-addres
By default "Site Url" is used in notification links, but can be overridden.
The base URL where dashboard notitification links will point to instead of the Metabase base URL.
- Only applicable for users who utilize interactive embedding and subscriptions.
+ Only applicable for users who use interactive embedding and subscriptions.
### `MB_NOTIFICATION_SYSTEM_EVENT_THREAD_POOL_SIZE`
@@ -1666,7 +1666,7 @@ When enabled, we show users a button to authenticate with Google to import data
- [Exported as](../installation-and-operation/serialization.md): `show-homepage-data`.
- [Configuration file name](./config-file.md): `show-homepage-data`
-Whether or not to display data on the homepage. Admins might turn this off in order to direct users to better content than raw data.
+Whether or not to display data on the homepage. Admins might turn this off to direct users to better content than raw data.
### `MB_SHOW_HOMEPAGE_XRAYS`
@@ -2128,7 +2128,7 @@ Type: integer<br>
Default: `600000`<br>
Since: v35.0
-Timeout of Jetty async threads, defined in milliseconds. The default is 10 minutes. Very few things might reach that timeout, since they return some type of data before, but things like CSV downloads might.
+Timeout of Jetty async threads, defined in milliseconds. The default is 10 minutes. Few things might reach that timeout, since they return some type of data before, but things like CSV downloads might.
### `MB_JETTY_DAEMON`
diff --git a/docs/configuring-metabase/fonts.md b/docs/configuring-metabase/fonts.md
index 149ea4bc829..17e813cb6e4 100644
--- a/docs/configuring-metabase/fonts.md
+++ b/docs/configuring-metabase/fonts.md
@@ -46,7 +46,7 @@ For **Font**, select **Custom...** and enter URLs to your font files.
## Font style options
-You can set three different font styles with three different URLs, one for each font style (size and weight) that Metabase will use in order to display its user interface properly. The font weights are:
+You can set three different font styles with three different URLs, one for each font style (size and weight) that Metabase will use to display its user interface properly. The font weights are:
- Regular 400
- Bold 700
diff --git a/docs/configuring-metabase/log-configuration.md b/docs/configuring-metabase/log-configuration.md
index 171740701ea..22f6c7c123e 100644
--- a/docs/configuring-metabase/log-configuration.md
+++ b/docs/configuring-metabase/log-configuration.md
@@ -80,7 +80,7 @@ java -Dlog4j.configurationFile=file:/path/to/custom/log4j2.xml -jar metabase.jar
## Configure Jetty logs
-You can configure Metabase's web server to provide more detail in the logs by setting the log level to `DEBUG`. Just keep in mind that Jetty's debug logs can be really chatty, which can make it difficult to find the data you're looking for.
+You can configure Metabase's web server to provide more detail in the logs by setting the log level to `DEBUG`. Just keep in mind that Jetty's debug logs can be chatty, which can make it difficult to find the data you're looking for.
To get Jetty logs, add the following lines to the Log4J2 XML file in the <Loggers> node:
diff --git a/docs/configuring-metabase/setting-up-metabase.md b/docs/configuring-metabase/setting-up-metabase.md
index 86fe297633b..5cb2be85d9a 100644
--- a/docs/configuring-metabase/setting-up-metabase.md
+++ b/docs/configuring-metabase/setting-up-metabase.md
@@ -15,7 +15,7 @@ Go ahead and click **Let’s get started**.
## Setting up an admin account
-The first thing you’ll need to do is set up an admin account. The account you create when you first install Metabase is an admin account by default — handy! If you’ve installed Metabase on a production server, you should be really careful to remember the password for this account since it will be used to add other users, connect to databases, set up email, and more. You can also create additional admin accounts later.
+The first thing you'll need to do is set up an admin account. The account you create when you first install Metabase is an admin account by default — handy! If you've installed Metabase on a production server, you should be careful to remember the password for this account since it will be used to add other users, connect to databases, set up email, and more. You can also create additional admin accounts later.
For now, let's just create an account for ourselves to explore Metabase. Type in your info, and when you’re ready to continue, click the **Next** button.
diff --git a/docs/configuring-metabase/timezones.md b/docs/configuring-metabase/timezones.md
index 39434a457a4..e42bef65ba0 100644
--- a/docs/configuring-metabase/timezones.md
+++ b/docs/configuring-metabase/timezones.md
@@ -45,6 +45,6 @@ The exact data type will depend on your database. Some Metabase features only wo
## Common pitfalls
1. Your database is using date/time columns without any timezone information. Typically when this happens your database will assume all the data is from whatever timezone the database is configured in or possible just default to UTC (check your database vendor to be sure).
-2. Your JVM timezone is different from your Metabase `Report Timezone` choice. This is a very common issue and can be corrected by launching java with the `-Duser.timezone=<timezone>` option properly set to match your Metabase report timezone.
+2. Your JVM timezone is different from your Metabase `Report Timezone` choice. This is a common issue and can be corrected by launching java with the `-Duser.timezone=<timezone>` option properly set to match your Metabase report timezone.
If you are still experiencing timezone problems, then have a look at the [timezone troubleshooting guide](../troubleshooting-guide/timezones.md).
diff --git a/docs/configuring-metabase/webhooks.md b/docs/configuring-metabase/webhooks.md
index 72ee03f557b..0dd8796bace 100644
--- a/docs/configuring-metabase/webhooks.md
+++ b/docs/configuring-metabase/webhooks.md
@@ -43,7 +43,7 @@ And the data as seen in the table view, which Metabase will send as a `raw_data`
![Results as table view](./images/table-view.png)
-Here's an example payload for an alert (we truncated the PNG encoding because it's long and extremely boring):
+Here's an example payload for an alert (we truncated the PNG encoding because it's boring):
```JSON
{
diff --git a/docs/dashboards/linked-filters.md b/docs/dashboards/linked-filters.md
index 034d2055058..81af4010927 100644
--- a/docs/dashboards/linked-filters.md
+++ b/docs/dashboards/linked-filters.md
@@ -56,7 +56,7 @@ Metabase uses database column metadata to populate values for linked filters, wh
- You can't create linked filters on custom columns.
-- Native/SQL questions must have a [field filter](../questions/native-editor/field-filters.md) variable in order to be linked. Basic SQL variables aren't connected to database columns, so they won't work for linked filters.
+- Native/SQL questions must have a [field filter](../questions/native-editor/field-filters.md) variable to be linked. Basic SQL variables aren't connected to database columns, so they won't work for linked filters.
- You can't link filters that use "Custom List" or "From another model or question" as their value's source.
diff --git a/docs/data-modeling/metadata-editing.md b/docs/data-modeling/metadata-editing.md
index ab299432b65..a992166e221 100644
--- a/docs/data-modeling/metadata-editing.md
+++ b/docs/data-modeling/metadata-editing.md
@@ -93,7 +93,7 @@ Click the preview button to see sample data from that field.
_Admin settings > Table Metadata > Database > Table > Field_
-To scan or discard field values for a specific field, click on the **Field values** button. Metabase uses these values to populate dropdown menus in filter widgets. (To be clear, values aren't actually dropped from your database.)
+To scan or discard field values for a specific field, click on the **Field values** button. Metabase uses these values to populate dropdown menus in filter widgets. (Values aren't dropped from your database.)
## Field data
diff --git a/docs/data-modeling/models.md b/docs/data-modeling/models.md
index a98ea4c1690..1d18cc61054 100644
--- a/docs/data-modeling/models.md
+++ b/docs/data-modeling/models.md
@@ -16,7 +16,7 @@ Models:
- Can [surface individual records in search results](#surface-individual-records-in-search-by-matching-against-this-column).
- Can be [persisted for faster loading](./model-persistence.md).
-For a deep dive on why and how to use models, check out our [Learn article on models][learn-models].
+For more on why and how to use models, check out our [Learn article on models][learn-models].
## How to use models
diff --git a/docs/data-modeling/semantic-types.md b/docs/data-modeling/semantic-types.md
index 76ad9f77ba8..32c4143e8a7 100644
--- a/docs/data-modeling/semantic-types.md
+++ b/docs/data-modeling/semantic-types.md
@@ -42,7 +42,7 @@ You can think of semantic types as adding meaning and context to a field to comm
- **Entity key.** Used to indicate that the field uniquely identifies each row. Could be a Product ID, serial number, etc.
-- **Foreign key.** Used to refer to an Entity key of another table in order to connect data from different tables that are related. For example, in a Products table, you might have a Customer ID field that points to a Customers table, where Customer ID is the Entity key. If you want to use [linked filters on dashboards](../dashboards/linked-filters.md), you must set up foreign key relationships.
+- **Foreign key.** Used to refer to an Entity key of another table to connect data from different tables that are related. For example, in a Products table, you might have a Customer ID field that points to a Customers table, where Customer ID is the Entity key. If you want to use [linked filters on dashboards](../dashboards/linked-filters.md), you must set up foreign key relationships.
### Semantic types for numeric fields
diff --git a/docs/databases/connections/mariadb.md b/docs/databases/connections/mariadb.md
index 36521c84f43..cb73388b510 100644
--- a/docs/databases/connections/mariadb.md
+++ b/docs/databases/connections/mariadb.md
@@ -77,13 +77,13 @@ If you've selected **Choose when syncs and scans happen** > **ON**, you'll be ab
#### Scanning for filter values
-Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
+Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a resource-intensive process, particularly if you have a large database.
If you've selected **Choose when syncs and scans happen** > **ON**, you'll see the following options under **Scanning for filter values**:
- **Regularly, on a schedule** allows you to run [scan queries](../sync-scan.md#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
-- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which never really have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which rarely have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
### Periodically refingerprint tables
diff --git a/docs/databases/connections/mysql.md b/docs/databases/connections/mysql.md
index 5277ca8c967..cd7e5490720 100644
--- a/docs/databases/connections/mysql.md
+++ b/docs/databases/connections/mysql.md
@@ -80,7 +80,7 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
## Connecting to MySQL 8+ servers
-Metabase uses the MariaDB connector to connect to MySQL servers. The MariaDB connector lacks support for MySQL 8's default authentication plugin. In order to connect, you'll need to change the plugin used by the Metabase user:
+Metabase uses the MariaDB connector to connect to MySQL servers. The MariaDB connector lacks support for MySQL 8's default authentication plugin. To connect, you'll need to change the plugin used by the Metabase user:
```
mysql_native_password`: `ALTER USER 'metabase'@'%' IDENTIFIED WITH mysql_native_password BY 'thepassword';
@@ -183,7 +183,7 @@ Choose whether to enable features related to [Metabase models](../../data-modeli
### Model actions
-Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions are able to read, write, and possibly delete data. Your database user will need write permissions.
+Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.
### Model persistence
diff --git a/docs/databases/connections/postgresql.md b/docs/databases/connections/postgresql.md
index df9f101eaa0..01cb5a710c4 100644
--- a/docs/databases/connections/postgresql.md
+++ b/docs/databases/connections/postgresql.md
@@ -102,7 +102,7 @@ Note that only the `*` wildcard is supported; you can't use other special charac
### Use a secure connection (SSL)
-Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we highly recommend keeping SSL turned on to keep your data secure.
+Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we recommend keeping SSL turned on to keep your data secure.
#### SSL Mode
@@ -188,7 +188,7 @@ Choose whether to enable features related to [Metabase models](../../data-modeli
### Model actions
-Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions are able to read, write, and possibly delete data. Your database user will need write permissions.
+Turn this setting on to allow [actions](../../actions/introduction.md) from models created from this data to be run. Actions can read, write, and delete data. Your database user will need write permissions.
### Model persistence
diff --git a/docs/databases/connections/presto.md b/docs/databases/connections/presto.md
index adde2bf6eb2..83cd7890702 100644
--- a/docs/databases/connections/presto.md
+++ b/docs/databases/connections/presto.md
@@ -46,7 +46,7 @@ The password for the username that you use to connect to the database.
### Use a secure connection (SSL)
-Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we highly recommend keeping SSL turned on to keep your data secure.
+Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we recommend keeping SSL turned on to keep your data secure.
### Use SSL certificate?
diff --git a/docs/databases/connections/sparksql.md b/docs/databases/connections/sparksql.md
index 3d3c0202238..06ca0544bb2 100644
--- a/docs/databases/connections/sparksql.md
+++ b/docs/databases/connections/sparksql.md
@@ -61,13 +61,13 @@ If you've selected **Choose when syncs and scans happen** > **ON**, you'll be ab
#### Scanning for filter values
-Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
+Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a resource-intensive process, particularly if you have a large database.
If you've selected **Choose when syncs and scans happen** > **ON**, you'll see the following options under **Scanning for filter values**:
- **Regularly, on a schedule** allows you to run [scan queries](../sync-scan.md#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
-- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which never really have new values added. Use the [Re-scan field values now](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which rarely have new values added. Use the [Re-scan field values now](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
### Periodically refingerprint tables
diff --git a/docs/databases/connections/sql-server.md b/docs/databases/connections/sql-server.md
index 8ec01eba2a0..1f5a078064d 100644
--- a/docs/databases/connections/sql-server.md
+++ b/docs/databases/connections/sql-server.md
@@ -48,7 +48,7 @@ The password for the username that you use to connect to the database.
### Use a secure connection (SSL)
-Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we highly recommend keeping SSL turned on to keep your data secure.
+Metabase automatically tries to connect to databases with SSL first, then without if that doesn't work. If it's possible to connect to your database with an SSL connection, Metabase will make that the default setting for your database. If you prefer to connect without this layer of security, you can always change this setting later, but we recommend keeping SSL turned on to keep your data secure.
### Use an SSH tunnel
@@ -77,13 +77,13 @@ If you've selected **Choose when syncs and scans happen** > **ON**, you'll be ab
### Scanning for filter values
-Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
+Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a resource-intensive process, particularly if you have a large database.
If you've selected **Choose when syncs and scans happen** > **ON**, you'll see the following options under **Scanning for filter values**:
- **Regularly, on a schedule** allows you to run [scan queries](../sync-scan.md#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
-- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which never really have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which rarely have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
### Periodically refingerprint tables
diff --git a/docs/databases/connections/sqlite.md b/docs/databases/connections/sqlite.md
index 39d187d2279..5439d6ae305 100644
--- a/docs/databases/connections/sqlite.md
+++ b/docs/databases/connections/sqlite.md
@@ -45,13 +45,13 @@ If you've selected **Choose when syncs and scans happen** > **ON**, you'll be ab
### Scanning for filter values
-Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
+Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a resource-intensive process, particularly if you have a large database.
If you've selected **Choose when syncs and scans happen** > **ON**, you'll see the following options under **Scanning for filter values**:
- **Regularly, on a schedule** allows you to run [scan queries](../sync-scan.md#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
-- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which never really have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which rarely have new values added. Use the [Re-scan field values](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
### Periodically refingerprint tables
diff --git a/docs/databases/connections/vertica.md b/docs/databases/connections/vertica.md
index 1e776bb4966..4b18122be49 100644
--- a/docs/databases/connections/vertica.md
+++ b/docs/databases/connections/vertica.md
@@ -16,7 +16,7 @@ You can download the JDBC driver from [Vertica's JDBC driver downloads page](htt
Head to this page, log in to your account, accept the license agreement, and download `vertica-jdbc-8.0.0-0.jar` (for Vertica DB version 8.0)
or whatever driver version most closely matches the version of Vertica you're running.
-It's very important to make sure you use the correct version of the JDBC driver; version
+It's important to make sure you use the correct version of the JDBC driver; version
8.0 of the driver won't work with Vertica version 7.2; version 7.2 of the driver won't work with Vertica version 7.1, and so forth. If in doubt,
consult Vertica's documentation to find the correct version of the JDBC driver for your version of Vertica.
diff --git a/docs/databases/sync-scan.md b/docs/databases/sync-scan.md
index db4cc958c9d..4a4aa6801c2 100644
--- a/docs/databases/sync-scan.md
+++ b/docs/databases/sync-scan.md
@@ -48,7 +48,7 @@ Options include:
- **Regularly, on a schedule** allows you to run [scan queries](#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database or tables with distinct values that get updated often.
- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when someone adds a new filter widget to a dashboard or SQL question (i.e., they add a parameter to their SQL query).
-- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large or which never really have new values added. Use the [Re-scan field values](#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large or which never have new values added. Use the [Re-scan field values](#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
Regardless of which option you pick, if you [set a field to use a dropdown list in filter widgets](../data-modeling/metadata-editing.md#filtering), Metabase will need to get values for that dropdown. Whenever someone uses that filter widget, Metabase will first look for cached values (valid for fourteen days) to populate that dropdown; otherwise, it will re-scan that field for the most up-to-date values.
@@ -165,7 +165,7 @@ Cached column values are displayed in filter dropdown menus. If people type in t
A scan is more intensive than a sync query, so it only runs once during setup and again once a day by default. If you [disable scans](#scanning-for-filter-values) entirely, you'll need to bring things up to date by running [manual scans](#manually-scanning-column-values).
-To reduce the number of tables and fields Metabase needs to scan in order to stay current with your connected database, Metabase will only scan values for fields that someone has used in the last fourteen days.
+To reduce the number of tables and fields Metabase needs to scan to stay current with your connected database, Metabase will only scan values for fields that someone has used in the last fourteen days.
Here's the kind of data that scans get and why:
diff --git a/docs/embedding/sdk/dashboards.md b/docs/embedding/sdk/dashboards.md
index 6ce336be539..5c950f48ac0 100644
--- a/docs/embedding/sdk/dashboards.md
+++ b/docs/embedding/sdk/dashboards.md
@@ -8,7 +8,7 @@ title: "Embedded analytics SDK - dashboards"
You can embed an interactive, editable, or static dashboard.
-**Please keep in mind - embedding multiple instances of dashboards on the same page is not yet supported.**
+**Keep in mind that embedding multiple instances of dashboards on the same page is not yet supported.**
## Embedding a dashboard
diff --git a/docs/embedding/sdk/quickstart.md b/docs/embedding/sdk/quickstart.md
index ce8ce0abfea..29e967c6641 100644
--- a/docs/embedding/sdk/quickstart.md
+++ b/docs/embedding/sdk/quickstart.md
@@ -78,4 +78,4 @@ Run your app and visit the page with the embedded dashboard.
## Next steps
- Explore [theming to change the look and feel](./appearance.md).
-- Continue by [setting up JWT SSO in Metabase and your app](./authentication.md) in order to sign people in, manage permissions, and deploy your app in production.
+- Continue by [setting up JWT SSO in Metabase and your app](./authentication.md) to sign people in, manage permissions, and deploy your app in production.
diff --git a/docs/exploration-and-organization/collections.md b/docs/exploration-and-organization/collections.md
index 93c804ee9c1..0b1e354fed4 100644
--- a/docs/exploration-and-organization/collections.md
+++ b/docs/exploration-and-organization/collections.md
@@ -36,7 +36,7 @@ Metabase admins can designate collections as "official" with the following effec
Pairing Official badges with [verified items](./content-verification.md) can help everyone in your Metabase sort out which questions people can trust.
-To add an Official badge to a collection, an admin can visit the collection and click on the dot dot dot menu (**...**) and select **Make collection official**. Admins can also remove an Official badge in the same menu. Admins can also mark a collection as Official or not when they first create the collection.
+To add an Official badge to a collection, an admin can visit the collection and click on the three-dot menu (**...**) and select **Make collection official**. Admins can also remove an Official badge in the same menu. Admins can also mark a collection as Official or not when they first create the collection.
## Collection permissions
diff --git a/docs/exploration-and-organization/events-and-timelines.md b/docs/exploration-and-organization/events-and-timelines.md
index 97af1890fc3..41fba9b1250 100644
--- a/docs/exploration-and-organization/events-and-timelines.md
+++ b/docs/exploration-and-organization/events-and-timelines.md
@@ -6,7 +6,7 @@ redirect_from:
# Events and timelines
-A lot of discussions around data have a moment when someone asks a question related to a specific point in time: "Wait, what's the spike in March again?", or "When did the new widget launch?"
+A lot of discussions around data have a moment when someone has a question related to a specific point in time: "Wait, what's the spike in March again?", or "When did the new widget launch?"
Events and timelines are a way to capture that chronological knowledge and make it available when you need it, in context (that is, when you're viewing a chart). Events are a great way to store institutional knowledge about what happened and when, so people (including yourself three months from now) won't have to figure out (again) why the line chart spiked back in March.
diff --git a/docs/exploration-and-organization/exploration.md b/docs/exploration-and-organization/exploration.md
index 46272baa971..dd06132119a 100644
--- a/docs/exploration-and-organization/exploration.md
+++ b/docs/exploration-and-organization/exploration.md
@@ -8,7 +8,7 @@ redirect_from:
## See what your teammates have made
-As long as you're not the very first user in your team's Metabase, the easiest way to start exploring your data is by looking at dashboards, charts, and lists that your teammates have already created. The best place to start is by checking out any dashboards that might be pinned on your home page, or in [collections][collections] you have access to.
+As long as you're not the first user in your team's Metabase, the easiest way to start exploring your data is by looking at dashboards, charts, and lists that your teammates have already created. The best place to start is by checking out any dashboards that might be pinned on your home page, or in [collections][collections] you have access to.
## Command palette
@@ -32,7 +32,7 @@ To filter your search results, hit `cmd/ctrl + k` to bring up the command palett
![Search results](./images/search-results.png)
-Searches take into account items’ titles, descriptions, and other metadata — you can even search the contents of your SQL queries. For example, you can search for things like `SELECT escape_pod FROM mothership` and find that one question you worked on six months ago. The results will display which collection each item is saved in, what kind of object it is, and whether it’s pinned. Note that you'll only ever see items in that are in collections you have permission to view.
+Searches consider items' titles, descriptions, and other metadata — you can even search the contents of your SQL queries. For example, you can search for things like `SELECT escape_pod FROM mothership` and find that one question you worked on six months ago. The results will display which collection each item is saved in, what kind of object it is, and whether it's pinned. Note that you'll only ever see items in that are in collections you have permission to view.
You can search by:
diff --git a/docs/installation-and-operation/accessibility.md b/docs/installation-and-operation/accessibility.md
index 9f6e85eecf1..7bfb475b45d 100644
--- a/docs/installation-and-operation/accessibility.md
+++ b/docs/installation-and-operation/accessibility.md
@@ -9,7 +9,7 @@ redirect_from:
While we're working to make a product that is easy to use and inclusive to all, we're not yet fully compliant with [the U.S. federal government's Section 508 standards](https://www.section508.gov/) or the [Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/) at Level AA. We expect to build on our current state in the future, and as of today these are some general notes on our state of compliance:
-- **Navigation and screen readers:** Most information is presented in a way to ensure it can be accessed by screen readers. Some interactive elements are not operable for screen reader users.
+- **Navigation and screen readers:** Most information should be accessible to screen readers. Some interactive elements are not operable for screen reader users.
- **Non-text content:** While Metabase provides text alternatives for most non-text elements, some functional images either lack descriptions or have incomplete alt text.
- **Keyboard navigation:** Most form elements are keyboard-accessible, but certain interactive components, such as custom controls and non-modal dialogs, may lack full keyboard operability.
- **Focus management:** Some interactive elements lack a visible focus indicator. A few hidden interactive elements receive the keyboard focus.
diff --git a/docs/installation-and-operation/information-collection.md b/docs/installation-and-operation/information-collection.md
index e9c6ff9a86c..4e6979db126 100644
--- a/docs/installation-and-operation/information-collection.md
+++ b/docs/installation-and-operation/information-collection.md
@@ -10,7 +10,7 @@ If you're self-hosting Metabase and you've opted in to provide us with anonymous
**[We only collect anonymous Metabase data; we don't collect any of your data](https://www.metabase.com/security).** We don't collect any usernames, emails, server IPs, database details of any kind, or any personally identifiable information (PII).
-This anonymous data helps us understand how people are actually using Metabase, which in turn helps us prioritize what to work on next.
+This anonymous data helps us understand how people are using Metabase, which in turn helps us prioritize what to work on next.
## Examples of the anonymous data we collect and how we use it
@@ -54,7 +54,7 @@ The token validation request includes:
- Count of internal users
- Count of email domains
- Count of embedded dashboards and questions
-- Types of embedding (static, interactive, Embedded analtyics SDK, Embedded analytics JS)
+- Types of embedding (static, interactive, Embedded analytics SDK, Embedded analytics JS)
- Site UUID (just an identifier for your Metabase)
- Metabase version
- Query execution timestamp (last UTC day)
diff --git a/docs/installation-and-operation/monitoring-metabase.md b/docs/installation-and-operation/monitoring-metabase.md
index 3bad8eb41a5..1602fc566c0 100644
--- a/docs/installation-and-operation/monitoring-metabase.md
+++ b/docs/installation-and-operation/monitoring-metabase.md
@@ -82,7 +82,7 @@ When running into memory-related issues, typically the first question to ask is:
### Thread dump
-Another useful picture of a running Metabase system is a Thread Dump. In cases when Metabase appears stalled or extremely slow, a thread dump will indicate what each thread is executing (or blocked on) for that specific point in time Collect a thread dump via the "Threads" tab:
+Another useful picture of a running Metabase system is a Thread Dump. In cases when Metabase appears stalled or slow, a thread dump will indicate what each thread is executing (or blocked on) for that specific point in time Collect a thread dump via the "Threads" tab:
![threaddump](images/ThreadDump.png)
diff --git a/docs/installation-and-operation/running-metabase-on-azure.md b/docs/installation-and-operation/running-metabase-on-azure.md
index e722e28819d..903d4ea026f 100644
--- a/docs/installation-and-operation/running-metabase-on-azure.md
+++ b/docs/installation-and-operation/running-metabase-on-azure.md
@@ -49,7 +49,7 @@ From the Azure Management console homepage, create a new resource. This time sea
![Azure PostgreSQL](images/AZDatabase.png)
-In the next page you will have to select the way you will use the service. Choose **Single server** for now, which is a good starting point, but take into account that this will create just one instance of PostgreSQL that will be your single point of failure.
+In the next page you will have to select the way you will use the service. Choose **Single server** for now, which is a good starting point, but consider that this will create just one instance of PostgreSQL that will be your single point of failure.
On the next screen, select or enter the following:
@@ -121,7 +121,7 @@ Return to the application configuration page and click on **Settings** -> **Conf
You'll need to add the [environment Variables](../configuring-metabase/environment-variables.md) for connecting Metabase to its [PostgreSQL Application Database](../installation-and-operation/configuring-application-database.md#postgresql). Make sure that you use the full **MB_DB_CONNECTION_URI**.
-Also, take into account that the username in Azure PostgreSQL is `user@name_of_your_database_engine` so in this case the entire connection uri would be as follows:
+Also, consider that the username in Azure PostgreSQL is `user@name_of_your_database_engine` so in this case the entire connection uri would be as follows:
```
postgresql://databasePrivateIPAddress:port/postgres?user=user@name_of_your_database_engine&password=configuredpassword&ssl=true&sslmode=required
@@ -182,7 +182,7 @@ In your Azure web app, visit **Settings** -> **Custom domains** to use a custom
Azure provides an easy way to increase the server's capacity by doing a Scale-up. Simply choose a pricing tier with more RAM and CPU count and restart the instance. This approach is easier than scaling out and you should choose this option first before scaling out.
-For a highly-available Metabase deployment, you can tell your web app to scale-out (more servers serving the application in parallel). Simply go to Scale-out and use the slider to ask for more instances, or use a custom autoscaling policy (like using more servers during your work hours and fewer during off hours).
+For a highly available Metabase deployment, you can tell your web app to scale-out (more servers serving the application in parallel). Simply go to Scale-out and use the slider to ask for more instances, or use a custom autoscaling policy (like using more servers during your work hours and fewer during off hours).
### CORS
diff --git a/docs/installation-and-operation/running-metabase-on-podman.md b/docs/installation-and-operation/running-metabase-on-podman.md
index c665b525b4e..2685ddfdc08 100644
--- a/docs/installation-and-operation/running-metabase-on-podman.md
+++ b/docs/installation-and-operation/running-metabase-on-podman.md
@@ -117,7 +117,7 @@ If you've already been running Metabase with the default application database (H
### Running Metabase as a service
-We can use the [systemd](https://systemd.io/) initialization service to register a Metabase service that can be started and stopped automatically. Before executing this process, ensure that the Metabase container is operational. Then, utilize Podman's built-in feature to generate the service file as follows:
+We can use the [systemd](https://systemd.io/) initialization service to register a Metabase service that can be started and stopped automatically. Before executing this process, ensure that the Metabase container is operational. Then, use Podman's built-in feature to generate the service file as follows:
```
sudo podman generate systemd --new --name metabase > metabase.service
diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.md
index ee98973b02a..fab5551e8d1 100644
--- a/docs/installation-and-operation/serialization.md
+++ b/docs/installation-and-operation/serialization.md
@@ -9,7 +9,7 @@ redirect_from:
{% include plans-blockquote.html feature="Serialization" %}
-Once you really get rolling with Metabase, it's often the case that you'll have more than one Metabase instance spun up. You might have a couple of testing or development instances and a few production ones, or maybe you have a separate Metabase per office or region.
+Once you get rolling with Metabase, it's often the case that you'll have more than one Metabase instance spun up. You might have a couple of testing or development instances and a few production ones, or maybe you have a separate Metabase per office or region.
To help you out in situations like this, Metabase has a serialization feature which lets you create an _export_ of the contents of a Metabase that can then be _imported_ into one or more Metabases.
diff --git a/docs/installation-and-operation/upgrading-metabase.md b/docs/installation-and-operation/upgrading-metabase.md
index a256d96f34f..eec75bb79ae 100644
--- a/docs/installation-and-operation/upgrading-metabase.md
+++ b/docs/installation-and-operation/upgrading-metabase.md
@@ -14,7 +14,7 @@ This page covers how to upgrade to a new Metabase release.
## Upgrading Metabase Cloud
-If you're on a [Metabase Cloud](https://www.metabase.com/pricing/) plan, we'll upgrade your Metabase automatically with each new release; no action needed on your end ([unless you're using the Embedded analytics SDK](#instances-using-the-embedded-analtyics-sdk-on-metabase-cloud-must-request-an-upgrade)).
+If you're on a [Metabase Cloud](https://www.metabase.com/pricing/) plan, we'll upgrade your Metabase automatically with each new release; no action needed on your end ([unless you're using the Embedded analytics SDK](#instances-using-the-embedded-analytics-sdk-on-metabase-cloud-must-request-an-upgrade)).
How soon we upgrade you depends on the type of release:
@@ -23,7 +23,7 @@ How soon we upgrade you depends on the type of release:
Cloud customers can request an early upgrade by emailing support at [email protected]. Include the URL of the Metabase you want us to upgrade.
-### Instances using the Embedded analtyics SDK on Metabase Cloud must request an upgrade
+### Instances using the Embedded analytics SDK on Metabase Cloud must request an upgrade
If you're using the [Embedded analytics SDK](../embedding/sdk/introduction.md) on Metabase Cloud, we pin your version so that it doesn't upgrade automatically, as you should test the changes before upgrading.
@@ -144,7 +144,7 @@ Durning a **minor version upgrade** (e.g., 54.1 to 54.2), the new Metabase conta
In general, regular backups (especially backups before upgrading), are the best policy, so we recommend reverting to a backup of your application database to roll back an upgrade.
-But if you've made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the `migrate down` command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The `migrate down` command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you definitely remembered to generate before upgrading), and only using the `migrate down` command if you really need to keep changes made after your upgrade.
+But if you've made any change (adding new questions/dashboards, etc) since upgrading that you want to keep, you may be able to use the `migrate down` command to roll back your Metabase application database to support the previous Metabase version you were running. When Metabase upgrades to a new version, it runs migrations that may change the application database schema. The `migrate down` command undoes those schema changes. In general, we recommend restoring from a backup (the backup that you remembered to generate before upgrading), and only using the `migrate down` command if you need to keep changes made after your upgrade.
### Using the migrate down command
diff --git a/docs/people-and-groups/authenticating-with-saml.md b/docs/people-and-groups/authenticating-with-saml.md
index 43918c72a48..0ea3cff1811 100644
--- a/docs/people-and-groups/authenticating-with-saml.md
+++ b/docs/people-and-groups/authenticating-with-saml.md
@@ -11,7 +11,7 @@ redirect_from:
Integrating your SSO with Metabase allows you to:
- Provision a Metabase account when someone logs in to Metabase.
-- Automatically pass user attributes from your SSO to Metabase in order to power [row and column security](../permissions/row-and-column-security.md).
+- Automatically pass user attributes from your SSO to Metabase to power [row and column security](../permissions/row-and-column-security.md).
- Let people access Metabase without re-authenticating.
## Confirm the password for your Metabase admin account
@@ -82,7 +82,7 @@ Different IdPs use different names for the redirect URL. Here are some common ex
### User attributes
-Metabase will automatically log in people who've been authenticated by your SAML identity provider. In order to do so, the first assertion returned in the identity provider's SAML response _must_ contain attributes for each person's first name, last name, and email.
+Metabase will automatically log in people who've been authenticated by your SAML identity provider. To do so, the first assertion returned in the identity provider's SAML response _must_ contain attributes for each person's first name, last name, and email.
Most IdPs already include these assertions by default, but some (such as [Okta](./saml-okta.md)) must be configured to include them.
@@ -126,7 +126,7 @@ We recommend that you set this value to make your SAML configuration more secure
The SAML identity provider certificate is an encoded certificate that Metabase will use when connecting to the IdP URI. The certificate will look like a big blob of text that you'll want to copy and paste carefully — the spacing is important!
-Your IdP might have you download this certificate as a file (usually `.cer` or `.pem`), which you'll then need to open up in a text editor in order to copy the contents to then paste into the box in Metabase.
+Your IdP might have you download this certificate as a file (usually `.cer` or `.pem`), which you'll then need to open up in a text editor to copy the contents to then paste into the box in Metabase.
Note that your certificate text may include header and footer comments that look like `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`. These comments should be included when pasting your certificate text into Metabase.
diff --git a/docs/permissions/application.md b/docs/permissions/application.md
index 853f87864f0..73e9130bb54 100644
--- a/docs/permissions/application.md
+++ b/docs/permissions/application.md
@@ -43,4 +43,4 @@ This setting determines who can set up:
- [Dashboard subscriptions](../dashboards/subscriptions.md)
- [Alerts](../questions/alerts.md)
-People will need to be in groups with either view or edit access to the collection that contains the dashboard or question in order to set up alerts. See [Collection permissions](../permissions/collections.md).
+People will need to be in groups with either view or edit access to the collection that contains the dashboard or question to set up alerts. See [Collection permissions](../permissions/collections.md).
diff --git a/docs/permissions/collections.md b/docs/permissions/collections.md
index d517af716d7..6ccbeb4b026 100644
--- a/docs/permissions/collections.md
+++ b/docs/permissions/collections.md
@@ -50,7 +50,7 @@ There is one, important exception: when a group has their data permission set to
## Dashboards with questions from multiple collections
-If a dashboard includes questions saved to other collections, the group will need view or curate access to all of those collections in order to view those questions. If not, Metabase will apologize and tell you that you lack permissions to see the cards saved to the other collections.
+If a dashboard includes questions saved to other collections, the group will need view or curate access to all of those collections to view those questions. If not, Metabase will apologize and tell you that you lack permissions to see the cards saved to the other collections.
![Dashboard with questions from multiple collections, where the person is not in a group with access to one of the collections](./images/dashboard-no-permissions.png)
diff --git a/docs/permissions/no-self-service-deprecation.md b/docs/permissions/no-self-service-deprecation.md
index 9d6ad3ae301..c6a05025a8d 100644
--- a/docs/permissions/no-self-service-deprecation.md
+++ b/docs/permissions/no-self-service-deprecation.md
@@ -83,13 +83,13 @@ We could migrate the permissions like so:
| **View data** | Can view | ? | Blocked | Row and column security | Impersonated |
| **Create queries** | Query Builder only | No | No | Query Builder only | Query Builder only |
-We can't really make a call on what Group B's View data should be. If we switch it to **Can view**, the person won't be affected by the Blocked, Row and column security, or Impersonated settings in their other group. If we set it to **Blocked**, they could lose access to data that you think they should have access to. So we created an interim setting, `No self-service (legacy)` to manage this (temporarily) awkward transition.
+We can't make a call on what Group B's View data should be. If we switch it to **Can view**, the person won't be affected by the Blocked, Row and column security, or Impersonated settings in their other group. If we set it to **Blocked**, they could lose access to data that you think they should have access to. So we created an interim setting, `No self-service (legacy)` to manage this (temporarily) awkward transition.
### For some permission setups with groups that have "No self-service" and "Sandboxed" data access, you may need to create a new group to replicate the setup in 50 or higher
In Metabase 49, the (more permissive) "No self-service" data access couldn't override the (less permissive) "Sandboxed" access, you could set up Metabase 49 in ways that were difficult to reason about.
-In the new permission system starting in Metabase 50, more permissive settings _always_ override less permissive settings. This consistent behavior makes permissions a _lot_ easier to reason about. One consequence of this improvement, however, is that in order to recreate certain permissions setups when upgrading to Metabase 50, you may need to create an _additional_ group.
+In the new permission system starting in Metabase 50, more permissive settings _always_ override less permissive settings. This consistent behavior makes permissions easier to reason about. One consequence of this improvement, however, is that to recreate certain permissions setups when upgrading to Metabase 50, you may need to create an _additional_ group.
For example, let's say you have two groups in Metabase 49 under the old data access permission, the All users group and the Foo group.
@@ -100,7 +100,7 @@ For example, let's say you have two groups in Metabase 49 under the old data acc
This data access setup in 49 would allow people to view questions and dashboards in collections they have access to. People in the Foo group, however, would get a sandboxed view of the items. In this case, the less permissive "Sandboxed" data access in the Foo group overrode the more permissive "No self-service" in the All users group.
-Starting with Metabase 50, however, more permissive settings _always_ override less permissive settings. So in order to keep Foo's sandboxes in tact, we'd need to make the All users group have a View data permission setting that is _less_ permissive than the "Sandboxed" setting. So we'll need to set the View data permission for All users to "Blocked."
+Starting with Metabase 50, however, more permissive settings _always_ override less permissive settings. So to keep Foo's sandboxes in tact, we'd need to make the All users group have a View data permission setting that is _less_ permissive than the "Sandboxed" setting. So we'll need to set the View data permission for All users to "Blocked."
But if you still want everyone else who _isn't_ in the Foo group to view items in collections they have access to, you'll need to create an additional group, Bar, that contains everyone _except for_ people in the Foo group, and grant that Bar group "Can view" access to the Sample database. The Bar group's "Can view" access will override the All Users group's "Blocked" setting, and they'll be able to view the questions and dashboards. Meanwhile, Foo group still has its sandboxes. Here's a summary of the settings for 50 that you'd need:
diff --git a/docs/questions/introduction.md b/docs/questions/introduction.md
index d0433ea74b0..b35c271ba77 100644
--- a/docs/questions/introduction.md
+++ b/docs/questions/introduction.md
@@ -52,7 +52,7 @@ Questions that live in a dashboard are only visible in that dashboard. These que
### Saving questions to collections
-Questions saved to a collection can be added to multiple dashboards. Moving a question from one collection to another collection won't have any effect on the dashboards the question has been added to. In order to save a question to a collection, you'll need to be in a group with [curate access](../permissions/collections.md#curate-access) to that collection.
+Questions saved to a collection can be added to multiple dashboards. Moving a question from one collection to another collection won't have any effect on the dashboards the question has been added to. To save a question to a collection, you'll need to be in a group with [curate access](../permissions/collections.md#curate-access) to that collection.
## Moving questions from collections to dashboards (and vice versa)
diff --git a/docs/questions/native-editor/writing-sql.md b/docs/questions/native-editor/writing-sql.md
index f88e021d9c2..75f91419138 100644
--- a/docs/questions/native-editor/writing-sql.md
+++ b/docs/questions/native-editor/writing-sql.md
@@ -84,7 +84,7 @@ If you or someone else wrote a SQL query that includes [variables][variable-glos
![SQL filter](../images/SQL-filter-widget.png)
-Writing SQL queries that use variables or parameters can be very powerful, but it's also a bit more advanced, so that topic has its own page if you'd like to [learn more](./sql-parameters.md).
+Writing SQL queries that use variables or parameters can be powerful, but it's also a bit more advanced, so that topic has its own page if you'd like to [learn more](./sql-parameters.md).
## Snippets
diff --git a/docs/questions/query-builder/expressions-list.md b/docs/questions/query-builder/expressions-list.md
index 2501decc722..40705e4fdc6 100644
--- a/docs/questions/query-builder/expressions-list.md
+++ b/docs/questions/query-builder/expressions-list.md
@@ -126,7 +126,7 @@ For an introduction to expressions, check out the [overview of custom expression
## Aggregations
-Aggregation expressions take into account all values in a field. They can only be used in the **Summarize** section of the query builder.
+Aggregation expressions consider all values in a field. They can only be used in the **Summarize** section of the query builder.
### Average
diff --git a/docs/questions/query-builder/expressions/converttimezone.md b/docs/questions/query-builder/expressions/converttimezone.md
index 606b8bed98a..bf0a96aa794 100644
--- a/docs/questions/query-builder/expressions/converttimezone.md
+++ b/docs/questions/query-builder/expressions/converttimezone.md
@@ -62,7 +62,7 @@ If **Source Time** is stored as a `timestamp without time zone`, you _must_ prov
convertTimezone([Source Time], 'EST', 'UTC')
```
-It's usually a good idea to label `convertTimezone` columns with the name of the target time zone (or add the target time zone to the metadata of a model). We promise this will make your life easier when someone inevitably asks why the numbers don't match.
+It's usually a good idea to label `convertTimezone` columns with the name of the target time zone (or add the target time zone to the metadata of a model). We promise this will make your life easier when someone inevitably questions why the numbers don't match.
If you're not getting the results that you expect:
diff --git a/docs/questions/query-builder/expressions/datetimediff.md b/docs/questions/query-builder/expressions/datetimediff.md
index 985336ebd38..432e41cb485 100644
--- a/docs/questions/query-builder/expressions/datetimediff.md
+++ b/docs/questions/query-builder/expressions/datetimediff.md
@@ -119,7 +119,7 @@ produces the same result as
datetimeDiff([Aging Start], [Aging End], "month")
```
-Yes, `DATEDIF` looks a bit wrong, but the spreadsheet function really is `DATEDIF()` with one "f", not `DATEDIFF()`.
+Yes, it's `DATEDIF` with one 'F'.
### Python
diff --git a/docs/questions/query-builder/expressions/now.md b/docs/questions/query-builder/expressions/now.md
index be96ac7062b..9e452ff9063 100644
--- a/docs/questions/query-builder/expressions/now.md
+++ b/docs/questions/query-builder/expressions/now.md
@@ -58,7 +58,7 @@ For more info about the way these data types behave in Metabase, see [Timezones]
## Limitations
-`now` might not actually be _now_ (in your local time) if you don't live in the same timezone as your Metabase [report time zone](../../../configuring-metabase/localization.md#report-timezone).
+`now` might not be _now_ (in your local time) if you don't live in the same timezone as your Metabase [report time zone](../../../configuring-metabase/localization.md#report-timezone).
If you need to compare `now` to a column in a different time zone, use [convertTimezone](./converttimezone.md) to shift both columns into the same time zone. For example:
diff --git a/docs/questions/query-builder/join.md b/docs/questions/query-builder/join.md
index 6231f0b2a4c..bc90a85165f 100644
--- a/docs/questions/query-builder/join.md
+++ b/docs/questions/query-builder/join.md
@@ -15,7 +15,7 @@ After you click the "Join Data" button to add a join step, you'll need to pick t
![Picking the data to join](../images/join-pick-data.png)
-Next, you'll need to pick the columns you want to join on. This means you pick a column from the first table and a column from the second table, and the join will stitch rows together where the value from the first column equals the value in the second column. A very common example is joining on an ID column in each table. If you pick a table to join where there's a foreign key relationship between the tables, Metabase will automatically pick those corresponding ID columns for you. At the end of your join step, there's a "Columns" button you can click to choose which columns you want to include from the joined data.
+Next, you'll need to pick the columns you want to join on. This means you pick a column from the first table and a column from the second table, and the join will stitch rows together where the value from the first column equals the value in the second column. A common example is joining on an ID column in each table. If you pick a table to join where there's a foreign key relationship between the tables, Metabase will automatically pick those corresponding ID columns for you. At the end of your join step, there's a "Columns" button you can click to choose which columns you want to include from the joined data.
By default, Metabase will do a left outer join, but you can click the Venn diagram icon to select a different type of join. Not all databases support all types of joins, so Metabase will only display the options supported by the database you're using.
diff --git a/docs/questions/visualizations/line-bar-and-area-charts.md b/docs/questions/visualizations/line-bar-and-area-charts.md
index a279ae26142..047ba9d4b39 100644
--- a/docs/questions/visualizations/line-bar-and-area-charts.md
+++ b/docs/questions/visualizations/line-bar-and-area-charts.md
@@ -44,7 +44,7 @@ By default, Metabase will automatically choose a good way to bin your results. B
## Settings for line, bar, and area charts
-These three charting types have very similar options, which are broken up into the following tabs. You can access these chart settings by clicking the **gear** icon in the lower left of the chart.
+These three charting types have similar options, which are broken up into the following tabs. You can access these chart settings by clicking the **gear** icon in the lower left of the chart.
- [Data settings](#data-settings)
- [Display settings](#display-settings)
diff --git a/docs/questions/visualizations/pivot-table.md b/docs/questions/visualizations/pivot-table.md
index 00fd3ac5807..8af3cca10d5 100644
--- a/docs/questions/visualizations/pivot-table.md
+++ b/docs/questions/visualizations/pivot-table.md
@@ -28,7 +28,7 @@ Pivot table is the only Metabase visualization type (besides the plain table, of
## How to create a pivot table
-To create a pivot table, you'll need to use the query builder. Currently, you can't build pivot tables for questions written in SQL, because Metabase would need to modify your SQL code in order to calculate subtotals. If you really need to use SQL, the workaround here is to create your question in two steps: first do all the complex things you need to do in SQL, save the results as a question, then use that saved SQL question as the starting point for a new query builder question which summarizes that data.
+To create a pivot table, you'll need to use the query builder. Currently, you can't build pivot tables for questions written in SQL, because Metabase would need to modify your SQL code to calculate subtotals. If you need to use SQL, the workaround here is to create your question in two steps: first do all the complex things you need to do in SQL, save the results as a question, then use that saved SQL question as the starting point for a new query builder question which summarizes that data.
1. Create a question in the query builder that has a summary with at least one breakout, for example "`Count` of orders by `Category` and `Month`".
@@ -102,4 +102,4 @@ There are special considerations when exporting pivot tables as XLSX files. See
- Pivot tables are only available for questions built with the query builder.
- The query builder question must have a summary block.
-If you must use SQL, and your SQL query doesn't have parameters, you can save that SQL query , then use its [results as the starting point](../native-editor/writing-sql.md#explore-sql-question-results-using-the-query-builder) for a query builder question in order to build a question. The trick here is to do your aggregation and grouping in the query builder. That is, use the SQL question to grab the raw data you want to work with (maybe [create a model](../../data-modeling/models.md)), then start a new question in the query builder to filter, summarize, and group that data.
+If you must use SQL, and your SQL query doesn't have parameters, you can save that SQL query , then use its [results as the starting point](../native-editor/writing-sql.md#explore-sql-question-results-using-the-query-builder) for a query builder question to build a question. The trick here is to do your aggregation and grouping in the query builder. That is, use the SQL question to grab the raw data you want to work with (maybe [create a model](../../data-modeling/models.md)), then start a new question in the query builder to filter, summarize, and group that data.
diff --git a/docs/questions/visualizations/visualizing-results.md b/docs/questions/visualizations/visualizing-results.md
index 5ecef7c1f31..c5697079154 100644
--- a/docs/questions/visualizations/visualizing-results.md
+++ b/docs/questions/visualizations/visualizing-results.md
@@ -36,7 +36,7 @@ To change how the answer to your question is displayed, click on the **Visualiza
![Visualization options](../images/VisualizeChoices.png)
-If a particular visualization doesn’t really make sense for your answer, that option will appear in the "Other charts" section. You can still select one of these other charts, though you might need to fiddle with the chart options to make the chart work with your data.
+If a particular visualization doesn't make sense for your answer, that option will appear in the "Other charts" section. You can still select one of these other charts, though you might need to fiddle with the chart options to make the chart work with your data.
Not sure which visualization type to use? Check out [Which chart should you use?](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/visualization/chart-guide)
diff --git a/docs/troubleshooting-guide/cant-see-tables.md b/docs/troubleshooting-guide/cant-see-tables.md
index 3b8d6015bdb..90a8c724b2b 100644
--- a/docs/troubleshooting-guide/cant-see-tables.md
+++ b/docs/troubleshooting-guide/cant-see-tables.md
@@ -39,7 +39,7 @@ Something may have changed on the database side (if you were previously connecte
## Check table access
-To make sure that your table is actually queryable by Metabase:
+To make sure that your table is queryable by Metabase:
1. Go to the Metabase [SQL editor](../questions/native-editor/writing-sql.md).
2. Look for your table:
diff --git a/docs/troubleshooting-guide/cant-send-email.md b/docs/troubleshooting-guide/cant-send-email.md
index bf577117ef9..da69f84e73d 100644
--- a/docs/troubleshooting-guide/cant-send-email.md
+++ b/docs/troubleshooting-guide/cant-send-email.md
@@ -22,9 +22,9 @@ Before any other troubleshooting, try sending a test email to isolate the proble
4. Verify that the email is delivered to your account.
5. If the message is not sent or an error message is displayed in Metabase, try to use the same account credentials in another email program and see if they work. See the logs for more detailed error by navigating to **Tools** and click **Logs** in the left sidebar.
-## Is the mail server actually sending the message?
+## Is the mail server sending the message?
-**Root cause:** Some email delivery services have very specific rules regarding valid "from" addresses, or have test modes that restrict delivery.
+**Root cause:** Some email delivery services have specific rules regarding valid "from" addresses, or have test modes that restrict delivery.
**Steps to take:**
diff --git a/docs/troubleshooting-guide/db-performance.md b/docs/troubleshooting-guide/db-performance.md
index af683851bed..475bf27f611 100644
--- a/docs/troubleshooting-guide/db-performance.md
+++ b/docs/troubleshooting-guide/db-performance.md
@@ -58,7 +58,7 @@ If someone or something creates 100 queries at the same time, this stampede of q
**Explanation**
-By default, Metabase makes regular sync and scan queries against your database to keep your tables up to date, get fresh values for filter dropdowns, and make helpful suggestions. If you've got a very large database, you can choose to trigger these queries manually instead of on a schedule.
+By default, Metabase makes regular sync and scan queries against your database to keep your tables up to date, get fresh values for filter dropdowns, and make helpful suggestions. If you've got a large database, you can choose to trigger these queries manually instead of on a schedule.
## Questions that use number, date, or timestamp columns
diff --git a/docs/troubleshooting-guide/filters.md b/docs/troubleshooting-guide/filters.md
index 14efa7631f6..83706068c63 100644
--- a/docs/troubleshooting-guide/filters.md
+++ b/docs/troubleshooting-guide/filters.md
@@ -26,7 +26,7 @@ If a dashboard filter is giving you no results or the wrong results:
If a question filter is giving you no results or the wrong results:
1. Make sure the question includes the column you want to filter on.
-2. Check that the column actually contains the value(s) you're filtering on. You can do this by:
+2. Check that the column contains the value(s) you're filtering on. You can do this by:
- sorting number or date columns,
- creating a "contains" filter for string columns, or
- asking your database admin.
@@ -72,7 +72,7 @@ If you're not a Metabase admin, you might have to ask your admin to help you wit
**Explanation**
-Metabase needs to know the data type of a column in order to present you with a curated selection of filter types. Sometimes these columns are mistyped---if a column stores your numbers as strings, Metabase will only show you text or category filters (with options like "is", "is not") instead of number filters (with options like "greater than", "less than").
+Metabase needs to know the data type of a column to present you with a curated selection of filter types. Sometimes these columns are mistyped---if a column stores your numbers as strings, Metabase will only show you text or category filters (with options like "is", "is not") instead of number filters (with options like "greater than", "less than").
Timestamps, in particular, are the root of all evil, so please be patient with your Metabase admin (or yourself!) when trying to get the data type right.
diff --git a/docs/troubleshooting-guide/known-issues.md b/docs/troubleshooting-guide/known-issues.md
index c31b2b7c5e3..139fa6f664f 100644
--- a/docs/troubleshooting-guide/known-issues.md
+++ b/docs/troubleshooting-guide/known-issues.md
@@ -38,7 +38,7 @@ If the functionality you're looking for simply doesn't exist (i.e., it hasn't su
> Add additional keywords to the search bar above the list of results. Hit Enter/Return to run the search.
- > Click **Sort** and select the thumbs up emoji (👍) to view the most highly requested features.
+ > Click **Sort** and select the thumbs up emoji (👍) to view the most requested features.
4. If you find a feature request that matches what you want to do, add a thumbs up emoji to help the team prioritize it.
diff --git a/docs/troubleshooting-guide/linked-filters.md b/docs/troubleshooting-guide/linked-filters.md
index 7b7a6a3e406..49de434518c 100644
--- a/docs/troubleshooting-guide/linked-filters.md
+++ b/docs/troubleshooting-guide/linked-filters.md
@@ -10,11 +10,11 @@ You have created a [linked filter][linked-filter-gloss] so that (for example) if
- your linked filter seems to have no effect, or
- your linked filter widget does not display a dropdown of filtered values.
-If you are having problems with a regular [filter widget][filter-widget-gloss], please see [this guide](./filters.md). In order to fix problems with linked filters, you need a clear understanding of how they work:
+If you are having problems with a regular [filter widget][filter-widget-gloss], please see [this guide](./filters.md). To fix problems with linked filters, you need a clear understanding of how they work:
## Does a connected dashboard card use a SQL variable?
-**Root cause**: Native/SQL questions must have a [field filter](../questions/native-editor/field-filters.md) variable in order to be linked. Regular SQL variables won't work.
+**Root cause**: Native/SQL questions must have a [field filter](../questions/native-editor/field-filters.md) variable to be linked. Regular SQL variables won't work.
**Steps to take**:
@@ -42,7 +42,7 @@ See [Limitations of linking filters](../dashboards/linked-filters.md#limitations
1. Remove the existing linkage and create a new one in the opposite direction.
-## Do some rows actually satisfy the full filter condition?
+## Do some rows satisfy the full filter condition?
**Root cause:** There aren't any rows that satisfy all the conditions in a linked filter. Continuing with the city and state example, if you manually enter the name of a city that isn't in the selected state, no record will satisfy both conditions.
diff --git a/docs/troubleshooting-guide/my-dashboard-is-slow.md b/docs/troubleshooting-guide/my-dashboard-is-slow.md
index e9938bc6808..ae5dd84991c 100644
--- a/docs/troubleshooting-guide/my-dashboard-is-slow.md
+++ b/docs/troubleshooting-guide/my-dashboard-is-slow.md
@@ -18,7 +18,7 @@ First, you'll want to make sure your browser is on friendly terms with Metabase:
**Explanation**
-A dashboard with 50 cards is almost always going to be slower than 5 dashboards with 10 cards. Metabase displays a dashboard by refreshing all of the questions on it (that is, re-executing all of the queries against your database). Your data warehouse may try to run these queries at the same time to return the results faster, however, these queries can actually compete with each other and slow things down (like having too many programs open on your computer at once).
+A dashboard with 50 cards is almost always going to be slower than 5 dashboards with 10 cards. Metabase displays a dashboard by refreshing all of the questions on it (that is, re-executing all of the queries against your database). Your data warehouse may try to run these queries at the same time to return the results faster, however, these queries can compete with each other and slow things down (like having too many programs open on your computer at once).
Aside from running faster, a small and focused dashboard is also easier for people to understand without getting overwhelmed. For more tips, check out our article on [BI dashboard best practices](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/dashboards/bi-dashboard-best-practices).
@@ -57,7 +57,7 @@ When someone loads a question or a dashboard in a static embed, however, that qu
**Explanation**
-When you update your question to use a minimal number of rows or columns (or switch your question to use a smaller table, such as a summary table) your database can spend less time scanning those records in order to return your results. Narrowing the scope of your question is especially important to think about if you're starting from someone else's saved question or model, because you might not need all of the data that the original creator decided to include.
+When you update your question to use a minimal number of rows or columns (or switch your question to use a smaller table, such as a summary table) your database can spend less time scanning those records to return your results. Narrowing the scope of your question is especially important to think about if you're starting from someone else's saved question or model, because you might not need all of the data that the original creator decided to include.
If all of your dashboards are slow, you might be limited by the performance of a particular data source. In that case, we recommend teaming up with your database admin to [Troubleshoot database performance](./db-performance.md).