From 21c36f8f4a5aea7b944345de01bffa4bf24c87df Mon Sep 17 00:00:00 2001
From: Nick Woolmer <29717167+nwoolmer@users.noreply.github.com>
Date: Mon, 7 Oct 2024 19:46:10 +0100
Subject: [PATCH 1/2] add new functions from recent releases (#60)

Adds functions from 8.1.2 and some that were added earlier.
---
 reference/function/finance.md | 130 ++++++++++++++++++++++++++++++++--
 reference/function/numeric.md |  50 +++++++++++++
 2 files changed, 176 insertions(+), 4 deletions(-)

diff --git a/reference/function/finance.md b/reference/function/finance.md
index 07739faf..c62207f2 100644
--- a/reference/function/finance.md
+++ b/reference/function/finance.md
@@ -28,9 +28,19 @@ Let's take the below order book as an example.
 A _buy market order_ with the size of 50 would wipe out the first two price levels of
 the _Ask_ side of the book, and would also trade on the third level.
 
-The full price of the trade: `14 * $14.50 + 16 * $14.60 + (50 - 14 - 16) * $14.80 = $732.6`
 
-The average price of the instrument in this trade: `$732.6 / 50 = $14.652`
+The full price of the trade:
+$$
+14 \cdot \$14.50 + 16 \cdot \$14.60 + (50 - 14 - 16) \cdot \$14.80 = \$732.60
+$$
+
+
+
+The average price of the instrument in this trade: 
+
+$$
+\$732.60 / 50 = \$14.652
+$$
 
 This average trade price is the output of the function when executed with the parameters taken from
 the above example:
@@ -115,11 +125,80 @@ SELECT ts, L2PRICE(100, askSize1, ask1, askSize2, ask2, askSize3, ask3)
 | 2024-05-22T09:40:15.175000Z | 0.565999999999 |
 | 2024-05-22T09:40:15.522000Z | 0.483          |
 
+
+## mid
+
+`mid(bid, ask)` - calculates the midpoint of a bidding price and asking price.
+
+Returns null if either argument is NaN or null.
+
+### Parameters
+
+- `bid` is any numeric bidding price value.
+- `ask` is any numeric asking price value.
+
+### Return value
+
+Return value type is `double`.
+
+### Examples
+
+```questdb-sql
+SELECT mid(1.5760, 1.5763)
+```
+
+| mid          |
+|:-------------|
+| 1.57615      |
+
+
+
+## spread_bps
+
+`spread_bps(bid, ask)` - calculates the quoted bid-ask spread, based on the highest bidding price,
+and the lowest asking price.
+
+The result is provided in basis points, and the calculation is:
+
+$$
+\frac
+{\text{spread}\left(\text{bid}, \text{ask}\right)}
+{\text{mid}\left(\text{bid}, \text{ask}\right)}
+\cdot
+10\,000
+$$
+
+
+### Parameters
+
+- `bid` is any numeric bidding price value.
+- `ask` is any numeric asking price value.
+
+### Return value
+
+Return value type is `double`.
+
+### Examples
+
+```questdb-sql
+SELECT spread_bps(1.5760, 1.5763)
+```
+
+| spread_bps     |
+|:---------------|
+| 1.903372140976 |
+
 ## vwap
 
 `vwap(price, quantity)` - Calculates the volume-weighted average price (VWAP)
-based on the given price and quantity columns. This is a handy replacement for
-the `sum(price * quantity) / sum(quantity)` expression.
+based on the given price and quantity columns. This is defined by the following formula:
+
+$$
+\text{vwap} =
+\frac
+{\text{sum}\left(\text{price} \cdot \text{quantity}\right)}
+{\text{sum}\left(\text{quantity}\right)}
+$$
 
 ### Parameters
 
@@ -140,3 +219,46 @@ FROM (SELECT x FROM long_sequence(100));
 | vwap |
 | :--- |
 | 67   |
+
+
+## wmid
+
+`wmid(bidSize, bidPrice, askPrice, askSize)` - calculates the weighted mid-price
+for a sized bid/ask pair.
+
+It is calculated with these formulae:
+
+$$
+\text{imbalance} = 
+\frac
+{ \text{bidSize} }
+{ \left(  \text{bidSize} + \text{askSize} \right) }
+$$
+
+$$
+\text{wmid} = \text{askPrice} \cdot \text{imbalance} 
++ \text{bidPrice} 
+\cdot \left( 1 - \text{imbalance} \right)
+$$
+
+### Parameters
+
+- `bidSize` is any numeric value representing the size of the bid offer.
+- `bidPrice` is any numeric value representing the bidding price.
+- `askPrice` is any numeric value representing the asking price.
+- `askSize` is any numeric value representing the size of the ask offer.
+
+### Return value
+
+Return value type is `double`.
+
+### Examples
+
+```questdb-sql
+SELECT wmid(100, 5, 6, 100)
+```
+
+| wmid |
+|:-----|
+| 5.5  |
+
diff --git a/reference/function/numeric.md b/reference/function/numeric.md
index 9e129e3e..00040edc 100644
--- a/reference/function/numeric.md
+++ b/reference/function/numeric.md
@@ -106,6 +106,56 @@ SELECT floor(15.75) as RoundedDown;
 | --------- |
 | 15        |
 
+
+## greatest
+
+`greatest(args...)` returns the largest entry in a series of numbers. 
+
+**Arguments:**
+
+- `args...` is a variable-size list of `long` or `double` values.
+
+**Return value:**
+
+Return value type is `double` or `long`.
+
+**Examples:**
+
+```questdb-sql
+SELECT greatest(11, 3, 8, 15)
+```
+
+| greatest |
+|----------|
+| 15       |
+
+
+
+## least
+
+`least(args...)` returns the smallest entry in a series of numbers.
+
+**Arguments:**
+
+- `args...` is a variable-size list of `long` or `double` values.
+
+**Return value:**
+
+Return value type is `double` or `long`.
+
+**Examples:**
+
+```questdb-sql
+SELECT least(11, 3, 8, 15)
+```
+
+| least |
+|-------|
+| 3     |
+
+
+
+
 ## ln
 
 `ln(value)` return the natural logarithm (**log*e***) of a given number.

From 6858c83e4b939b6e783ec961fa5240bbe64eb9ad Mon Sep 17 00:00:00 2001
From: goodroot <9484709+goodroot@users.noreply.github.com>
Date: Mon, 7 Oct 2024 13:33:31 -0700
Subject: [PATCH 2/2] Add new interlinks (#61)

* improves interlink coverage
---
 concept/root-directory-structure.md           |  2 +-
 configuration.md                              | 44 +++++++--------
 deployment/aws-official-ami.md                | 14 ++---
 deployment/capacity-planning.md               |  4 +-
 deployment/digitalocean.md                    |  7 ++-
 deployment/docker.md                          | 54 +++++++++----------
 deployment/google-cloud-platform.md           |  4 +-
 deployment/systemd.md                         |  2 +-
 guides/active-directory-pingfederate.md       | 14 ++---
 guides/create-database.md                     |  2 +-
 guides/enterprise-quick-start.md              | 10 ++--
 guides/import-csv.md                          |  2 +-
 guides/replication-tuning.md                  |  2 +-
 ingestion-overview.md                         |  6 +--
 operations/data-retention.md                  |  5 +-
 operations/design-for-performance.md          |  2 +-
 .../openid-connect-oidc-integration.mdx       | 28 +++++-----
 operations/rbac.md                            | 22 ++++----
 operations/updating-data.md                   |  2 +-
 .../_options-not-windows.partial.mdx          |  2 +-
 .../_options-windows.partial.mdx              |  2 +-
 quick-start.mdx                               |  2 +-
 reference/api/rest.md                         |  3 +-
 reference/command-line-options.md             |  2 +-
 reference/function/aggregation.md             |  8 +--
 reference/sql/cancel-query.md                 |  2 +-
 reference/sql/overview.md                     | 42 +++++++--------
 reference/sql/sample-by.md                    |  2 +-
 reference/sql/select.md                       |  2 +-
 reference/sql/update.md                       |  2 +-
 sidebars.js                                   |  2 +-
 .../{data-bento.md => databento.md}           |  4 +-
 third-party-tools/flink.md                    |  2 +-
 third-party-tools/grafana.md                  |  4 +-
 third-party-tools/kafka/questdb-kafka.md      |  6 +++
 third-party-tools/mindsdb.md                  |  9 ++--
 third-party-tools/overview.md                 |  6 +--
 third-party-tools/prometheus.md               | 12 ++---
 third-party-tools/spark.md                    | 14 ++---
 third-party-tools/telegraf.md                 |  4 +-
 web-console.md                                |  7 ++-
 41 files changed, 183 insertions(+), 182 deletions(-)
 rename third-party-tools/{data-bento.md => databento.md} (92%)

diff --git a/concept/root-directory-structure.md b/concept/root-directory-structure.md
index d97c5c6f..2ea388fb 100644
--- a/concept/root-directory-structure.md
+++ b/concept/root-directory-structure.md
@@ -239,7 +239,7 @@ Log files look like this:
 
 ## `public` directory
 
-Contains the web files for the Web Console:
+Contains the web files for the [Web Console](/docs/web-console/):
 
 ```filestructure
 └── public
diff --git a/configuration.md b/configuration.md
index 9265c674..ae2b022e 100644
--- a/configuration.md
+++ b/configuration.md
@@ -4,17 +4,17 @@ description: Server configuration keys reference documentation.
 ---
 
 import { ConfigTable } from "@theme/ConfigTable"
-import sharedWorkerConfig from "./configuration-utils/_shared-worker.config.json"
-import httpConfig from "./configuration-utils/_http.config.json"
-import cairoConfig from "./configuration-utils/_cairo.config.json"
-import parallelSqlConfig from "./configuration-utils/_parallel-sql.config.json"
-import walConfig from "./configuration-utils/_wal.config.json"
-import csvImportConfig from "./configuration-utils/_csv-import.config.json"
-import postgresConfig from "./configuration-utils/_postgres.config.json"
-import tcpConfig from "./configuration-utils/_tcp.config.json"
-import udpConfig from "./configuration-utils/_udp.config.json"
-import replicationConfig from "./configuration-utils/_replication.config.json"
-import oidcConfig from "./configuration-utils/_oidc.config.json"
+import sharedWorkerConfig from "./configuration-utils/\_shared-worker.config.json"
+import httpConfig from "./configuration-utils/\_http.config.json"
+import cairoConfig from "./configuration-utils/\_cairo.config.json"
+import parallelSqlConfig from "./configuration-utils/\_parallel-sql.config.json"
+import walConfig from "./configuration-utils/\_wal.config.json"
+import csvImportConfig from "./configuration-utils/\_csv-import.config.json"
+import postgresConfig from "./configuration-utils/\_postgres.config.json"
+import tcpConfig from "./configuration-utils/\_tcp.config.json"
+import udpConfig from "./configuration-utils/\_udp.config.json"
+import replicationConfig from "./configuration-utils/\_replication.config.json"
+import oidcConfig from "./configuration-utils/\_oidc.config.json"
 
 This page describes methods for configuring QuestDB server settings.
 
@@ -115,7 +115,7 @@ configuration) every other subsystem.
 
 ### HTTP server
 
-This section describes configuration settings for the Web Console and the REST
+This section describes configuration settings for the [Web Console](/docs/web-console/) and the REST
 API available by default on port `9000`. For details on the use of this
 component, refer to the [web console documentation](/docs/web-console/) page.
 
@@ -143,16 +143,16 @@ CSV files.
 Settings for `COPY`:
 
 <ConfigTable
-  rows={csvImportConfig}
-  pick={[
-    "cairo.sql.copy.root", 
-    "cairo.sql.copy.work.root",
-    "cairo.iouring.enabled",
-    "cairo.sql.copy.buffer.size",
-    "cairo.sql.copy.log.retention.days",
-    "cairo.sql.copy.max.index.chunk.size",
-    "cairo.sql.copy.queue.capacity",
-  ]}
+rows={csvImportConfig}
+pick={[
+"cairo.sql.copy.root",
+"cairo.sql.copy.work.root",
+"cairo.iouring.enabled",
+"cairo.sql.copy.buffer.size",
+"cairo.sql.copy.log.retention.days",
+"cairo.sql.copy.max.index.chunk.size",
+"cairo.sql.copy.queue.capacity",
+]}
 />
 
 #### CSV import configuration for Docker
diff --git a/deployment/aws-official-ami.md b/deployment/aws-official-ami.md
index 9949b115..6544f0da 100644
--- a/deployment/aws-official-ami.md
+++ b/deployment/aws-official-ami.md
@@ -15,7 +15,7 @@ software vendors that runs on AWS. This guide describes how to launch QuestDB
 via the AWS Marketplace using the official listing. This document also describes
 usage instructions after you have launched the instance, including hints for
 authentication, the available interfaces, and tips for accessing the REST API
-and web console.
+and [Web Console](/docs/web-console/).
 
 ## Prerequisites
 
@@ -51,7 +51,7 @@ For details on the server properties and using this file, see the
 
 The default ports used by QuestDB interfaces are as follows:
 
-- Web console &amp; REST API is available on port `9000`
+- [Web Console](/docs/web-console/) &amp; REST API is available on port `9000`
 - PostgreSQL wire protocol available on `8812`
 - InfluxDB line protocol `9009` (TCP and UDP)
 - Health monitoring &amp; Prometheus `/metrics` `9003`
@@ -143,14 +143,14 @@ systemctl stop questdb.service
 - Download and copy over the new binary
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`wget https://github.com/questdb/questdb/releases/download/${release.name}/questdb-${release.name}-no-jre-bin.tar.gz \\
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`wget https://github.com/questdb/questdb/releases/download/${release.name}/questdb-${release.name}-no-jre-bin.tar.gz \\
 tar xzvf questdb-${release.name}-no-jre-bin.tar.gz
 cp questdb-${release.name}-no-jre-bin/questdb.jar /usr/local/bin/questdb.jar
 cp questdb-${release.name}-no-jre-bin/questdb.jar /usr/local/bin/questdb-${release.name}.jar`}
-    </CodeBlock>
-  )}
+</CodeBlock>
+)}
 />
 
 - Restart the service again:
