docs: update links in documentation

Author: hassankhan

docs/content/Caching/Running-in-Production.mdx

@@ -5,25 +5,24 @@ category: Caching
 menuOrder: 4
 ---
 
-Cube.js makes use of two different kinds of cache:
+Cube makes use of two different kinds of cache:
 
 - Redis, for in-memory storage of query results
 - Cube Store for storing pre-aggregations
 
-In development, Cube.js uses in-memory storage on the server. In production, we
+In development, Cube uses in-memory storage on the server. In production, we
 **strongly** recommend running Redis as a separate service.
 
 <WarningBox>
 
-Cube Store [will replace
-Redis][replace-redis] for in-memory cache and queue management in late
-2022.
+Cube Store [will replace Redis][replace-redis] for in-memory cache and queue
+management in late 2022.
 
 </WarningBox>
 
-Cube Store is enabled by default when running Cube.js in development mode. In
+Cube Store is enabled by default when running Cube in development mode. In
 production, Cube Store **must** run as a separate process. The easiest way to do
-this is to use the official Docker images for Cube.js and Cube Store.
+this is to use the official Docker images for Cube and Cube Store.
 
 <InfoBox>
 
@@ -41,13 +40,13 @@ docker run -p 3030:3030 cubejs/cubestore
 <InfoBox>
 
 Cube Store can further be configured via environment variables. To see a
-complete reference, please consult the [Cube Store section of the Environment
-Variables reference][ref-config-env].
+complete reference, please consult the `CUBESTORE_*` environment variables in
+the [Environment Variables reference][ref-config-env].
 
 </InfoBox>
 
-Next, run Cube.js and tell it to connect to Cube Store running on `localhost`
-(on the default port `3030`):
+Next, run Cube and tell it to connect to Cube Store running on `localhost` (on
+the default port `3030`):
 
 ```bash
 docker run -p 4000:4000 \
@@ -56,8 +55,8 @@ docker run -p 4000:4000 \
   cubejs/cube
 ```
 
-In the command above, we're specifying `CUBEJS_CUBESTORE_HOST` to let Cube.js
-know where Cube Store is running.
+In the command above, we're specifying `CUBEJS_CUBESTORE_HOST` to let Cube know
+where Cube Store is running.
 
 You can also use Docker Compose to achieve the same:
 
@@ -87,7 +86,8 @@ services:
 
 ## Architecture
 
