diff --git a/docs/pages/product/workspace/query-history.mdx b/docs/pages/product/workspace/query-history.mdx
index da74f474cb882..377b6aaaed0ba 100644
--- a/docs/pages/product/workspace/query-history.mdx
+++ b/docs/pages/product/workspace/query-history.mdx
@@ -67,9 +67,12 @@ while Top Queries will show the most-frequently executed queries:
### Filtering
-You can also use filters to find problematic queries; you can filter by query
-duration, cache status, whether the query was accelerated, and by failing
-queries:
+You can use filters to find queries by various criteria:
+- duration,
+- cache status,
+- whether the query was accelerated with pre-aggregations,
+- whether the query yielded an error,
+- API type.
❯ next to any query:
+In the table, all queries are shown in their collapsed view by default.
+To see an expanded view of a query, click on the ❯ button
+to the left of any query.
-This will show us how long the query took, whether the query was accelerated,
-and even view the raw query by clicking ❮/❯:
-
-
+Check the columns to see the details:
+- **Query** shows a representation of a query, similar to the REST API
+[query format][ref-query-format]. In case of the SQL API, if the query is
+not coercible to a REST API query, raw SQL is shown "as is."
+- **API** shows the API type that was used to run the query: REST API via
+HTTP transport, REST API via WebSockets, GraphQL API, or SQL API.
+- **Duration** shows how long the query took, and the **bolt** indicates
+whether the query was accelerated with pre-aggregations, in-memory cache, etc.
+- **Time** shows the time the query was run at.
To drill down on a specific query, click it to see more information.
@@ -198,3 +205,4 @@ while the query is in the query execution queue:
[ref-deployment-api-instance]: /product/deployment#api-instances
[ref-deployment-refresh-worker]: /product/deployment#refresh-worker
[ref-workspace-sqlrunner]: /product/workspace/sql-runner
+[ref-query-format]: /product/apis-integrations/rest-api/query-format
\ No newline at end of file