diff --git a/deployment/capacity-planning.md b/deployment/capacity-planning.md
index ac2de541..72cb3c1d 100644
--- a/deployment/capacity-planning.md
+++ b/deployment/capacity-planning.md
@@ -358,9 +358,9 @@ If you are running the QuestDB using `systemd`, you will also need to set the `L
 
 If you have followed the [setup guide](https://questdb.io/docs/deployment/systemd/), then the file should be called `questdb.service` and be located at `~/.config/systemd/user/questdb.service`.
 
-Add this property to the `[Service]` section, setting it to at least `1048576`, or higher if you have set higher OS-wide limits. 
+Add this property to the `[Service]` section, setting it to at least `1048576`, or higher if you have set higher OS-wide limits.
 
-Then restart the service. If you have configured these settings correctly, any warnings in the web console should now be cleared.
+Then restart the service. If you have configured these settings correctly, any warnings in the [Web Console](/docs/web-console/) should now be cleared.
 
 #### Setting system-wide open file limit on MacOS:
 
diff --git a/deployment/digitalocean.md b/deployment/digitalocean.md
index b3681bf6..c7125eac 100644
--- a/deployment/digitalocean.md
+++ b/deployment/digitalocean.md
@@ -1,8 +1,7 @@
 ---
 title: Launch QuestDB on DigitalOcean
 sidebar_label: DigitalOcean Droplet
-description:
-  This document describes how to launch DigitalOcean droplet with QuestDB
+description: This document describes how to launch DigitalOcean droplet with QuestDB
 ---
 
 DigitalOcean is a platform with software listings from independent vendors that
@@ -10,7 +9,7 @@ run on cloud resources. This guide describes how to launch QuestDB via the
 DigitalOcean marketplace using the official listing. This document also
 describes usage instructions after you have launched the instance, including
 hints for authentication, the available interfaces, and tips for accessing the
-REST API and web console.
+REST API and [Web Console](/docs/web-console/).
 
 ## Prerequisites
 
@@ -75,7 +74,7 @@ For details on the server properties and using this file, see the
 
 The default ports used by QuestDB interfaces are as follows:
 
-- Web console &amp; REST API is available on port `9000`
+- [Web Console](/docs/web-console/) &amp; REST API is available on port `9000`
 - PostgreSQL wire protocol available on `8812`
 - InfluxDB line protocol `9009` (TCP and UDP)
 - Health monitoring &amp; Prometheus `/metrics` `9003`
diff --git a/deployment/docker.md b/deployment/docker.md
index 5dbc607b..15e6879a 100644
--- a/deployment/docker.md
+++ b/deployment/docker.md
@@ -27,13 +27,13 @@ Once Docker is installed, you will need to pull QuestDB's image from
 This can be done with a single command using:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`docker run \\
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`docker run \\
   -p 9000:9000 -p 9009:9009 -p 8812:8812 -p 9003:9003 \\
   questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+</CodeBlock>
+)}
 />
 
 This command starts a Docker container from `questdb/questdb` image. In
@@ -79,11 +79,11 @@ By default, `questdb/questdb` points to the latest QuestDB version available on
 Docker. However, it is recommended to define the version used.
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`questdb/questdb:${release.name}`}
+</CodeBlock>
+)}
 />
 
 ## Environment variables
@@ -177,16 +177,16 @@ following example demonstrated how to mount the current directory to a QuestDB
 container using the `-v` flag in a Docker `run` command:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell" title={"Mounting a volume"}>
-      {`docker run -p 9000:9000 \\
+renderText={(release) => (
+<CodeBlock className="language-shell" title={"Mounting a volume"}>
+{`docker run -p 9000:9000 \\
   -p 9009:9009 \\
   -p 8812:8812 \\
   -p 9003:9003 \\
   -v "$(pwd):/var/lib/questdb" \\
   questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+</CodeBlock>
+)}
 />
 
 The current directory will then have data persisted to disk for convenient
@@ -211,14 +211,14 @@ http.bind.to=0.0.0.0:4000
 
 Running the container with the `-v` flag allows for mounting the current
 directory to QuestDB's `conf` directory in the container. With the server
-configuration above, HTTP ports for the web console and REST API will be
+configuration above, HTTP ports for the [Web Console](/docs/web-console/) and REST API will be
 available on [localhost:4000](http://localhost:4000):
 
 ```bash
 docker run -v "$(pwd):/var/lib/questdb/conf" -p 4000:4000 questdb/questdb
 ```
 
-:::note 
+:::note
 
 If you wish to use ZFS for your QuestDB deployment, with Docker, then you will need to enable ZFS on the host volume that Docker uses.
 
@@ -261,21 +261,21 @@ docker rm dd363939f261
 3. Download the latest QuestDB image:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`docker pull questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`docker pull questdb/questdb:${release.name}`}
+</CodeBlock>
+)}
 />
 
 4. Start a new container with the new version and the same volume mounted:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`docker run -p 8812:8812 -p 9000:9000 -v "$(pwd):/var/lib/questdb" questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`docker run -p 8812:8812 -p 9000:9000 -v "$(pwd):/var/lib/questdb" questdb/questdb:${release.name}`}
+</CodeBlock>
+)}
 />
 
 ### Writing logs to disk
diff --git a/deployment/google-cloud-platform.md b/deployment/google-cloud-platform.md
index a73480ec..bfe8b253 100644
--- a/deployment/google-cloud-platform.md
+++ b/deployment/google-cloud-platform.md
@@ -124,7 +124,7 @@ tag** `questdb` will now have this firewall rule applied.
 
 The ports we have opened are:
 
-- `9000` for the REST API and Web Console
+- `9000` for the REST API and [Web Console](/docs/web-console/)
 - `8812` for the PostgreSQL wire protocol
 
 ## Verify the deployment
@@ -145,7 +145,7 @@ To verify that the QuestDB deployment is operating as expected:
 1. Copy the **External IP** of the instance
 2. Navigate to `http://<external_ip>:9000` in a browser
 
