docs: run lint and prettify

Author: hassankhan

docs/.markdownlint.json

@@ -4,8 +4,19 @@
   "no-inline-html": {
     "allowed_elements": [
       "a",
+      "br",
+      "code",
+      "div",
       "img",
-      "p"
+      "iframe",
+      "p",
+      "pre",
+      "sup",
+      "CodeTabs",
+      "Grid",
+      "InfoBox",
+      "LoomVideo",
+      "WarningBox"
     ]
   },
   "no-trailing-punctuation": ""

docs/content/API-Reference/GraphQL-API.mdx

@@ -22,10 +22,10 @@ client. Instead inline variables directly in the query.
 </WarningBox>
 
 First, ensure you're running Cube v0.28.58 or later. Then start the project
-locally in development mode, and navigate to
-`http://localhost:4000/` in your browser. 
-After generating schema and running query you should see the GraphiQL interface if you click 'GraphiQL' button.
-If you click the 'Docs' button in the top-right, you can explore the introspected schema.
+locally in development mode, and navigate to `http://localhost:4000/` in your
+browser. After generating schema and running query you should see the GraphiQL
+interface if you click 'GraphiQL' button. If you click the 'Docs' button in the
+top-right, you can explore the introspected schema.
 
 As an example, let's use the `Orders` cube from the example eCommerce database:
 
@@ -126,10 +126,13 @@ Filters can be set on the load query or on a specific cube. Specifying the
 filter on the load query applies it to all cubes in the query. Filters can be
 added to the query as follows:
 
