docs: Tiny fixes

Author: igorlukanin

docs/pages/guides/recipes/queries/pagination.mdx

@@ -20,7 +20,7 @@ We have the following data model:
 
 ```yaml
 cubes:
-  - name: Orders
+  - name: orders
     sql_table: orders
 
     measures:
@@ -38,7 +38,7 @@ cubes:
 ```
 
 ```javascript
-cube(`Orders`, {
+cube(`orders`, {
   sql_table: `orders`,
 
   measures: {

docs/pages/product/caching/running-in-production.mdx

@@ -377,10 +377,67 @@ It also requires the M [Cube Store Worker tier](/product/deployment/cloud/pricin
 You can provide, rotate, or drop your own [customer-managed keys][ref-cmk] (CMK)
 for Cube Store via the <Btn>Encryption Keys</Btn> page in Cube Cloud.
 
+## Troubleshooting
+
+### Heavy pre-aggregations
+
+When building some pre-aggregations, you might encounter the following error:
+
+```
+Error: Error during create table: CREATE TABLE <REDACTED>
+Error: Query execution timeout after 10 min of waiting
+```
+
+It means that your pre-aggregation is too heavy and takes too long to build.
+
+As a temporary solution, you can increase the timeout for all queies that Cube
+runs against your data source via the `CUBEJS_DB_QUERY_TIMEOUT` environment variable.
+
+However, it is recommended that you optimize your pre-aggregations instead:
+
+* Use an export bucket if your [data source][ref-data-sources] supports it. Cube will then load the pre-aggregation data in a much more efficient way.
+* Use [partitions][ref-pre-agg-partitions]. Cube will then run a separate query to build each partition.
+* Build pre-aggregations [incrementally][ref-pre-agg-incremental]. Cube will then build only the necessary partitions with each pre-aggregation refresh.
+* Set an appropriate [build range][ref-pre-agg-build-range] if you don't need to query the whole date range. Cube will then include only the necessary data in the pre-aggregation.
+* Check that your pre-aggregation includes only necessary dimensions. Each additional dimension usually increases the volume of the pre-aggregation data.
+  * If you include a high cardinality dimension, Cube needs to store a lot of data in the pre-aggregation. For example, if you include the primary key into the pre-aggregation, Cube will effectively need to store a copy of the original table in the pre-aggregation, which is rarely useful.
+  * If a single pre-aggregation is used by queries with different sets of dimensions, consider creating separate pre-aggregations for each set of dimensions. This way, Cube will only include necessary data in each pre-aggregation.
+* Check if you have a heavy calculation in the [`sql` expression][ref-cube-sql] of your cubes (rather than a simple `sql_table` reference). If it's the case, you can build an additional [`original_sql` pre-aggregation][ref-pre-agg-original-sql] and [instruct][ref-pre-agg-use-original-sql] Cube to use it when building other pre-aggregations for this cube.
+
+### MinIO
+
+When using MinIO for persistent storage, you might encounter the following error:
+
+```
+Error: Error during upload of <REDACTED>
+File <REDACTED> can't be listed after upload.
+Either there's Cube Store cluster misconfiguration,
+or storage can't provide the required consistency.
+```
+
+Most likely, it happens because MinIO is not providing strong consistency guarantees,
+as required for Cube Store's [persistent storage](#persistent-storage).
+You can either try configuring MinIO to provide strong consistency or switch to
+using S3 or GCS.
+
+<WarningBox>
+
+The support for MinIO as persistent storage in Cube Store was contributed by the community.
+It's not supported by Cube or the vendor.
+
+</WarningBox>
+
 
 [link-wsl2]: https://docs.microsoft.com/en-us/windows/wsl/install-win10
 [ref-caching-partitioning]: /product/caching/using-pre-aggregations#partitioning
 [ref-config-env]: /reference/configuration/environment-variables
 [link-parquet-encryption]: https://parquet.apache.org/docs/file-format/data-pages/encryption/
 [link-aes]: https://en.wikipedia.org/wiki/Advanced_Encryption_Standard
-[ref-cmk]: /product/workspace/encryption-keys
+[ref-cmk]: /product/workspace/encryption-keys
+[ref-data-sources]: /product/configuration/data-sources
+[ref-pre-agg-partitions]: /product/caching/using-pre-aggregations#partitioning
+[ref-pre-agg-incremental]: /reference/data-model/pre-aggregations#incremental
+[ref-pre-agg-build-range]: /reference/data-model/pre-aggregations#build_range_start-and-build_range_end
+[ref-cube-sql]: /reference/data-model/cube#sql
+[ref-pre-agg-original-sql]: /reference/data-model/pre-aggregations#original_sql
+[ref-pre-agg-use-original-sql]: /reference/data-model/pre-aggregations#use_original_sql_pre_aggregations

docs/pages/product/configuration/data-sources/pinot.mdx

@@ -3,7 +3,7 @@ redirect_from:
   - /config/databases/pinot
 ---
 
-# Pinot
+# Apache Pinot
 
 [Apache Pinot][link-pinot] is a real-time distributed OLAP datastore purpose-built
 for low-latency, high-throughput analytics, and perfect for user-facing analytical
@@ -14,6 +14,9 @@ workloads. [StarTree][link-startree] is a fully-managed platform for Pinot.
 - The hostname for the [Pinot][pinot] broker
 - The port for the [Pinot][pinot] broker
 
+With the current implementation of the Pinot driver, you have to enable the
+[multi-stage query engine][link-pinot-msqe] in your Pinot cluster.
+
 ## Setup
 
 <ReferenceBox>
@@ -93,6 +96,7 @@ Cube does not require any additional configuration to enable SSL as Pinot connec
 
 [link-pinot]: https://pinot.apache.org/
 [pinot]: https://docs.pinot.apache.org/
+[link-pinot-msqe]: https://docs.pinot.apache.org/reference/multi-stage-engine
 [pinot-docs-approx-agg-fns]:
   https://docs.pinot.apache.org/users/user-guide-query/query-syntax/how-to-handle-unique-counting
 [ref-recipe-enable-ssl]:

docs/pages/product/configuration/data-sources/vertica.mdx

@@ -1,5 +1,8 @@
 # Vertica
 
+[OpenText Analytics Database][opentext-adb] (Vertica) is a columnar database
+designed for big data analytics.
+
 ## Prerequisites
 
 - The hostname for the [Vertica][vertica] database server
@@ -41,6 +44,7 @@ To enable SSL-encrypted connections between Cube and Verica, set the
 configure custom certificates, please check out [Enable SSL Connections to the
 Database][ref-recipe-enable-ssl].
 
+[opentext-adb]: https://www.opentext.com/products/analytics-database?o=vert
 [vertica]: https://www.vertica.com/documentation/vertica/all/
 [ref-recipe-enable-ssl]:/guides/recipes/data-sources/using-ssl-connections-to-data-source
 

docs/pages/product/data-modeling/concepts/working-with-joins.mdx

@@ -70,7 +70,7 @@ cubes:
         sql: company
         type: string
 
-  - name: Orders
+  - name: orders
     # ...
 
     dimensions:

docs/pages/product/deployment/cloud/deployments.mdx

@@ -59,7 +59,7 @@ make sure to run a few queries in [Playground][ref-playground].
 ## Deployment overview
 
 The&nbsp;<Btn>Overview</Btn> page of each deployment provides a high-level
-summary if its components and state:
+summary of its components and state:
 * API endpoints with URLs and connection instructions.
 * Allocated resources in line with the [deployment type][ref-deployment-types].
 * Activity log of the most recent events.

docs/pages/product/faqs/troubleshooting.mdx

@@ -34,8 +34,6 @@ details which will help narrow down the scope of the issue.
 If you see `has a key that already exists in Name index` message, it means that your
 multitenancy setup is missing the `pre_aggregations_schema` configuration setting in your `cube.py` file. 
 
-If you see `Error: Query execution timeout after 10 min of waiting` message, it means pre-aggregation is too large to be built.
-
 For any other error types, feel free to reach out to us in our support chat.
 
 ## Warning: There were queries in these timezones which are not added in the CUBEJS_SCHEDULED_REFRESH_TIMEZONES environment variable.

docs/pages/reference/frontend/cubejs-client-react.mdx

@@ -4,7 +4,7 @@
 
 ## `useCubeQuery`
 
->  **useCubeQuery**‹**TData**›(**query**: Query | Query[], **options?**: [UseCubeQueryOptions](#use-cube-query-options)): *[UseCubeQueryResult](#use-cube-query-result)‹Query, TData›*
+>  **useCubeQuery**‹**TData**›(**query**: Query | Query[], **options?**: [UseCubeQueryOptions](#usecubequeryoptions)): *[UseCubeQueryResult](#usecubequeryresulttquery-tdata)‹Query, TData›*
 
 A React hook for executing Cube queries
 ```js

docs/pages/reference/rest-api.mdx

@@ -165,7 +165,9 @@ Response
   - `meta` - Custom metadata
   - `measures` - Array of measures in this cube/view
   - `dimensions` - Array of dimensions in this cube/view
+  - `hierarchies` - Array of hierarchies in this cube
   - `segments` - Array of segments in this cube/view
+  - `folders` - Array of folders in this view
   - `connectedComponent` - An integer representing a join relationship. If the same value is returned for two cubes, then there is
     at least one join path between them.