-The Web Console should now be visible:
+The [Web Console](/docs/web-console/) should now be visible:
 
 <Screenshot
   alt="The QuestDB Web Console running on a VM instance on Google Cloud Platform"
diff --git a/deployment/systemd.md b/deployment/systemd.md
index 0f925125..8751a199 100644
--- a/deployment/systemd.md
+++ b/deployment/systemd.md
@@ -124,7 +124,7 @@ systemctl --user status questdb.service
 Your QuestDB instance should now be accessible at localhost, with services
 available at the following default ports:
 
-- Web console &amp; REST API is available on port `9000`
+- [Web Console](/docs/web-console/) &amp; REST API is available on port `9000`
 - PostgreSQL wire protocol available on `8812`
 - InfluxDB line protocol `9009` (TCP and UDP)
 - Health monitoring &amp; Prometheus `/metrics` `9003`
diff --git a/guides/active-directory-pingfederate.md b/guides/active-directory-pingfederate.md
index ae6fe904..37a048b0 100644
--- a/guides/active-directory-pingfederate.md
+++ b/guides/active-directory-pingfederate.md
@@ -25,7 +25,7 @@ First thing first, let's pick a name for the client!
   width={750}
 />
 
-The QuestDB Web Console is a SPA (Single Page App).
+The QuestDB [Web Console](/docs/web-console/) is a SPA (Single Page App).
 
 As a result, it cannot store safely a client secret.
 
@@ -33,7 +33,7 @@ Instead it can use PKCE (Proof Key for Code Exchange) to secure the flow.
 
 As shown above, leave the client authentication disabled.
 
-We also have to white list the URL of the Web Console as a redirection URL:
+We also have to white list the URL of the [Web Console](/docs/web-console/) as a redirection URL:
 
 <Screenshot
   alt="PingFederate image, redirection URL"
@@ -43,7 +43,7 @@ We also have to white list the URL of the Web Console as a redirection URL:
 />
 
 We can instruct PingFederate to automatically authorize the scopes requested by
-the Web Console.
+the [Web Console](/docs/web-console/).
 
 The user will not be presented the extra window asking for consent after
 authentication:
@@ -55,7 +55,7 @@ authentication:
   width={500}
 />
 