-```
+```graphql
 query {
   cube(limit: 100, offset: 50, timezone: "America/Los_Angeles") {
-    orders(orderBy: { createdAt: asc, count: desc }, where: {status: {equals: "completed"}}) {
+    orders(
+      orderBy: { createdAt: asc, count: desc }
+      where: { status: { equals: "completed" } }
+    ) {
       count
       status
       createdAt
@@ -148,10 +151,13 @@ note:
 
 The GraphQL API supports `@skip` and `@include` directives too:
 
-```
+```graphql
 query GetOrders($byStatus: Boolean) {
   cube(limit: 100, offset: 50, timezone: "America/Los_Angeles") {
-    orders(orderBy: { createdAt: asc, count: desc }, where: {status: {equals: "completed"}}) {
+    orders(
+      orderBy: { createdAt: asc, count: desc }
+      where: { status: { equals: "completed" } }
+    ) {
       count
       status @include(if: $byStatus)
       createdAt
@@ -187,7 +193,7 @@ to our query as follows:
 
 ### <--{"id" : "Reference"}--> cube
 
-```
+```graphql
 query {
   cube [([cubeQueryArgs])] {
     <cubeName> [([cubeArgs])] {
@@ -204,13 +210,13 @@ query {
 
 ### <--{"id" : "Reference"}--> CubeQueryArgs
 
-| Key          | Schema                                | Description                                                                                                                                         |
-| ------------ | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `where`      | [`RootWhereInput`](#root-where-input) | Represents a SQL `WHERE` clause                                                                                                                     |
-| `limit`      | `Int`                                 | A row limit for your query. The default value is `10000`. The maximum allowed limit is `50000`                                                      |
-| `offset`     | `Int`                                 | The number of initial rows to be skipped for your query. The default value is `0`                                                                   |
-| `timezone`   | `String`                              | The timezone to use for the query. The default value is `UTC`                                                                                       |
-| `renewQuery` | `Boolean`                             | If `renewQuery` is set to `true`, Cube.js will renew all `refreshKey` for queries and query results in the foreground. The default value is `false` |
+| Key          | Schema                                | Description                                                                                                                                      |
+| ------------ | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `where`      | [`RootWhereInput`](#root-where-input) | Represents a SQL `WHERE` clause                                                                                                                  |
+| `limit`      | `Int`                                 | A row limit for your query. The default value is `10000`. The maximum allowed limit is `50000`                                                   |
+| `offset`     | `Int`                                 | The number of initial rows to be skipped for your query. The default value is `0`                                                                |
+| `timezone`   | `String`                              | The timezone to use for the query. The default value is `UTC`                                                                                    |
+| `renewQuery` | `Boolean`                             | If `renewQuery` is set to `true`, Cube will renew all `refreshKey` for queries and query results in the foreground. The default value is `false` |
 
 ### <--{"id" : "Reference"}--> RootWhereInput
 

docs/content/API-Reference/Query-Format.md

@@ -132,7 +132,7 @@ A filter is a Javascript object with the following properties:
 - `values`: An array of values for the filter. Values must be of type String. If
   you need to pass a date, pass it as a string in `YYYY-MM-DD` format.
 
-#### Filtering Dimensions vs Filtering Measures
+### <--{"id" : "Filters Format"}--> Filtering Dimensions vs Filtering Measures
 
 Filters are applied differently to dimensions and measures.
 
@@ -527,8 +527,8 @@ provides a convenient shortcut to pass a dimension and a filter as a
   previous period
 - `granularity`: A granularity for a time dimension. It supports the following
   values `second`, `minute`, `hour`, `day`, `week`, `month`, `quarter`, `year`.
-  If you pass `null` to the granularity, Cube will only perform filtering by
-  a specified time dimension, without grouping.
+  If you pass `null` to the granularity, Cube will only perform filtering by a
+  specified time dimension, without grouping.
 
 ```javascript
 {

docs/content/API-Reference/REST-API.mdx

@@ -33,7 +33,7 @@ you can still use it to pass a security context.
 
 ### <--{"id" : "Prerequisites"}--> Example request
 
-```bash
+```bash{promptUser: user}
 curl -H "Authorization: EXAMPLE-API-TOKEN" https://example.com/cubejs-api/v1/sql
 ```
 
@@ -129,13 +129,13 @@ Response
 
 Example request:
 
-```bash
+```bash{outputLines: 1,3-9,11-15}
 # Request with http method GET
 curl \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -G \
- --data-urlencode 'query={"measures":["Users.count"]}' \
- http://localhost:4000/cubejs-api/v1/load
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -G \
+  --data-urlencode 'query={"measures":["Users.count"]}' \
+  http://localhost:4000/cubejs-api/v1/load
 
 # Request with http method POST
 # Use POST to fix problem with query length limits
@@ -208,13 +208,13 @@ Response
 
 Example request:
 
-```bash
+```bash{outputLines: 2-6}
 curl \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -G \
- --data-urlencode 'query={"measures":["Users.count"],
- "timeDimensions":[{"dimension": "Users.createdAt","granularity":"day","dateRange":["2019-03-01","2019-03-31"]}]}' \
- http://localhost:4000/cubejs-api/v1/sql
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -G \
+  --data-urlencode 'query={"measures":["Users.count"],
+  "timeDimensions":[{"dimension": "Users.createdAt","granularity":"day","dateRange":["2019-03-01","2019-03-31"]}]}' \
+  http://localhost:4000/cubejs-api/v1/sql
 ```
 
 Example response:
@@ -268,11 +268,11 @@ Response
 
 Example request:
 
-```bash
+```bash{outputLines: 2-4}
 curl \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -G \
- http://localhost:4000/cubejs-api/v1/meta
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -G \
+  http://localhost:4000/cubejs-api/v1/meta
 ```
 
 Example response:
@@ -335,12 +335,12 @@ Empty object response if scheduled successfully.
 
 Example request:
 
-```bash
+```bash{outputLines: 2-5}
 curl \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -G \
- --data-urlencode 'queryingOptions={"timezone":"UTC"}' \
- http://localhost:4000/cubejs-api/v1/run-scheduled-refresh
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -G \
+  --data-urlencode 'queryingOptions={"timezone":"UTC"}' \
+  http://localhost:4000/cubejs-api/v1/run-scheduled-refresh
 ```
 
 ### <--{"id" : "API Reference"}--> /cubejs-system/v1/pre-aggregations/jobs
@@ -364,12 +364,12 @@ job.
 
 Example request:
 
-```bash
+```bash{outputLines: 2-5}
 curl \
- -d '{"action": "post", "selector": { "preAggregations": ["Orders.ordersByStatus"]}}' \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -X POST \
- https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
+  -d '{"action": "post", "selector": { "preAggregations": ["Orders.ordersByStatus"]}}' \
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -X POST \
+  https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
 ```
 
 Example response:
@@ -396,12 +396,12 @@ a `tokens` property.
 
 Example request:
 
-```bash
+```bash{outputLines: 2-5}
 curl \
- -d '{"action": "get", "tokens": ["e9a6a0c55885cea5371348500ce7d7dc","d1329b6c8d152e734fc4dcf7307b1b58","6f4ea38373663fffc4334a576574845b","ea903b10634b2f3141b35a2529870e89"]}' \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -X POST \
- https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
+  -d '{"action": "get", "tokens": ["e9a6a0c55885cea5371348500ce7d7dc","d1329b6c8d152e734fc4dcf7307b1b58","6f4ea38373663fffc4334a576574845b","ea903b10634b2f3141b35a2529870e89"]}' \
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -X POST \
+  https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
 ```
 
 Example response:
@@ -485,12 +485,12 @@ Example response:
 
 Example request with `resType: object`:
 
-```bash
+```bash{outputLines: 2-5}
 curl \
- -d '{"action": "get", "resType": "object", "tokens": ["e9a6a0c55885cea5371348500ce7d7dc","d1329b6c8d152e734fc4dcf7307b1b58","6f4ea38373663fffc4334a576574845b","ea903b10634b2f3141b35a2529870e89"]}' \
- -H "Authorization: EXAMPLE-API-TOKEN" \
- -X POST \
- https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
+  -d '{"action": "get", "resType": "object", "tokens": ["e9a6a0c55885cea5371348500ce7d7dc","d1329b6c8d152e734fc4dcf7307b1b58","6f4ea38373663fffc4334a576574845b","ea903b10634b2f3141b35a2529870e89"]}' \
+  -H "Authorization: EXAMPLE-API-TOKEN" \
+  -X POST \
+  https://localhost:4000/cubejs-system/v1/pre-aggregations/jobs
 ```
 
 Example response with `resType: object`:
@@ -578,15 +578,10 @@ connection to the default `dataSource`.
 **Multi-tenant:** Tests connections per-tenant. If no connections exist, it will
 report as successful.
 
-Example request:
+Example of a successful request:
 
-```bash
+```bash{outputLines: 2-12}
 curl -i http://localhost:4000/readyz
-```
-
-Successful example response:
-
-```bash
 HTTP/1.1 200 OK
 X-Powered-By: Express
 Access-Control-Allow-Origin: *
@@ -600,9 +595,10 @@ Keep-Alive: timeout=5
 {"health":"HEALTH"}
 ```
 
-Failure example response:
+Example of a failed response:
 
-```bash
+```bash{outputLines: 2-12}
+curl -i http://localhost:4000/readyz
 HTTP/1.1 500 Internal Server Error
 X-Powered-By: Express
 Access-Control-Allow-Origin: *
@@ -622,13 +618,10 @@ Returns the liveness state of the deployment. This is confirmed by testing any
 existing connections to `dataSource`. If no connections exist, it will report as
 successful.
 
-```bash
-curl -i http://localhost:4000/livez
-```
-
-Successful example response:
+Example of a successful response:
 
-```bash
+```bash{outputLines: 2-12}
+curl -i http://localhost:4000/livez
 HTTP/1.1 200 OK
 X-Powered-By: Express
 Access-Control-Allow-Origin: *
@@ -642,9 +635,10 @@ Keep-Alive: timeout=5
 {"health":"HEALTH"}
 ```
 
-Failure example response:
+Example of a failed response:
 
-```bash
+```bash{outputLines: 2-12}
+curl -i http://localhost:4000/livez
 HTTP/1.1 500 Internal Server Error
 X-Powered-By: Express
 Access-Control-Allow-Origin: *

docs/content/Auth/AWS-Cognito.mdx

@@ -9,9 +9,9 @@ menuOrder: 4
 ## Introduction
 
 In this guide, you'll learn how to integrate AWS Cognito authentication with a
-Cube.js deployment. If you already have a pre-existing Cognito User Pool in AWS
+Cube deployment. If you already have a pre-existing Cognito User Pool in AWS
 that you'd like to re-use, please skip ahead to
-[Configure Cube.js](#configure-cube-js).
+[Configure Cube](#configure-cube-js).
 
 ## Create and configure a User Pool
 
@@ -68,13 +68,13 @@ left sidebar and associate the Lambda function you created previously:
 You can find more examples of [modifying claims in JWTs
 here][link-aws-cognito-pretoken-example].
 
-## Configure Cube.js
+## Configure Cube
 
-Now we're ready to configure Cube.js to use AWS Cognito. Go to your Cube.js
-project and open the `.env` file and add the following, replacing the values
-wrapped in `<>`.
+Now we're ready to configure Cube to use AWS Cognito. Go to your Cube project
+and open the `.env` file and add the following, replacing the values wrapped in
+`<>`.
 
-```bash
+```dotenv
 CUBEJS_JWK_URL=https://cognito-idp.<AWS_REGION>.amazonaws.com/<USER_POOL_ID>/.well-known/jwks.json
 CUBEJS_JWT_AUDIENCE=<APPLICATION_URL>
 CUBEJS_JWT_ISSUER=https://cognito-idp.<AWS_REGION>.amazonaws.com/<USER_POOL_ID>