The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:
TypeScript analyticsbibusiness-intelligencebusinessintelligenceclojuredashboarddatadata-analysisdata-visualizationdatabasemetabasemysqlpostgrespostgresqlreportingslacksql-editorvisualization
docs - minor edits (#65021)
Jeff Bruemmer20c7cb44a33d
diff --git a/docs/cloud/cloud-vs-self-hosting.md b/docs/cloud/cloud-vs-self-hosting.mdindex cdac182ad39..a52aff29a1d 100644--- a/docs/cloud/cloud-vs-self-hosting.md+++ b/docs/cloud/cloud-vs-self-hosting.md@@ -49,4 +49,4 @@ Metabase also has a paid version that ships with all of the bells and whistles (- [Metabase Pro](https://www.metabase.com/product/pro)- [Metabase Enterprise](https://www.metabase.com/product/enterprise)-You can self-host this paid version, or have have us host it for you on Metabase Cloud for no additional cost. We don't charge more because we believe you'll have such a better experience that it'll be easier for us to support you.+You can self-host this paid version, or have us host it for you on Metabase Cloud for no additional cost. We don't charge more because we believe you'll have such a better experience that it'll be easier for us to support you.diff --git a/docs/cloud/how-billing-works.md b/docs/cloud/how-billing-works.mdindex e02214693c5..10b13674e60 100644--- a/docs/cloud/how-billing-works.md+++ b/docs/cloud/how-billing-works.md@@ -26,7 +26,7 @@ Companies with large number of users can talk to sales about our [Enterprise plaThough we bill you monthly, we calculate how much you owe each day. So, say you're on the [Starter plan](https://www.metabase.com/pricing/). Your monthly bill would include:- $100 flat payment for the month. This payment additionally covers the first five people who use your Metabase that month. If you have fewer than five people using your Metabase, your bill will still be $100 that month.-- Each additional person costs \$6, prorated for how many days their [accounts were available](#what-counts-as-a-user-account) that month. So if an account only existed for the last 10 days of your 30 day billing period, you'd only be charged for those 10 days, not for the full 30 days. Same goes if you deactivated an account prior to the end of the billing period, you'll only be charged for the days when the account was available for use during that billing period. Basically, you only ever pay for all accounts in your Metabase that haven't been deactivated yet.+- Each additional person costs \$6, prorated for how many days their [accounts were available](#what-counts-as-a-user-account) that month. So if an account only existed for the last 10 days of your 30 day billing period, you'd only be charged for those 10 days, not for the full 30 days. Same goes if you deactivated an account before the end of the billing period, you'll only be charged for the days when the account was available for use during that billing period. Basically, you only ever pay for all accounts in your Metabase that haven't been deactivated yet.## How annual billing worksdiff --git a/docs/developers-guide/api-changelog.md b/docs/developers-guide/api-changelog.mdindex 9eea3388972..3e07898db49 100644--- a/docs/developers-guide/api-changelog.md+++ b/docs/developers-guide/api-changelog.md@@ -98,7 +98,7 @@ title: API changelogWhen setting `archived` to `false`, you may optionally also provide a `collection_id` (for Dashboards or Cards) or a`parent_id` (for Collections). In this case, the entity will be re-parented to the specified Collection when it ismoved from the Trash. If a new `collection_id` or `parent_id` is not provided, the entity will be moved back to its- original location if possible. If this is not possible (for example, the original location is also in the Trash) an+ original location if possible. If this is impossible (for example, the original location is also in the Trash) anerror will occur.- `/api/metric`@@ -130,7 +130,7 @@ NOTE: These endpoint changes were added in 0.49.3, and a bug in `GET /api/embed/The above endpoints now accept the `format_rows` query parameter. It is an optional boolean parameter that will default to `true` if not included in the request.When `format_rows` is `true`, the export will have formatting applied such that the values match what they appear as in the app.- When `format_rows` is `false`, formatting is not applied and exports will behave as they did prior to 0.49.0.+ When `format_rows` is `false`, formatting is not applied and exports will behave as they did before 0.49.0.The value of `format_rows` has no effect when exporting xlsx files.diff --git a/docs/developers-guide/driver-changelog.md b/docs/developers-guide/driver-changelog.mdindex 645947c27ef..b9b82caedd1 100644--- a/docs/developers-guide/driver-changelog.md+++ b/docs/developers-guide/driver-changelog.md@@ -106,7 +106,7 @@ title: Driver interface changelog- Added a feature `:multi-level-schema` for drivers that support hierarchical levels between database and schema. Such as databricks' catalog. Defaults to false.-- Added the multi-method `adjust-schema-qualification` that allows drivers to to qualify, or unqualify table schemas based on enabling or disabling multi-level-schema support. Drivers may need to implement `sql.qp/->honeysql [driver ::h2x/identifier]` to properly quote fully qualified schemas.+- Added the multi-method `adjust-schema-qualification` that allows drivers to qualify, or unqualify table schemas based on enabling or disabling multi-level-schema support. Drivers may need to implement `sql.qp/->honeysql [driver ::h2x/identifier]` to properly quote fully qualified schemas.- Added the multi-method `float-dbtype` which returns the name of the float type we coerce to for coercion strategies and the `float()` custom expression function.@@ -247,7 +247,7 @@ title: Driver interface changelogfor better performance when saving Questions. Refer to the method docstring for more information and where to findan example implementation.-- Prior to 0.51.0, to generate SQL queries with inline parameters, Metabase would generate a parameterized SQL string,+- Before 0.51.0, to generate SQL queries with inline parameters, Metabase would generate a parameterized SQL string,then attempt to parse the SQL replace and replace `?` placeholders with inline values from the driver method`metabase.driver.sql.util.unprepare/unprepare-value`. In 0.51.0+, Metabase instead generates these queries usingHoney SQL 2's `:inline` option, eliminating the need to parse and replace `?` placeholders. As such, the@@ -325,7 +325,7 @@ title: Driver interface changelog- Similarly, `metabase.test.data.sql-jdbc.execute/execute-sql!` and helper functions like`metabase.test.data.sql-jdbc.execute/sequentially-execute-sql!` are now called with a `java.sql.Connection`instead of both a `DatabaseDefinition` and either `:server` or `:db` _context_; the appropriate connection type is- created automatically and passed in in the calling code. Update your method implementations and usages+ created automatically and passed in the calling code. Update your method implementations and usagesaccordingly.- Added method `metabase.test.data.interface/dataset-already-loaded?` to check if a test dataset has already been@@ -458,7 +458,7 @@ title: Driver interface changelog- New feature `:identifiers-with-spaces` has been added to indicate where a driver supports identifiers like table orcolumn names that contains a space character. Defaults to `false`.-- New feature `:uuid-type` has been added to indicate that this database is able to distinguish and filter against UUIDs.+- New feature `:uuid-type` has been added to indicate that this database can distinguish and filter against UUIDs.Only a few database support native UUID types. The default is `false`.## Metabase 0.49.22@@ -582,7 +582,7 @@ title: Driver interface changelognew function takes a Field as returned by `lib.metadata/field`, i.e. a `kebab-case` map.- Tests should try to avoid using any of the `with-temp` helpers or application database objects; instead, use the- metadata functions above and and the helper _metadata providers_ in `metabase.lib`, `metabase.lib.test-util`, and+ metadata functions above and the helper _metadata providers_ in `metabase.lib`, `metabase.lib.test-util`, and`metabase.query-processor.test-util` for mocking them, such as `mock-metadata-provider`,`metabase-provider-with-cards-for-queries`, `remap-metadata-provider`, and `merged-mock-metadata-provider`.@@ -837,7 +837,7 @@ differences between the library versions.#### Breaking Changes in 0.46.0 related to the Honey SQL 2 transition-**Note: these breaking changes will hopefully be fixed before 0.46.0 ships. This will be updated if they are.**+**Note: we expect these breaking changes to be fixed before 0.46.0 ships. This will be updated if they are.**The classes `metabase.util.honeysql_extensions.Identifer` and `metabase.util.honeysql_extensions.TypedHoneySQLForm`have been moved to `metabase.util.honey_sql_1.Identifer` and `metabase.util.honey_sql_1.TypedHoneySQLForm`,diff --git a/docs/documents/introduction.md b/docs/documents/introduction.mdindex a11719b7936..3a6fc73aec0 100644--- a/docs/documents/introduction.md+++ b/docs/documents/introduction.md@@ -139,7 +139,7 @@ Documents work best for:Dashboards work best for:-- Regular analysis. Numbers you want to keep an eye on every day, week, or month.+- Regular analysis. Numbers you want to monitor every day, week, or month.- Filtering results across multiple charts.- More control over presentation.diff --git a/docs/embedding/embedded-analytics-js.md b/docs/embedding/embedded-analytics-js.mdindex a3c34033f54..57d6d41c221 100644--- a/docs/embedding/embedded-analytics-js.md+++ b/docs/embedding/embedded-analytics-js.md@@ -59,7 +59,7 @@ The exact customization options you see will depend on what type of entity you'r-You'll also be be able to pick brand, text, and background color used for all your embeds. To configure other colors (e.g. secondary colors, query builder colors etc), as well as font, you can specify a [theme](#theming) in your embed code snippet.+You'll also be able to pick brand, text, and background color used for all your embeds. To configure other colors (e.g. secondary colors, query builder colors etc), as well as font, you can specify a [theme](#theming) in your embed code snippet.All the customization options you select in this interactive flow will be reflected in the parameter values in the embed code, so you'll be able to adjust them later by editing the embed snippet.@@ -129,7 +129,7 @@ Here's an example of a script:Note the `defer` attribute and the reference to your Metabase URL in the script that loads `embed.js` library.-If you're embedding multiple entities on the same page, you only need to include the `<script>` tags once globally.+If you're embedding multiple entities in a single page, you only need to include the `<script>` tags once globally.You can also generate the code snippet for Embedded Analytics JS interactively in Metabase through **Admin > Embedding > Setup guide > Embed in your code**. Check out the [quickstart](#quickstart).diff --git a/docs/embedding/public-links.md b/docs/embedding/public-links.mdindex 8792324dc1a..3b01bed222c 100644--- a/docs/embedding/public-links.md+++ b/docs/embedding/public-links.md@@ -9,7 +9,7 @@ redirect_from:> Only admins can create public links and iframes.-Admins can create and share public links (URLs) for questions and dashboards. People can view them as standalone destinations (URLs) or as embedded iframes in another page or app. In both cases, the public item will display static (view-only) results of your question or dashboard, so visitors won't be able to drill-down into the underlying data on their own.+Admins can create and share public links (URLs) for questions and dashboards. People can view them as standalone destinations (URLs) or as embedded iframes in another page or app. In both cases, the public item will display static (view-only) results of your question or dashboard, so visitors won't be able to drill down into the underlying data on their own.## Create a public link for a questiondiff --git a/docs/embedding/sdk/quickstart-with-sample-app.md b/docs/embedding/sdk/quickstart-with-sample-app.mdindex 727a5675616..2119245b343 100644--- a/docs/embedding/sdk/quickstart-with-sample-app.md+++ b/docs/embedding/sdk/quickstart-with-sample-app.md@@ -102,7 +102,7 @@ From any Metabase page, click on the **gear** icon in the upper right and selectTurn on:-- Embedded analytics SDK (it's in in the **Modular** section)+- Embedded analytics SDK (it's in the **Modular** section)- Static embeddingOtherwise, this whole thing is hopeless.diff --git a/docs/embedding/sdk/upgrade.md b/docs/embedding/sdk/upgrade.mdindex ee5142318fa..9faff2a268f 100644--- a/docs/embedding/sdk/upgrade.md+++ b/docs/embedding/sdk/upgrade.md@@ -51,7 +51,7 @@ yarn add @metabase/embedding-sdk-react@{next-major-version-number}-stableSee more on [SDK versions](./version.md).-### If there are deprecations or breaking changes changes, make the necessary changes to your application code+### If there are deprecations or breaking changes, make the necessary changes to your application codeDeprecations or breaking changes are rare, but if you do need to make changes, we'll mention it in the release notes for the new major version and have docs that walk you through the changes.diff --git a/docs/exploration-and-organization/start.md b/docs/exploration-and-organization/start.mdindex 8bacbdff33e..eee73f7dc34 100644--- a/docs/exploration-and-organization/start.md+++ b/docs/exploration-and-organization/start.md@@ -26,7 +26,7 @@ View changes to a question, dashboard or model and revert to previous versions.## [Delete and restore items](./delete-and-restore.md)-Move outdated outdated questions, models, and dashboards to trash, or delete them permanently.+Move outdated questions, models, and dashboards to trash, or delete them permanently.## [Data reference](./data-model-reference.md)diff --git a/docs/installation-and-operation/running-metabase-on-docker.md b/docs/installation-and-operation/running-metabase-on-docker.mdindex ef43707fef4..786a3020173 100644--- a/docs/installation-and-operation/running-metabase-on-docker.md+++ b/docs/installation-and-operation/running-metabase-on-docker.md@@ -117,7 +117,7 @@ If you've already been running Metabase with the default application database (HHere's an example `docker-compose.yml` file for running Metabase with a PostgreSQL database `metabaseappdb`:-> This is an example file and and is not meant to be used when running Metabase in a production environment. Please refer to our guide about [How to run Metabase in production](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production)+> This is an example file and is not meant to be used when running Metabase in a production environment. Please refer to our guide about [How to run Metabase in production](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production)```ymlservices:@@ -343,7 +343,7 @@ We currently support the following [environment variables](../configuring-metabaIn order for the Metabase container to read the files and use the contents as a secret, the environment variable name needs to be appended with a "\_FILE" as explained above.-> This is an example file and and is not meant to be used when running Metabase in a production environment. Please refer to our guide about [How to run Metabase in production](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production).+> This is an example file and is not meant to be used when running Metabase in a production environment. Please refer to our guide about [How to run Metabase in production](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production).## Troubleshootingdiff --git a/docs/installation-and-operation/running-metabase-on-podman.md b/docs/installation-and-operation/running-metabase-on-podman.mdindex 965b7b4e49a..c665b525b4e 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. Prior to 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, utilize Podman's built-in feature to generate the service file as follows:```sudo podman generate systemd --new --name metabase > metabase.servicediff --git a/docs/people-and-groups/managing.md b/docs/people-and-groups/managing.mdindex 6c606ee3d61..17752545067 100644--- a/docs/people-and-groups/managing.md+++ b/docs/people-and-groups/managing.md@@ -50,7 +50,7 @@ To add a user attribute manually:4. Click **+ Add an attribute**.5. Add the name of the user attribute under "Key". For example, "Department".6. Add the value that applies to the specific person. For example, "Engineering".-7. Optional: [create a group](#creating-a-group) to organize people who will get get row and column security.+7. Optional: [create a group](#creating-a-group) to organize people who will get row and column security.8. Add the person to the group.You can also sync user attributes from your identity provider [via SSO](./start.md#authentication).diff --git a/docs/permissions/impersonation.md b/docs/permissions/impersonation.mdindex 65f7385504c..fc51e499244 100644--- a/docs/permissions/impersonation.md+++ b/docs/permissions/impersonation.md@@ -47,7 +47,7 @@ For impersonation access to work, you'll first need to set up roles in your data### Set up Metabase database connection for impersonation-Impersonation uses database roles to run queries on your database, but there still needs to be a default role that that will be used to run operations like [sync, scans, and fingerprinting](../databases/sync-scan.md). So the user account that Metabase uses to [connect to your database](../databases/connecting.md) should have access to everything in that database that any Metabase group may need access to, as that database user account is what Metabase uses to sync table information.+Impersonation uses database roles to run queries on your database, but there still needs to be a default role that will be used to run operations like [sync, scans, and fingerprinting](../databases/sync-scan.md). So the user account that Metabase uses to [connect to your database](../databases/connecting.md) should have access to everything in that database that any Metabase group may need access to, as that database user account is what Metabase uses to sync table information.You can then create roles in the database that have more restrictive access to the database (like row-level or table-level security). When the role is passed to the database using impersonation, the engine will return a subset of the data, or restrict the query altogether.@@ -119,7 +119,7 @@ People in one group can have different attribute values, but must have the same1. In Metabase, hit Cmd/Ctrl + K to bring up the command palette and search for **Permissions**, or go directly to **Admin settings** > **Permissions** > **Data**.-2. Select the group that you want to to associate with the database role you created.+2. Select the group that you want to associate with the database role you created.3. Select the database to configure access to.diff --git a/docs/questions/query-builder/expressions/cumulative.md b/docs/questions/query-builder/expressions/cumulative.mdindex b2c506693ff..a400ef8a0d1 100644--- a/docs/questions/query-builder/expressions/cumulative.md+++ b/docs/questions/query-builder/expressions/cumulative.md@@ -61,7 +61,7 @@ If you use a datetime dimension in the **Group by** block, Metabase will accumul-If there are multiple datetime dimensions (including multiple groupings by the same datetime column), Metabase will accumulate along the the more granular dimension, regardless of their order. For example, if you're grouping by "Created At: Month" and "Viewed At: Week", Metabase will accumulate along "Viewed At: Week".+If there are multiple datetime dimensions (including multiple groupings by the same datetime column), Metabase will accumulate along the more granular dimension, regardless of their order. For example, if you're grouping by "Created At: Month" and "Viewed At: Week", Metabase will accumulate along "Viewed At: Week".diff --git a/docs/questions/query-builder/expressions/week.md b/docs/questions/query-builder/expressions/week.mdindex 3acb4881e71..7b68ce9fe83 100644--- a/docs/questions/query-builder/expressions/week.md+++ b/docs/questions/query-builder/expressions/week.md@@ -91,5 +91,5 @@ Here's an incomplete list of example functions:| -------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------- || Postgres | `EXTRACT(WEEK FROM TIMESTAMP created_at)` | ISO algorithm || MySQL | `WEEKOFYEAR("2017-06-15")` | The first day of the week is Monday and the first week of the year has more than 3 days. Alternative functions exist. |-| BigQuery | `EXTRACT(WEEK FROM DATE ticreated_at)` | Weeks numbered from 0. Dates prior to the first Sunday of the year are in week 0. Alternative functions exist. |+| BigQuery | `EXTRACT(WEEK FROM DATE ticreated_at)` | Weeks numbered from 0. Dates before the first Sunday of the year are in week 0. Alternative functions exist. || Redshift | `DATE_PART(week, TIMESTAMP created_at)` | ISO algorithm |diff --git a/docs/questions/visualizations/funnel.md b/docs/questions/visualizations/funnel.mdindex a4e15e1a34a..7fdc104972c 100644--- a/docs/questions/visualizations/funnel.md+++ b/docs/questions/visualizations/funnel.md@@ -36,7 +36,7 @@ By default, Metabase will present steps in the same order as they appear in theTo create a query with a result that has the shape required for a funnel chart, you'll probably need to summarize your data.-If your (original, unaggregated) data already contains a field with the the step for every data point, you can build a simple query with a breakout by steps:+If your (original, unaggregated) data already contains a field with the step for every data point, you can build a simple query with a breakout by steps:diff --git a/docs/questions/visualizations/map.md b/docs/questions/visualizations/map.mdindex 19ab38e719b..0cce86c373b 100644--- a/docs/questions/visualizations/map.md+++ b/docs/questions/visualizations/map.md@@ -2,7 +2,7 @@title: Mapsredirect_from:- /docs/latest/questions/sharing/visualizations/maps-description: "Maps in Metabase allow you to visualize geographical data either using coordinates or by region. Metabase gives you three types of maps : pin map for unaggregated data, grid map for histograms, and region map for distributions by regions like countries or states. You can also create custom maps."+description: "Maps in Metabase allow you to visualize geographic data either using coordinates or by region. Metabase gives you three types of maps : pin map for unaggregated data, grid map for histograms, and region map for distributions by regions like countries or states. You can also create custom maps."---# Maps@@ -13,7 +13,7 @@ Metabase has three types of map visualization:- [**Grid map**](#grid-map) for distributing a large number of points over a specified area.- [**Region map**](#region-maps) for data broken out by regions, like countries or states. Metabase comes with two built-in maps, but you can upload your own custom regions.-When you select the **Map** visualization setting, Metabase will automatically try and pick the best kind of map to use based on the table or result set, as long as the columns with the geographical data have the [right metadata](../../data-modeling/metadata-editing.md).+When you select the **Map** visualization setting, Metabase will automatically try and pick the best kind of map to use based on the table or result set, as long as the columns with the geographic data have the [right metadata](../../data-modeling/metadata-editing.md).@@ -21,7 +21,7 @@ When you select the **Map** visualization setting, Metabase will automatically t## Pin map-Pin maps display markers or tiles for individual data points on the map. They work best for displaying small amounts of unaggregated geographical data.+Pin maps display markers or tiles for individual data points on the map. They work best for displaying small amounts of unaggregated geographic data.### Pin map data shape@@ -59,11 +59,11 @@ To change the pin type:By default, maps can't display more than 2,000 individual unaggregated data points, regardless of the pin type. This limit is the same for every chart displaying unaggregated data in Metabase. To increase the number of data points rendered on charts based on unaggregated queries, you can use the environment variable [`MB_UNAGGREGATED_QUERY_ROW_LIMIT`](../../configuring-metabase/environment-variables.md#mb_unaggregated_query_row_limit). This setting will affect data points on _all_ charts—not just the pin maps—so increasing the limit too much could significantly slow down your Metabase and your browswer.-If you need to display a large number of geographical data points, consider using a grid map to display the distribution instead.+If you need to display a large number of geographic data points, consider using a grid map to display the distribution instead.## Grid map-Grid map is an aggregated version of the pin map — like a heatmap for the distribution of pins. Grid map breaks the the map into a grid based on latitude/longitude, and then colors each grid cell based on how many data points fall in it.+Grid map is an aggregated version of the pin map — like a heatmap for the distribution of pins. Grid map breaks the map into a grid based on latitude/longitude, and then colors each grid cell based on how many data points fall in it.diff --git a/docs/questions/visualizations/pie-or-donut-chart.md b/docs/questions/visualizations/pie-or-donut-chart.mdindex 9ad59d170dc..8e536a509e1 100644--- a/docs/questions/visualizations/pie-or-donut-chart.md+++ b/docs/questions/visualizations/pie-or-donut-chart.md@@ -14,7 +14,7 @@ A **pie chart** can be used when breaking out a metric by a single dimension. InPie charts can be used to visualize a metric as part of a whole. Sunburst charts can be used to visualize hierarchical or nested data, or display multiple levels of categorization.-Pie and sunburst charts work best when when the number of possible breakout values is small, like accounts by plan. These charts should only be used to visualize metrics that add up to 100% (like count or sum of total).+Pie and sunburst charts work best when the number of possible breakout values is small, like accounts by plan. These charts should only be used to visualize metrics that add up to 100% (like count or sum of total).Pie charts should be used to communicate a general sense of the relative sizes of breakouts. If precise comparison is important so people can see the exact differences between values, or you have more than a few breakouts (like customers per country), it's usually better to use a bar or row chart.diff --git a/docs/questions/visualizations/pivot-table.md b/docs/questions/visualizations/pivot-table.mdindex f77a8565fe4..00fd3ac5807 100644--- a/docs/questions/visualizations/pivot-table.md+++ b/docs/questions/visualizations/pivot-table.md@@ -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 does not 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 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.diff --git a/docs/questions/visualizations/progress-bar.md b/docs/questions/visualizations/progress-bar.mdindex 23640380dc0..4c1b98a159d 100644--- a/docs/questions/visualizations/progress-bar.md+++ b/docs/questions/visualizations/progress-bar.md@@ -12,7 +12,7 @@ redirect_from:## When to use a progress bar-Progress bars are useful when you want to show the movement of a metric toward a goal, like assessing performance of a KPI, or tracking the percentage of of completion on a project.+Progress bars are useful when you want to show the movement of a metric toward a goal, like assessing performance of a KPI, or tracking the percentage of completion on a project.Progress bars give you an option to set up an alert whenever the result of a question reaches the goal set in the progress bar settings. See [Progress bar alerts](../alerts.md#progress-bar-alerts).diff --git a/docs/questions/visualizations/tooltips.md b/docs/questions/visualizations/tooltips.mdindex 729ff2f9c2a..320418415b5 100644--- a/docs/questions/visualizations/tooltips.md+++ b/docs/questions/visualizations/tooltips.md@@ -26,6 +26,6 @@ Or you could display one of the metrics on the chart, and include the other metrRemoving a metric will give you the option to add it as an additional metric to the tooltip. In the visualization settings, click on the **Display** tab, and add **Additional tooltip metrics**. Only metrics included in the summarization step of the question are available to add to the tooltip.-+Here we've kept the count on the chart, but now when you hover over a bar on the chart, the tooltip also includes the relevant average.