-The Web Console uses the
+The [Web Console](/docs/web-console/) uses the
 [Authorization Code Flow](/docs/operations/openid-connect-oidc-integration/#authentication-and-authorization-flow),
 and refreshes tokens automatically.
 
@@ -96,7 +96,7 @@ QuestDB does not require any special setup regarding the access token.
 We recommend that you do not to use shorter tokens than the default 28
 characters.
 
-As the QuestDB Web Console refreshes the token automatically, there is no need
+As the QuestDB [Web Console](/docs/web-console/) refreshes the token automatically, there is no need
 for long-lived tokens:
 
 <Screenshot
@@ -142,7 +142,7 @@ Next, ensure the `ROLL REFRESH TOKEN VALUES` option is selected:
   jumbo={true}
 />
 
-It is also important to whitelist the Web Console's URL on the CORS list:
+It is also important to whitelist the [Web Console](/docs/web-console/)'s URL on the CORS list:
 
 <Screenshot
   alt="PingFederate, authorization server ui"
@@ -327,7 +327,7 @@ QuestDB requires a mapping, as laid out in the
 [OIDC operations document](/docs/operations/openid-connect-oidc-integration/#mapping-user-permissions).
 
 If a given user has the HTTP permission, they will be able to now login via the
-Web Console.
+[Web Console](/docs/web-console/).
 
 Head to [http://localhost:9000](http://localhost:9000) and login, to test.
 
diff --git a/guides/create-database.md b/guides/create-database.md
index 0d7c3f8e..aeb7fceb 100644
--- a/guides/create-database.md
+++ b/guides/create-database.md
@@ -12,7 +12,7 @@ specific types.
 
 For most applications, you will import your data using methods like the InfluxDB
 Line Protocol, CSV imports, or integration with third-party tools such as
-Telegraf, Kafka, or Prometheus. If your interest lies in data ingestion rather
+Telegraf, [Kafka](/docs/third-party-tools/kafka/overview/), or Prometheus. If your interest lies in data ingestion rather
 than generation, refer to our [ingestion overview](/docs/ingestion-overview/).
 Alternatively, the [QuestDB demo instance](https://demo.questdb.io) offers a
 practical way to explore data creation and manipulation without setting up your
diff --git a/guides/enterprise-quick-start.md b/guides/enterprise-quick-start.md
index 4909c8f9..1a8d8282 100644
--- a/guides/enterprise-quick-start.md
+++ b/guides/enterprise-quick-start.md
@@ -47,7 +47,7 @@ The following are required prior to following this guide:
 
 ## Installation guide
 
-Changes take place in your `conf/server.conf` file, the QuestDB Web Console,
+Changes take place in your `conf/server.conf` file, the QuestDB [Web Console](/docs/web-console/),
 your app code or third-party tool.
 
 Check the code snippet's title to see where the command is to be invoked.
@@ -89,7 +89,7 @@ tls.private.key.path=/path/to/private_key
 ```
 
 To hot-reload the certificate and private key and update the files on disk,
-login to your QuestDB Web Console. This is accessible by default at
+login to your QuestDB [Web Console](/docs/web-console/). This is accessible by default at
 [localhost:9000](http://localhost:9000). Login using the built-in administrator
 credential.
 
@@ -145,14 +145,14 @@ delegate permissions.
 Create and govern users through **role-based access control** and the curation
 of your **access control list**.
 
-Interactive users may utilize the Web Console and/or the Postgres querying
+Interactive users may utilize the [Web Console](/docs/web-console/) and/or the Postgres querying
 clients. It is common practice to set them up as `readonly`. But how you setup
 these users or groups is up to you.
 
 For ingestion, we'll cover that in the next section. Consider this first wave of
 users your "database consumers".
 
-For permissions, the Web Console requires `HTTP`, and the PostgreSQL interface
+For permissions, the [Web Console](/docs/web-console/) requires `HTTP`, and the PostgreSQL interface
 requires `PGWIRE`:
 
 ```questdb-sql title="Web Console - Creating multiple users with differing permissions."
@@ -272,7 +272,7 @@ Once generated, safely store it.
 
 Connecting a client to ILP is a common path.
 
-However, you may use something like Kafka.
+However, you may use something like [Kafka](/docs/third-party-tools/kafka/overview/).
 
 ## 5. Ingest data, Kafka Connect (optional)
 
diff --git a/guides/import-csv.md b/guides/import-csv.md
index d8d5d8f8..fb945519 100644
--- a/guides/import-csv.md
+++ b/guides/import-csv.md
@@ -175,7 +175,7 @@ process running in the background:
 | ---------------- |
 | 5179978a6d7a1772 |
 
-3. In the Web Console right click table and select `Copy Schema to Clipboard` -
+3. In the [Web Console](/docs/web-console/) right click table and select `Copy Schema to Clipboard` -
    this copies the schema generated by the input file analysis.
 
 4. Paste the table schema to the code editor:
diff --git a/guides/replication-tuning.md b/guides/replication-tuning.md
index 809b86f6..0dfe39fb 100644
--- a/guides/replication-tuning.md
+++ b/guides/replication-tuning.md
@@ -78,7 +78,7 @@ What do these options do?
 
 In QuestDB each table replicates in a cycle independently of other tables. Thus
 each of the database's network client connections writes its data to its own
-segment in the Write-Ahead Log (WAL).
+segment in the [Write-Ahead Log (WAL)](/docs/concept/write-ahead-log/).
 
 Once a WAL segment reaches a certain size, it's closed and a new one is opened.
 The smaller the size, the more often segments roll over. This results in
diff --git a/ingestion-overview.md b/ingestion-overview.md
index a503967c..0b8bad15 100644
--- a/ingestion-overview.md
+++ b/ingestion-overview.md
@@ -20,7 +20,7 @@ platforms, queues, and more.
 **Recommended!**
 
 Our first party clients are **the fastest way to insert data, and they excel
-with high volume, high cardinality data streaming.**
+with high volume, [high cardinality](/glossary/high-cardinality/) data streaming.**
 
 To start quickly, select your language:
 
@@ -74,7 +74,7 @@ Checkout our quick start guides for the following:
 
 For GUI-driven CSV upload which leverages the
 [built-in REST HTTP API](/docs/reference/api/rest/), use the
-[Import tab](/docs/web-console/#import) in the Web Console:
+[Import tab](/docs/web-console/#import) in the [Web Console](/docs/web-console/):
 
 <Screenshot
   alt="Screenshot of the UI for import"
@@ -107,7 +107,7 @@ No data yet? Just starting? No worries. We've got you covered.
 There are several quick scaffolding options:
 
 1. [QuestDB demo instance](https://demo.questdb.io): Hosted, fully loaded and
-   ready to go. Quickly explore the Web Console and SQL syntax.
+   ready to go. Quickly explore the [Web Console](/docs/web-console/) and SQL syntax.
 2. [Create my first data set guide](/docs/guides/create-database/): Create
    tables, use `rnd_` functions and make your own data.
 3. [Sample dataset repos](https://github.com/questdb/sample-datasets): IoT,
diff --git a/operations/data-retention.md b/operations/data-retention.md
index 70840960..512e33ea 100644
--- a/operations/data-retention.md
+++ b/operations/data-retention.md
@@ -1,12 +1,11 @@
 ---
 title: Data retention
-description:
-  How to employ a data retention strategy to delete old data and save disk space
+description: How to employ a data retention strategy to delete old data and save disk space
 ---
 
 ## Background
 
-The nature of time-series data is that the relevance of information diminishes
+The nature of [time-series data](/blog/what-is-time-series-data/) is that the relevance of information diminishes
 over time. If stale data is no longer required, users can delete old data from
 QuestDB to either save disk space or adhere to a data retention policy. This is
 achieved in QuestDB by removing data partitions from a table.
diff --git a/operations/design-for-performance.md b/operations/design-for-performance.md
index 402caa83..1f945f02 100644
--- a/operations/design-for-performance.md
+++ b/operations/design-for-performance.md
@@ -23,7 +23,7 @@ formulating queries.
 ### Row serialization
 
 Row serialization and deserialization has a cost on both client and server. The
-QuestDB Web Console limits fetching to 10,000 dataset. When fetching a large
+QuestDB [Web Console](/docs/web-console/) limits fetching to 10,000 dataset. When fetching a large
 (10K+) dataset via a single query using other methods, consider using
 pagination, hence multiple queries instead.
 
diff --git a/operations/openid-connect-oidc-integration.mdx b/operations/openid-connect-oidc-integration.mdx
index ff6363e9..609bb5f4 100644
--- a/operations/openid-connect-oidc-integration.mdx
+++ b/operations/openid-connect-oidc-integration.mdx
@@ -3,13 +3,13 @@ title: OpenID Connect (OIDC) Integration
 description: ""
 ---
 
-import Screenshot from "@theme/Screenshot"
+import Screenshot from "@theme/Screenshot";
 
 OpenID Connect (OIDC) integrates with Identity Providers (IdP) external to
 QuestDB.
 
 It is a convenient way to integrate QuestDB into your enterprise environment,
-and it provides SSO (Single Sign-On) for the Web Console.
+and it provides SSO (Single Sign-On) for the [Web Console](/docs/web-console/).
 
 Microsoft Active Directory and Azure AD, for example, can be turned into an
 Identity Provider.
@@ -45,10 +45,10 @@ We can break it down into core components.
 QuestDB's interactive UI. Users must authenticate before accessing the database
 via the interface.
 
-The Web Console uses PKCE (Proof Key for Code Exchange) to secure the
+The [Web Console](/docs/web-console/) uses PKCE (Proof Key for Code Exchange) to secure the
 authentication and authorization flow.
 
-In OAuth2/OIDC terms, the Web Console is referred to as the _client_, and it is
+In OAuth2/OIDC terms, the [Web Console](/docs/web-console/) is referred to as the _client_, and it is
 assigned an identifier, the _Client Id._
 
 Each application integrates via OIDC should be given a different Client Id.
@@ -92,20 +92,20 @@ Console, authenticated.
 Then, it allows QuestDB to determine the user's permissions based on user
 information provided by the Identity Providers.
 
-Specifically, the QuestDB Web Console uses the
+Specifically, the QuestDB [Web Console](/docs/web-console/) uses the
 `Authorization Code Flow with PKCE` option.
 
 It consists of ten steps...
 
 ### 1. Secret generation
 
-First the Web Console generates a cryptographically strong random secret, called
+First the [Web Console](/docs/web-console/) generates a cryptographically strong random secret, called
 the _code verifier_.
 
 The secret is hashed using the _SHA256 algorithm_, the result is the _code
 challenge_.
 
-After PKCE initialization the Web Console requests an _authorization code_ from
+After PKCE initialization the [Web Console](/docs/web-console/) requests an _authorization code_ from
 the OIDC Provider.
 
 It calls the Authorization endpoint with a few parameters, including the:
@@ -170,7 +170,7 @@ without presenting the user with an additional screen in the browser.
 
 Consent is granted!
 
-The Authorization Server redirects the user back to the Web Console with the
+The Authorization Server redirects the user back to the [Web Console](/docs/web-console/) with the
 _authorization code_:
 
 ```bash title="Authorization code response example"
@@ -179,7 +179,7 @@ https://questdb.host:9000/?code=1L344XEY5XRka1j4ySNa8bVQSLf71as9uGLEuv_A
 
 ### 5. Credential request
 
-Now, the QuestDB Web Console requests the ID and access tokens from the Token
+Now, the QuestDB [Web Console](/docs/web-console/) requests the ID and access tokens from the Token
 endpoint of the OIDC Provider with the authorization code.
 
 It includes the Client ID and the PKCE code verifier together with the
@@ -201,11 +201,11 @@ grant_type=authorization_code&code=1L344XEY5XRka1j4ySNa8bVQSLf71as9uGLEuv_A&clie
 
 ### 6. Credentials received
 
-If the PKCE check is passed, the Web Console receives the ID and access tokens.
+If the PKCE check is passed, the [Web Console](/docs/web-console/) receives the ID and access tokens.
 
 There is also a third token in the response too, the refresh token.
 
-The refresh token is used by the Web Console to refresh the access token before
+The refresh token is used by the [Web Console](/docs/web-console/) to refresh the access token before
 it expires.
 
 Without the refresh token mechanism, the user would be forced to re-authenticate
@@ -225,7 +225,7 @@ The validity of the tokens are configurable inside the OIDC Provider.
 
 ### 7. Database access
 
-With the tokens, the Web Console can interact with the database.
+With the tokens, the [Web Console](/docs/web-console/) can interact with the database.
 
 The access token is in the header of every request sent to QuestDB.
 
@@ -358,7 +358,7 @@ the database.
 Although the user is authenticated, they have no permissions at all.
 
 The user has to have at least the `HTTP` permission to be able to successfully
-login via the Web Console.
+login via the [Web Console](/docs/web-console/).
 
 ```json title=""User info response example"
 {
@@ -393,7 +393,7 @@ It should be set accordingly to your organization's policies.
 Other parts of the user information, such as the `sub` and the `name` also used
 by QuestDB.
 
-They could be displayed in the Web Console, or appear in the logs, for example.
+They could be displayed in the [Web Console](/docs/web-console/), or appear in the logs, for example.
 
 ## Configuration options
 
diff --git a/operations/rbac.md b/operations/rbac.md
index 61de89ba..e920106f 100644
--- a/operations/rbac.md
+++ b/operations/rbac.md
@@ -488,11 +488,11 @@ There are three levels of permissions:
 
 #### Database endpoint permissions
 
-| permission | level    | description                                                                            |
-| ---------- | -------- | -------------------------------------------------------------------------------------- |
-| HTTP       | Database | Allows access to the REST API endpoint, this includes connection from the Web Console. |
-| ILP        | Database | Allows access to the InfluxDB Line Protocol (ILP) endpoint.                            |
-| PGWIRE     | Database | Allows access to the Postgres Wire endpoint.                                           |
+| permission | level    | description                                                                                                  |
+| ---------- | -------- | ------------------------------------------------------------------------------------------------------------ |
+| HTTP       | Database | Allows access to the REST API endpoint, this includes connection from the [Web Console](/docs/web-console/). |
+| ILP        | Database | Allows access to the InfluxDB Line Protocol (ILP) endpoint.                                                  |
+| PGWIRE     | Database | Allows access to the Postgres Wire endpoint.                                                                 |
 
 #### Special permissions
 
@@ -614,12 +614,12 @@ database.
 The table below shows the permission required for each endpoint and protocol
 combination.
 
-| Endpoint               | Protocol   | Transport Layer | Port (default) |     | Permission |
-| ---------------------- | ---------- | --------------- | -------------- | --- | ---------- |
-| Web Console            | JSON       | HTTP            | 9000           |     | HTTP       |
-| REST API               | JSON, TEXT | HTTP            | 9000           |     | HTTP       |
-| InfluxDB Line Protocol | ILP        | TCP             | 9009           |     | ILP        |
-| Postgres Wire Protocol | PG Wire    | TCP             | 8812           |     | PGWIRE     |
+| Endpoint                          | Protocol   | Transport Layer | Port (default) |     | Permission |
+| --------------------------------- | ---------- | --------------- | -------------- | --- | ---------- |
+| [Web Console](/docs/web-console/) | JSON       | HTTP            | 9000           |     | HTTP       |
+| REST API                          | JSON, TEXT | HTTP            | 9000           |     | HTTP       |
+| InfluxDB Line Protocol            | ILP        | TCP             | 9009           |     | ILP        |
+| Postgres Wire Protocol            | PG Wire    | TCP             | 8812           |     | PGWIRE     |
 
 An example where we create a new user to access the database only via the
 Postgres endpoint:
diff --git a/operations/updating-data.md b/operations/updating-data.md
index 4813e278..a190f8ef 100644
--- a/operations/updating-data.md
+++ b/operations/updating-data.md
@@ -21,7 +21,7 @@ we quickly want to summarize it:
   the table
 - The actual data is stored in column files inside these subdirectories
 - Column files store data **ordered by the designated timestamp** and they are
-  **append-only**. This goes naturally with time-series data, just think about
+  **append-only**. This goes naturally with [time-series data](/blog/what-is-time-series-data/), just think about
   market data where the price of different financial instruments are tracked
   during the trading day, for example
 
diff --git a/quick-start-utils/_options-not-windows.partial.mdx b/quick-start-utils/_options-not-windows.partial.mdx
index 324c91a3..486d2f20 100644
--- a/quick-start-utils/_options-not-windows.partial.mdx
+++ b/quick-start-utils/_options-not-windows.partial.mdx
@@ -2,5 +2,5 @@
 | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `-d`   | Expects a `dir` directory value which is a folder that will be used as QuestDB's root directory. For more information and the default values, see the [default root](#default-root-directory) section below.            |
 | `-t`   | Expects a `tag` string value which will be as a tag for the service. This option allows users to run several QuestDB services and manage them separately. If this option is omitted, the default tag will be `questdb`. |
-| `-f`   | Force re-deploying the Web Console. Without this option, the Web Console is cached and deployed only when missing.                                                                                                      |
+| `-f`   | Force re-deploying the [Web Console](/docs/web-console/). Without this option, the [Web Console](/docs/web-console/) is cached and deployed only when missing.                                                          |
 | `-n`   | Do not respond to the HUP signal. This keeps QuestDB alive after you close the terminal window where you started it.                                                                                                    |
diff --git a/quick-start-utils/_options-windows.partial.mdx b/quick-start-utils/_options-windows.partial.mdx
index a4babccd..06eb4376 100644
--- a/quick-start-utils/_options-windows.partial.mdx
+++ b/quick-start-utils/_options-windows.partial.mdx
@@ -4,5 +4,5 @@
 | `remove`  | Removes the Windows QuestDB service. It will no longer start at startup.                                                                                                                                                |
 | `-d`      | Expects a `dir` directory value which is a folder that will be used as QuestDB's root directory. For more information and the default values, see the [default root](#default-root-directory) section below.            |
 | `-t`      | Expects a `tag` string value which will be as a tag for the service. This option allows users to run several QuestDB services and manage them separately. If this option is omitted, the default tag will be `questdb`. |
-| `-f`      | Force re-deploying the Web Console. Without this option, the Web Console is cached and deployed only when missing.                                                                                                      |
+| `-f`      | Force re-deploying the [Web Console](/docs/web-console/). Without this option, the [Web Console](/docs/web-console/) is cached and deployed only when missing.                                                          |
 | `-j`      | **Windows only!** This option allows to specify a path to `JAVA_HOME`.                                                                                                                                                  |
diff --git a/quick-start.mdx b/quick-start.mdx
index 48a2b1aa..9442930c 100644
--- a/quick-start.mdx
+++ b/quick-start.mdx
@@ -197,7 +197,7 @@ questdb.exe [start|stop|status|install|remove] \
 
 Congratulations! 🎉 QuestDB is now running.
 
-The QuestDB Web Console is available by default at:
+The QuestDB [Web Console](/docs/web-console/) is available by default at:
 [http://localhost:9000](http://localhost:9000).
 
 Also by default, QuestDB will use the following ports:
diff --git a/reference/api/rest.md b/reference/api/rest.md
index 659bb8e8..66b74f95 100644
--- a/reference/api/rest.md
+++ b/reference/api/rest.md
@@ -20,8 +20,7 @@ off-the-shelf HTTP clients. It provides a simple way to interact with QuestDB
 and is compatible with most programming languages. API functions are fully keyed
 on the URL and they use query parameters as their arguments.
 
-The Web Console is the official Web client relying on the REST API. Find out
-more in the section [using the Web Console](/docs/web-console/).
+The Web Console[Web Console](/docs/web-console/) is the official Web client relying on the REST API.
 
 **Available methods**
 
diff --git a/reference/command-line-options.md b/reference/command-line-options.md
index f6322f8d..0dc5eab0 100644
--- a/reference/command-line-options.md
+++ b/reference/command-line-options.md
@@ -61,7 +61,7 @@ questdb.exe [start|stop|status|install|remove] \
 | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `-d`   | Expects a `dir` directory value which is a folder that will be used as QuestDB's root directory. For more information and the default values, see the [default root](#default-root-directory) section below.            |
 | `-t`   | Expects a `tag` string value which will be as a tag for the service. This option allows users to run several QuestDB services and manage them separately. If this option is omitted, the default tag will be `questdb`. |
-| `-f`   | Force re-deploying the Web Console. Without this option, the Web Console is cached and deployed only when missing.                                                                                                      |
+| `-f`   | Force re-deploying the [Web Console](/docs/web-console/). Without this option, the [Web Console](/docs/web-console/) is cached and deployed only when missing.                                                          |
 | `-n`   | Do not respond to the HUP signal. This keeps QuestDB alive after you close the terminal window where you started it.                                                                                                    |
 | `-j`   | **Windows only!** This option allows to specify a path to `JAVA_HOME`.                                                                                                                                                  |
 
diff --git a/reference/function/aggregation.md b/reference/function/aggregation.md
index 0ccc5281..89808053 100644
--- a/reference/function/aggregation.md
+++ b/reference/function/aggregation.md
@@ -18,7 +18,7 @@ The precision of HyperLogLog can be controlled via the optional `precision`
 parameter, typically between 4 and 16. A higher precision leads to more accurate
 results with increased memory usage. The default is 1.
 
-This function is useful within high cardinality datasets where an exact count is
+This function is useful within [high cardinality](/glossary/high-cardinality/) datasets where an exact count is
 not required. Thus consider it the higher cardinality alternative to
 [`count_dinstinct`](/docs/reference/function/aggregation/#count_distinct).
 
@@ -451,7 +451,7 @@ SELECT first(device_id) FROM sensors;
 ```
 
 | first      |
-|:-----------|
+| :--------- |
 | arduino-01 |
 
 The following query returns the latest symbol value for the `device_id` column:
@@ -461,7 +461,7 @@ SELECT last(device_id) FROM sensors;
 ```
 
 | last       |
-|:-----------|
+| :--------- |
 | arduino-03 |
 
 Without selecting a designated timestamp column, the table may be unordered and
@@ -469,7 +469,7 @@ the query may return different result. Given an unordered table
 `sensors_unordered`:
 
 | device_id  | temperature | ts                          |
-|:-----------|:------------|:----------------------------|
+| :--------- | :---------- | :-------------------------- |
 | arduino-01 | 12          | 2021-06-02T14:33:19.970258Z |
 | arduino-03 | 18          | 2021-06-02T14:33:23.707013Z |
 | arduino-02 | 10          | 2021-06-02T14:33:21.703934Z |
diff --git a/reference/sql/cancel-query.md b/reference/sql/cancel-query.md
index df8eae73..e5caca2b 100644
--- a/reference/sql/cancel-query.md
+++ b/reference/sql/cancel-query.md
@@ -30,7 +30,7 @@ meta-function.
 
 ## Examples
 
-Consider we have two open tabs of the QuestDB Web Console.
+Consider we have two open tabs of the QuestDB [Web Console](/docs/web-console/).
 
 If we execute the following command in the first tab:
 
diff --git a/reference/sql/overview.md b/reference/sql/overview.md
index 08cfe720..9a70208f 100644
--- a/reference/sql/overview.md
+++ b/reference/sql/overview.md
@@ -66,7 +66,7 @@ The Web Console is available by default at
 [localhost:9000](http://localhost:9000). The GUI makes it easy to write, return
 and chart queries. There is autocomplete, syntax highlighting, errors, and more.
 If you want to test a query or interact direclty with your data in the cleanest
-and simplest way, apply queries via the Web Console.
+and simplest way, apply queries via the [Web Console](/docs/web-console/).
 
 <Screenshot
   alt="A shot of the Web Console, showing auto complete and a colourful returned table."
@@ -75,7 +75,7 @@ and simplest way, apply queries via the Web Console.
 />
 
 For an example, click _Demo this query_ in the below snippet. This will run a
-query within our public demo instance and Web Console:
+query within our public demo instance and [Web Console](/docs/web-console/):
 
 ```questdb-sql title='Navigate time with SQL' demo
 SELECT
@@ -298,56 +298,56 @@ curl -G \
 The `node-fetch` package can be installed using `npm i node-fetch`.
 
 ```javascript
-const fetch = require("node-fetch")
+const fetch = require("node-fetch");
 
-const HOST = "http://localhost:9000"
+const HOST = "http://localhost:9000";
 
 async function createTable() {
   try {
-    const query = "CREATE TABLE IF NOT EXISTS trades (name VARCHAR, value INT)"
+    const query = "CREATE TABLE IF NOT EXISTS trades (name VARCHAR, value INT)";
 
     const response = await fetch(
       `${HOST}/exec?query=${encodeURIComponent(query)}`,
-    )
-    const json = await response.json()
+    );
+    const json = await response.json();
 
-    console.log(json)
+    console.log(json);
   } catch (error) {
-    console.log(error)
+    console.log(error);
   }
 }
 
 async function insertData() {
   try {
-    const query = "INSERT INTO trades VALUES('abc', 123456)"
+    const query = "INSERT INTO trades VALUES('abc', 123456)";
 
     const response = await fetch(
       `${HOST}/exec?query=${encodeURIComponent(query)}`,
-    )
-    const json = await response.json()
+    );
+    const json = await response.json();
 
-    console.log(json)
+    console.log(json);
   } catch (error) {
-    console.log(error)
+    console.log(error);
   }
 }
 
 async function updateData() {
   try {
-    const query = "UPDATE trades SET value = 9876 WHERE name = 'abc'"
+    const query = "UPDATE trades SET value = 9876 WHERE name = 'abc'";
 
     const response = await fetch(
       `${HOST}/exec?query=${encodeURIComponent(query)}`,
-    )
-    const json = await response.json()
+    );
+    const json = await response.json();
 
-    console.log(json)
+    console.log(json);
   } catch (error) {
-    console.log(error)
+    console.log(error);
   }
 }
 
-createTable().then(insertData).then(updateData)
+createTable().then(insertData).then(updateData);
 ```
 
 </TabItem>
@@ -429,7 +429,7 @@ For more information, see the
 
 Now... SQL! It's query time.
 
-Whether you want to use the Web Console, PostgreSQL or REST HTTP (or both),
+Whether you want to use the [Web Console](/docs/web-console/), PostgreSQL or REST HTTP (or both),
 query construction is rich.
 
 To brush up and learn what's unique in QuestDB, consider the following:
diff --git a/reference/sql/sample-by.md b/reference/sql/sample-by.md
index d15072b0..73d12eb4 100644
--- a/reference/sql/sample-by.md
+++ b/reference/sql/sample-by.md
@@ -4,7 +4,7 @@ sidebar_label: SAMPLE BY
 description: SAMPLE BY SQL keyword reference documentation.
 ---
 
-`SAMPLE BY` is used on time-series data to summarize large datasets into
+`SAMPLE BY` is used on [time-series data](/blog/what-is-time-series-data/) to summarize large datasets into
 aggregates of homogeneous time chunks as part of a
 [SELECT statement](/docs/reference/sql/select/).
 
diff --git a/reference/sql/select.md b/reference/sql/select.md
index a909ff9e..4da49320 100644
--- a/reference/sql/select.md
+++ b/reference/sql/select.md
@@ -302,7 +302,7 @@ For more information, please refer to the
 
 ### SAMPLE BY
 
-Aggregates time-series data into homogeneous time chunks. For example daily
+Aggregates [time-series data](/blog/what-is-time-series-data/) into homogeneous time chunks. For example daily
 average, monthly maximum etc. This function requires a
 [designated timestamp](/docs/concept/designated-timestamp/).
 
diff --git a/reference/sql/update.md b/reference/sql/update.md
index 989a9422..e349ca26 100644
--- a/reference/sql/update.md
+++ b/reference/sql/update.md
@@ -15,7 +15,7 @@ Updates data in a database table.
 - the same `columnName` cannot be specified multiple times after the SET keyword
   as it would be ambiguous
 - the designated timestamp column cannot be updated as it would lead to altering
-  history of the time-series data
+  history of the [time-series data](/blog/what-is-time-series-data/)
 - If the target partition is
   [attached by a symbolic link](/docs/reference/sql/alter-table-attach-partition/#symbolic-links),
   the partition is read-only. `UPDATE` operation on a read-only partition will
diff --git a/sidebars.js b/sidebars.js
index f7c589e8..bf244341 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -430,7 +430,7 @@ module.exports = {
           id: "third-party-tools/overview",
         },
         "third-party-tools/cube",
-        "third-party-tools/data-bento",
+        "third-party-tools/databento",
         "third-party-tools/embeddable",
         "third-party-tools/flink",
         "third-party-tools/grafana",
diff --git a/third-party-tools/data-bento.md b/third-party-tools/databento.md
similarity index 92%
rename from third-party-tools/data-bento.md
rename to third-party-tools/databento.md
index 289f7365..a8d0180d 100644
--- a/third-party-tools/data-bento.md
+++ b/third-party-tools/databento.md
@@ -3,12 +3,12 @@ title: "Databento"
 description: Guide to ingest and analyze live multi-stream market data from Databento using QuestDB and Grafana.
 ---
 
-[Databento](https://databento.com/) is a market data aggregator that provides a single,
+[Databento](/docs/third-party-tools/databento/) is a market data aggregator that provides a single,
 normalized feed covering multiple venues,
 simplifying the process of ingesting live market data.
 It interfaces well with QuestDB for real-time data analysis and visualization in Grafana.
 
-This guide will show how to ingest live market data from Databento into QuestDB and visualize it using Grafana.
+This guide will show how to ingest live market data from [Databento](/docs/third-party-tools/databento/) into QuestDB and visualize it using Grafana.
 
 For a deeper dive, see our [Databento & QuestDB blog](/blog/ingesting-live-market-data-data-bento/).
 
diff --git a/third-party-tools/flink.md b/third-party-tools/flink.md
index 729b4220..c193d963 100644
--- a/third-party-tools/flink.md
+++ b/third-party-tools/flink.md
@@ -97,7 +97,7 @@ Flink. The overall steps are the followings:
   This command used Flink SQL to insert a row into the `Orders` table in Flink.
   The table is connected to QuestDB, so the row is also into QuestDB.
 
-- Go to the QuestDB web console [http://localhost:9000](http://localhost:9000)
+- Go to the QuestDB [Web Console](/docs/web-console/) [http://localhost:9000](http://localhost:9000)
   and execute this query:
 
   ```questdb-sql
diff --git a/third-party-tools/grafana.md b/third-party-tools/grafana.md
index c0d30d11..644e55bd 100644
--- a/third-party-tools/grafana.md
+++ b/third-party-tools/grafana.md
@@ -8,7 +8,7 @@ description:
 import Screenshot from "@theme/Screenshot"
 
 [Grafana](https://grafana.com/) is a popular observability and monitoring
-application used to visualize data and enable time-series data analysis.
+application used to visualize data and enable [time-series data analysis](/glossary/time-series-analysis/).
 
 QuestDB is available within Grafana via the
 [official QuestDB plugin](https://grafana.com/grafana/plugins/questdb-questdb-datasource/).
@@ -44,7 +44,7 @@ password:admin
 ## Start QuestDB
 
 The Docker version runs on port `8812` for the database connection and port
-`9000` for the Web Console and REST interface:
+`9000` for the [Web Console](/docs/web-console/) and REST interface:
 
 ```shell
 docker run --add-host=host.docker.internal:host-gateway \
diff --git a/third-party-tools/kafka/questdb-kafka.md b/third-party-tools/kafka/questdb-kafka.md
index fa8aa52e..fdda0775 100644
--- a/third-party-tools/kafka/questdb-kafka.md
+++ b/third-party-tools/kafka/questdb-kafka.md
@@ -469,7 +469,9 @@ correct column types instead of relying on the connector to infer them. See the
 paragraph below.
 
 ### Target table considerations
+
 #### Table name
+
 By default, the target table name in QuestDB is the same as the Kafka topic
 name from which a message originates. When a connector is configured to read
 from multiple topics, it uses a separate table for each topic.
@@ -478,6 +480,7 @@ Set the table configuration option to override this behavior. Once set, the conn
 regardless of the topic from which they originate.
 
 Example:
+
 ```shell title="Configuration file an explicit table name"
 name=questdb-sink
 connector.class=io.questdb.kafka.QuestDBSinkConnector
@@ -493,6 +496,7 @@ variables in the table name: `${topic}`, `${key}`. The connector will replace
 these variables with the actual topic name and key value from the Kafka message.
 
 Example:
+
 ```shell title="Configuration file with a templated table name"
 name=questdb-sink
 connector.class=io.questdb.kafka.QuestDBSinkConnector
@@ -502,11 +506,13 @@ table=from_kafka_${topic}_${key}_suffix
 
 [...]
 ```
+
 The placeholder `${key}` will be replaced with the actual key value from the
 Kafka message. If the key is not present in the message, the placeholder will be
 replaced with the string `null`.
 
 #### Table schema
+
 When a target table does not exist in QuestDB, it will be created automatically.
 This is the recommended approach for development and testing.
 
diff --git a/third-party-tools/mindsdb.md b/third-party-tools/mindsdb.md
index 97051b8a..9fcf7208 100644
--- a/third-party-tools/mindsdb.md
+++ b/third-party-tools/mindsdb.md
@@ -1,7 +1,6 @@
 ---
 title: MindsDB
-description:
-  Guide for getting started in Machine Learning with MindsDB and QuestDB
+description: Guide for getting started in Machine Learning with MindsDB and QuestDB
 ---
 
 [MindsDB](https://mindsdb.com/questdb-machine-learning/) provides Machine
@@ -96,7 +95,7 @@ The container has these mount points:
 The container is running `Debian GNU/Linux 11 (bullseye)` and exposes these
 ports:
 
-- 9000: QuestDB Web Console
+- 9000: QuestDB [Web Console](/docs/web-console/)
 - 8812: QuestDB pg-wire
 - 9009: QuestDB InfluxDB Line Protocol ingress line protocol
 - 47334: MindsDB WebConsole
@@ -109,7 +108,7 @@ There are different ways to [insert data to QuestDB](/docs/ingestion-overview/).
 
 #### SQL
 
-We can access QuestDB's web console at
+We can access QuestDB's [Web Console](/docs/web-console/) at
 [http://localhost:9000](http://localhost:9000).
 
 Run the following SQL query to create a simple table:
@@ -271,7 +270,7 @@ The result should be something like this:
 ```
 
 Beyond SELECT statements, for instance when we need to save the results of a
-query into a new table, we need to use QuestDB's web console available at
+query into a new table, we need to use QuestDB's [Web Console](/docs/web-console/) available at
 [http://localhost:9000](http://localhost:9000):
 
 ```questdb-sql
diff --git a/third-party-tools/overview.md b/third-party-tools/overview.md
index 90f6981c..28b0ae4c 100644
--- a/third-party-tools/overview.md
+++ b/third-party-tools/overview.md
@@ -16,7 +16,7 @@ Interact with and visualize your QuestDB data using these powerful visualization
 platforms:
 
 - **[Grafana](/docs/third-party-tools/grafana/):** Create stunning dashboards
-  and interactive graphs for time-series data visualization.
+  and interactive graphs for [time-series data](/blog/what-is-time-series-data/) visualization.
 - [Superset](/docs/third-party-tools/superset/): Build interactive
   visualizations and perform ad-hoc data analysis.
 
@@ -41,10 +41,10 @@ integrations:
 Enhance your data analysis and processing capabilities with QuestDB through
 these tools:
 
-- [Pandas](/docs/third-party-tools/pandas/): Analyze time-series data in Python
+- [Pandas](/docs/third-party-tools/pandas/): Analyze [time-series data](/blog/what-is-time-series-data/) in Python
   with powerful data structures.
 - [MindsDB](/docs/third-party-tools/mindsdb/): Build machine learning models for
-  predictive analytics on time-series data.
+  predictive analytics on[time-series data](/blog/what-is-time-series-data/).
 - [Embeddable](/docs/third-party-tools/embeddable/): Developer toolkit for
   building fast, interactive customer-facing analytics.
 
diff --git a/third-party-tools/prometheus.md b/third-party-tools/prometheus.md
index 40f84074..f842e7fb 100644
--- a/third-party-tools/prometheus.md
+++ b/third-party-tools/prometheus.md
@@ -11,7 +11,7 @@ import InterpolateReleaseData from "../../src/components/InterpolateReleaseData"
 import CodeBlock from "@theme/CodeBlock"
 
 Prometheus is an open-source systems monitoring and alerting toolkit. Prometheus
-collects and stores metrics as time-series data, i.e. metrics information is
+collects and stores metrics as [time-series data](/blog/what-is-time-series-data/), i.e. metrics information is
 stored with the timestamp at which it was recorded, alongside optional key-value
 pairs called labels.
 
@@ -51,15 +51,15 @@ When running QuestDB via Docker, port `9003` must be exposed and the metrics
 configuration can be enabled via the `QDB_METRICS_ENABLED` environment variable:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell" title={"Docker"}>
-      {`docker run \\
+renderText={(release) => (
+<CodeBlock className="language-shell" title={"Docker"}>
+{`docker run \\
   -e QDB_METRICS_ENABLED=TRUE \\
   -p 8812:8812 -p 9000:9000 -p 9003:9003 -p 9009:9009 \\
   -v "$(pwd):/var/lib/questdb" \\
   questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+</CodeBlock>
+)}
 />
 
 To verify that metrics are being exposed correctly by QuestDB, navigate to
diff --git a/third-party-tools/spark.md b/third-party-tools/spark.md
index 393d72fa..e912d917 100644
--- a/third-party-tools/spark.md
+++ b/third-party-tools/spark.md
@@ -93,18 +93,18 @@ postgresql-42.5.1.jar
 First, start QuestDB. If you are using Docker run the following command:
 
 <InterpolateReleaseData
-  renderText={(release) => (
-    <CodeBlock className="language-shell">
-      {`docker run -p 9000:9000 -p 8812:8812 questdb/questdb:${release.name}`}
-    </CodeBlock>
-  )}
+renderText={(release) => (
+<CodeBlock className="language-shell">
+{`docker run -p 9000:9000 -p 8812:8812 questdb/questdb:${release.name}`}
+</CodeBlock>
+)}
 />
 
 The port mappings allow us to connect to QuestDB's REST and PostgreSQL Wire
 Protocol endpoints. The former is required for opening the Web Console, and the
 latter is used by Spark to connect to the database.
 
-Open the Web Console in your browser at
+Open the [Web Console](/docs/web-console/) in your browser at
 [http://localhost:9000](http://localhost:9000).
 
 Run the following SQL commands using the console:
@@ -210,7 +210,7 @@ After the execution is completed, we can check the content of the
 SELECT * FROM trades_enriched;
 ```
 
-The enriched data should be displayed in the Web Console.
+The enriched data should be displayed in the [Web Console](/docs/web-console/).
 
 ## See also
 
diff --git a/third-party-tools/telegraf.md b/third-party-tools/telegraf.md
index af206ef0..74fe056b 100644
--- a/third-party-tools/telegraf.md
+++ b/third-party-tools/telegraf.md
@@ -95,7 +95,7 @@ load configuration files from and paste the following example:
 [[outputs.influxdb_v2]]
 # Use InfluxDB Line Protocol to write metrics to QuestDB
   urls = ["http://localhost:9000"]
-# Disable gzip compression  
+# Disable gzip compression
   content_encoding = "identity"
 
 # -- INPUT PLUGINS -- #
@@ -148,7 +148,7 @@ Telegraf should report the following if configured correctly:
 
 ## Verifying the integration
 
-1. Navigate to the QuestDB Web Console at `http://127.0.0.1:9000/`. The Schema
+1. Navigate to the QuestDB [Web Console](/docs/web-console/) at `http://127.0.0.1:9000/`. The Schema
    Navigator in the top left should display two new tables:
 
 - `cpu` generated from `inputs.cpu`
diff --git a/web-console.md b/web-console.md
index b19cc656..cef96064 100644
--- a/web-console.md
+++ b/web-console.md
@@ -1,7 +1,6 @@
 ---
 title: Web Console
-description:
-  Learn how to use the QuestDB Web Console. Launch queries, create
+description: Learn how to use the QuestDB Web Console. Launch queries, create
   visualizations and more. Includes pictures and examples.
 ---
 
@@ -9,7 +8,7 @@ import Screenshot from "@theme/Screenshot"
 
 ## Web Console
 
-The Web Console is a client that allows you to interact with QuestDB. It
+The [Web Console](/docs/web-console/) is a client that allows you to interact with QuestDB. It
 provides UI tools to query data and visualize the results in a table or plot.
 
 <Screenshot
@@ -19,7 +18,7 @@ provides UI tools to query data and visualize the results in a table or plot.
 
 ### Accessing the Web Console
 
-The Web Console will be available at `http://[server-address]:9000`. When
+The [Web Console](/docs/web-console/) will be available at `http://[server-address]:9000`. When
 running locally, this will be [http://localhost:9000](http://localhost:9000).
 
 ### Layout