-Deep dive on Cube Store architecture can be found in [this presentation](https://docs.google.com/presentation/d/1oQ-koloag0UcL-bUHOpBXK4txpqiGl41rxhgDVrw7gw/).
+Deep dive on Cube Store architecture can be found in
+[this presentation](https://docs.google.com/presentation/d/1oQ-koloag0UcL-bUHOpBXK4txpqiGl41rxhgDVrw7gw/).
 
 ## Scaling
 
@@ -123,8 +123,10 @@ reference][ref-config-env].
 | `CUBESTORE_WORKER_PORT` | -                  | Yes                |
 | `CUBESTORE_META_ADDR`   | -                  | Yes                |
 
-`CUBESTORE_WORKERS` and `CUBESTORE_META_ADDR` variables should be set with stable addresses, which should not change.
-You can use stable DNS names and put load balancers in front of your worker and router instances to fulfill stable name requirements in environments where stable IP addresses can't be guaranteed.
+`CUBESTORE_WORKERS` and `CUBESTORE_META_ADDR` variables should be set with
+stable addresses, which should not change. You can use stable DNS names and put
+load balancers in front of your worker and router instances to fulfill stable
+name requirements in environments where stable IP addresses can't be guaranteed.
 
 <InfoBox>
 
@@ -133,7 +135,8 @@ recommend using [partitioned pre-aggregations][ref-caching-partitioning].
 
 </InfoBox>
 
-A sample Docker Compose stack for the single machine setting this up might look like:
+A sample Docker Compose stack for the single machine setting this up might look
+like:
 
 ```yaml
 version: '2.2'
@@ -188,11 +191,13 @@ services:
 
 ## Replication and High Availability
 
-The open-source version of Cube Store doesn't support replicating any of its nodes.
-The router node and every worker node should always have only one instance copy if served behind the load balancer or service address.
-Replication will lead to undefined behavior of the cluster, including connection errors and data loss.
-If any cluster node is down, it'll lead to a complete cluster outage.
-If Cube Store replication and high availability are required, please consider using Cube Cloud.
+The open-source version of Cube Store doesn't support replicating any of its
+nodes. The router node and every worker node should always have only one
+instance copy if served behind the load balancer or service address. Replication
+will lead to undefined behavior of the cluster, including connection errors and
+data loss. If any cluster node is down, it'll lead to a complete cluster outage.
+If Cube Store replication and high availability are required, please consider
+using Cube Cloud.
 
 ## Storage
 
@@ -204,14 +209,17 @@ Cube Store can only use one type of remote storage at runtime.
 
 Cube Store makes use of a separate storage layer for storing metadata as well as
 for persisting pre-aggregations as Parquet files. Cube Store [can be configured
-to use either AWS S3 or Google Cloud Storage][ref-config-env-cloud-storage]. 
-If desired, local path on the server can also be used in case all Cube Store cluster nodes are co-located on a single machine.
+to use either AWS S3 or Google Cloud Storage][ref-config-env]. If desired, local
+path on the server can also be used in case all Cube Store cluster nodes are
+co-located on a single machine.
 
 <WarningBox>
 
-Cube Store requires strong consistency guarantees from underlying distributed storage.
-AWS S3, Google Cloud Storage, and Azure Blob Storage (Cube Cloud only) are the only known implementations that provide strong consistency.
-Using other implementations in production is discouraged and can lead to consistency and data corruption errors.
+Cube Store requires strong consistency guarantees from underlying distributed
+storage. AWS S3, Google Cloud Storage, and Azure Blob Storage (Cube Cloud only)
+are the only known implementations that provide strong consistency. Using other
+implementations in production is discouraged and can lead to consistency and
+data corruption errors.
 
 </WarningBox>
 
@@ -247,9 +255,12 @@ services:
 
 ### Local Storage
 
-Separately from remote storage, Cube Store requires local scratch space to warm up partitions by downloading Parquet files before querying them.
-By default, this directory should be mounted to `.cubestore/data` dir inside contained and can be configured by [CUBESTORE_DATA_DIR][ref-config-env] environment variable.
-It is advised to use local SSDs for this scratch space to maximize querying performance.
+Separately from remote storage, Cube Store requires local scratch space to warm
+up partitions by downloading Parquet files before querying them. By default,
+this directory should be mounted to `.cubestore/data` dir inside contained and
+can be configured by [CUBESTORE_DATA_DIR][ref-config-env] environment variable.
+It is advised to use local SSDs for this scratch space to maximize querying
+performance.
 
 ### <--{"id" : "Storage"}--> AWS
 
@@ -271,10 +282,9 @@ default.
 
 Cube Store currently does not have any in-built authentication mechanisms. For
 this reason, we recommend running your Cube Store cluster on a network that only
-allows requests from the Cube.js deployment.
+allows requests from the Cube deployment.
 
 [link-wsl2]: https://docs.microsoft.com/en-us/windows/wsl/install-win10
 [ref-caching-partitioning]: /caching/using-pre-aggregations#partitioning
-[ref-config-env]: /reference/environment-variables#cube-store
-[ref-config-env-cloud-storage]: /reference/environment-variables#cloud-storage
+[ref-config-env]: /reference/environment-variables
 [replace-redis]: https://cube.dev/blog/replacing-redis-with-cube-store

docs/content/Caching/Using-Pre-Aggregations.mdx

@@ -5,8 +5,8 @@ category: Caching
 menuOrder: 3
 ---
 
-Pre-aggregations is a powerful way to speed up your Cube.js queries. There are
-many configuration options to consider. Please make sure to also check [the
+Pre-aggregations is a powerful way to speed up your Cube queries. There are many
+configuration options to consider. Please make sure to also check [the
 Pre-Aggregations reference in the data schema section][ref-schema-ref-preaggs].
 
 ## Refresh Strategy
@@ -81,15 +81,15 @@ cube(`Orders`, {
 });
 ```
 
-When `every` and `sql` are used together, Cube.js will run the query from the
-`sql` property on an interval defined by the `every` property. If the query
-returns new results, then the pre-aggregation will be refreshed.
+When `every` and `sql` are used together, Cube will run the query from the `sql`
+property on an interval defined by the `every` property. If the query returns
+new results, then the pre-aggregation will be refreshed.
 
 ## Rollup Only Mode
 
-To make Cube.js _only_ serve requests from pre-aggregations, the
-[`CUBEJS_ROLLUP_ONLY` environment variable][ref-config-env-general] can be set
-to `true` on an API instance. This will prevent serving data on API requests
+To make Cube _only_ serve requests from pre-aggregations, the
+[`CUBEJS_ROLLUP_ONLY`][ref-config-env-rolluponly] environment variable can be
+set to `true` on an API instance. This will prevent serving data on API requests
 from the source database.
 
 <WarningBox>
@@ -435,8 +435,8 @@ or [Export Bucket][self-export-bucket] strategies instead.
 
 ### <--{"id" : "Pre-Aggregation Build Strategies"}--> Batching
 
-Batching is a more performant strategy where Cube.js sends compressed CSVs for
-Cube Store to ingest.
+Batching is a more performant strategy where Cube sends compressed CSVs for Cube
+Store to ingest.
 
 <div style="text-align: center">
   <img
@@ -447,9 +447,8 @@ Cube Store to ingest.
   />
 </div>
 
-The performance scales to the amount of memory available on the Cube.js
-instance. Batching is automatically enabled for any databases that can support
-it.
+The performance scales to the amount of memory available on the Cube instance.
+Batching is automatically enabled for any databases that can support it.
 
 ### <--{"id" : "Pre-Aggregation Build Strategies"}--> Export bucket
 
@@ -483,30 +482,40 @@ refer to the database-specific documentation for more details:
 - [Snowflake][ref-connect-db-snowflake]
 
 When using cloud storage, it is important to correctly configure any data
-retention policies to clean up the data in the export bucket as Cube.js does not
+retention policies to clean up the data in the export bucket as Cube does not
 currently manage this. For most use-cases, 1 day is sufficient.
 
 ## Streaming pre-aggregations
 
-Streaming pre-aggregations are different from traditional pre-aggregations in the way they are being updated. Traditional pre-aggregations follow the “pull” model — Cube **pulls updates** from the data source based on some cadence and/or condition. Streaming pre-aggregations follow the “push” model — Cube **subscribes to the updates** from the data source and always keeps pre-aggregation up to date. 
+Streaming pre-aggregations are different from traditional pre-aggregations in
+the way they are being updated. Traditional pre-aggregations follow the “pull”
+model — Cube **pulls updates** from the data source based on some cadence and/or
+condition. Streaming pre-aggregations follow the “push” model — Cube
+**subscribes to the updates** from the data source and always keeps
+pre-aggregation up to date.
 
-You don’t need to define `refreshKey` for streaming pre-aggregations. Whether pre-aggregation is streaming or not is defined by the data source. 
+You don’t need to define `refreshKey` for streaming pre-aggregations. Whether
+pre-aggregation is streaming or not is defined by the data source.
 
-Currently, Cube supports only one streaming data source - [ksqlDB](/config/databases/ksqldb). All pre-aggregations where data source is ksqlDB are streaming. 
+Currently, Cube supports only one streaming data source -
+[ksqlDB](/config/databases/ksqldb). All pre-aggregations where data source is
+ksqlDB are streaming.
 
-We’re working on supporting streaming pre-aggregations for the following data sources -
+We’re working on supporting streaming pre-aggregations for the following data
+sources -
 
 - Materialize
 - Flink SQL
 - Spark Streaming
 
-Please [let us know](https://cube.dev/contact) if you are interested in early access to any of these drivers or would like Cube to support any other SQL streaming engine.
+Please [let us know](https://cube.dev/contact) if you are interested in early
+access to any of these drivers or would like Cube to support any other SQL
+streaming engine.
 
 [ref-caching-in-mem-default-refresh-key]: /caching#default-refresh-keys
 [ref-config-db]: /config/databases
 [ref-config-driverfactory]: /config#driver-factory
-[ref-config-env]: /reference/environment-variables#cube-store
-[ref-config-env-general]: /config#general
+[ref-config-env-rolluponly]: /reference/environment-variables#cubejs-rollup-only
 [ref-config-extdriverfactory]: /config#external-driver-factory
 [ref-connect-db-athena]: /config/databases/aws-athena
 [ref-connect-db-redshift]: /config/databases/aws-redshift

docs/content/Configuration/Databases/Google-BigQuery.mdx

@@ -133,7 +133,6 @@ BigQuery connections are made over HTTPS.
   /caching/using-pre-aggregations#pre-aggregation-build-strategies
 [ref-config-multiple-ds-decorating-env]:
   /config/multiple-data-sources#configuring-data-sources-with-environment-variables-decorated-environment-variables
-[ref-env-var]: /reference/environment-variables#database-connection
 [ref-schema-ref-types-formats-countdistinctapprox]:
   /schema/reference/types-and-formats#count-distinct-approx
 [self-preaggs-batching]: #batching

docs/content/Configuration/Databases/Snowflake.mdx

@@ -127,7 +127,6 @@ connections are made over HTTPS.
 [google-cloud-storage]: https://cloud.google.com/storage
 [ref-caching-using-preaggs-build-strats]:
   /caching/using-pre-aggregations#pre-aggregation-build-strategies
-[ref-env-var]: /reference/environment-variables#database-connection
 [ref-schema-ref-types-formats-countdistinctapprox]:
   /schema/reference/types-and-formats#count-distinct-approx
 [self-preaggs-batching]: #batching

docs/content/Cube-Cloud/Configuration/Connecting-to-Databases.mdx

@@ -7,7 +7,7 @@ redirect_from:
   - /cloud/configuration/connecting-to-databases
 ---
 
-You can connect all Cube.js supported databases to your Cube Cloud deployment.
+You can connect all Cube supported databases to your Cube Cloud deployment.
 
 <div style="text-align: center">
   <img
@@ -32,12 +32,12 @@ vendors.
 
 The following fields are required when creating an AWS Athena connection:
 
-| Field                     | Description                                                       | Examples                                   |
-| ------------------------- | ----------------------------------------------------------------- | ------------------------------------------ |
-| **AWS Access Key ID**     | The AWS Access Key ID to use for database connections             | `AKIAXXXXXXXXXXXXXXXX`                     |
-| **AWS Secret Access Key** | The AWS Secret Access Key to use for database connections         | `asd+/Ead123456asc23ASD2Acsf23/1A3fAc56af` |
-| **AWS Region**            | The AWS region of the Cube.js deployment                          | `us-east-1`                                |
-| **S3 Output Location**    | The S3 path to store query results made by the Cube.js deployment | `s3://my-output-bucket/outputs/`           |
+| Field                     | Description                                                    | Examples                                   |
+| ------------------------- | -------------------------------------------------------------- | ------------------------------------------ |
+| **AWS Access Key ID**     | The AWS Access Key ID to use for database connections          | `AKIAXXXXXXXXXXXXXXXX`                     |
+| **AWS Secret Access Key** | The AWS Secret Access Key to use for database connections      | `asd+/Ead123456asc23ASD2Acsf23/1A3fAc56af` |
+| **AWS Region**            | The AWS region of the Cube deployment                          | `us-east-1`                                |
+| **S3 Output Location**    | The S3 path to store query results made by the Cube deployment | `s3://my-output-bucket/outputs/`           |
 
 <div style="text-align: center">
   <img
@@ -167,7 +167,7 @@ Add the following environment variables:
 
 | Environment Variable | Description                                                                                                                                                                                                 | Example                                  |
 | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
-| `CUBEJS_DB_SSL`      | If `true`, enables SSL encryption for database connections from Cube.js                                                                                                                                     | `true`, `false`                          |
+| `CUBEJS_DB_SSL`      | If `true`, enables SSL encryption for database connections from Cube                                                                                                                                        | `true`, `false`                          |
 | `CUBEJS_DB_SSL_CA`   | The contents of a CA bundle in PEM format, or a path to one. For more information, check the `options.ca` property for TLS Secure Contexts [in the Node.js documentation][link-nodejs-tls-options]          | A valid CA bundle or a path to one       |
 | `CUBEJS_DB_SSL_CERT` | The contents of an SSL certificate in PEM format, or a path to one. For more information, check the `options.cert` property for TLS Secure Contexts [in the Node.js documentation][link-nodejs-tls-options] | A valid SSL certificate or a path to one |
 | `CUBEJS_DB_SSL_KEY`  | The contents of a private key in PEM format, or a path to one. For more information, check the `options.key` property for TLS Secure Contexts [in the Node.js documentation][link-nodejs-tls-options]       | A valid SSL private key or a path to one |
@@ -191,4 +191,4 @@ Settings page.
   https://docs.getdbt.com/reference/warehouse-profiles/snowflake-profile#account
 [link-snowflake-regions]:
   https://docs.snowflake.com/en/user-guide/intro-regions.html
-[ref-config-env-vars]: /reference/environment-variables#database-connection
+[ref-config-env-vars]: /reference/environment-variables