diff --git a/Makefile b/Makefile
index 4c6f93b9d..d05d08bfc 100644
--- a/Makefile
+++ b/Makefile
@@ -77,7 +77,6 @@ deploy:
 	@echo "Deploy..."
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=31536000, immutable" --exclude '.DS_Store' --exclude '*' --include '*.webp' --content-type 'image/webp' ./dist/docs/_astro s3://www.surrealdb.com/docs/_astro/
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=31536000, immutable" --exclude '.DS_Store' --exclude '*.webp' ./dist/docs/_astro s3://www.surrealdb.com/docs/_astro/
-	aws s3 sync --region eu-west-2 --cache-control "public, max-age=86400" --exclude '.DS_Store' ./dist/docs/~partytown s3://www.surrealdb.com/docs/~partytown/
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=30" --delete --exclude '*' --include '*.html' ./dist/docs/ s3://www.surrealdb.com/docs/
 
 .PHONY: stage
@@ -85,5 +84,4 @@ stage:
 	@echo "Stage..."
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=31536000, immutable" --exclude '.DS_Store' --exclude '*' --include '*.webp' --content-type 'image/webp' ./dist/docs/_astro s3://www.surrealdb.dev/docs/_astro/
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=31536000, immutable" --exclude '.DS_Store' --exclude '*.webp' ./dist/docs/_astro s3://www.surrealdb.dev/docs/_astro/
-	aws s3 sync --region eu-west-2 --cache-control "public, max-age=86400" --exclude '.DS_Store' ./dist/docs/~partytown s3://www.surrealdb.dev/docs/~partytown/
 	aws s3 sync --region eu-west-2 --cache-control "public, max-age=30" --delete --exclude '*' --include '*.html' ./dist/docs/ s3://www.surrealdb.dev/docs/
diff --git a/astro.config.mjs b/astro.config.mjs
index 2c172b5b9..3263f8e9a 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -1,5 +1,4 @@
 import mdx from '@astrojs/mdx';
-import partytown from '@astrojs/partytown';
 import solidJs from '@astrojs/solid-js';
 import tailwind from '@astrojs/tailwind';
 import compress from 'astro-compress';
@@ -32,7 +31,6 @@ export default defineConfig({
         tailwind({
             nesting: true,
         }),
-        partytown(),
         compress({
             Image: false,
         }),
diff --git a/aws/viewer-request/index.js b/aws/viewer-request/index.js
index d270a32cc..9d27c2262 100644
--- a/aws/viewer-request/index.js
+++ b/aws/viewer-request/index.js
@@ -244,6 +244,7 @@ function handler(event) {
 				case 'surrealql':
 				case 'sdk':
 				case 'tutorials':
+				case 'cloud': 
 				case undefined:
 					break;
 				default:
@@ -256,4 +257,4 @@ function handler(event) {
 
 	return request;
 
-}
\ No newline at end of file
+}
diff --git a/bun.lockb b/bun.lockb
index 21293ac5e..0325a2426 100755
Binary files a/bun.lockb and b/bun.lockb differ
diff --git a/package.json b/package.json
index cbd9244c0..3dce2f932 100644
--- a/package.json
+++ b/package.json
@@ -62,7 +62,6 @@
         "unist-util-visit": "^5.0.0"
     },
     "devDependencies": {
-        "@astrojs/partytown": "^2.1.2",
         "@biomejs/biome": "1.8.3",
         "astro-compress": "^2.3.5",
         "esbuild": "^0.23.1",
diff --git a/scripts/post-build.ts b/scripts/post-build.ts
index 9a477285c..8d5bbdbcf 100644
--- a/scripts/post-build.ts
+++ b/scripts/post-build.ts
@@ -15,8 +15,132 @@ const scripts = [
     'https://static.ads-twitter.com/uwt.js',
 ];
 
-await extractInlineResources();
+await checkBrokenLinks();
 await fetchRemoteResources();
+await extractInlineResources();
+
+async function checkBrokenLinks() {
+    const broken: string[] = [];
+    const files = await glob('**/*.html', {
+        cwd: __dist,
+        dot: true,
+        absolute: true,
+        filesOnly: true,
+    });
+
+    const websiteCache = new Map<string, boolean>();
+    const self = ['https://surrealdb.com', 'https://www.surrealdb.com'];
+
+    for (const file of files) {
+        let loggedFile = false;
+        const raw = fs.readFileSync(file, { encoding: 'utf-8' });
+        const parsed = parseHTML(raw, {
+            comment: true,
+        });
+
+        const links = parsed.querySelectorAll('a');
+        for (const link of links) {
+            let href = link.getAttribute('href');
+            if (!href) {
+                continue;
+            }
+
+            let hasIssue = false;
+            function issue(issue: string) {
+                if (!href) {
+                    return;
+                }
+
+                if (!broken.includes(href)) {
+                    broken.push(href);
+                }
+
+                if (!hasIssue && !loggedFile) {
+                    console.error(`\n[ERROR] In file: ${file}`);
+                    loggedFile = true;
+                }
+
+                hasIssue = true;
+                console.error(`[ERROR] ${issue}`);
+            }
+
+            for (const domain of self) {
+                if (href.startsWith(domain)) {
+                    issue(`External link should be local: ${href}`);
+                    href = href.slice(domain.length);
+                    break;
+                }
+            }
+
+            if (href.startsWith('/')) {
+                href = href.split('#')[0];
+                href = href.split('?')[0];
+
+                let exists = false;
+
+                switch (true) {
+                    case href === '/docs':
+                    case href.startsWith('/docs/'): {
+                        exists = fs.existsSync(
+                            path.join(__root, 'dist', href, 'index.html')
+                        );
+                        break;
+                    }
+
+                    default: {
+                        if (!websiteCache.has(href)) {
+                            const res = await fetch(
+                                `https://surrealdb.com${href}`,
+                                {
+                                    redirect: 'manual',
+                                }
+                            );
+                            websiteCache.set(href, res.ok);
+                        }
+
+                        const res = websiteCache.get(href);
+                        if (res === undefined) {
+                            throw new Error(`Cache miss for ${href}`);
+                        }
+
+                        exists = res;
+                        break;
+                    }
+                }
+
+                if (!exists) {
+                    issue(`Broken link: ${href}`);
+                }
+            }
+
+            if (hasIssue) {
+                let elemStr = link.toString();
+                if (elemStr.length > 100) {
+                    elemStr = `${elemStr.slice(0, 97)}...`;
+                }
+
+                console.error(`[ERROR] For element: ${elemStr}`);
+            }
+        }
+    }
+
+    if (broken.length > 0) {
+        console.error('\n=============================================');
+        console.error('\n[ERROR] Broken links found.');
+        console.error(
+            '[ERROR] Possible issues include dead links, redirected links, or external links that should be local.'
+        );
+        console.error('[ERROR] Check the above logs for more in-depth details');
+        console.error("[ERROR] Here's the list: \n");
+        for (const link of broken) {
+            console.error(`[ERROR] Broken link: ${link}`);
+        }
+
+        console.error('\n');
+
+        throw new Error('Broken links found');
+    }
+}
 
 async function fetchRemoteResources() {
     // Fetch the remote scripts
@@ -28,12 +152,20 @@ async function fetchRemoteResources() {
         fs.writeFileSync(path.join(__astro, name), await minifyJS(content));
         // Scan the JS files in the dist folder
         console.log('[EXTRACT] Scanning JS files in dist/docs/ folder');
-        const files = await glob('**/*.js', {
-            cwd: __dist,
-            dot: true,
-            absolute: true,
-            filesOnly: true,
-        });
+        const files = [
+            ...(await glob('**/*.js', {
+                cwd: __dist,
+                dot: true,
+                absolute: true,
+                filesOnly: true,
+            })),
+            ...(await glob('**/*.html', {
+                cwd: __dist,
+                dot: true,
+                absolute: true,
+                filesOnly: true,
+            })),
+        ];
         // Loop over each file and process the content
         console.log(`[EXTRACT] Found ${files.length} JS files`);
         for (const file of files) {
diff --git a/src/assets/img/image/cloud/cloud-architecture-dark.png b/src/assets/img/image/cloud/cloud-architecture-dark.png
new file mode 100644
index 000000000..5515dba48
Binary files /dev/null and b/src/assets/img/image/cloud/cloud-architecture-dark.png differ
diff --git a/src/assets/img/image/cloud/cloud-dark.png b/src/assets/img/image/cloud/cloud-dark.png
new file mode 100644
index 000000000..d970bda12
Binary files /dev/null and b/src/assets/img/image/cloud/cloud-dark.png differ
diff --git a/src/assets/img/image/cloud/configure-dark.png b/src/assets/img/image/cloud/configure-dark.png
new file mode 100644
index 000000000..14adaba0e
Binary files /dev/null and b/src/assets/img/image/cloud/configure-dark.png differ
diff --git a/src/assets/img/image/cloud/create-instance.png b/src/assets/img/image/cloud/create-instance.png
new file mode 100644
index 000000000..5de21d86e
Binary files /dev/null and b/src/assets/img/image/cloud/create-instance.png differ
diff --git a/src/assets/img/image/cloud/create-root-user.png b/src/assets/img/image/cloud/create-root-user.png
new file mode 100644
index 000000000..993a65b8a
Binary files /dev/null and b/src/assets/img/image/cloud/create-root-user.png differ
diff --git a/src/assets/img/image/cloud/highly-available-and-scalable-dark.png b/src/assets/img/image/cloud/highly-available-and-scalable-dark.png
new file mode 100644
index 000000000..52f7bc1de
Binary files /dev/null and b/src/assets/img/image/cloud/highly-available-and-scalable-dark.png differ
diff --git a/src/assets/img/image/cloud/instance-capabilities.png b/src/assets/img/image/cloud/instance-capabilities.png
new file mode 100644
index 000000000..c57766cd6
Binary files /dev/null and b/src/assets/img/image/cloud/instance-capabilities.png differ
diff --git a/src/assets/img/image/cloud/light/cloud-architecture-light.png b/src/assets/img/image/cloud/light/cloud-architecture-light.png
new file mode 100644
index 000000000..d81d3bcea
Binary files /dev/null and b/src/assets/img/image/cloud/light/cloud-architecture-light.png differ
diff --git a/src/assets/img/image/cloud/light/cloud-light.png b/src/assets/img/image/cloud/light/cloud-light.png
new file mode 100644
index 000000000..84fd5da23
Binary files /dev/null and b/src/assets/img/image/cloud/light/cloud-light.png differ
diff --git a/src/assets/img/image/cloud/light/highly-available-and-scalable-light.png b/src/assets/img/image/cloud/light/highly-available-and-scalable-light.png
new file mode 100644
index 000000000..204eb2c9e
Binary files /dev/null and b/src/assets/img/image/cloud/light/highly-available-and-scalable-light.png differ
diff --git a/src/assets/img/image/cloud/namespace-database.png b/src/assets/img/image/cloud/namespace-database.png
new file mode 100644
index 000000000..5a8c3dc30
Binary files /dev/null and b/src/assets/img/image/cloud/namespace-database.png differ
diff --git a/src/assets/img/image/cloud/open-in-cli.png b/src/assets/img/image/cloud/open-in-cli.png
new file mode 100644
index 000000000..9e80d5f67
Binary files /dev/null and b/src/assets/img/image/cloud/open-in-cli.png differ
diff --git a/src/assets/img/image/cloud/open-in-http.png b/src/assets/img/image/cloud/open-in-http.png
new file mode 100644
index 000000000..2dff7609a
Binary files /dev/null and b/src/assets/img/image/cloud/open-in-http.png differ
diff --git a/src/assets/img/image/cloud/open-in-sdk.png b/src/assets/img/image/cloud/open-in-sdk.png
new file mode 100644
index 000000000..ee5239edb
Binary files /dev/null and b/src/assets/img/image/cloud/open-in-sdk.png differ
diff --git a/src/assets/img/image/cloud/open-in-surrealist.png b/src/assets/img/image/cloud/open-in-surrealist.png
new file mode 100644
index 000000000..7c5bedc7f
Binary files /dev/null and b/src/assets/img/image/cloud/open-in-surrealist.png differ
diff --git a/src/assets/img/image/cloud/querying-instance.png b/src/assets/img/image/cloud/querying-instance.png
new file mode 100644
index 000000000..c40027cf7
Binary files /dev/null and b/src/assets/img/image/cloud/querying-instance.png differ
diff --git a/src/assets/img/image/cloud/surreal-sidekick.png b/src/assets/img/image/cloud/surreal-sidekick.png
new file mode 100644
index 000000000..eeb6c07a6
Binary files /dev/null and b/src/assets/img/image/cloud/surreal-sidekick.png differ
diff --git a/src/assets/img/image/cloud/surrealcloud.png b/src/assets/img/image/cloud/surrealcloud.png
new file mode 100644
index 000000000..5194bb1cb
Binary files /dev/null and b/src/assets/img/image/cloud/surrealcloud.png differ
diff --git a/src/assets/img/image/cloud/update-billing.png b/src/assets/img/image/cloud/update-billing.png
new file mode 100644
index 000000000..31677e1a5
Binary files /dev/null and b/src/assets/img/image/cloud/update-billing.png differ
diff --git a/src/components/RenderDoc.astro b/src/components/RenderDoc.astro
index d2110930a..25356fbf3 100644
--- a/src/components/RenderDoc.astro
+++ b/src/components/RenderDoc.astro
@@ -4,7 +4,12 @@ import { getEntry } from 'astro:content';
 import type { CollectionKey } from 'astro:content';
 import { PageHeadings } from '@components/PageHeadings.tsx';
 import Sidebar from '@components/Sidebar/index.astro';
-import { generateBreadcrumb, generateSidebar } from '@src/util/doc';
+import {
+    findNextPage,
+    findPreviousPage,
+    generateBreadcrumb,
+    generateSidebar,
+} from '@src/util/doc';
 import { Icon } from 'astro-icon/components';
 import BaseLayout from './layout/BaseLayout.astro';
 import MarkdownContainer from './shared/MarkdownContainer.astro';
@@ -31,8 +36,9 @@ if (!entry) {
 const { Content, headings } = await entry.render();
 const sidebarItems = await generateSidebar(collection);
 const sidebarIndex = sidebarItems.flat.findIndex((item) => item.slug === slug);
-const prev = sidebarItems.flat.at(sidebarIndex - 1);
-const next = sidebarItems.flat.at(sidebarIndex + 1) ?? sidebarItems.flat[0];
+const prev = findPreviousPage(sidebarItems.flat, sidebarIndex);
+const next =
+    findNextPage(sidebarItems.flat, sidebarIndex) ?? sidebarItems.flat[0];
 
 function filteredHeadings() {
     if (
diff --git a/src/components/Sidebar/metadata.ts b/src/components/Sidebar/metadata.ts
index 9ebccf55e..4b2a60ab9 100644
--- a/src/components/Sidebar/metadata.ts
+++ b/src/components/Sidebar/metadata.ts
@@ -21,6 +21,8 @@ import LightSurrealDB from '@img/icon/light/surrealdb.png';
 import LightSurrealist from '@img/icon/light/surrealdb.png';
 import LightSurrealML from '@img/icon/light/surrealml.png';
 import LightSurrealQL from '@img/icon/light/surrealql.png';
+import LightCloud from '@img/image/cloud/surrealcloud.png';
+import DarkCloud from '@img/image/cloud/surrealcloud.png';
 
 import DarkSurrealDB from '@img/icon/dark/surrealdb.png';
 import DarkSurrealist from '@img/icon/dark/surrealist.png';
@@ -127,6 +129,17 @@ export const metadata = {
             href: 'https://github.com/surrealdb/surrealdb',
         },
     },
+    'doc-cloud': {
+        title: 'Surreal Cloud (Beta)',
+        icon: {
+            light: LightCloud,
+            dark: DarkCloud,
+        },
+        repo: {
+            title: 'Forum',
+            href: '/community',
+        },
+    },
     'doc-surrealist': {
         title: 'Surrealist',
         icon: {
diff --git a/src/components/layout/Analytics.astro b/src/components/layout/Analytics.astro
index e981d5fb7..7dd3da029 100644
--- a/src/components/layout/Analytics.astro
+++ b/src/components/layout/Analytics.astro
@@ -9,22 +9,6 @@
 
 <script defer is:inline>
 
-	// Clarity
-
-	window.clarity = function () { (window.clarity.q = window.clarity.q || []).push(arguments) };
-
-	{
-		let s = document.createElement('script');
-		s.src = 'https://www.clarity.ms/tag/idmjleqtib';
-		s.async = false;
-		s.defer = true;
-		document.head.appendChild(s);
-	}
-
-</script>
-
-<script defer is:inline type="text/partytown">
-
 	// Common Room
 
 	window.signals = Object.assign(
@@ -65,9 +49,7 @@
 	// Google
 
 	window.dataLayer = window.dataLayer || [];
-
     window.gtag = function () { window.dataLayer.push(arguments); };
-
     gtag('js', new Date());
     gtag('config', 'G-J1NWM32T1V');
 
diff --git a/src/components/layout/Footer/Footer.astro b/src/components/layout/Footer/Footer.astro
index 24612500d..6bbc871c5 100644
--- a/src/components/layout/Footer/Footer.astro
+++ b/src/components/layout/Footer/Footer.astro
@@ -17,23 +17,23 @@
         Discord
     </a>
     <span>•</span>
-    <a href="https://surrealdb.com/community">
+    <a href="/community">
         Community
     </a>
     <span>•</span>
-    <a href="https://surrealdb.com/cloud">
+    <a href="/cloud">
         Cloud
     </a>
     <span>•</span>
-    <a href="https://surrealdb.com/features">
+    <a href="/features">
         Features
     </a>
     <span>•</span>
-    <a href="https://surrealdb.com/releases">
+    <a href="/releases">
         Releases
     </a>
     <span>•</span>
-    <a href="https://surrealdb.com/install">
+    <a href="/install">
         Install
     </a>
 </div>
diff --git a/src/content/config.ts b/src/content/config.ts
index 588fb9548..6886cb501 100644
--- a/src/content/config.ts
+++ b/src/content/config.ts
@@ -15,6 +15,7 @@ const abstractDoc = defineCollection({
 
 export const docs = [
     'surrealdb',
+    'cloud',
     'surrealist',
     'surrealml',
     'surrealql',
diff --git a/src/content/doc-cloud/advanced-topics/_category_.json b/src/content/doc-cloud/advanced-topics/_category_.json
new file mode 100644
index 000000000..3c4ec0591
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/_category_.json
@@ -0,0 +1,4 @@
+{
+    "sidebar_label": "Advanced topics",
+    "sidebar_position": 5
+}
diff --git a/src/content/doc-cloud/advanced-topics/configure-an-instance.mdx b/src/content/doc-cloud/advanced-topics/configure-an-instance.mdx
new file mode 100644
index 000000000..616f77ac4
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/configure-an-instance.mdx
@@ -0,0 +1,68 @@
+---
+sidebar_position: 3
+sidebar_label: Configure an Instance
+title: Configure an Instance
+description: Surreal Cloud is a hosted version of SurrealDB, providing a fully managed, scalable, and secure database solution. This guide will help you migrate your existing SurrealDB instance to Surreal Cloud.
+---
+
+import Image from "@components/Image.astro";
+import LightConfigure from "@img/image/cloud/configure-dark.png";
+import DarkConfigure from "@img/image/cloud/configure-dark.png";
+
+import InstanceCapabilities from "@img/image/cloud/instance-capabilities.png";
+
+
+# Configure an Instance
+
+You can configure your Instance in the Surreal Cloud dashboard by clicking on the **Configure** button on the Instance card.
+
+<Image
+alt="Configure an Instance"
+src={{
+	light: LightConfigure,
+	dark: DarkConfigure,
+	}}  
+/>
+
+## Configuration options
+
+From the **Configure** modal, you can change the following settings:
+
+- **Instance type**: the type of the Instance.
+- **Compute nodes**: the number of compute nodes to use.
+- **Capabilities**: the capabilities of the Instance.
+
+You can also access the Instance hostname and delete the Instance from this modal.
+
+### Instance type
+
+The Instance type you choose will determine the compute and memory available to your Instance.
+
+> [!IMPORTANT]
+> You can only change the type of the Instance on a paid plan. Please add billing information to your account before changing the Instance type.
+
+### Compute nodes
+
+> [!NOTE]
+> In beta, you can only have 1 compute node. Customising compute nodes will be available soon.
+
+The number of compute nodes you choose will determine the number of Instances you can run on the same plan. For example, if you choose 2 compute nodes, you can run 2 Instances on the same plan.
+
+### Instance capabilities
+
+The capabilities you choose will determine the features available to your Instance. This includes scripting, guest access, enabled endpoints for RPC and HTTP and more.
+
+> [!IMPORTANT]
+> In beta, these Instance capabilities are read-only.
+
+<Image
+alt="Configure an Instance"
+src={{
+	light: InstanceCapabilities,
+	dark: InstanceCapabilities,
+	}}  
+/>
+
+### Delete an Instance 
+
+You can delete an Instance by clicking the **Delete** button on the Instance card. This will bring up a confirmation modal. Once confirmed, the Instance will be deleted and you will be redirected to the Instances page. 
\ No newline at end of file
diff --git a/src/content/doc-cloud/advanced-topics/index.mdx b/src/content/doc-cloud/advanced-topics/index.mdx
new file mode 100644
index 000000000..da34f235d
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/index.mdx
@@ -0,0 +1,21 @@
+---
+sidebar_position: 1
+sidebar_label: Advanced topics
+title: Advanced topics | Surreal Cloud
+description: In this section you will explore the advanced topics for navigating Surreal Cloud in Surrealist.
+---
+
+# Advanced topics
+
+In this section you will explore the following advanced topics for navigating Surreal Cloud in Surrealist :
+
+- [Search and shortcuts](/docs/cloud/advanced-topics/search-and-shortcuts)
+- [Configure an Instance](/docs/cloud/advanced-topics/configure-an-instance)
+- [Migrating databases](/docs/cloud/advanced-topics/migrating-data)
+- [Settings and customisation](/docs/cloud/advanced-topics/settings-and-customisation)
+- [SurrealQL editor](/docs/cloud/advanced-topics/surrealql-editors)
+
+
+## Next steps 
+
+Explore the advanced topics for navigating Surreal Cloud in Surrealist in detail. 
\ No newline at end of file
diff --git a/src/content/doc-cloud/advanced-topics/migrating-data.mdx b/src/content/doc-cloud/advanced-topics/migrating-data.mdx
new file mode 100644
index 000000000..4bb7cc393
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/migrating-data.mdx
@@ -0,0 +1,29 @@
+---
+sidebar_position: 3
+sidebar_label: Migrating data
+title: Migrating Data to Surreal Cloud
+description: Surreal Cloud is a hosted version of SurrealDB, providing a fully managed, scalable, and secure database solution. This guide will help you migrate your existing SurrealDB instance to Surreal Cloud.
+---
+
+# Migrating data from SurrealDB to Surreal Cloud
+
+Surreal Cloud is a hosted version of SurrealDB, providing a fully managed, scalable, and secure database solution. This guide will help you migrate your existing SurrealDB Instance to Surreal Cloud.
+
+
+## Exporting and importing data
+
+1. Export your current data as a `.surql` (SurrealQL) file. You can do this using the [`surreal export`](/docs/surrealdb/cli/export) command in the terminal:
+
+```bash
+# Example export command to export data to a file called `export.surql` in the downloads directory.
+surreal export --conn <connection-url> --user root --pass root --ns test --db test downloads/export.surql
+``` 
+
+2. This will create a file called `export.surql` in the current directory.
+
+3. You can now import this file into your Surreal Cloud Instance.
+
+
+```bash
+surreal import --conn <connection-url> --user root --pass root --ns test --db test downloads/export.surql
+```
diff --git a/src/content/doc-cloud/advanced-topics/search-and-shortcuts.mdx b/src/content/doc-cloud/advanced-topics/search-and-shortcuts.mdx
new file mode 100644
index 000000000..5d016ae7a
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/search-and-shortcuts.mdx
@@ -0,0 +1,123 @@
+---
+sidebar_position: 1
+sidebar_label: Search and shortcuts
+title: Surreal Cloud | Search and shortcuts
+description: In this section, you will learn about the search and shortcuts in Surrealist as it relates to the Surreal Cloud dashboard.
+---
+
+import Image from "@components/Image.astro";
+
+import SearchAndShortcutsLight from "@img/image/surrealist/search-and-hot-key.png";
+import SearchAndShortcutsDark from "@img/image/surrealist/search-and-hot-key.png";
+
+# Search and shortcuts
+
+Surrealist offers a range of shortcuts to help you navigate the interface more efficiently. You can find a list of all available shortcuts by pressing `Ctrl + K` or `Cmd + K` on your keyboard.
+
+In the search modal, you can access all available shortcuts for open sessions, the views, all available tables in your connect database and the settings dialog.
+
+<Image
+alt="Search and Shortcuts"
+src={{
+    light: SearchAndShortcutsLight,
+    dark: SearchAndShortcutsDark,
+    }}
+/>
+
+<br/>
+
+<br/>
+
+<table>
+    <thead>
+        <tr>
+            <th scope="col">Options</th>
+            <th scope="col">Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Connections</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Open a list of all available connections and create a new connection type.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Views</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Open all available views in the current session. This can be the Cloud view, GraphQL view, Query view, Designer view or the Authentication view.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Tables</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Shows all available tables in the connected database. If you have no tables in the connection, load the Surreal Deal Store dataset, you can see the tables in the dataset.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Query</code>
+            </td>
+            <td scope="row" data-label="Description">
+                See all saved queries, view the query history and create a new query. Comment out a line in the query editor using `Cmd + /` or `Ctrl + /`. 
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Explorer</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Import and export your database schema in a `.surql` file format.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Authentication</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Create user permissions and roles for your connected database.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>API Docs</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Access the SurrealDB API documentation and access snippets for your queries in different SDK languages.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Settings</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Access the Settings dialog to customise the appearance and behaviour of Surrealist.
+                Increase the view size of your editor with `cmd + Option + +` or reduce with `cmd + Option + -`.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Navigator</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Reload the navigator to see all available shortcuts and open the search modal.
+            </td>
+        </tr>
+        <tr>
+            <td scope="row" data-label="Type">
+                <code>Developer</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Open a new connection and reset tour settings.
+            </td>
+        </tr>
+    </tbody>
+</table>
+
+
diff --git a/src/content/doc-cloud/advanced-topics/settings-and-customisation.mdx b/src/content/doc-cloud/advanced-topics/settings-and-customisation.mdx
new file mode 100644
index 000000000..feb4b8c02
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/settings-and-customisation.mdx
@@ -0,0 +1,29 @@
+---
+sidebar_position: 4
+sidebar_label: Settings and customisation
+title: Surreal Cloud | Settings and Customisation
+description: Surrealist is a user interface for interacting with your SurrealDB database visually. It enables you to seamlessly connect to any SurrealDB instance, allowing you to execute queries, explore your tables, design your schemas, and much more.
+---
+
+
+#  Settings and customisation
+
+In the bottom left of the interface you can find a settings(⚙) button to open the Settings dialog. These Settings allow you to further customise the behaviour and appearance of Surrealist, such as switching between light and dark mode, increasing or decreasing the editor font sizes, and configure default values for new connections.
+
+## Behaviour
+
+In this section you can configure the behaviour of the interface, such as **connection** and **editor** related settings.
+
+## Appearance
+
+The appearance section allows you to scale the fonts in the editor and also select your default query output view and set the behaviour for your Query and designer views.
+
+You can also show your created instances in a list or a grid. 
+
+## Filters
+
+You can filter the instances by their type (**nano**, **small**) and their region (**AWS US East (N. Virginia)** or **AWS EU West (Ireland)**).
+
+## Templates
+
+You can configure [connection templates](/docs/surrealist/advanced-topics/connection-templates) to reuse connection details when creating new connections. This is especially useful when you find yourself connecting to similar databases frequently.
diff --git a/src/content/doc-cloud/advanced-topics/surrealql-editors.mdx b/src/content/doc-cloud/advanced-topics/surrealql-editors.mdx
new file mode 100644
index 000000000..d93482961
--- /dev/null
+++ b/src/content/doc-cloud/advanced-topics/surrealql-editors.mdx
@@ -0,0 +1,98 @@
+---
+sidebar_position: 6
+sidebar_label: SurrealQL editors
+title: Surreal Cloud | SurrealQL Editors
+description: Surrealist is a user interface for interacting with your SurrealDB database visually. It enables you to seamlessly connect to any SurrealDB instance, allowing you to execute queries, explore your tables, design your schemas, and much more.
+---
+
+# SurrealQL editors
+
+Throughout Surrealist you will encounter various SurrealQL editors. These editors support intelligent SurrealQL highlighting and provide a range of features to help you write queries and edit records.
+
+## Shortcuts
+
+Editors support an array of useful shortcuts to help you navigate and edit more efficiently.
+
+<table>
+    <thead>
+        <tr>
+            <th scope="col">Shortcuts</th>
+            <th scope="col">Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>tab</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Indent the current line by 4 spaces.
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>shift + tab</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Unindent the current line by 4 spaces.
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + f</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Open the search and replace panel
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + /</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Toggles comments on the selected or active line(s)
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + left click</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Place multiple cursors at the clicked locations
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + shift + L</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Selects all occurrences of the currently selected text
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + d</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Selects next occurrence of the currently selected text
+            </td>
+        </tr>
+		<tr>
+            <td scope="row" data-label="Shortcuts">
+                <code>ctrl/cmd + enter</code>
+            </td>
+            <td scope="row" data-label="Description">
+                Execute the query query (only applied to the query editor)
+            </td>
+        </tr>
+	</tbody>
+</table>
+
+## Record inspection
+
+Some editors support record inspection, which allows you to open a record in the Record inspector drawer by holding `ctrl/cmd` and left-clicking on a record id.
+
+## JSON
+
+Some editors, such as the record editor and query responses, support falling back to a JSON representation.
+This can be configured in the Settings dialog under `Appearance > Value formatting mode`.
\ No newline at end of file
diff --git a/src/content/doc-cloud/billing-and-support/_category_.json b/src/content/doc-cloud/billing-and-support/_category_.json
new file mode 100644
index 000000000..4f2bb39e1
--- /dev/null
+++ b/src/content/doc-cloud/billing-and-support/_category_.json
@@ -0,0 +1,4 @@
+{
+    "sidebar_label": "Billing and support",
+    "sidebar_position": 5
+}
diff --git a/src/content/doc-cloud/billing-and-support/billing.mdx b/src/content/doc-cloud/billing-and-support/billing.mdx
new file mode 100644
index 000000000..258f3b288
--- /dev/null
+++ b/src/content/doc-cloud/billing-and-support/billing.mdx
@@ -0,0 +1,61 @@
+---
+sidebar_position: 1
+sidebar_label: Billing
+title: Billing | Surreal Cloud (Beta)
+description: Overview of Surreal Cloud (Beta) and how to get started with it.
+---
+
+import Image from "@components/Image.astro";
+
+import UpdateBillingLight from '@img/image/cloud/update-billing.png';
+import UpdateBillingDark from '@img/image/cloud/update-billing.png';
+
+# Billing
+
+Surreal Cloud (Beta) offers a flexible pricing model that allows you to pay only for the resources you use. The pricing is based on the amount of storage, compute power, and network bandwidth you consume, enabling you to scale your resources up or down based on your requirements.
+
+You can manage your billing information and payment details in the Billing section of the Surreal Cloud (Beta) dashboard.
+
+
+## Update billing information
+
+To update your billing information, you can click on the **Update** button on the top right corner of the billing information page.
+
+<Image
+alt="Update Billing"
+src={{
+	light: UpdateBillingLight,
+	dark: UpdateBillingDark,
+	}}
+/>
+
+
+## View payment details
+
+To view your payment details, you can click on the **Billing** tab in the Surreal Cloud (Beta) dashboard. This will display a comprehensive overview of your payment history, including past invoices, current charges, and upcoming payments. 
+
+You can also see information about your payment method, billing cycle, and any active subscriptions or usage-based charges.
+
+
+## Discount codes
+
+If you have a discount code, you can enter it in the **Discount code** field on the billing page. This will apply the discount to your account and reduce the amount you owe.
+
+
+## Referrals
+
+The Surreal Cloud (Beta) referral program allows you to invite a friend in exchange for benefits.
+
+1. Refer a friend by sharing your personalized referral link. You can find your personalized referral link [in the Billing dashboard](https://surrealist.app/cloud/billing).
+2. After your friend signs up, you will receive $10 of credit (up to a max of $50 or 5 referrals) and your friend will receive $25. In order to use your rewards you must enter your billing details.
+
+## Invoices
+
+You can view and download your payment invoices in the Surreal Cloud (Beta) dashboard.
+
+## Billing support
+
+If you have any questions or need help with Surreal Cloud (Beta) billing, please send an email to [support@surrealdb.com](mailto:support@surrealdb.com) outlining the nature of your query and we will help you.
+
+> [!IMPORTANT]
+> Please reach out using the email address associated with your Surreal Cloud account. You can find this by hovering over the Person icon in the top right hand corner within Surrealist.
\ No newline at end of file
diff --git a/src/content/doc-cloud/billing-and-support/index.mdx b/src/content/doc-cloud/billing-and-support/index.mdx
new file mode 100644
index 000000000..6be2d6087
--- /dev/null
+++ b/src/content/doc-cloud/billing-and-support/index.mdx
@@ -0,0 +1,13 @@
+---
+sidebar_position: 1
+sidebar_label: Billing and support
+title: Billing and support | Surreal Cloud
+description: In this section you will explore the billing and support options for Surreal Cloud.
+---
+
+# Billing and support
+
+In this section you will explore the following billing and support options for Surreal Cloud :
+
+- [Billing](/docs/cloud/billing-and-support/billing)
+- [Support](/docs/cloud/billing-and-support/support)
diff --git a/src/content/doc-cloud/billing-and-support/support.mdx b/src/content/doc-cloud/billing-and-support/support.mdx
new file mode 100644
index 000000000..cc0d6ad2f
--- /dev/null
+++ b/src/content/doc-cloud/billing-and-support/support.mdx
@@ -0,0 +1,46 @@
+---
+sidebar_position: 2
+sidebar_label: Support
+title: Support | Surreal Cloud
+description: Support offered by Surreal Cloud.
+---
+import Image from "@components/Image.astro";
+
+import SurrealSidekickDark from '@img/image/cloud/surreal-sidekick.png';
+
+# Support
+
+Surreal Cloud offers a variety of tools, resources, and community channels to help you get started, enhance your skills, and resolve any issues you may encounter depending on your problem.
+
+## Surreal Sidekick (beta)
+
+Surreal Sidekick (beta) is an AI copilot that can help you get started with SurrealDB, convert queries to SurrealQL, and answer general questions. Surreal Sidekick is only trained with public facing resources, such as our [SurrealDB documentation](/docs/surrealdb), [SurrealDB University](/learn), and the [SurrealDB Book](/learn/book).
+
+<Image
+alt="Surreal Sidekick"
+src={{
+	light: SurrealSidekickDark,
+	dark: SurrealSidekickDark,
+	}}  
+/>
+
+### Getting started
+To start using Surreal Sidekick, you'll need a [Surreal Cloud account](/docs/cloud/getting-started/create-an-account). Once logged in, navigate to Surreal Sidekick in the sidebar and start asking questions.
+
+> [!WARNING]
+>Surreal Sidekick, like any AI model, can occasionally provide incorrect information or hallucinate. We continuously improve our documentation and public resources to enhance Surreal Sidekick's accuracy. In accordance with our terms, please don’t submit any sensitive data.
+
+## Account and billing support
+
+For account or billing-related issues, you can raise a support ticket by emailing [support@surrealdb.com](mailto:support@surrealdb.com).
+
+## Community support
+
+Join our [Discord](https://discord.gg/surrealdb) community to connect with knowledgeable users and get help with your questions. Within the `#surreal-cloud` channel you can troubleshoot issues, ask for tips or chat with other Surreal Cloud users. 
+
+Our team is active in the server too and can escalate more complex issues if needed.
+
+## Additional support channels
+
+If you need further assistance with your Surreal Cloud account, our community is here to help through our [Discord](https://discord.gg/surrealdb). 
+
diff --git a/src/content/doc-cloud/connect/_category_.json b/src/content/doc-cloud/connect/_category_.json
new file mode 100644
index 000000000..3db0a8d43
--- /dev/null
+++ b/src/content/doc-cloud/connect/_category_.json
@@ -0,0 +1,4 @@
+{
+    "sidebar_label": "Connect to an Instance",
+    "sidebar_position": 3
+}
diff --git a/src/content/doc-cloud/connect/cli.mdx b/src/content/doc-cloud/connect/cli.mdx
new file mode 100644
index 000000000..c0ab1fac0
--- /dev/null
+++ b/src/content/doc-cloud/connect/cli.mdx
@@ -0,0 +1,41 @@
+---
+sidebar_position: 3
+sidebar_label: Connect via CLI
+title: Connect via CLI | Surreal Cloud
+description: Connect to your Surreal Cloud instance using the CLI and run queries.
+---
+
+import Image from "@components/Image.astro";
+
+import OpenInCLI from '@img/image/cloud/open-in-cli.png';
+
+# Connect via CLI
+
+Once you have created a Surreal Cloud Instance, you can connect to it via CLI. The SurrealDB CLI lets you interact with your Surreal Cloud Instance from the command line.
+
+
+## Prerequisites
+
+Before connecting to your Surreal Cloud Instance using the CLI, you need to install the [SurrealDB CLI](/docs/surrealdb/installation).
+
+## Connect to your Surreal Cloud Instance
+
+Once it is installed, you can connect to your Surreal Cloud Instance using the [`surreal sql`](/docs/surrealdb/cli/sql) command. This command connects to your Surreal Cloud Instance using the specified endpoint and token. 
+
+```bash
+surreal sql --endpoint <endpoint> --token <token>
+```
+
+<Image
+alt="Surreal Cloud"
+src={{
+	light: OpenInCLI,
+	dark: OpenInCLI,
+	}}
+/>
+
+The `token` is a JSON Web Token (JWT) that is used to authenticate your connection to the Surreal Cloud Instance. You can find the token in the Instance details page in the Surreal Cloud console.
+
+## Next steps
+
+Learn more about the [SurrealDB CLI](/docs/surrealdb/cli) in the SurrealDB documentation.
diff --git a/src/content/doc-cloud/connect/http.mdx b/src/content/doc-cloud/connect/http.mdx
new file mode 100644
index 000000000..b081c913b
--- /dev/null
+++ b/src/content/doc-cloud/connect/http.mdx
@@ -0,0 +1,39 @@
+---
+sidebar_position: 5
+sidebar_label: Connect via HTTP using cURL
+title: Connect via HTTP using cURL | Surreal Cloud
+description: Connect to your Surreal Cloud instance using the HTTP API and run queries.
+---
+
+import Image from "@components/Image.astro";
+
+import OpenInHTTPCurlLight from '@img/image/cloud/open-in-http.png';
+import OpenInHTTPCurlDark from '@img/image/cloud/open-in-http.png';
+
+# Connect via HTTP using cURL
+
+Surreal Cloud supports connection via HTTP. This allows you to connect to your Surreal Cloud Instance using curl or any HTTP client. To get started, select the **Connect** button on your Instance. Then select **HTTP cURL**. 
+
+This will open a modal to fill in your credentials for **Namespace** and **Database** and authentication before you can copy the URL. 
+
+
+<Image
+alt="Open in HTTP cURL"
+src={{
+	light: OpenInHTTPCurlLight,
+	dark: OpenInHTTPCurlDark,
+	}}
+/>
+
+
+> [!NOTE]
+> The URL provided can be used in any HTTP client, but by default it is set to use curl. Use the URL in your HTTP client to connect to your Surreal Cloud Instance from clients like Postman or any other HTTP client.
+
+## Connect to your Surreal Cloud Instance
+
+Once you have filled in the credentials, copy the URL and connect to your Surreal Cloud Instance. Below is an example of the connection URL in curl.
+
+```bash
+curl -X GET "https://cloud-demo-069qmb9jjttknc0djomp73flfs.aws-use1.surreal.cloud/version"
+```
+
diff --git a/src/content/doc-cloud/connect/index.mdx b/src/content/doc-cloud/connect/index.mdx
new file mode 100644
index 000000000..e34c5b56b
--- /dev/null
+++ b/src/content/doc-cloud/connect/index.mdx
@@ -0,0 +1,28 @@
+---
+sidebar_position: 1
+sidebar_label: Connect to Instance
+title: Connect to Instance | Surreal Cloud
+description: In this section you will explore the connection options for Surreal Cloud instances. You can connect to your Instance using the Surreal Cloud CLI or any of the supported SDKs.
+---
+
+# Connect to your Surreal Cloud Instance
+
+You can connect to your Surreal Cloud instances in three main ways. In this section you will explore the following connection options:
+
+ 
+- [connect via Surrealist](/docs/cloud/connect/surrealist) : Surrealist is a query builder and IDE for SurrealDB. It allows you to connect to your Surreal Cloud Instance and run queries in a graphical interface.
+- [connect via CLI](/docs/cloud/connect/cli) : using the command-line interface for SurrealDB, you can connect to your Surreal Cloud Instance and run queries in a command-line interface.
+- [connect via SDK](/docs/cloud/connect/sdk) : Surreal Cloud supports a variety of SDKs for connecting to your Instance. You can use the SDKs to connect to your Instance and run queries in your preferred programming language.
+- [connect via HTTP](/docs/cloud/connect/http) : Surreal Cloud supports a REST API for connecting to your Instance. You can use the API to connect to your Instance and run queries using CURL or any HTTP client.
+
+## Before you begin
+
+To connect to an Instance, you must have the following:
+
+- [a Surreal Cloud account](/docs/cloud/getting-started/create-an-account).
+- [an Instance to connect to](/docs/cloud/getting-started/create-an-instance).
+
+
+## Next steps 
+
+Explore the connection options for Surreal Cloud instances in detail. 
\ No newline at end of file
diff --git a/src/content/doc-cloud/connect/sdk.mdx b/src/content/doc-cloud/connect/sdk.mdx
new file mode 100644
index 000000000..5a876a265
--- /dev/null
+++ b/src/content/doc-cloud/connect/sdk.mdx
@@ -0,0 +1,185 @@
+---
+sidebar_position: 4
+sidebar_label: Connect via SDK
+title: Connect via SDK | Surreal Cloud
+description: Connect to your Surreal Cloud Instance using any of the available SDKs.
+---
+
+import Image from "@components/Image.astro";
+
+import OpenInSDK from '@img/image/cloud/open-in-sdk.png';
+
+import CreateRootUser from '@img/image/cloud/create-root-user.png';
+
+import Tabs from "@components/Tabs/Tabs.astro";
+import TabItem from "@components/Tabs/TabItem.astro";
+
+# Connect via SDK
+
+Once you have created a Surreal Cloud Instance, you can connect to it using any of the [available SDKs](/docs/surrealdb/integration/sdks). This allows you to interact with your Surreal Cloud Instance programmatically.
+
+
+<Image
+alt="Open in SDK"
+src={{
+	light: OpenInSDK,
+	dark: OpenInSDK,
+	}}
+/>
+ 
+After you have selected your SDK, you will need to provide your connection details which will populate the code snippet to your Surreal Cloud Instance.
+
+
+## Enter connection details
+
+When using any of the SurrealDB SDKs, before you can start querying your Surreal Cloud Instance, you will need to provide your connection details. SurrealDB requires **namespace** & **database** details so that it knows where to run and store your data. Learn more about [namespaces](/docs/surrealdb/introduction/concepts/namespace) and [databases](/docs/surrealdb/introduction/concepts/database) in the SurrealDB documentation.
+
+
+
+### Create a root authentication
+
+> [!NOTE]
+> This step is only required if you are authenticating using the `signin` method on your initial connection. Learn more about [access methods](/docs/surrealql/statements/define/access) and [system Users](/docs/surrealql/statements/define/user) in the SurrealDB documentation.
+
+
+First navigate to the Authentication panel of Surrealist. There, you can create a root user by clicking on the **+** button in the **Root Authentication** section. 
+
+In the dialog that appears, select either:
+
+- **new system user**: create a root user by entering a username, password, and selecting a role to define their access level to Instance resources and permissions
+- **new access method**: create an access method by entering a name and selecting the type to define its access level to Instance resources and permissions
+
+For both options, you can configure the Token duration and session duration.
+
+<Image
+alt="Open in SDK"
+src={{
+	light: CreateRootUser,
+	dark: CreateRootUser,
+	}}
+/>
+
+After creating your root authentication, you will be able to authenticate with your Surreal Cloud Instance using any of the available SDKs.
+
+If you want to create a Namespace and Database authentication for record-level access, you will need to first create a Namespace and Database. Learn more about [namespaces](/docs/surrealdb/introduction/concepts/namespace) and [databases](/docs/surrealdb/introduction/concepts/database) in the SurrealDB documentation.
+
+
+## Connect to your Surreal Cloud Instance
+
+After you have created your root authentication for root-level access, you can use the credentials to sign in to your Surreal Cloud Instance. 
+
+The `connect` method takes your Surreal Cloud connection string as an argument to connect to your Surreal Cloud Instance. You can then fill in the **namespace** and **database** details to select the specific namespace and database you want to use. 
+
+If you are using a system user option of the root authentication, you can also fill in the **username** and **password** details to sign in to your Surreal Cloud Instance.
+
+> [!NOTE]
+>If you are using a non-root user, depending on the access method you have created, you will need to fill in the `access` details to sign in to your Surreal Cloud Instance. Please refer to the [documentation for your specific SDK](/docs/surrealdb/integration/sdks) for more information.
+
+
+{/* Surreal Cloud provides a connection string that you can use to connect to your instance. This connection string includes the endpoint and token that you need to authenticate your connection. 
+
+In your preferred SDK, using the `connect` method, which takes a connection string as an argument to connect to your Surreal Cloud Instance.  */}
+
+
+
+Below are examples of how you can connect to your Instance using the SurrealDB SDK:
+
+
+<Tabs groupId="SDKs">
+  <TabItem value="Rust" label="Rust" default>
+
+```rust
+use surrealdb::engine::remote::ws::Wss;
+use surrealdb::opt::auth::Root;
+use surrealdb::Surreal;
+
+#[tokio::main]
+async fn main() -> surrealdb::Result<()> {
+	// Connect to the server
+	let db = Surreal::new::<Wss>("cloud-docs-068rp16e0hsnl62vgooa7omjks.aws-euw1.staging.surrealdb.cloud").await?;
+
+	// Signin as a namespace, database, or root user
+	db.signin(Root {
+		username: "<created root user>",
+		password: "<created root password>",
+	})
+	.await?;
+
+	// Select a specific namespace / database
+	db.use_ns("Cloud Namespace").use_db("Cloud Database").await?;
+
+	Ok(())
+}
+```
+  </TabItem>
+<TabItem value="JavaScript" label="JavaScript">
+
+```js
+import { Surreal } from "surrealdb";
+const db = new Surreal();
+
+// Connect to the server
+await db.connect('wss://cloud-docs-068rp16e0hsnl62vgooa7omjks.aws-euw1.staging.surrealdb.cloud');
+
+// Signin as a namespace, database, or root user
+await db.signin({
+	username: '<created root user>',
+	password: '<created root password>',
+});
+
+// Select a specific namespace / database
+await db.use({ ns: 'Cloud Namespace', db: 'Cloud Database' });
+```
+</TabItem>
+  <TabItem value="Python" label="Python">
+
+```py
+from surrealdb import SurrealDB
+
+db = SurrealDB("ws://localhost:8000")
+db.connect()
+db.use("example_ns", "example_db")
+db.sign_in("root", "root")
+```
+</TabItem>
+<TabItem value=".NET" label=".NET">
+
+```csharp
+using SurrealDb.Net;
+using SurrealDb.Net.Models.Auth;
+
+using var db = new SurrealDbClient("https://cloud-docs-068rp16e0hsnl62vgooa7omjks.aws-euw1.staging.surrealdb.cloud/rpc");
+
+// Select a namespace and database
+await db.Use("Cloud Namespace", "Cloud Database");
+
+// Authenticate
+await db.SignIn(new RootAuth
+{
+    Username = "<created root user>",
+    Password = "<created root password>",
+});
+```
+</TabItem>
+<TabItem value="PHP" label="PHP">
+```php
+db = new Surreal();
+
+$db->connect("wss://cloud-docs-068rp16e0hsnl62vgooa7omjks.aws-euw1.staging.surrealdb.cloud/rpc", [
+    "namespace" => "Cloud Namespace",
+    "database" => "Cloud Database",
+    "versionCheck" => false // <-- optional ( default: true )
+]);
+
+$db->signin([
+   "username" => "<created root user>",
+   "password" => "<created root password>"
+]);
+```
+</TabItem>
+</Tabs>
+
+## Next steps
+
+Learn more about the [SurrealDB SDKs](/docs/surrealdb/integration/sdks) in the SurrealDB documentation.
+ 
\ No newline at end of file
diff --git a/src/content/doc-cloud/connect/surrealist.mdx b/src/content/doc-cloud/connect/surrealist.mdx
new file mode 100644
index 000000000..57d137945
--- /dev/null
+++ b/src/content/doc-cloud/connect/surrealist.mdx
@@ -0,0 +1,61 @@
+---
+sidebar_position: 2
+sidebar_label: Connect via Surrealist
+title: Connect via Surrealist | Surreal Cloud
+description: Connect to your Surreal Cloud instance using Surrealist.
+---
+
+import Image from "@components/Image.astro";
+
+import OpenInSurrealistLight from '@img/image/cloud/open-in-surrealist.png';
+import OpenInSurrealistDark from '@img/image/cloud/open-in-surrealist.png';
+
+import NamespaceDatabaseLight from '@img/image/cloud/namespace-database.png';
+import NamespaceDatabaseDark from '@img/image/cloud/namespace-database.png';
+
+import QueryingInstanceLight from '@img/image/cloud/querying-instance.png';
+import QueryingInstanceDark from '@img/image/cloud/querying-instance.png';
+
+# Connect via Surrealist
+
+Once you have created a Surreal Cloud Instance, you can connect to it in Surrealist, which allows you to interact with your created Cloud Instance from the [query view in Surrealist](/docs/surrealist/concepts/sending-queries).
+
+Start by clicking the **Connect** button on your Instance. Then select the **Open in Surrealist** option in the connection modal. This will open the Surrealist query view.
+
+<Image
+alt="Open in Surrealist"
+src={{
+	light: OpenInSurrealistLight,
+	dark: OpenInSurrealistDark,
+	}}
+/>
+
+## Querying your Instance 
+
+Once in the query view, and before you can run queries in Surrealist, you need to select a [Namespace](/docs/surrealdb/introduction/concepts) and a [Database](/docs/surrealdb/introduction/concepts) to work in.
+
+First click on the **Namespace** dropdown and select the namespace you want to work in (if you have not created a namespace, you will see an option to create one). Then click on the **Database** dropdown and select the database you want to work in.
+
+<Image
+alt="Namespace and Database"
+src={{
+	light: NamespaceDatabaseLight,
+	dark: NamespaceDatabaseDark,
+	}}
+/>
+
+Once you have selected a namespace and database, you can start running queries in Surrealist. You can run queries to create, read, update, and delete data in your Surreal Cloud Instance.
+
+<Image
+alt="Querying Instance"
+src={{
+	light: QueryingInstanceLight,
+	dark: QueryingInstanceDark,
+	}}
+/>
+
+You can now see your queries and results in the Surrealist query view. You can also see the created records in the explore view.
+
+## Next steps
+
+Learn more about [Surrealist](/docs/surrealist) and SurrealQL in the [SurrealDB documentation](/docs/surrealql).
diff --git a/src/content/doc-cloud/faqs/_category_.json b/src/content/doc-cloud/faqs/_category_.json
new file mode 100644
index 000000000..657dc9851
--- /dev/null
+++ b/src/content/doc-cloud/faqs/_category_.json
@@ -0,0 +1,4 @@
+{
+    "sidebar_label": "FAQs",
+    "sidebar_position": 6
+}
diff --git a/src/content/doc-cloud/faqs/index.mdx b/src/content/doc-cloud/faqs/index.mdx
new file mode 100644
index 000000000..ddd652ee3
--- /dev/null
+++ b/src/content/doc-cloud/faqs/index.mdx
@@ -0,0 +1,186 @@
+---
+sidebar_position: 7
+sidebar_label: FAQs
+title: FAQs | Surreal Cloud (Beta)
+description: If you have questions about Surreal Cloud (Beta), you can find answers here. This document provides a comprehensive understanding of Surreal Cloud (Beta), whether you are a beginner getting started with Surreal Cloud (Beta) or an experienced user looking for specific information.
+---
+
+# Frequently asked questions
+
+If you have questions about Surreal Cloud (Beta), you can find answers on this page. This document provides a comprehensive understanding of Surreal Cloud (Beta), whether you are a beginner getting started with Surreal Cloud (Beta) or an experienced user looking for specific information.
+
+## General questions 
+
+### What is Surreal Cloud (Beta)? 
+
+Surreal Cloud (Beta) offers the power and flexibility of SurrealDB without the pain of managing infrastructure. We take care of managing and operating the underlying infrastructure so that you can focus on what you do best-building great applications for your customers. 
+
+
+### How do I get started with Surreal Cloud (Beta)?
+
+Getting started is easy.  [Sign up for an account on Surrealist](https://surrealist.app/cloud/). Once registered, you can access the dashboard, choose services, and start building with Surreal Cloud (Beta) immediately.
+
+### Are there self-help resources like documentation or tutorials available?
+Yes. We have a [resource hub with all our latest documentation](/docs).  We also recommend our [YouTube channel](https://www.youtube.com/channel/UCjf2teVEuYVvvVC-gFZNq6w) where you can find easy-to-follow tutorials, and content from our Community.
+
+
+### What kind of support is available at the launch of Surreal Cloud (Beta)?
+
+We are offering community support at launch.  You can get help via our [Discord channel](https://discord.gg/surrealdb) `#surreal-cloud` or any of our [community channels](/community). 
+
+### Which cloud platform is SurrealDB available on?
+
+At present, SurrealDB is available on AWS. In the future we plan to expand to other cloud platforms.
+
+### My current application is on SurrealDB.  Can I move this to Surreal Cloud (Beta)?
+Yes. You can move your current application built in SurrealDB to Surreal Cloud (Beta). You can find more information in the [migrate your existing data](/docs/cloud/advanced-topics/migrating-data) documentation.
+
+### How do I migrate my existing on-premises instance to Surreal Cloud (Beta)?
+
+We are working on a migration tool to help you move your existing on-premises instance to Surreal Cloud (Beta).  In the meantime, you can use the `import` and `export` commands to move data between your on-premises instance and Surreal Cloud (Beta). 
+
+### What programming languages are supported?
+
+Surreal Cloud (Beta) supports the following programming languages:
+
+- [JavaScript/TypeScript](/docs/sdk/javascript)
+- [Python](/docs/sdk/python)
+- [Go](/docs/sdk/golang)
+- [Java](/docs/sdk/java)
+- [Rust](/docs/sdk/rust)
+- [PHP](/docs/sdk/php)
+- [.NET](/docs/sdk/dotnet)
+
+### Why am I getting an authentication error connecting via SDK? 
+
+You need to create a User first. Head to the [connect via SDK](/docs/cloud/connect/sdk) documentation for more details.
+
+### How do I backup my data? 
+
+Currently, you can not backup your data with Surreal Cloud (Beta). However, you can use the [`export` command](/docs/surrealdb/cli/export) to backup your data via the SurrealDB CLI. 
+
+### What are the limits of the Surreal Cloud (Beta)?
+
+It is not currently possible to configure [CLI](/docs/surrealdb/cli) arguments or environment variables in Surreal Cloud (Beta).
+
+Surreal Cloud (Beta) nodes run with the default [SurrealDB capabilities](/docs/surrealdb/security/capabilities) except for allowing network access to the Cloud API for the purposes of authenticating with Surrealist.
+
+Surreal Cloud (Beta) does not currently allow outgoing network requests, scripting, or guest access. All functions, RPC methods and all HTTP routes are allowed.
+
+[GraphQL support](/docs/surrealdb/querying/graphql) is not yet enabled on Surreal Cloud (Beta) instances.
+
+> [!NOTE]
+> Free Tier instances surpassing the 1GB free storage allowance will be limited to data retrieval only. Unless you upgrade to a paid tier, you will not be able to create new data.
+
+## Security
+
+### How secure is Surreal Cloud (Beta)?
+
+Surreal Cloud (Beta) is designed with security in mind and aims to provide robust protection for your data and applications. The platform leverages industry-standard security practices, including encryption at rest and in transit, network isolation, access controls and monitoring. For authentication, Surreal Cloud (Beta) supports multi-factor authentication through the available identity providers that offer it to their users. We are also working towards ISO 27001 and SOC 2 compliance, with plans to expand to other industry-specific compliance programs in the future, such as HIPAA or PCI DSS.
+
+Additionally, Surreal Cloud (Beta) is built on top of SurrealDB, which provides powerful and flexible [security features](/docs/surrealdb/security/summary#product) that are available to all Surreal Cloud (Beta) customers. SurrealDB is developed and maintained following modern [security practices](/docs/surrealdb/security/summary#process) to ensure early detection of security vulnerabilities and other security issues.
+
+Please note that we will keep improving security during the ongoing beta stage and, as a precaution, we recommend abstaining from hosting sensitive data in Surreal Cloud (Beta) during this stage.
+
+### How can I report a security issue in Surreal Cloud (Beta)?
+
+If you believe you have found a security vulnerability in Surreal Cloud (Beta) or SurrealDB, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly address the issue. Please report any security issue to [security@surrealdb.com](mailto:security@surrealdb.com). For security issues in SurrealDB, please submit a report via [Github Security Advisories](https://github.com/surrealdb/surrealdb/security/advisories) rather than posting a public issue in GitHub.
+
+We ask that you...
+
+- ... privately disclose the details of any potential vulnerability to SurrealDB.
+- ... provide enough information to reproduce the vulnerability in your report.
+
+We ask that you refrain from...
+
+- ... disclosing the details of a vulnerability publicly or to third parties.
+- ... exploiting a vulnerability beyond what is strictly necessary to verify its existence.
+- ... running automated security tools against SurrealDB infrastructure without permission.
+
+We commit to...
+
+- ... acknowledging your report within three business days of the date of communication.
+- ... verifying the issue and keeping you informed of the progress toward its resolution.
+- ... handling your report and any data you share with us with strict confidentiality.
+- ... abstaining from legal action against you for any report made following this policy.
+- ... crediting you in any relevant public security advisory unless you desire otherwise.
+
+### How do I configure user authentication?
+Surreal Cloud allows users to authenticate directly into their instances from Surrealist using a pre-defined access method. Once connected to your Instance, you may [define users](/docs/surrealql/statements/define/user) or [access methods](/docs/surrealql/statements/define/access) that users can use to access your Instance or specific namespaces or databases using any of the available [interfaces](/docs/surrealdb/integration), the [SurrealDB CLI](/docs/surrealdb/cli) or [Surrealist](https://surrealist.app/query).
+
+### Can I use my own encryption keys?
+Currently, any encryption keys used to encrypt data at rest are managed by Surreal Cloud. Since the architecture technically supports it, we may consider allowing customers to associate their own Customer-Managed Encryption Keys (CMEK) to be used to encrypt data at rest in the future. If you are interested in CMEK, please, contact us.
+
+### Can I limit who can reach my instances over the internet?
+All instances created in Surreal Cloud are publicly reachable over the internet and currently rely exclusively on the authentication and authorization mechanisms that are defined within the instance to prevent access to their data. We plan on providing the ability to restrict network access to instances as well as the ability to limit the [capabilities](/docs/surrealdb/security/capabilities) of each instance in the future. If your use case requires private network access to the instances, please, contact us.
+
+## Pricing
+
+### How much does Surreal Cloud (Beta) cost?
+
+Surreal Cloud (Beta) offers a flexible pricing model that allows you to pay only for the resources you use. The pricing is based on storage and compute you consume. For detailed pricing information, please refer to the [pricing](/pricing) page.
+
+### Is there a free tier available for Surreal Cloud (Beta)?
+
+Yes, Surreal Cloud (Beta) offers a free tier that allows you to get started with the platform at no cost. The free tier provides limited resources for development and testing purposes, enabling you to explore the features and capabilities of Surreal Cloud (Beta) without incurring any charges.
+
+
+### I am on the free tier.  Can I add another cluster?
+
+Anyone using the Individual (free) tier wishing to add another cluster will be alerted in their account that they must fill in their [billing information](/docs/cloud/billing-and-support/billing).
+
+
+### What pricing models are available?
+
+At launch, we will offer a free and a paid tier. We are working on our future offerings.
+
+### Will SurrealDB provide itemised invoices with tax identified?
+Yes. Customers with a VAT or tax identification number, should insert this in the billing section of their customer profile. 
+
+### Who do I contact for billing queries or account issues?
+Please send an email to support@surrealdb.com outlining the nature of your query and we will help you. 
+
+### Are there any additional fees? 
+
+No, we are transparent about our pricing. All costs are outlined on our [pricing page](/pricing), and there are no hidden fees or unexpected charges. Prices quoted on our website are exclusive of VAT or sales tax. Any relevant taxes will be displayed clearly on all customer invoices.
+
+### How am I billed for usage? 
+
+You are billed on a monthly basis for all services used during the previous month. The billing cycle starts on the first day of each month and ends on the last day. You will receive an invoice via email.
+
+## Legal
+
+### What terms and conditions govern my use of Surreal Cloud (Beta)?
+
+Using Surreal Cloud (Beta) means that the User agrees to the terms and conditions of our Master Services Agreement (MSA) available on our [legal page](/legal). Here we endeavour to be open and transparent with our legal, compliance, and privacy processes and our shared responsibilities and commitments to supporting your use of the Services.
+
+### Are you located in a US-Embargoed country or in Russia?
+
+SurrealDB Inc., complies with U.S. regulations related to embargoed countries and regions. As such, SurrealDB currently prohibits use of its products and services in Cuba, Iran, North Korea, Syria, and the regions of Crimea, Luhansk People's Republic (LNR), and Donetsk People's Republic (DNR).  SurrealDB uses geoblocker software to prevent logins from these restricted countries however, regional blocks may mean that an entire country is restricted from using our services. **This is beyond our direct control.**
+
+Additionally, Surreal DB Ltd is subject to Article 5n(2b) of Council Regulation 833/2014 in which it is prohibited to sell, supply, transfer, export, or provide, directly or indirectly, software for the management of enterprises and software for design and manufacture, to the Government of Russia or to legal persons, entities or bodies established in Russia.
+SurrealDB takes its compliance obligations very seriously and will update them as needed from time to time.
+
+## Troubleshooting and Support
+
+### What should I do if I cannot connect to Surreal Cloud (Beta)?
+
+If you are unable to connect to Surreal Cloud (Beta), please check the following:
+
+- Ensure that your network connection is stable and that you have internet access.
+- Verify that your credentials are correct and that you have the necessary permissions to access Surreal Cloud (Beta).
+- Check the status of the Surreal Cloud (Beta) service to see if there are any ongoing issues or maintenance activities.
+- If you are still unable to connect, please contact Surreal Cloud (Beta) support for further assistance.
+
+### Where can I find further documentation or tutorials?
+
+You can find a variety of resources to help you learn more about SurrealDB via [our website](http://www.surrealdb.com) including:
+
+- [SurrealDB Docs](http://www.surrealdb.com/docs): Comprehensive guides and references for all features, including docs to accompany [Surrealist](http://www.surrealdb.com/docs/cloud)
+- [YouTube Channel](https://youtube.com/surrealdb): Stay up-to-date with the latest releases, learn new skills and discover what other developers are building with SurrealDB.
+- [SurrealDB University](/learn): A self-paced video course with hands-on labs and interactive tutorials.
+- [SurrealDB Book](http://www.surrealdb.com/learn/book): An in-depth, story-driven guide to mastering SurrealDB.
+
+### How do I report a bug or request a feature in Surreal Cloud (Beta)?
+
+If you encounter a bug or have a feature request for Surreal Cloud (Beta), you can report it through the support portal or contact the Surreal Cloud (Beta) team directly. Please provide detailed information about the issue or feature request, including steps to reproduce the problem, screenshots, and any other relevant details. The Surreal Cloud (Beta) team will review your submission and work to address the issue or implement the feature in a future release.
diff --git a/src/content/doc-cloud/getting-started/_category_.json b/src/content/doc-cloud/getting-started/_category_.json
new file mode 100644
index 000000000..76b13e4dc
--- /dev/null
+++ b/src/content/doc-cloud/getting-started/_category_.json
@@ -0,0 +1,4 @@
+{
+    "sidebar_label": "Get started",
+    "sidebar_position": 2
+}
diff --git a/src/content/doc-cloud/getting-started/create-an-account.mdx b/src/content/doc-cloud/getting-started/create-an-account.mdx
new file mode 100644
index 000000000..2a8e3d868
--- /dev/null
+++ b/src/content/doc-cloud/getting-started/create-an-account.mdx
@@ -0,0 +1,101 @@
+---
+sidebar_position: 2
+sidebar_label: Create an Account
+title: Create a Surreal Cloud Account 
+description: To get started with Surreal Cloud, you need to create an account. You can use your email address, a passkey, Google, or GitHub to create an account.
+---
+
+
+# Create a Surreal Cloud account
+
+To get started, in the Surrealist app, click on the **Explore Surreal Cloud** option on the start screen. This will open the Cloud dashboard on the sidebar. Click on the **continue** button to create a Surreal Cloud account. You will be redirected to the Surreal Cloud authentication page where you can create or sign in to your account.
+
+This account is used to authenticate your access to Surreal Cloud and [manage your created Instances](/docs/cloud/getting-started/create-an-instance).
+
+
+
+## Registration options
+
+There are several ways to create a Surreal Cloud account. The options are Google, GitHub. Please use only one of the available options to avoid conflicts: 
+
+- [Create an Account with Google](#create-an-account-with-google)
+- [Create an Account with GitHub](#create-an-account-with-github)
+- [Create an Account with Email](#create-an-account-with-email)
+
+> [!IMPORTANT]
+> When you sign in with Google or GitHub, you're briefly redirected to their secure sign-in page through Surreal Cloud. This process uses OAuth2, a secure authentication protocol that allows you to use your existing account without sharing your password with us. We only request basic information (email address and name) from your account. After you authorize the connection, the provider sends a secure token back to Surreal Cloud, confirming your identity and granting you access to our services.
+
+### Create an Account with Google
+
+Using your Google account to sign up offers a quick and convenient way to create a Surreal Cloud account. It leverages Google's secure authentication system and eliminates the need for a separate password. 
+
+
+To create an account with Google, follow these steps:
+
+1. Select **Sign up with Google** option that says "Sign Up with Google" or displays the Google logo in the authentication page
+2. Choose Google Account: a Google sign-in window will appear; select the Google account you wish to use or enter your Google email and password
+3. Grant permissions: review the permissions requested by the platform and click "Allow" to grant access
+4. **Account created and logged in**: your new account is now created using your Google credentials, and you're automatically logged in
+
+### Create an Account with GitHub
+
+Creating an account with your GitHub account is a quick and convenient way to create a Surreal Cloud account. It leverages GitHub's secure authentication system and eliminates the need for a separate password. 
+
+To create an account with GitHub, follow these steps:
+
+1. Select **Sign up with GitHub** option that says "Sign Up with GitHub" or displays the GitHub logo in the authentication page
+2. Choose GitHub Account: a GitHub sign-in window will appear; select the GitHub account you wish to use or enter your GitHub email and password if prompted
+3. Grant permissions: review the permissions requested by the platform and click "Allow" to grant access
+4. **Account created and logged in**: your new account is now created using your GitHub credentials, and you're automatically logged in
+
+### Create an Account with Email
+
+Creating an account using your email address allows you to register without linking a third-party service. This option is ideal if you prefer to use a custom password or don't want to connect your Google or GitHub accounts.
+
+To create an account with Email, follow these steps:
+
+1. Select **Sign up with Email** on the authentication page.
+2. Enter your email address 
+3. You'll have the option to create a secure password or use a passkey.
+4. Confirm your email address by clicking the verification link sent to your inbox.
+5. Your new account is now created, and you can log in with your email and password.
+
+> [!NOTE]
+> If you forget your password, you can reset it by clicking on the **Forgot password?** link on the authentication page and follow the instructions sent to your email.
+
+## Sign in to Surreal Cloud
+
+If you already have an account, you can sign in to Surreal Cloud. Sign in is required to access your Surreal Cloud instances. You can sign in using the same email address, Google, or GitHub account you used to create your account. 
+
+### Sign in with Google
+
+1. Navigate to the [Surreal Cloud](https://surrealist.app/cloud) dashboard in [Surrealist](https://surrealist.app).
+2. **Select "Continue with Google"**: click on the "Continue with Google" option.
+3. **Choose Google account**: a Google sign-in window may appear; select your Google account or enter your Google email and password if prompted.
+4. **Authenticate**: complete any additional security steps if required, such as two-factor authentication.
+5. **Access granted**: you're now securely logged into your account using your Google credentials.
+
+### Sign in with GitHub
+
+1. Navigate to the [Surreal Cloud](https://surrealist.app/cloud) dashboard in [Surrealist](https://surrealist.app).
+2. **Select "Continue with GitHub"**: click on the "Continue with GitHub" option.
+3. **Choose GitHub account**: a GitHub sign-in window may appear; select your GitHub account or enter your GitHub email and password if prompted.
+4. **Authenticate**: complete any additional security steps if required, such as two-factor authentication.
+5. **Access granted**: you're now securely logged into your account using your GitHub credentials.
+
+### Sign in with Email
+
+1. Navigate to the [Surreal Cloud](https://surrealist.app/cloud) dashboard in [Surrealist](https://surrealist.app).
+2. **Select "Sign In with Email"**: click on the "Sign In with Email" option.
+3. **Enter your email and password**: enter your email address and password.
+4. **Access granted**: you're now securely logged into your account using your email and password.
+
+### Sign in with Passkey
+
+1. Navigate to the [Surreal Cloud](https://surrealist.app/cloud) dashboard in [Surrealist](https://surrealist.app).
+2. **Select "Continue with Passkey"**: click on the "Continue with Passkey" option.
+3. **Access granted**: you're now securely logged into your account using your passkey.
+
+## Next steps
+
+After creating an account, you can connect to a Surreal Cloud instance using Surrealist, a command-line interface, or any of the supported SDKs. For more information, see the [create a Surreal Cloud Instance](/docs/cloud/getting-started/create-an-instance) document.
\ No newline at end of file
diff --git a/src/content/doc-cloud/getting-started/create-an-instance.mdx b/src/content/doc-cloud/getting-started/create-an-instance.mdx
new file mode 100644
index 000000000..1fa5004d1
--- /dev/null
+++ b/src/content/doc-cloud/getting-started/create-an-instance.mdx
@@ -0,0 +1,75 @@
+---
+sidebar_position: 3
+sidebar_label: Create an Instance
+title: Create an Instance | Surreal Cloud (Beta)
+description: In this section, you will learn how to create an Instance in Surreal Cloud (Beta).
+---
+
+import Image from "@components/Image.astro";
+
+import CreateInstanceLight from '@img/image/cloud/create-instance.png';
+import CreateInstanceDark from '@img/image/cloud/create-instance.png';
+
+# Create an Instance
+
+Surreal Cloud (Beta) allows you to create a new Instance with a few clicks. You can create an Instance in your personal account or in an organization. 
+
+> [!IMPORTANT]
+> In Beta, you can create instances only in a personal account. Support for creating instances in organizations is coming soon.
+
+You can create an Instance in these steps from your Cloud dashboard:
+
+1. Click on the **Create Instance** button.
+    - You can choose to create a new Instance either in your personal account or in an organization.
+    - If you choose to create an Instance in an organization, you need to select the organization from the dropdown list.
+
+2. Input your Instance details.
+    - **Instance name**: the name of the Instance.
+    - **Instance version**: the version of SurrealDB you want to use. In the Beta release, only version `>v2.0.0` is available to use as it is the latest stable release. 
+
+3. Select a region where you want to deploy your Instance.
+    - AWS Europe (Ireland)
+    - AWS US East (N. Virginia)
+
+> [!IMPORTANT]
+> The region you choose will affect your application's latency. For optimal performance, choose a region that is closest to your users.
+
+
+4. Select an Instance category: Instance category defines the resources allocated to your cloud Instance. The Instance categories are in three different categories - **Development**, **Production**, and **Free Tier**. You can choose between the following configurations:
+
+> [!NOTE]
+> To use a Production or Development Instance, you need to enter your billing and payment information.
+
+- **Production**: for production environments, data at scale, or professional use cases.
+    {/* - **large**: this configuration has 1 vCPU, 4096 MB of memory and a 40GB storage limit.
+    - **xlarge**: this configuration has 2 vCPUs, 8192 MB of memory and a 80GB storage limit.
+    - **2xlarge**: this configuration is suitable for applications with very high traffic. It has 4 vCPUs, 16384 MB of memory and a 160GB storage limit. */}
+
+- **Development**: for testing, starter projects, or for low-traffic applications. Clusters under heavy load may experience CPU throttling.
+
+    {/* - **tiny**: this configuration has 0.128 vCPUs, 256 MB of memory and a 10GB storage limit.
+    - **small**: this configuration has 0.256 vCPUs, 512 MB of memory and a 10GB storage limit.
+    - **medium**: this configuration has 0.512 vCPUs, 1024 MB of memory and a 20GB storage limit. */}
+
+- **Free Tier**: experience SurrealDB with a free Instance.
+    {/* - **tiny**: this configuration has 0.128 vCPUs, 256 MB of memory and a 10GB storage limit. */}
+
+<Image
+alt="Surreal Sidekick"
+src={{
+	light: CreateInstanceLight,
+	dark: CreateInstanceLight,
+	}}  
+/>
+
+5. Choose nodes: the number of nodes selected will define the number of compute nodes allocated to your Instance.
+
+> [!IMPORTANT]
+> The number of nodes you choose will affect the cost of your Instance.
+
+6. After customising your Instance, click the **Create** button. You will see a confirmation message with the details of your Instance. You can now connect to your Instance using your [preferred connection method](/docs/cloud/connect).
+
+
+## Next steps
+
+Now that you have created an Instance, you can [connect to your Surreal Cloud (Beta) Instance](/docs/cloud/connect). You can also [configure your Instance](/docs/cloud/advanced-topics/configure-an-instance) to change the Instance type, number of nodes, and capabilities.
\ No newline at end of file
diff --git a/src/content/doc-cloud/getting-started/index.mdx b/src/content/doc-cloud/getting-started/index.mdx
new file mode 100644
index 000000000..9688cb179
--- /dev/null
+++ b/src/content/doc-cloud/getting-started/index.mdx
@@ -0,0 +1,23 @@
+---
+sidebar_position: 1
+sidebar_label: Get Started
+title: Get Started with Surreal Cloud (Beta) 
+description: Surreal Cloud (Beta) is a cloud-based platform that provides a comprehensive suite of tools and services to help you build, manage, and deploy your database.
+---
+
+
+# Get started with Surreal Cloud (Beta) 
+
+Surreal Cloud (Beta) provides services to help you build, manage, and deploy your database. Whether you are a beginner getting started with Surreal Cloud (Beta) or an experienced user looking for specific information, this document provides a comprehensive understanding of Surreal Cloud (Beta).
+
+To get started with Surreal Cloud (Beta), you need to sign up for an account and create an instance. Once you have created a project, you can start building your database, managing your data, and deploying your application.
+
+Surreal Cloud (Beta) offers several options for connecting to your created database instance, [including Surrealist](/docs/cloud/connect/surrealist), [a command-line interface](/docs/cloud/connect/cli), and [any of the supported SDKs](/docs/cloud/connect/sdk). 
+
+
+## Next Steps
+
+- [Create a Surreal Cloud (Beta) account](/docs/cloud/getting-started/create-an-account)
+- [Create a Surreal Cloud (Beta) Instance](/docs/cloud/getting-started/create-an-instance)
+- [Connect to your Instance](/docs/cloud/connect)
+- [Getting Started with Surreal Cloud (Beta)](https://youtu.be/upm1lwaHmwU?si=8Xcmz-wFt6OMDc6R)
diff --git a/src/content/doc-cloud/index.mdx b/src/content/doc-cloud/index.mdx
new file mode 100644
index 000000000..184fae4c5
--- /dev/null
+++ b/src/content/doc-cloud/index.mdx
@@ -0,0 +1,164 @@
+---
+sidebar_position: 1
+sidebar_label: Surreal Cloud (Beta)
+title: Surreal Cloud (Beta) | Introduction
+description: Surreal Cloud (Beta) redefines the database experience, offering the power and flexibility of SurrealDB without the pain of managing infrastructure. Elevate your business to unparalleled levels of scale and resilience. Focus on building tomorrow's applications. Let us take care of the rest.
+no_page_headings: true
+---
+
+import Image from "@components/Image.astro";
+
+import Tabs from "@components/Tabs/Tabs.astro";
+import TabItem from "@components/Tabs/TabItem.astro";
+
+import CloudImageLight from '@img/image/cloud/light/cloud-light.png';
+import CloudImageDark from '@img/image/cloud/cloud-dark.png';
+
+import LightCloud from '@img/image/cloud/surrealcloud.png';
+import DarkCloud from '@img/image/cloud/surrealcloud.png';
+
+import HighlyAvailable from '@img/image/cloud/light/highly-available-and-scalable-light.png';
+import HighlyAvailableDark from '@img/image/cloud/highly-available-and-scalable-dark.png';
+
+<Image
+alt="Surreal Cloud (Beta)"
+width={100}
+className="flag-image-title"
+src={{
+	light: LightCloud,
+	dark: DarkCloud,
+	}}  
+/>
+
+# What is Surreal Cloud (Beta)?
+
+<div className="flex flex-col md:flex-row items-center justify-between">
+  <div className="flex-1">
+    {/* <p>
+      Surreal Cloud (Beta) redefines the database experience, offering the power and flexibility of SurrealDB without the pain of managing infrastructure. Elevate your business to unparalleled levels of scale and resilience. Focus on building tomorrow's applications. Let us take care of the rest.
+    </p>
+
+    <p>
+      Designed to be lightweight, the Surreal Cloud (Beta) product leverages the Open-Source SurrealDB product as much as possible. Its features are intended to complement those of the open-source version and offer you a seamless deployment experience.
+    </p> */}
+
+<p>
+   Surreal Cloud (Beta) transforms the database experience, providing the power and versatility of SurrealDB without the complexity of managing infrastructure. Whether you’re building for passion projects or enterprise-scale applications, Surreal Cloud (Beta) offers the scalability, resilience, and innovation you need to stay ahead.
+</p>
+
+<p>
+   Enjoy a fully managed solution that takes the hassle out of infrastructure operations. With SurrealDB’s ACID compliance, you can confidently run transactions at scale across multiple environments, ensuring data integrity and reliability.
+</p>
+
+<p>
+   Designed to support your growth, Surreal Cloud (Beta) scales effortlessly [from prototypes to large-scale deployments](/docs/cloud/getting-started/create-an-instance). By leveraging centralized data, it enables departments or teams to work efficiently while maintaining consistent data integrity and reducing redundancy.
+</p>
+
+<p>
+   Our transparent and [predictable pricing](/pricing) ensures you only pay for what you need.
+</p>
+
+    <a href="/docs/cloud/getting-started/" style={{ display: 'inline-block' }}>
+      <button class=" cursor-pointer text-[0.8125rem] mt-5 px-3 py-[0.45rem] rounded-2xl border-2 border-solid border-[#ff00A00] hover:border-[$hover-color] hover:text-[$hover-color];" style={{ fontSize: '1rem', marginTop: 0, marginBottom: '1rem' }}>Get Started</button>
+    </a>
+
+  </div>
+
+  <div className="flex-1 mt-4 md:mt-0 md:ml-2.5">
+    <Image
+      alt="Surreal Cloud (Beta)"
+      src={{
+        light: CloudImageLight,
+        dark: CloudImageDark,
+      }}
+    />
+  </div>
+</div>
+
+
+<iframe
+	width="100%"
+	src="https://www.youtube.com/embed/upm1lwaHmwU?si=P0fG9ppuPcindRZw"
+	title="Getting Started with Surreal Cloud (Beta)"
+	frameborder="0"
+	allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+	referrerpolicy="strict-origin-when-cross-origin"
+	style={{ aspectRatio: 1.7, paddingTop: '20px' }}
+	allowfullscreen
+></iframe>
+
+## What can you do? 
+
+When using Surreal Cloud (Beta), you can connect to your SurrealDB instance with a few clicks. You can connect to any SurrealDB instance via Surrealist, a command-line interface, and any of the supported SDKs. 
+
+
+<div className="flex flex-col items-start justify-between">
+  <div className="w-full">
+    <Tabs groupId="What can you do">
+      <TabItem value="Create an instance" label="Create an instance" default>
+        <div className="flex flex-col md:flex-row items-start justify-between">
+          <div className="flex-1">
+            Surreal Cloud (Beta) allows you to connect to your SurrealDB instance with just a few clicks. You can create an instance, connect to it, and start building your application.
+
+            <h4>1. Create Instance.</h4>
+
+            When creating an instance, you will enter the instance name and organization to ensure that you can easily identify your instance. Finally, you can select the version of SurrealDB to use and the region to deploy your instance.
+
+            <h4>2. Select a region.</h4>
+
+            Once you have created your instance, you can select the region to deploy your instance. This will allow you to connect to your instance from anywhere in the world.
+
+            <h4>3. Select an Instance preset.</h4>
+
+            Once you have selected a region, you can select an instance preset. This will allow you to select the instance size and type to best suit your needs.
+
+            <h4>4. Finalize and connect to your Instance.</h4>
+
+            Once you have created your instance, you can connect to it from anywhere in the world. You can connect to your instance from anywhere in the world.
+          </div>
+          <div className="flex-1 mt-4 md:mt-0 md:ml-10">
+            <Image
+              alt="Highly Available"
+              src={{
+                light: HighlyAvailable,
+                dark: HighlyAvailableDark,
+              }}  
+            />
+          </div>
+        </div>
+      </TabItem>
+      <TabItem value="Connect to your instance" label="Connect to your instance">
+        <div className="flex flex-col md:flex-row items-start justify-between">
+          <div className="flex-1 text-left">
+            You can connect to any Surreal Cloud (Beta) Instance via [Surrealist](/docs/cloud/connect/surrealist), a [command-line interface (CLI)](/docs/cloud/connect/cli), and [any of the supported SDKs](/docs/cloud/connect/sdk).
+
+            <h4>[Connect via Surrealist](/docs/cloud/connect/surrealist)</h4>
+
+            Since Surreal Cloud (Beta) is closely integrated with Surrealist, you can execute queries directly from the interface. This allows you to interact with your data in real-time, without having to switch between different tools.
+
+            <h4>[Connect via CLI](/docs/cloud/connect/cli)</h4>
+
+            If you prefer to use a command-line interface, you can use the SurrealDB CLI to connect to your instance. This connection includes a token that is used to authenticate your connection.
+
+            To do so, select the connect with the CLI option and copy the command.
+
+            <h4>[Connect via SDK](/docs/cloud/connect/sdk)</h4>
+
+            You can also connect to your instance using any of the supported SDKs. In your preferred SDK, use the connect method and pass in your instance endpoint.
+          </div>
+          <div className="flex-1 mt-4 md:mt-0 md:ml-10">
+            <Image
+              alt="Highly Available"
+              src={{
+                light: HighlyAvailable,
+                dark: HighlyAvailableDark,
+              }}  
+            />
+          </div>
+        </div>
+      </TabItem>
+    </Tabs>
+  </div>
+</div>
+
+
diff --git a/src/content/doc-sdk-dotnet/installation.mdx b/src/content/doc-sdk-dotnet/installation.mdx
index 2e6dacac7..d32c3c332 100644
--- a/src/content/doc-sdk-dotnet/installation.mdx
+++ b/src/content/doc-sdk-dotnet/installation.mdx
@@ -13,6 +13,7 @@ import TabItem from "@components/Tabs/TabItem.astro";
 import { packageName, fetchNugetVersion } from './utils';
 
 export const value = await fetchNugetVersion();
+export const packageReferenceXml = `<PackageReference Include="SurrealDb.Net" Version="${value}" />`;
 
 # Installation
 
@@ -37,9 +38,11 @@ dotnet add package SurrealDb.Net
   </TabItem>
   <TabItem value="package-reference" label="PackageReference">
 
-```xml
-<PackageReference Include="SurrealDb.Net" Version="0.6.0" />
-```
+<pre>
+  <code class="language-xml">
+    {packageReferenceXml}
+  </code>
+</pre>
 
   </TabItem>
 </Tabs>
@@ -58,5 +61,5 @@ Here is an example within Visual Studio:
 
 The SDK's initialization may vary depending on the context of your project.
 
-The de facto initialization method is to create and [consume a SurrealDbClient created manually](/docs/sdk/dotnet/core/initialization).
+The de facto initialization method is to create and [consume a SurrealDbClient created manually](/docs/sdk/dotnet/core/create-a-new-connection).
 Most .NET projects provide a way to configure services using [Dependency Injection](/docs/sdk/dotnet/core/dependency-injection), which is the recommended way to use the SDK in your application.
\ No newline at end of file
diff --git a/src/content/doc-sdk-java/components/JavaVersion.astro b/src/content/doc-sdk-java/components/JavaVersion.astro
index 9ef9fb291..649bc132f 100644
--- a/src/content/doc-sdk-java/components/JavaVersion.astro
+++ b/src/content/doc-sdk-java/components/JavaVersion.astro
@@ -5,11 +5,24 @@ const result = await fetch(
 const data = await result.json();
 const version = data?.response?.docs[0]?.latestVersion ?? 'Unknown';
 ---
-const result = await fetch(
-    'https://search.maven.org/solrsearch/select?q=g:%22com.surrealdb%22+AND+a:%22surrealdb%22&wt=json'
-);
-const data = await result.json();
-const version = data?.response?.docs[0]?.latestVersion ?? 'Unknown';
+let version = 'Unknown';
+try {
+    const result = await fetch(
+        'https://search.maven.org/solrsearch/select?q=g:%22com.surrealdb%22+AND+a:%22surrealdb%22&wt=json'
+    );
+    if (!result.ok) {
+        throw new Error(`HTTP error! status: ${result.status}`);
+    }
+    const contentType = result.headers.get('content-type');
+    if (!contentType || !contentType.includes('application/json')) {
+        throw new Error('Response is not JSON');
+    }
+    const data = await result.json();
+    version = data?.response?.docs[0]?.latestVersion ?? 'Unknown';
+} catch (error) {
+    console.error('Error fetching version:', error);
+    // Keep the default 'Unknown' value
+}
 ---
 
 <code>{version}</code>
\ No newline at end of file
diff --git a/src/content/doc-sdk-java/data-types.mdx b/src/content/doc-sdk-java/data-types.mdx
index 066b9c5c0..63a312806 100644
--- a/src/content/doc-sdk-java/data-types.mdx
+++ b/src/content/doc-sdk-java/data-types.mdx
@@ -10,7 +10,7 @@ description: Where you can find the API documentation for the SurrealDB SDK for
 The Java SDK translates all datatypes native to SurrealQL into either datatypes native to Java, or a custom implementation. This document describes all datatypes, and links to their respective documentation.
 
 ## Data Types overview
-
+{/* 
 <table>
     <thead>
         <tr>
@@ -157,4 +157,4 @@ The Java SDK translates all datatypes native to SurrealQL into either datatypes
             </td>
         </tr>
     </tbody>
-</table>
\ No newline at end of file
+</table> */}
\ No newline at end of file
diff --git a/src/content/doc-sdk-java/installation.mdx b/src/content/doc-sdk-java/installation.mdx
index be33ed62b..b6a9c53a1 100644
--- a/src/content/doc-sdk-java/installation.mdx
+++ b/src/content/doc-sdk-java/installation.mdx
@@ -17,7 +17,8 @@ In this section, you will learn how to install the Java SDK in your project.
 
 First, install the [SurrealDB SDK](https://mvnrepository.com/artifact/com.surrealdb/surrealdb) from the Maven Central repository using [Gradle](https://gradle.org/) or [Maven](https://maven.apache.org/).
 
-The latest version of the SDK is currently <JavaVersion />
+{/* The latest version of the SDK is currently <JavaVersion/> */}
+
 
 <Tabs groupId="java-build-tool">
   <TabItem value="gradle-groovy" label="Gradle (Groovy)" default>
@@ -31,7 +32,9 @@ dependencies {
 }
 ```
   </TabItem>
+  
   <TabItem value="gradle-kotlin" label="Gradle (Kotlin)">
+
 ```groovy
 val surrealdbVersion by extra("0.2.0")
 
@@ -72,4 +75,4 @@ In the Quick Start guide, you will learn how to create a new connection and auth
 After installing the SDK, check out the quick start guide to build your a simple application with the SDK. You can also learn more about carrying out common tasks with the SDK in the following sections:
 - [Quick Start](/docs/sdk/java/start)
 - [Creating a new connection](/docs/sdk/java/core/create-a-new-connection)
-- [Authenticating users](/docs/sdk/java/core/authenticating-users)
+- [Authenticating users](/docs/sdk/java/core/handling-authentication)
diff --git a/src/content/doc-sdk-java/start.mdx b/src/content/doc-sdk-java/start.mdx
index 93a84269e..a9e33e6c9 100644
--- a/src/content/doc-sdk-java/start.mdx
+++ b/src/content/doc-sdk-java/start.mdx
@@ -33,7 +33,7 @@ This guide assumes the following:
 The SurrealDB Java SDK is available on the Maven Central repository. You can install it using [Gradle](https://gradle.org/) or [Maven](https://maven.apache.org/).
 Copy the relevant code snippet into your `build.gradle` or `pom.xml` file to add the SDK as a dependency.
 
-The latest version of the SDK is currently <JavaVersion />
+{/* The latest version of the SDK is currently <JavaVersion /> */}
 
 <Tabs groupId="java-build-tool">
   <TabItem value="gradle-groovy" label="Gradle (Groovy)" default>
diff --git a/src/content/doc-sdk-rust/concepts/authenticating-users.mdx b/src/content/doc-sdk-rust/concepts/authenticating-users.mdx
index 6dd142c15..c23348abe 100644
--- a/src/content/doc-sdk-rust/concepts/authenticating-users.mdx
+++ b/src/content/doc-sdk-rust/concepts/authenticating-users.mdx
@@ -282,9 +282,9 @@ Two `person` records: [Person { name: "Created by record user", id: Thing { tb:
 
 Each of the crates featured in the Rust SDK also use the schema above. Three of them (Actix, Axum, Rocket) are web servers, while Egui is a visual UI. See the mini tutorials for each of these crates here:
 
-* [Actix](/docs/sdk/rust/crates/actix)
-* [Axum](/docs/sdk/rust/crates/axum)
-* [Rocket](/docs/sdk/rust/crates/rocket)
-* [Egui](/docs/sdk/rust/crates/egui)
+* [Actix](/docs/sdk/rust/frameworks/actix)
+* [Axum](/docs/sdk/rust/frameworks/axum)
+* [Rocket](/docs/sdk/rust/frameworks/rocket)
+* [Egui](/docs/sdk/rust/frameworks/egui)
 
 Learn more about authentication in SurrealDB in our [security best practices](/docs/surrealdb/reference-guide/security-best-practices#authentication) documentation and in the [security](/docs/surrealdb/security/authentication#expiration) section of the SurrealDB documentation.
\ No newline at end of file
diff --git a/src/content/doc-sdk-rust/concepts/fetch.mdx b/src/content/doc-sdk-rust/concepts/fetch.mdx
index 3be08328c..cd2e6d61d 100644
--- a/src/content/doc-sdk-rust/concepts/fetch.mdx
+++ b/src/content/doc-sdk-rust/concepts/fetch.mdx
@@ -109,7 +109,7 @@ Here is the result:
 
 ## The Rust code
 
-The code below that shows an example of `FETCH` is another example related to classes and students. Note that in one part it passes a [`Resource`](https://docs.rs/surrealdb/latest/surrealdb/opt/enum.Resource.html) into the [`create`](https://docs.rs/surrealdb/latest/surrealdb/struct.Surreal.html#method.create) method in order to return a [`Value`](https://docs.rs/surrealdb/latest/surrealdb/struct.Value.html) and thus not have to specify a return type to deserialize into. For more information on this technique, see [the page on flexible typing](/docs/sdk/rust/concepts/flexible_typing).
+The code below that shows an example of `FETCH` is another example related to classes and students. Note that in one part it passes a [`Resource`](https://docs.rs/surrealdb/latest/surrealdb/opt/enum.Resource.html) into the [`create`](https://docs.rs/surrealdb/latest/surrealdb/struct.Surreal.html#method.create) method in order to return a [`Value`](https://docs.rs/surrealdb/latest/surrealdb/struct.Value.html) and thus not have to specify a return type to deserialize into. For more information on this technique, see [the page on flexible typing](/docs/sdk/rust/concepts/flexible-typing).
 
 ```rust
 use serde::{Deserialize, Serialize};
diff --git a/src/content/doc-sdk-rust/concepts/flexible_typing.mdx b/src/content/doc-sdk-rust/concepts/flexible-typing.mdx
similarity index 100%
rename from src/content/doc-sdk-rust/concepts/flexible_typing.mdx
rename to src/content/doc-sdk-rust/concepts/flexible-typing.mdx
diff --git a/src/content/doc-sdk-rust/index.mdx b/src/content/doc-sdk-rust/index.mdx
index 97a30b3a1..c489ce2ef 100644
--- a/src/content/doc-sdk-rust/index.mdx
+++ b/src/content/doc-sdk-rust/index.mdx
@@ -36,12 +36,12 @@ import DarkRocketLogo from "@img/icon/dark/rocket.png";
 The SurrealDB SDK for Rust is the primary method of interacting with SurrealDB from client-side, server-side applications, systems, APIs, embedded systems, and IOT devices. The Rust SDK has support for robust error handling and type-safe operations, using an asynchronous API for efficient concurrent database interactions. You can use the Rust SDK to interact with your SurrealDB database instances, or to run SurrealDB as an embedded database within your Rust application, with functionality for executing queries, managing data, running database functions, authenticating to the database, building user signup and authentication functionality, and subscribing to data changes with live queries.
 
 > [!IMPORTANT]
-> The SDK requires Rust JDK version `1.80.1` or greater, and is available as a [crate](https://crates.io/crates/surrealdb).
+> The SDK requires Rust version `1.80.1` or greater, and is available as a [crate](https://crates.io/crates/surrealdb).
 
 > [!NOTE]
 > The SDK works seamlessly with SurrealDB versions `v2.0.0` to <Version />, ensuring compatibility with the latest version.
 
-To contribute to the SDK code, submit an Issue or Pull Request in the [surrealdb.rust](https://github.com/surrealdb/surrealdb.rust) repository. To contribute to this documentation, submit an Issue or Pull Request in the [docs.surrealdb.com](https://github.com/surrealdb/docs.surrealdb.com) repository.
+To contribute to the SDK code, submit an Issue or Pull Request in the [surrealdb.rust](https://github.com/surrealdb/surrealdb/tree/main/crates/sdk) repository. To contribute to this documentation, submit an Issue or Pull Request in the [docs.surrealdb.com](https://github.com/surrealdb/docs.surrealdb.com) repository.
 
 ## Frameworks
 
@@ -82,6 +82,6 @@ To contribute to the SDK code, submit an Issue or Pull Request in the [surrealdb
 
 ## Sources
 
-- [GitHub repository](https://github.com/surrealdb/surrealdb/tree/main/sdk)
+- [GitHub repository](https://github.com/surrealdb/surrealdb/tree/main/crates/sdk)
 - [Crates.io package](https://crates.io/crates/surrealdb)
 - [Docs.rs documentation](https://docs.rs/surrealdb/latest/surrealdb/) 
diff --git a/src/content/doc-sdk-rust/setup.mdx b/src/content/doc-sdk-rust/setup.mdx
index c9dcf05d3..cb3ebc2b3 100644
--- a/src/content/doc-sdk-rust/setup.mdx
+++ b/src/content/doc-sdk-rust/setup.mdx
@@ -30,6 +30,17 @@ cargo add serde --features derive
 
 The examples inside this SDK manual assume that all of these crates and features are present.
 
+To maximize performance when compiling in release mode, it is recommended to use the following profile inside `Cargo.toml`, the same as [the profile used by SurrealDB](https://github.com/surrealdb/surrealdb/blob/main/Cargo.toml#L45C1-L50C18) when building each version for release.
+
+```toml
+[profile.release]
+lto = true
+strip = true
+opt-level = 3
+panic = 'abort'
+codegen-units = 1
+```
+
 ### Start SurrealDB
 
 Before using `cargo run` to try out your code, make sure that the SurrealDB server is running by using the [`surreal start`](/docs/surrealdb/cli/start) command. The following command will start an in-memory server with a single root user at the default address `127.0.0.1:8000`.
diff --git a/src/content/doc-surrealdb/cli/env.mdx b/src/content/doc-surrealdb/cli/env.mdx
index f10dfeba2..1df5ed36c 100644
--- a/src/content/doc-surrealdb/cli/env.mdx
+++ b/src/content/doc-surrealdb/cli/env.mdx
@@ -88,6 +88,11 @@ Environment variables can be used to tailor the behaviour of a running SurrealDB
       <td scope="row" data-label="Default">4398046511104 (4 GiB)</td>
       <td scope="row" data-label="Notes">Maximum HTTP body size of the HTTP /import endpoints</td>
     </tr>
+    <tr>
+      <td scope="row" data-label="Env var"><code>SURREAL_IMPORT_FILE</code></td>
+      <td scope="row" data-label="Default">None</td>
+      <td scope="row" data-label="Notes">Path to a SurrealQL file that will be imported when starting the server.</td>
+    </tr>
     <tr>
       <td scope="row" data-label="Env var"><code> SURREAL_INSECURE_FORWARD_ACCESS_ERRORS </code></td>
       <td scope="row" data-label="Default">false</td>
@@ -143,6 +148,11 @@ Environment variables can be used to tailor the behaviour of a running SurrealDB
       <td scope="row" data-label="Default">Number of CPUs on the current device</td>
       <td scope="row" data-label="Notes">Size of the SurrealCS connection pool.</td>
     </tr>
+    <tr>
+      <td scope="row" data-label="Env var"><code>SURREAL_TEMPORARY_DIRECTORY</code></td>
+      <td scope="row" data-label="Default">None</td>
+      <td scope="row" data-label="Notes">Sets the directory for storing temporary database files.</td>
+    </tr>
     <tr>
       <td scope="row" data-label="Env var"><code>SURREAL_TRANSACTION_CACHE_SIZE</code></td>
       <td scope="row" data-label="Default">10000</td>
diff --git a/src/content/doc-surrealdb/cli/fix.mdx b/src/content/doc-surrealdb/cli/fix.mdx
index 3a7c9c8f4..bb8cee46b 100644
--- a/src/content/doc-surrealdb/cli/fix.mdx
+++ b/src/content/doc-surrealdb/cli/fix.mdx
@@ -51,7 +51,7 @@ The fix command converts SurrealDB version 1.x data into a format that can be us
                 `file`
             </td>
             <td>
-                Sets the the path to the existing data to convert to 2.x storage format
+                Sets the path to the existing data to convert to 2.x storage format
             </td>
         </tr>
     </tbody>
diff --git a/src/content/doc-surrealdb/cli/help.mdx b/src/content/doc-surrealdb/cli/help.mdx
index c912a6cd7..99d4d4f6d 100644
--- a/src/content/doc-surrealdb/cli/help.mdx
+++ b/src/content/doc-surrealdb/cli/help.mdx
@@ -36,7 +36,7 @@ Y88b  d88P Y88b 888 888     888     Y8b.     888  888 888 888  .d88P 888   d88P
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on GitHub (https://github.com/surrealdb/surrealdb/issues).
 
diff --git a/src/content/doc-surrealdb/cli/import.mdx b/src/content/doc-surrealdb/cli/import.mdx
index 12f342bed..5a0fc093d 100644
--- a/src/content/doc-surrealdb/cli/import.mdx
+++ b/src/content/doc-surrealdb/cli/import.mdx
@@ -97,7 +97,7 @@ The import command imports a SurrealQL script file into a local or remote Surrea
                 <Label label="required" />
             </td>
             <td>
-            Sets the the path to the file which should be imported
+            Sets the path to the file which should be imported
             </td>
         </tr>
     </tbody>
@@ -117,10 +117,6 @@ Using token based authentication
 surreal import --conn http://localhost:8000 --token <token> --ns test --db test downloads/surreal_deal_v1.surql
 ```
 
-
-> [!NOTE]
-> The Import statement has a file size limit of 4 GiB per import, this prevents the import process from running out of memory and crashing. Please make sure your import file is under this limit.
-
 ## OPTION IMPORT
 
 The output of a database export includes a line that contains the keywords `OPTION IMPORT`. This command is used internally to ensure that side effects do not run when the data is imported, such as [events](/docs/surrealql/statements/define/event) and [table views](/docs/surrealql/statements/define/table#pre-computed-table-views).
@@ -164,4 +160,4 @@ When using the `surreal import` command, you can also use environment variables
 >
 > For example, the `--username` flag can be configured with the `SURREAL_USER` environment variable instead. 
 
-For more on the environment variables available for CLI commands or SurrealDB instances in general, see the [environment variables](/docs/surrealdb/cli/env#command-environment-variables) page.
\ No newline at end of file
+For more on the environment variables available for CLI commands or SurrealDB instances in general, see the [environment variables](/docs/surrealdb/cli/env#command-environment-variables) page.
diff --git a/src/content/doc-surrealdb/cli/index.mdx b/src/content/doc-surrealdb/cli/index.mdx
index 248cedb5a..7757af1b2 100644
--- a/src/content/doc-surrealdb/cli/index.mdx
+++ b/src/content/doc-surrealdb/cli/index.mdx
@@ -29,7 +29,7 @@ Unless you specify otherwise, the CLI will start a database in memory that serve
 In another window, you can then open up an interactive shell to make queries using the  `surreal sql` command.
 
 ```bash
-surreal sql --endpoint http://localhost:8000 --namespace ns --database db --pretty
+surreal sql --endpoint http://localhost:8000 --namespace ns --database db --username root --password root --pretty
 ```
 
 > [!WARNING]
diff --git a/src/content/doc-surrealdb/cli/ml/export.mdx b/src/content/doc-surrealdb/cli/ml/export.mdx
index ad16141a2..5c168b7f8 100644
--- a/src/content/doc-surrealdb/cli/ml/export.mdx
+++ b/src/content/doc-surrealdb/cli/ml/export.mdx
@@ -115,7 +115,7 @@ The ML export command is used to export an existing machine learning model from
                 <Label label="required" />
             </td>
             <td>
-            Sets the the path to the file which should be exported
+            Sets the path to the file which should be exported
             </td>
         </tr>
     </tbody>
diff --git a/src/content/doc-surrealdb/cli/ml/import.mdx b/src/content/doc-surrealdb/cli/ml/import.mdx
index 33ef007e9..446b0d564 100644
--- a/src/content/doc-surrealdb/cli/ml/import.mdx
+++ b/src/content/doc-surrealdb/cli/ml/import.mdx
@@ -98,7 +98,7 @@ The ML import command is used to import a new machine learning model into Surrea
                 <Label label="required" />
             </td>
             <td>
-            Sets the the path to the file which should be imported
+            Sets the path to the file which should be imported
             </td>
         </tr>
     </tbody>
diff --git a/src/content/doc-surrealdb/cli/start.mdx b/src/content/doc-surrealdb/cli/start.mdx
index 820060033..d6eec1b76 100644
--- a/src/content/doc-surrealdb/cli/start.mdx
+++ b/src/content/doc-surrealdb/cli/start.mdx
@@ -114,6 +114,15 @@ The start command starts a SurrealDB server in memory, on disk, or in a distribu
             Sets the hostname or IP address to listen for connections on
             </td>
         </tr>
+        <tr>
+            <td colspan="2">
+                `--import-file`
+               <Label label="optional" />
+            </td>
+            <td>
+            Path to a SurrealQL (`.surql`) file that will be imported when starting the server
+            </td>
+        </tr>
         <tr>
             <td colspan="2">
                 `-l` / `--log`
@@ -168,6 +177,15 @@ The start command starts a SurrealDB server in memory, on disk, or in a distribu
                 Sets whether strict mode is enabled on this database instance
             </td>
         </tr>
+        <tr>
+            <td colspan="2">
+                `--temporary-directory`
+               <Label label="optional" />
+            </td>
+            <td>
+                Sets the directory for storing temporary database files
+            </td>
+        </tr>
     </tbody>
 </table>
 </TabItem>
@@ -198,7 +216,7 @@ file:// is deprecated, please use surrealkv:// or rocksdb://
                <Label label="optional" />
             </td>
             <td>
-                Sets the the path for storing data. If no argument is given, the default of `memory` for non-persistent storage in memory is assumed.
+                Sets the path for storing data. If no argument is given, the default of `memory` for non-persistent storage in memory is assumed.
                 
                 <br/>
                 Arguments for persistent backends are a combination of the backend name, a `:` or `://`, and an address or filename.
@@ -233,14 +251,12 @@ surreal start memory --user my_username --pass my_password
 
 The server is actively running, and should be left alone until you want to stop hosting the SurrealDB server.
 
-
 > [!NOTE]
 > The message "Started web server on 127.0.0.1:8000", indicates where the server is being hosted and must be accessed by clients. The location `127.0.0.1:8000` is the default, and can be manually changed by specifying the `--bind` option of the `surreal start` command.
 
+The `surreal start` command starts the server as a whole without regard to individual namespaces or databases.
 
-To access the SurrealDB server that you have started hosting, open a separate terminal which will act as the "client", while the previous terminal is still running the `surreal start` command described above. 
-
-In the new terminal, run the [`surreal sql` command](/docs/surrealdb/cli/sql) using the options shown below.
+To access the SurrealDB server that you have started hosting, open a new terminal which will act as the "client", while the previous terminal is still running the `surreal start` command described above. This is done using a separate [`surreal sql` command](/docs/surrealdb/cli/sql). A particular namespace and database can be specified using the `surreal sql` command, as seen below.
 
 ```bash
 surreal sql --endpoint http://127.0.0.1:8000 --namespace my_namespace --database my_database --auth-level root --username my_username --password my_password
diff --git a/src/content/doc-surrealdb/deployment/azure.mdx b/src/content/doc-surrealdb/deployment/azure.mdx
index a6b6f3251..1b9add02b 100644
--- a/src/content/doc-surrealdb/deployment/azure.mdx
+++ b/src/content/doc-surrealdb/deployment/azure.mdx
@@ -40,7 +40,7 @@ In order for you to complete this tutorial you'll need:
 - The [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli)
 - [`kubectl`](https://kubernetes.io/docs/tasks/tools/install-kubectl/) to manage the Kubernetes cluster
 - [`helm`](https://helm.sh/docs/intro/install/) to install SurrealDB server and TiKV
-- [`Surreal CLI`](https://surrealdb.com/install) to interact with the SurrealDB server
+- [`Surreal CLI`](/install) to interact with the SurrealDB server
 
 > [!NOTE]
 > Provisioning the environment in your Azure account will create resources and there will be cost associated with them. The cleanup section provides a guide to remove them, preventing further charges.
diff --git a/src/content/doc-surrealdb/deployment/google.mdx b/src/content/doc-surrealdb/deployment/google.mdx
index 0dfd97aab..4576f221c 100644
--- a/src/content/doc-surrealdb/deployment/google.mdx
+++ b/src/content/doc-surrealdb/deployment/google.mdx
@@ -37,7 +37,7 @@ In order for you to complete this tutorial you'll need:
 - The [gcloud CLI](https://cloud.google.com/sdk/gcloud) installed and configured
 - `kubectl` with gcloud integration for accessing the GKE cluster. Installation [here](https://cloud.google.com/kubernetes-engine/docs/tutorials/cluster-access-for-kubectl)
 - `helm` : To install SurrealDB server and TiKV
-- [`Surreal CLI`](https://surrealdb.com/install) : To interact with the SurrealDB server
+- [`Surreal CLI`](/install) : To interact with the SurrealDB server
 
 ## Create GKE Cluster
 
diff --git a/src/content/doc-surrealdb/deployment/kubernetes.mdx b/src/content/doc-surrealdb/deployment/kubernetes.mdx
index 6fec87298..81ddaee89 100644
--- a/src/content/doc-surrealdb/deployment/kubernetes.mdx
+++ b/src/content/doc-surrealdb/deployment/kubernetes.mdx
@@ -32,7 +32,7 @@ For this guide, we need to install:
 - [`kubectl`](https://kubernetes.io/docs/tasks/tools/install-kubectl/) : To manage the Kubernetes cluster
 - [`helm`](https://helm.sh/docs/intro/install/) : To install SurrealDB server and TiKV
 - [`KIND`](https://kind.sigs.k8s.io/) and [Docker](https://www.docker.com/) :To run a local Kubernetes cluster inside a Docker container
-- [`Surreal CLI`](https://surrealdb.com/install) : To interact with the SurrealDB server
+- [`Surreal CLI`](/install) : To interact with the SurrealDB server
 
 ## Create `KIND` Cluster
 
diff --git a/src/content/doc-surrealdb/embedding/javascript.mdx b/src/content/doc-surrealdb/embedding/javascript.mdx
index 93cef491f..c609e498d 100644
--- a/src/content/doc-surrealdb/embedding/javascript.mdx
+++ b/src/content/doc-surrealdb/embedding/javascript.mdx
@@ -23,7 +23,7 @@ import DarkLogo from "@img/icon/dark/javascript.png";
 
 SurrealDB is designed to be run in many different ways, and environments. Due to the [separation of the storage and compute](/docs/surrealdb/introduction/architecture) layers, SurrealDB can be run in embedded mode, from within your JavaScript environments. 
 
-You can embed SurrealDB in both browser and server environments. In browser environments using the [Wasm engine](/docs/sdk/javascript/engines/wasm), SurrealDB can be run as an in-memory database, or it can persist data using IndexedDB. In server environments using the [Node.js engine](/docs/sdk/javascript/engines/nodejs), SurrealDB can be run as an embedded database, backed by either an in-memory engine or [SurrealKV](/docs/surrealdb/cli/start#surrealkv-beta).
+You can embed SurrealDB in both browser and server environments. In browser environments using the [Wasm engine](/docs/sdk/javascript/engines/wasm), SurrealDB can be run as an in-memory database, or it can persist data using IndexedDB. In server environments using the [Node.js engine](/docs/sdk/javascript/engines/node), SurrealDB can be run as an embedded database, backed by either an in-memory engine or [SurrealKV](/docs/surrealdb/cli/start#surrealkv-beta).
 
 In this document, we will cover how to embed SurrealDB in both browser and server environments.
 
@@ -34,6 +34,6 @@ For more information on how to embed SurrealDB in browser environments, please s
 
 ## Server
 
-In server environments, you can use the [Node.js engine](/docs/sdk/javascript/engines/nodejs) to run SurrealDB as an embedded database. 
+In server environments, you can use the [Node.js engine](/docs/sdk/javascript/engines/node) to run SurrealDB as an embedded database. 
 
-For more information on how to embed SurrealDB in server environments, please see the [Node.js engine](/docs/sdk/javascript/engines/nodejs) documentation.
\ No newline at end of file
+For more information on how to embed SurrealDB in server environments, please see the [Node.js engine](/docs/sdk/javascript/engines/node) documentation.
diff --git a/src/content/doc-surrealdb/faqs/index.mdx b/src/content/doc-surrealdb/faqs/index.mdx
index 9934aa71b..79d096868 100644
--- a/src/content/doc-surrealdb/faqs/index.mdx
+++ b/src/content/doc-surrealdb/faqs/index.mdx
@@ -13,13 +13,13 @@ View some of the frequently asked questions regarding SurrealDB, SurrealQL, and
 
 ## Where can I find the latest features?
 
-Once features are released, we document them in our [release notes](https://surrealdb.com/releases) and on our [features page](https://surrealdb.com/features), which is a great place to understand capabilities.
+Once features are released, we document them in our [release notes](/releases) and on our [features page](/features), which is a great place to understand capabilities.
 
 You can also check some of our new features for <Version />:
-- [`SurrealLQ`](https://surrealdb.com/products/realtime-data-sync)
-- [`SurrealIX`](https://surrealdb.com/products/full-text-search)
-- [`SurrealCF`](https://surrealdb.com/products/change-data-capture)
-- [`SurrealML`](https://surrealdb.com/products/machine-learning)
+- [`SurrealLQ`](/features/realtime-data-sync)
+- [`SurrealIX`](/features/full-text-search)
+- [`SurrealCF`](/features/change-data-capture)
+- [`SurrealML`](/features/machine-learning)
 
 ## How do I scale SurrealDB?
 
@@ -28,7 +28,7 @@ SurrealDB can be scaled vertically on a single-node, by adding more compute powe
 
 ## What is the license for SurrealDB?
 
-Source code for SurrealDB is variously licensed under a number of different licenses. A copy of each license can be found in [each repository](https://github.com/surrealdb) on GitHub. For more information on the licenses view the license [details page](https://surrealdb.com/license).
+Source code for SurrealDB is variously licensed under a number of different licenses. A copy of each license can be found in [each repository](https://github.com/surrealdb) on GitHub. For more information on the licenses view the license [details page](/license).
 
 ## Do I need to purchase a license for development use?
 
diff --git a/src/content/doc-surrealdb/index.mdx b/src/content/doc-surrealdb/index.mdx
index 43c09c231..bb5e27d7d 100644
--- a/src/content/doc-surrealdb/index.mdx
+++ b/src/content/doc-surrealdb/index.mdx
@@ -39,4 +39,4 @@ SurrealDB makes building and scaling realtime apps dramatically quicker and easi
 
 To quickly test out SurrealDB and [SurrealQL](/docs/surrealql) functionality, we've included [demo dataset](/docs/surrealql/demo) which you can download and [<code>import</code> ](/docs/surrealdb/cli/import)into your SurrealDB instance.
 
-<span>The current stable version of SurrealDB </span><span> is <a href='https://surrealdb.com/releases'> <Version /> </a></span>
+<span>The current stable version of SurrealDB </span><span> is <a href='/releases'> <Version /> </a></span>
diff --git a/src/content/doc-surrealdb/installation/linux.mdx b/src/content/doc-surrealdb/installation/linux.mdx
index 17425dc55..a9165b6e8 100644
--- a/src/content/doc-surrealdb/installation/linux.mdx
+++ b/src/content/doc-surrealdb/installation/linux.mdx
@@ -66,7 +66,7 @@ SurrealDB command-line interface and server
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on Github (https://github.com/surrealdb/surrealdb/issues).
 
diff --git a/src/content/doc-surrealdb/installation/macos.mdx b/src/content/doc-surrealdb/installation/macos.mdx
index 63299be8c..870603b8b 100644
--- a/src/content/doc-surrealdb/installation/macos.mdx
+++ b/src/content/doc-surrealdb/installation/macos.mdx
@@ -65,7 +65,7 @@ SurrealDB command-line interface and server
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on Github (https://github.com/surrealdb/surrealdb/issues).
 
@@ -131,7 +131,7 @@ SurrealDB command-line interface and server
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on Github (https://github.com/surrealdb/surrealdb/issues).
 
diff --git a/src/content/doc-surrealdb/installation/running/docker.mdx b/src/content/doc-surrealdb/installation/running/docker.mdx
index f65b0f4e7..0a12ea999 100644
--- a/src/content/doc-surrealdb/installation/running/docker.mdx
+++ b/src/content/doc-surrealdb/installation/running/docker.mdx
@@ -106,7 +106,7 @@ SurrealDB command-line interface and server
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on Github (https://github.com/surrealdb/surrealdb/issues).
 
diff --git a/src/content/doc-surrealdb/installation/upgrading/migrating-data-to-2.x.mdx b/src/content/doc-surrealdb/installation/upgrading/migrating-data-to-2.x.mdx
index 91e5618ff..e2d396a01 100644
--- a/src/content/doc-surrealdb/installation/upgrading/migrating-data-to-2.x.mdx
+++ b/src/content/doc-surrealdb/installation/upgrading/migrating-data-to-2.x.mdx
@@ -7,7 +7,7 @@ description: This guide will help you upgrade your current SurrealDB installatio
 
 # Upgrading from `1.x` to `2.x`
 
-The `2.0.0` release of SurrealDB includes [many new features, improvements, and bug fixes](https://surrealdb.com/releases#v2-0-0). However, due to this there are some breaking changes that you should be aware of when upgrading.
+The `2.0.0` release of SurrealDB includes [many new features, improvements, and bug fixes](/releases#v2-0-0). However, due to this there are some breaking changes that you should be aware of when upgrading.
 
 This guide will help you upgrade your current SurrealDB installation to the latest `2.x` release.
 
@@ -19,7 +19,7 @@ This guide will help you upgrade your current SurrealDB installation to the late
   - [Ranges are now their own value as suppose to being available as just record id ranges](https://github.com/surrealdb/surrealdb/pull/4506)
 
 ### SurrealQL
-- The `UPDATE` statement no longer creates records if these are missing. Instead, use the new [UPSERT](https://surrealdb.com/docs/surrealql/statements/upsert) statement for this behaviour.
+- The `UPDATE` statement no longer creates records if these are missing. Instead, use the new [UPSERT](/docs/surrealql/statements/upsert) statement for this behaviour.
 - The `file://` connection protocol has been deprecated in favour of the more explicit `rocksdb://` protocol.
 - The `DEFINE SCOPE` statement has been dropped in favor for the new [`DEFINE ACCESS TYPE RECORD`](/docs/surrealql/statements/define/access/record) statement
   - `DEFINE TOKEN` definitions defined under scopes are now integrated into `DEFINE ACCESS TYPE RECORD`.
@@ -61,7 +61,7 @@ Although the `surreal fix` command is a quick way to migrate your data, it is no
 
 The `surreal fix` command above has been created specifically for 1.x instances. However, data currently on a `2.0.0-alpha` instance can still be manually exported and then reimported into a project running on `2.0.0` via the following steps.
 
-1. Export your current data as SQL. You can do this using the [`surreal export`](/docs/surrealdb/cli/export) command in the terminal:
+1. Export your current data as a `.surql` (SurrealQL) file. You can do this using the [`surreal export`](/docs/surrealdb/cli/export) command in the terminal:
 
 ```bash
 # Example export command to export data to a file called `export.surql` in the downloads directory.
@@ -89,4 +89,4 @@ error: Storage version is out-of-date.
 
 ## Read the full changelog
 
-There have been major improvements to SurrealDB in `2.0.0` release both in alpha and beta. Check out the changes on the [release page](https://surrealdb.com/releases).
+There have been major improvements to SurrealDB in `2.0.0` release both in alpha and beta. Check out the changes on the [release page](/releases).
diff --git a/src/content/doc-surrealdb/installation/windows.mdx b/src/content/doc-surrealdb/installation/windows.mdx
index a1e5f0679..42cfae2a5 100644
--- a/src/content/doc-surrealdb/installation/windows.mdx
+++ b/src/content/doc-surrealdb/installation/windows.mdx
@@ -66,7 +66,7 @@ SurrealDB command-line interface and server
 To get started using SurrealDB, and for guides on connecting to and building applications
 on top of SurrealDB, check out the SurrealDB documentation (https://surrealdb.com/docs).
 
-If you have questions or ideas, join the SurrealDB community (https://surrealdb.com/community).
+If you have questions or ideas, join the SurrealDB community (/community).
 
 If you find a bug, submit an issue on Github (https://github.com/surrealdb/surrealdb/issues).
 
diff --git a/src/content/doc-surrealdb/integration/cbor.mdx b/src/content/doc-surrealdb/integration/cbor.mdx
index 4a1c3576b..e05202210 100644
--- a/src/content/doc-surrealdb/integration/cbor.mdx
+++ b/src/content/doc-surrealdb/integration/cbor.mdx
@@ -5,15 +5,15 @@ title: CBOR Protocol| Integration
 description: SurrealDB supports a number of methods for connecting to the database and performing data queries.
 ---
 
-# CBOR
+# CBOR Protocol
 
-SurrealDB Supports the CBOR protocol, shipped with an additional couple of custom tags.
+SurrealDB extends the [CBOR](https://www.rfc-editor.org/rfc/rfc8949.html) protocol with a number of custom tags to support the full range of data types available in SurrealDB. This document provides an overview of the custom tags and their respective values.
 
 ## References:
 - CBOR Protocol - [RFC 8949](https://www.rfc-editor.org/rfc/rfc8949.html)
 - CBOR Official Tags - [Iana](https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml)
 
-## Tags Overview
+## Custom tags
 
 <table>
     <thead>
diff --git a/src/content/doc-surrealdb/integration/http.mdx b/src/content/doc-surrealdb/integration/http.mdx
index fa2a15dea..6a2cd3817 100644
--- a/src/content/doc-surrealdb/integration/http.mdx
+++ b/src/content/doc-surrealdb/integration/http.mdx
@@ -12,9 +12,9 @@ import Label from "@components/shared/Label.astro";
 
 # HTTP & Rest
 
-The HTTP endpoints enable simple selection and modifications of all records or a single record in a table, in addition to support for custom SurrealQL queries with multiple statements, using traditional RESTful HTTP url endpoints.
+The HTTP endpoints exposed by SurrealDB instances provide a simple way to interact with the database over a traditional RESTful interface. This includes selecting and modifying one or more records, executing custom SurrealQL queries, and managing SurrealML models. The endpoints are designed to be simple and easy to use in stateless environments, making them ideal for lightweight applications where a persistent database connection is not required.
 
-## Accessing Endpoints via Postman
+## Getting started via Postman
 
 The most convenient way to access these endpoints is via SurrealDB's Postman Collection. To do so, follow these steps:
 
@@ -27,6 +27,8 @@ The most convenient way to access these endpoints is via SurrealDB's Postman Col
 > [!IMPORTANT]
 > Ensure that your URL is set correctly, if running locally, the URL should be `http://localhost:8000`.By default, the URL is set to local. Start your server using the [`surreal start`](/docs/surrealdb/cli/start) command in the CLI or through Surrealist's [local database serving](/docs/surrealist/concepts/local-database-serving) functionality, before querying the endpoints.
 
+## Supported methods
+
 You can use the HTTP endpoints to perform the following actions:
 
 <br />
diff --git a/src/content/doc-surrealdb/integration/index.mdx b/src/content/doc-surrealdb/integration/index.mdx
index e113f56f1..b5e9710f1 100644
--- a/src/content/doc-surrealdb/integration/index.mdx
+++ b/src/content/doc-surrealdb/integration/index.mdx
@@ -11,7 +11,7 @@ In this section, you will explore the various integration options and techniques
 
 ## Introduction
 
-SurrealDB is designed to be flexible and compatible with a wide range of technologies and frameworks. This section will guide you through the process of integrating SurrealDB into your projects, whether you are working with JavaScript /TypeScript, Python, React, Node.js, or other popular technologies.
+SurrealDB is designed to be flexible and compatible with a wide range of technologies and frameworks. This section will guide you through the process of integrating SurrealDB into your projects, whether you are working directly from code, or integrating with one of our supported network protocols.
 
 ## API Reference
 
diff --git a/src/content/doc-surrealdb/integration/rpc.mdx b/src/content/doc-surrealdb/integration/rpc.mdx
index 99902ac52..02e8625ec 100644
--- a/src/content/doc-surrealdb/integration/rpc.mdx
+++ b/src/content/doc-surrealdb/integration/rpc.mdx
@@ -10,7 +10,11 @@ import Label from "@components/shared/Label.astro";
 
 # RPC Protocol
 
-The RPC protocol allows for easy bi-directional communication with SurrealDB. This allows you to maintain a single connection to run all your queries, but also opens up the possibility of Live Queries!
+The RPC protocol allows for network-protocol agnostic communication with SurrealDB. It is used internally by our client SDKs, and supports both HTTP and WebSocket based communication. Combined with the power of our [CBOR protocol](./cbor) specification, the RPC protocol provides a fully type-safe and efficient way to interact with SurrealDB over the network.
+
+## Supported methods
+
+You can use the RPC protocol to perform the following actions:
 
 <table>
     <thead>
diff --git a/src/content/doc-surrealdb/integration/sdks.mdx b/src/content/doc-surrealdb/integration/sdks.mdx
index 025c08b66..e2cf5f0bf 100644
--- a/src/content/doc-surrealdb/integration/sdks.mdx
+++ b/src/content/doc-surrealdb/integration/sdks.mdx
@@ -33,7 +33,7 @@ import DarkWasm from "@img/icon/dark/webassembly.png";
 
 # SDKs
 
-SurrealDB supports a number of methods for connecting to the database and performing data queries.
+SurrealDB supports numerous client SDKs for connecting to the database and performing data queries. These SDKs are designed to simplify the integration process and provide developers with the tools they need to interact with SurrealDB from their preferred programming languages.
 
 <Boxes>
     <IconBox
diff --git a/src/content/doc-surrealdb/introduction/mongo.mdx b/src/content/doc-surrealdb/introduction/mongo.mdx
index ce808a056..adf34949d 100644
--- a/src/content/doc-surrealdb/introduction/mongo.mdx
+++ b/src/content/doc-surrealdb/introduction/mongo.mdx
@@ -112,9 +112,9 @@ Let's get you up to speed with SurrealQL syntax with some CRUD examples.
 
 ### Create
 
-As MongoDB is schemaless, only the SurrealQL schemaless approach is shown below. For a schemafull option see the [define table](/docs/surrealdb/surrealql/statements/define/table) page.
+As MongoDB is schemaless, only the SurrealQL schemaless approach is shown below. For a schemafull option see the [define table](/docs/surrealql/statements/define/table) page.
 
-For more SurrealQL examples, see the [create](/docs/surrealdb/surrealql/statements/create) and [insert](/docs/surrealdb/surrealql/statements/insert) pages.
+For more SurrealQL examples, see the [create](/docs/surrealql/statements/create) and [insert](/docs/surrealql/statements/insert) pages.
 
 <table>
     <thead>
@@ -153,7 +153,7 @@ For more SurrealQL examples, see the [create](/docs/surrealdb/surrealql/statemen
 
 ### Read
 
-For more SurrealQL examples, see the [select](/docs/surrealdb/surrealql/statements/select), [live select](/docs/surrealdb/surrealql/statements/live) and [return](/docs/surrealdb/surrealql/statements/return) pages.
+For more SurrealQL examples, see the [select](/docs/surrealql/statements/select), [live select](/docs/surrealql/statements/live) and [return](/docs/surrealql/statements/return) pages.
 
 <table>
     <thead>
@@ -232,7 +232,7 @@ For more SurrealQL examples, see the [select](/docs/surrealdb/surrealql/statemen
 
 ### Update
 
-For more SurrealQL examples, see the [update](/docs/surrealdb/surrealql/statements/update) page.
+For more SurrealQL examples, see the [update](/docs/surrealql/statements/update) page.
 
 <table>
     <thead>
@@ -263,7 +263,7 @@ For more SurrealQL examples, see the [update](/docs/surrealdb/surrealql/statemen
 
 ### Delete
 
-For more SurrealQL examples, see the [delete](/docs/surrealdb/surrealql/statements/delete) and [remove](/docs/surrealdb/surrealql/statements/remove) pages.
+For more SurrealQL examples, see the [delete](/docs/surrealql/statements/delete) and [remove](/docs/surrealql/statements/remove) pages.
 
 <table>
     <thead>
diff --git a/src/content/doc-surrealdb/introduction/neo4j.mdx b/src/content/doc-surrealdb/introduction/neo4j.mdx
index 3fa334614..fc523fcb5 100644
--- a/src/content/doc-surrealdb/introduction/neo4j.mdx
+++ b/src/content/doc-surrealdb/introduction/neo4j.mdx
@@ -112,9 +112,9 @@ Let's get you up to speed with SurrealQL syntax with some CRUD examples.
 
 ### Create
 
-As Neo4j is schemafull, only the SurrealQL schemafull approach is shown below. For a schemafull option see the [define table](/docs/surrealdb/surrealql/statements/define/table) page.
+As Neo4j is schemafull, only the SurrealQL schemafull approach is shown below. For a schemafull option see the [define table](/docs/surrealql/statements/define/table) page.
 
-For more SurrealQL examples, see the [create](/docs/surrealdb/surrealql/statements/create), [insert](/docs/surrealdb/surrealql/statements/insert) and [relate](/docs/surrealdb/surrealql/statements/relate) pages.
+For more SurrealQL examples, see the [create](/docs/surrealql/statements/create), [insert](/docs/surrealql/statements/insert) and [relate](/docs/surrealql/statements/relate) pages.
 
 <table>
     <thead>
@@ -153,7 +153,7 @@ For more SurrealQL examples, see the [create](/docs/surrealdb/surrealql/statemen
 
 ### Read
 
-For more SurrealQL examples, see the [select](/docs/surrealdb/surrealql/statements/select), [live select](/docs/surrealdb/surrealql/statements/live) and [return](/docs/surrealdb/surrealql/statements/return) pages.
+For more SurrealQL examples, see the [select](/docs/surrealql/statements/select), [live select](/docs/surrealql/statements/live) and [return](/docs/surrealql/statements/return) pages.
 
 <table>
     <thead>
@@ -240,7 +240,7 @@ For more SurrealQL examples, see the [select](/docs/surrealdb/surrealql/statemen
 
 ### Update
 
-For more SurrealQL examples, see the [update](/docs/surrealdb/surrealql/statements/update) page.
+For more SurrealQL examples, see the [update](/docs/surrealql/statements/update) page.
 
 <table>
     <thead>
@@ -279,7 +279,7 @@ For more SurrealQL examples, see the [update](/docs/surrealdb/surrealql/statemen
 
 ### Delete
 
-For more SurrealQL examples, see the [delete](/docs/surrealdb/surrealql/statements/delete) and [remove](/docs/surrealdb/surrealql/statements/remove) pages.
+For more SurrealQL examples, see the [delete](/docs/surrealql/statements/delete) and [remove](/docs/surrealql/statements/remove) pages.
 
 <table>
     <thead>
diff --git a/src/content/doc-surrealdb/querying/surrealql/surrealist.mdx b/src/content/doc-surrealdb/querying/surrealql/surrealist.mdx
index 87e790731..b81e061cb 100644
--- a/src/content/doc-surrealdb/querying/surrealql/surrealist.mdx
+++ b/src/content/doc-surrealdb/querying/surrealql/surrealist.mdx
@@ -26,7 +26,7 @@ In order to interact with a SurrealDB database you must first create a connectio
 
 After opening a connection, you can switch to another connection at any time by pressing the connection name in the top left of the interface. This will open the connection list allowing you to switch to another connection, or create a new one.
 
-Within the connection list you will also find a special connection called Sandbox, which is always available and allows you to test and experiment without storing data persistently. This connection is useful for learning SurrealQL, testing queries, and more.
+Within the connection list you will also find a special connection called Sandbox, which is always available and allows you to test and experiment without storing data persistently. This connection is useful for learning SurrealQL, testing queries, and more. The Sandbox connection is designed for simple testing and not for evaluating performance, as it is limited to a single thread within the browser's WebAssembly engine.
 
 You can also create a new custom connection, this will allow you to connect to a remote SurrealDB instance, or a local instance this will also require you to set the namespace and database.
 
diff --git a/src/content/doc-surrealdb/reference-guide/vector-search.mdx b/src/content/doc-surrealdb/reference-guide/vector-search.mdx
index 102246eef..a5cee7a57 100644
--- a/src/content/doc-surrealdb/reference-guide/vector-search.mdx
+++ b/src/content/doc-surrealdb/reference-guide/vector-search.mdx
@@ -17,7 +17,7 @@ import DarkDistanceMetrics from "@img/image/dark/distance-metrics.png";
 
 # Vector Search
 
-SurrealDB supports [Full-Text Search](/docs/surrealdb/reference-guide/full-text-search) and Vector Search. Full-Text search(FTS) involves indexing documents using the [FTS index](/docs/surrealdb/surrealql/statements/define/indexes#full-text-search-index) and breaking down the content of the document into smaller tokens with the help of [analysers](/docs/surrealdb/surrealql/statements/define/analyzer) and [tokenizers](/docs/surrealdb/surrealql/statements/define/analyzer#tokenizers).
+SurrealDB supports [Full-Text Search](/docs/surrealdb/reference-guide/full-text-search) and Vector Search. Full-Text search(FTS) involves indexing documents using the [FTS index](/docs/surrealql/statements/define/indexes#full-text-search-index) and breaking down the content of the document into smaller tokens with the help of [analysers](/docs/surrealql/statements/define/analyzer) and [tokenizers](/docs/surrealql/statements/define/analyzer#tokenizers).
 
 Vector Search in SurrealDB is introduced to support efficient and accurate searching of high-dimensional data. This guide will walk you through the essentials of working with vectors in SurrealDB, from storing vectors in embeddings to performing computations and optimizing searches with various indexing strategies.
 
@@ -45,7 +45,7 @@ Lead can mean `taking initiative`, as well as the chemical element with the symb
 
 Now let’s add some context to the word. Consider a database of liquid samples which note down harmful chemicals that are found in them.
 
-In the example below, we have a table called `liquids` with a `sample` field and a `content` field.  Next, we can do a [Full-Text index](/docs/surrealdb/surrealql/statements/define/indexes#full-text-search-index) on the `content` field by first defining an analyzer called `liquid_analyzer`. We can then [Define an index](/docs/surrealdb/surrealql/statements/define/indexes) on the content field in the liquid table and set our [custom analyzer](/docs/surrealdb/surrealql/statements/define/analyzer) (`liquid_analyzer`)to search through the index.
+In the example below, we have a table called `liquids` with a `sample` field and a `content` field.  Next, we can do a [Full-Text index](/docs/surrealql/statements/define/indexes#full-text-search-index) on the `content` field by first defining an analyzer called `liquid_analyzer`. We can then [Define an index](/docs/surrealql/statements/define/indexes) on the content field in the liquid table and set our [custom analyzer](/docs/surrealql/statements/define/analyzer) (`liquid_analyzer`)to search through the index.
 
 Then, using the select statement to retrieve all the samples containing the chemical lead will also bring up samples that mention the word `lead`.
 
@@ -83,11 +83,11 @@ Notice that we have added an `embedding` field to the table. This field will sto
 
 You have the option of using 3 different approaches for performing Vector search.
 
-- [Bruteforce](/docs/surrealdb/surrealql/operators#brute-force-method)
-- [Hierarchical navigable small world(HNSW)](/docs/surrealdb/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world)
-- [M-Tree](/docs/surrealdb/surrealql/statements/define/indexes#m-tree-index)
+- [Bruteforce](/docs/surrealql/operators#brute-force-method)
+- [Hierarchical navigable small world(HNSW)](/docs/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world)
+- [M-Tree](/docs/surrealql/statements/define/indexes#m-tree-index)
 
-As you want to perform a nearest neighbour search and not an exact search, you would typically use an index like [HNSW](/docs/surrealdb/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world) or [M-Tree](/docs/surrealdb/surrealql/statements/define/indexes#m-tree-index).
+As you want to perform a nearest neighbour search and not an exact search, you would typically use an index like [HNSW](/docs/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world) or [M-Tree](/docs/surrealql/statements/define/indexes#m-tree-index).
 
 
 
@@ -121,7 +121,7 @@ There are no strict rules or limitations regarding the length of the embeddings,
 
 ## Computation on Vectors: "vector::" Package of Functions
 
-SurrealDB provides [Vector Functions](/docs/surrealdb/surrealql/functions/database/vector) for most of the major numerical computations done on vectors. They include functions for element-wise addition, division and even normalisation.
+SurrealDB provides [Vector Functions](/docs/surrealql/functions/database/vector) for most of the major numerical computations done on vectors. They include functions for element-wise addition, division and even normalisation.
 
 They also include similarity and distance functions, which help in understanding how similar or dissimilar two vectors are.
 Usually, the vector with the smallest distance or the largest cosine similarity value (closest to 1) is deemed the most similar to the item you are trying to search for.
@@ -136,12 +136,12 @@ Usually, the vector with the smallest distance or the largest cosine similarity
 
 The choice of distance or similarity function depends on the nature of your data and the specific requirements of your application.
 
-In the liquids examples, we assumed that the embeddings represented the harmfulness of lead (as a substance). We used the [`vector::similarity::cosine`](/docs/surrealdb/surrealql/functions/database/vector#vectorsimilaritycosine) function because cosine similarity is typically preferred when absolute distances are less important, but proportions and direction matter more.
+In the liquids examples, we assumed that the embeddings represented the harmfulness of lead (as a substance). We used the [`vector::similarity::cosine`](/docs/surrealql/functions/database/vector#vectorsimilaritycosine) function because cosine similarity is typically preferred when absolute distances are less important, but proportions and direction matter more.
 
 ## Vector Indexes
 
 When it comes to search, you can always use brute force.
-In SurrealDB, you can use the [Brute force approach](/docs/surrealdb/surrealql/statements/define/indexes#brute-force-method) to search through your vector embeddings and data.
+In SurrealDB, you can use the [Brute force approach](/docs/surrealql/statements/define/indexes#brute-force-method) to search through your vector embeddings and data.
 
 Brute force search compares a query vector against all vectors in the dataset to find the closest match. As this is a brute-force approach, you do not create an index for this approach.
 
@@ -162,21 +162,21 @@ This is where Vector indexes come in.
 In SurrealDB, you can perform a vector search using the two primary indexes:
 
 1. M-Tree Index:
-    - The [M-Tree index](/docs/surrealdb/surrealql/statements/define/indexes#m-tree-index) is a metric tree-based index suitable for similarity search in metric spaces.
+    - The [M-Tree index](/docs/surrealql/statements/define/indexes#m-tree-index) is a metric tree-based index suitable for similarity search in metric spaces.
     - The M-Tree index can be configured with parameters such as the distance function to compare the vectors.
 2. Hierarchical Navigable Small World (HNSW) Index:
     - [HNSW](https://en.wikipedia.org/wiki/Hierarchical_navigable_small_world) (Hierarchical Navigable Small World) is a state-of-the-art algorithm for approximate nearest neighbour search in high-dimensional spaces. It offers a balance between search efficiency and accuracy.
-    - The [HNSW index](/docs/surrealdb/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world) is a proximity graph-based index.
+    - The [HNSW index](/docs/surrealql/statements/define/indexes#hnsw-hierarchical-navigable-small-world) is a proximity graph-based index.
 
 By design, HNSW currently operates as an "in-memory" structure. Introducing persistence to this feature, while beneficial for retaining index states, is an ongoing area of development. Our goal is to balance the speed of data ingestion with the advantages of persistence.
 
-You can also use the  [`REBUILD` statement](/docs/surrealdb/surrealql/statements/rebuild), which allows for the manual rebuilding of indexes as needed. This approach ensures that while we explore persistence options, we maintain the optimal performance that users expect from HNSW and MTree, providing flexibility and control over the indexing process.
+You can also use the  [`REBUILD` statement](/docs/surrealql/statements/rebuild), which allows for the manual rebuilding of indexes as needed. This approach ensures that while we explore persistence options, we maintain the optimal performance that users expect from HNSW and MTree, providing flexibility and control over the indexing process.
 
 Both indexes are designed to handle the challenges of searching in spaces where traditional indexing methods become inefficient. The choice between HNSW and M-Tree would depend on the application's specific requirements, such as the need for an exact versus approximate nearest neighbour search, the distance metric used, and the nature of the data.
 
 ## Filtering through Vector Search
 
-The [`vector::distance::knn()`](/docs/surrealdb/surrealql/functions/database/vector#vectordistanceknn) function from SurrealDB returns the distance computed between vectors by the KNN operator. This operator can be used to avoid recomputation of the distance in every `select` query.
+The [`vector::distance::knn()`](/docs/surrealql/functions/database/vector#vectordistanceknn) function from SurrealDB returns the distance computed between vectors by the KNN operator. This operator can be used to avoid recomputation of the distance in every `select` query.
 
 Consider a scenario where you’re searching for actors who look like you but they should have won an Oscar. You set a flag, which is true for actors who’ve won the golden trophy.
 
@@ -224,8 +224,8 @@ SELECT id, flag, vector::distance::knn() AS distance FROM actor WHERE flag = tru
 
 ## Conclusion
 
-Vector Search does not need to be complicated and overwhelming. Once you have your embeddings available, you can try out different vector functions in combination with your query vector to see what works best for your use case. As discussed in the reference guide, you have 3 options to perform Vector Search in SurrealDB. Based on the complexity of your data and accuracy expectations, you can choose between them. You can design your `select` statements to query your search results along with filters and conditions. In order to avoid recalculation of the KNN distance for every single query, you also have the [`vector::distance::knn()`](/docs/surrealdb/surrealql/functions/database/vector#vectordistanceknn).
+Vector Search does not need to be complicated and overwhelming. Once you have your embeddings available, you can try out different vector functions in combination with your query vector to see what works best for your use case. As discussed in the reference guide, you have 3 options to perform Vector Search in SurrealDB. Based on the complexity of your data and accuracy expectations, you can choose between them. You can design your `select` statements to query your search results along with filters and conditions. In order to avoid recalculation of the KNN distance for every single query, you also have the [`vector::distance::knn()`](/docs/surrealql/functions/database/vector#vectordistanceknn).
 
 Due to [GenAI](https://en.wikipedia.org/wiki/Generative_artificial_intelligence), most applications today deal with intricate data with layered meanings and characteristics. Vector search plays a big role in analyzing such data to find what you’re looking for or to make informed decisions.
 
-You can start using Vector Search in SurrealDB by [installing SurrealDB](/docs/surrealdb/installation/) on your machines or by using [Surrealist](https://surrealdb.com/surrealist). And if you’re looking for a [quick video explaining Vector Search](https://www.youtube.com/watch?v=MqddPmgKSCs), check out our [YouTube channel](https://www.youtube.com/@SurrealDB).
+You can start using Vector Search in SurrealDB by [installing SurrealDB](/docs/surrealdb/installation/) on your machines or by using [Surrealist](/surrealist). And if you’re looking for a [quick video explaining Vector Search](https://www.youtube.com/watch?v=MqddPmgKSCs), check out our [YouTube channel](https://www.youtube.com/@SurrealDB).
diff --git a/src/content/doc-surrealdb/security/summary.mdx b/src/content/doc-surrealdb/security/summary.mdx
index d0462deb8..65d138202 100644
--- a/src/content/doc-surrealdb/security/summary.mdx
+++ b/src/content/doc-surrealdb/security/summary.mdx
@@ -91,7 +91,7 @@ SurrealDB has the ability to provide a secure TLS connection to its HTTP server
 ### Open Source Security
 SurrealDB has an open source security policy extending its security process to the wider community. This policy is made available through Github and a “security.txt” file, and allows SurrealDB to benefit from the security expertise and resources of its community. In turn, it provides the community with safe and responsible avenues to contribute to the security of an open source product that they rely on.
 - [Github: Security Policy](https://github.com/surrealdb/surrealdb/security/policy)
-- [Website: Well-Known Security File](https://surrealdb.com/.well-known/security.txt)
+- [Website: Well-Known Security File](/.well-known/security.txt)
 
 ### Responsible Disclosure
 SurrealDB encourages external contributors to report security vulnerabilities following a small set of practices described in the open source security policy. SurrealDB commits to address all legitimate reports within three days, work on resolving the issue while keeping the reporter updated and crediting the reporter when an advisory is eventually published. The responsible disclosure process protects legitimate security reporters from legal repercussions and promotes an open discussion around the security of SurrealDB.
@@ -105,7 +105,7 @@ SurrealDB releases security advisories whenever a significant security issue has
 
 
 ### Software Composition Analysis
-SurrealDB includes SCA in its development process by using both the Cargo Deny binary crate for Rust code as well as Dependabot in its CI/CD pipelines. The later ensures that changes including dependencies with known vulnerabilities cannot be merged unless those vulnerabilities are explicitly acknowledged in a public file; this usually requires either updating or replacing the affected dependency. The former provides notification of emerging vulnerabilities in dependencies that are currently being used by SurrealDB so that they can be updated or replaced.
+SurrealDB includes SCA in its development process by using both the Cargo Deny binary crate for Rust code as well as Dependabot in its CI/CD pipelines. The latter ensures that changes including dependencies with known vulnerabilities cannot be merged unless those vulnerabilities are explicitly acknowledged in a public file; this usually requires either updating or replacing the affected dependency. The former provides notification of emerging vulnerabilities in dependencies that are currently being used by SurrealDB so that they can be updated or replaced.
 - [Github: Security Policy (Dependencies)](https://github.com/surrealdb/surrealdb/security/policy#dependencies)
 - [Github: Cargo Deny Configuration](https://github.com/surrealdb/surrealdb/blob/main/deny.toml)
 
diff --git a/src/content/doc-surrealdb/security/troubleshooting.mdx b/src/content/doc-surrealdb/security/troubleshooting.mdx
index 98270e7d7..10c0ad8cb 100644
--- a/src/content/doc-surrealdb/security/troubleshooting.mdx
+++ b/src/content/doc-surrealdb/security/troubleshooting.mdx
@@ -73,7 +73,7 @@ Although tokens accepted by SurrealDB must have some expiration, you can configu
 
 In SurrealDB, clients can authenticate using different methods, such as credentials (e.g. username and password), a token (i.e. JWT) and other experimental access methods like bearer keys. These access methods provide different benefits and have different performance implications. Different options are provided precisely to allow flexibility for different use cases.
 
-If you observe that authentication requests are slow or computationally (e.g. CPU, memory...) expensive, consider switching from authentication with credentials to token authentication. By default, SurrealDB verifies passwords for system users with [Argon2id](https://en.wikipedia.org/wiki/Argon2), which is a password hashing algorithm that ensures that the password verification process is slow and expensive to prevent password cracking. If you are using the [HTTP REST API](/docs/surrealdb/integration/http) to authenticate using credentials (i.e. with `Authorization: Basic ...` rather than `Authorization: Bearer ...`), this password verification process will be performed for every request. Instead, consider [authenticating once with credentials](https://surrealdb.com/docs/surrealdb/integration/http#signin) to obtain a token and performing subsequent requests using that token in the `Authorization` header prefixed by `Bearer`. Token verification is a different cryptographic process that is designed to be orders of magnitude faster and cheaper.
+If you observe that authentication requests are slow or computationally (e.g. CPU, memory...) expensive, consider switching from authentication with credentials to token authentication. By default, SurrealDB verifies passwords for system users with [Argon2id](https://en.wikipedia.org/wiki/Argon2), which is a password hashing algorithm that ensures that the password verification process is slow and expensive to prevent password cracking. If you are using the [HTTP REST API](/docs/surrealdb/integration/http) to authenticate using credentials (i.e. with `Authorization: Basic ...` rather than `Authorization: Bearer ...`), this password verification process will be performed for every request. Instead, consider [authenticating once with credentials](/docs/surrealdb/integration/http#signin) to obtain a token and performing subsequent requests using that token in the `Authorization` header prefixed by `Bearer`. Token verification is a different cryptographic process that is designed to be orders of magnitude faster and cheaper.
 
 When using credentials to authenticate record users, you are able to choose the password hashing algorithm that you use in your `SIGNIN` query. If you must repeatedly authenticate using credentials and the performance impact of using Argon2id is unacceptable to your use case, you may consider using different password hashing algorithms (e.g. [Bcrypt](/docs/surrealql/functions/database/crypto#cryptobcryptcompare), [Scrypt](/docs/surrealql/functions/database/crypto#cryptoscryptcompare) or [PBKDF2](/docs/surrealql/functions/database/crypto#cryptopbkdf2compare)) that may be more efficient at the cost of diminished security against certain types of password cracking.
 
diff --git a/src/content/doc-surrealist/advanced-topics/surrealql-editors.mdx b/src/content/doc-surrealist/advanced-topics/surrealql-editors.mdx
index af3dbbde7..67945a5e9 100644
--- a/src/content/doc-surrealist/advanced-topics/surrealql-editors.mdx
+++ b/src/content/doc-surrealist/advanced-topics/surrealql-editors.mdx
@@ -94,5 +94,5 @@ Some editors support record inspection, which allows you to open a record in the
 
 ## JSON
 
-Some editors, such the the record editor and query responses, support falling back to a JSON representation.
+Some editors, such as the record editor and query responses, support falling back to a JSON representation.
 This can be configured in the settings dialog under `Appearance > Value formatting mode`.
diff --git a/src/content/doc-surrealist/concepts/surreal-cloud.mdx b/src/content/doc-surrealist/concepts/surreal-cloud.mdx
new file mode 100644
index 000000000..8cb925201
--- /dev/null
+++ b/src/content/doc-surrealist/concepts/surreal-cloud.mdx
@@ -0,0 +1,126 @@
+---
+sidebar_position: 9
+sidebar_label: Deploying your database
+title: Surrealist | Surreal Cloud | Deploying your database
+description:  Surreal Cloud redefines the database experience, offering the power and flexibility of SurrealDB without the pain of managing infrastructure. Elevate your business to unparalleled levels of scale and resilience. Focus on building tomorrow's applications. Let us take care of the rest.
+---
+
+import Image from "@components/Image.astro";
+
+import Tabs from "@components/Tabs/Tabs.astro";
+import TabItem from "@components/Tabs/TabItem.astro";
+
+import CloudImageLight from '@img/image/cloud/light/cloud-light.png';
+import CloudImageDark from '@img/image/cloud/cloud-dark.png';
+
+import OpenInSurrealistLight from '@img/image/cloud/open-in-surrealist.png';
+import OpenInSurrealistDark from '@img/image/cloud/open-in-surrealist.png';
+
+import LightCloud from '@img/image/cloud/surrealcloud.png';
+import DarkCloud from '@img/image/cloud/surrealcloud.png';
+
+import HighlyAvailable from '@img/image/cloud/light/highly-available-and-scalable-light.png';
+import HighlyAvailableDark from '@img/image/cloud/highly-available-and-scalable-dark.png';
+
+
+<Image
+alt="Surreal Cloud"
+width={100}
+className="flag-image-title"
+src={{
+	light: LightCloud,
+	dark: DarkCloud,
+	}}  
+/>
+
+# Surreal Cloud
+
+Surreal Cloud transforms the database experience, providing the power and versatility of SurrealDB without the complexity of managing infrastructure. Whether you’re building for passion projects or enterprise-scale applications, Surreal Cloud offers the scalability, resilience, and innovation you need to stay ahead.
+
+Enjoy a fully managed solution that takes the hassle out of infrastructure operations. With SurrealDB’s ACID compliance, you can confidently run transactions at scale across multiple environments, ensuring data integrity and reliability.
+
+Designed to support your growth, Surreal Cloud scales effortlessly [from prototypes to large-scale deployments](/docs/cloud/getting-started/create-an-instance). By leveraging centralized data, it enables departments or teams to work efficiently while maintaining consistent data integrity and reducing redundancy.
+
+Our transparent and [predictable pricing](/pricing) ensures you only pay for what you need.
+
+<Image
+  alt="Surrealist API Docs view"
+  src={{
+    light: OpenInSurrealistLight,
+    dark: OpenInSurrealistDark,
+  }}
+/>
+
+## What can you do? 
+
+When using Surreal Cloud, you can connect to your SurrealDB instance with a few clicks. You can connect to any SurrealDB instance via surrealist, a command-line interface, and any of the supported SDKs. 
+
+
+<div className="flex flex-col items-start justify-between">
+  <div className="w-full">
+    <Tabs groupId="What can you do">
+      <TabItem value="Create an instance" label="Create an instance" default>
+        <div className="flex flex-col md:flex-row items-start justify-between">
+          <div className="flex-1">
+            Surreal Cloud allows you to connect to your SurrealDB instance with just a few clicks. You can create an instance, connect to it, and start building your application.
+
+            <h4>1. Create Instance.</h4>
+
+            When creating an instance, you will enter the instance name and organization to ensure that you can easily identify your instance. Finally, you can select the version of SurrealDB to use and the region to deploy your instance.
+
+            <h4>2. Select a region.</h4>
+
+            Once you have created your instance, you can select the region to deploy your instance. This will allow you to connect to your instance from anywhere in the world.
+
+            <h4>3. Select an Instance preset.</h4>
+
+            Once you have selected a region, you can select an instance preset. This will allow you to select the instance size and type to best suit your needs.
+
+            <h4>4. Finalize and connect to your Instance.</h4>
+
+            Once you have created your instance, you can connect to it from anywhere in the world. You can connect to your instance from anywhere in the world.
+          </div>
+          <div className="flex-1 mt-4 md:mt-0 md:ml-10">
+            <Image
+              alt="Highly Available"
+              src={{
+                light: HighlyAvailable,
+                dark: HighlyAvailableDark,
+              }}  
+            />
+          </div>
+        </div>
+      </TabItem>
+      <TabItem value="Connect to your instance" label="Connect to your instance">
+        <div className="flex flex-col md:flex-row items-start justify-between">
+          <div className="flex-1 text-left">
+            You can connect to any Surreal Cloud Instance via [Surrealist](/docs/cloud/connect/surrealist), a [command-line interface (CLI)](/docs/cloud/connect/cli), and [any of the supported SDKs](/docs/cloud/connect/sdk).
+
+            <h4>[Connect via Surrealist](/docs/cloud/connect/surrealist)</h4>
+
+            Since Surreal Cloud is closely integrated with Surrealist, you can execute queries directly from the interface. This allows you to interact with your data in real-time, without having to switch between different tools.
+
+            <h4>[Connect via CLI](/docs/cloud/connect/cli)</h4>
+
+            If you prefer to use a command-line interface, you can use the SurrealDB CLI to connect to your instance. This connection includes a token that is used to authenticate your connection.
+
+            To do so, select the connect with the CLI option and copy the command.
+
+            <h4>[Connect via SDK](/docs/cloud/connect/sdk)</h4>
+
+            You can also connect to your instance using any of the supported SDKs. In your preferred SDK, use the connect method and pass in your instance endpoint.
+          </div>
+          <div className="flex-1 mt-4 md:mt-0 md:ml-10">
+            <Image
+              alt="Highly Available"
+              src={{
+                light: HighlyAvailable,
+                dark: HighlyAvailableDark,
+              }}  
+            />
+          </div>
+        </div>
+      </TabItem>
+    </Tabs>
+  </div>
+</div>
\ No newline at end of file
diff --git a/src/content/doc-surrealist/getting-started.mdx b/src/content/doc-surrealist/getting-started.mdx
index 1d42b87d1..a496becf4 100644
--- a/src/content/doc-surrealist/getting-started.mdx
+++ b/src/content/doc-surrealist/getting-started.mdx
@@ -33,8 +33,7 @@ When you select an active connection in Surrealist, you will connect to the data
 
 After opening a connection, you can switch to another connection at any time by pressing the connection name in the top left of the interface. This will open the connection list allowing you to switch to another connection, or create a new one.
 
-Within the connection list you will also find a special connection called <span style={{ color: 'var(--ifm-font-color-base)' }}>Sandbox</span>, which is always available and allows you to test and experiment without storing data persistently.
-This connection is useful for learning SurrealQL, testing queries, and more.
+Within the connection list you will also find a special connection called <span style={{ color: 'var(--ifm-font-color-base)' }}>Sandbox</span>, which is always available and allows you to test and experiment without storing data persistently. This connection is useful for learning SurrealQL, testing queries, and more. As the Sandbox connection runs inside a single thread within the browser's WebAssembly engine, it should not be used to estimate or evaluate performance.
 
 ## Creating a connection
 
@@ -74,8 +73,7 @@ dialog you can also find an option to change the appearance of the navigation si
 
 ## Using the Sandbox
 
-As mentioned earlier, the sandbox environment is a special connection that allows you to test and learn SurrealQL. When active, the toolbar will provide
-some additional buttons useful for working with the sandbox environment.
+As mentioned earlier, the sandbox environment is a special connection that allows you to test and learn SurrealQL. When active, the toolbar will provide some additional buttons useful for working with the sandbox environment.
 
 - **Reset sandbox**: This button will clear any records and schema you have configured in the sandbox. Use this button to start fresh or clear your sandbox environment.
 - **Load demo dataset**: This button will load an official demo dataset into the sandbox environment. This dataset contains a set of records and relations that you can explore and query.
diff --git a/src/content/doc-surrealist/installation.mdx b/src/content/doc-surrealist/installation.mdx
index 9ed8264b8..d7856a5ac 100644
--- a/src/content/doc-surrealist/installation.mdx
+++ b/src/content/doc-surrealist/installation.mdx
@@ -27,7 +27,7 @@ This web app contains most of the features available in the desktop app, but wit
 The Surrealist Desktop app is the recommended way to use Surrealist, as it offers more features and flexibility compared to the web app. Some advantages of the desktop app include the ability to connect to insecure endpoints,
 directly opening `.surql` files from your file system, and more.
 
-<a href="https://surrealdb.com/surrealist?download" style={{ marginTop: '20px', display: 'block' }}>
+<a href="/surrealist?download" style={{ marginTop: '20px', display: 'block' }}>
       <button class="bg-transparent cursor-pointer text-[0.8125rem] mt-5 px-3 py-[0.45rem] rounded-2xl border-2 border-solid border-[#ff00A00] hover:border-[$hover-color] hover:text-[$hover-color];" style={{ fontSize: '1rem', marginTop: 0 }}>Download Surrealist Desktop</button>
 </a>
 
diff --git a/src/content/doc-surrealist/troubleshooting.mdx b/src/content/doc-surrealist/troubleshooting.mdx
index 99b6d542a..0d1e71ff0 100644
--- a/src/content/doc-surrealist/troubleshooting.mdx
+++ b/src/content/doc-surrealist/troubleshooting.mdx
@@ -15,11 +15,13 @@ If you are still running into issues you can attempt one of the following:
 
 The developer console may include hints to the cause of your problem. Include any errors you find inside with reported GitHub issues as it may significantly help the maintainers understand your problem.
 
-You can open the developer tools using the following key combination
+You can open the developer tools panel using the following key combination
 
 - **Windows / Linux:** `Ctrl + Shift + i`
 - **MacOS:** `Command + Option + i`
 
+Once the developer tools are open, navigate to the console tab to view any errors or warnings. These may help you diagnose any issues.
+
 ### Backing up / resetting the configuration file
 
 Removing your configuration file may solve issues, however you will lose configured connections and other settings. It is recommended to backup the config file before deleting it.
diff --git a/src/content/doc-surrealql/datamodel/idioms.mdx b/src/content/doc-surrealql/datamodel/idioms.mdx
index d2ebb375a..7608789c5 100644
--- a/src/content/doc-surrealql/datamodel/idioms.mdx
+++ b/src/content/doc-surrealql/datamodel/idioms.mdx
@@ -133,8 +133,8 @@ SELECT results[0].score FROM student;
 ```surql title="Response"
 [
   {
-    "results": [
-      { "score": 76 }
+    results: [
+      { score: 76 }
     ]
   }
 ]
@@ -144,10 +144,10 @@ Here, `results[0].score` accesses the score of the first student in the `results
 
 ### All Elements
 
-To access all elements in an array or all fields in an object, use `[*]` or `.*`. This is useful when you want to access all the elements in an array or all the fields in an object. 
+To access all elements in an array or all fields in an object, use `.*`. This is useful when you want to access all the elements in an array or all the fields in an object. 
 
-```surql
-SELECT results[*].score FROM student;
+```surql 
+SELECT results.* FROM student;
 ```
 
 ```surql title="Response"
@@ -167,6 +167,28 @@ SELECT results[*].score FROM student;
 
 This idiom selects all elements in the `score` array.
 
+The operator `[*]` can also be used as an alias of `.*`, and is often seen in definitions and error messages.
+
+```surql
+DEFINE FIELD friends ON TABLE person TYPE array<record<person>>;
+INFO FOR TABLE person;
+```
+
+The output for `INFO FOR TABLE person` includes an automatically generated definition for `friends[*]`, namely every item inside the `friends` field.
+
+```surql
+{
+	events: {},
+	fields: {
+		friends: 'DEFINE FIELD friends ON person TYPE array<record<person>> PERMISSIONS FULL',
+		"friends[*]": 'DEFINE FIELD friends[*] ON person TYPE record<person> PERMISSIONS FULL'
+	},
+	indexes: {},
+	lives: {},
+	tables: {}
+}
+```
+
 #### Using `.*` to return values
 
 <Since v="v2.1.0" />
@@ -429,8 +451,8 @@ Explanation:
 
 - `*`: Selects all fields of `explorer:drake`.
 - `->? AS actions`: Retrieves all outgoing relationships from Drake and aliases them as actions.
-- `<-? AS interactions`: Retrieves all incoming relationships to Drake and aliases them as interactions.
-- `<->? AS connections`: Retrieves all relationships connected to Drake, regardless of direction, and aliases them as connections.
+- `<-? AS was`: Retrieves all incoming relationships to Drake and aliases them as was.
+- `<->? AS involved_in`: Retrieves all relationships connected to Drake, regardless of direction, and aliases them as involved_in.
 
 
 ### Destructuring
@@ -963,9 +985,9 @@ SELECT @.{1..3}(->has->(?)) AS cities FROM planet;
 SELECT name.len()           AS length FROM planet;
 ```
 
-#### Using `@` and `{}` to combine results
+#### Using `{}` and `.@` to combine results
 
-The `@` symbol can also be used to refer to the current record when setting the structure of a recursive graph query. This allows not just the fields on the final depth of the query to be returned, but each one along the way as well.
+Inside the structure of a recursive graph query, the `@` symbol is used in the form of `.@` at the end of a path to inform the database that this is the path to be repeated during the recursion. This allows not just the fields on the final depth of the query to be returned, but each one along the way as well.
 
 ```surql
 planet:earth
@@ -1003,11 +1025,68 @@ planet:earth
 }
 ```
 
-Using `.@` in this way will return the fields for a depth of up to three levels.
+The following two rules of thumb are a good way to understand how the syntax inside the structure of the query.
+
+* The individual fields inside a recursive query are simply populated at each point,
+* The field with `.@` is used as the gateway to the next depth.
+
+To see this visually, here is the unfolded output of the query above. The `name` and `id` fields appear at each point, while `contains` is used to move on to the next depth.
+
+```surql
+-- Original query
+planet:earth.{1..2}.{ name, id, contains: ->has->(?).@ };
+
+-- Unfolds to:
+planet:earth
+	.{
+		name, 
+		id,
+		contains: ->has->(?).{
+		  name, 
+		  id,
+		  contains: ->has->(?)
+	    }
+	};
+```
+
+Similarly, only one `.@` can be present inside such a query, as this is the path that is used to follow the recursive query until the end.
+
+```surql
+planet:earth
+	.{1..2}
+	.{
+		name, 
+		id,
+-- Query with ->has->(?) on the current record
+		contains: ->has->(?).@,
+        contains2: ->has->(?).@
+	};
+```
+
+```surql
+'Tried to use a `@` repeat recurse symbol in a position where it is not supported'
+```
 
 Here are some more simple examples of recursive queries and notes on the output they generate.
 
 ```surql
+INSERT INTO person [
+	{ id: person:tobie, name: 'Tobie', friends: [person:jaime, person:micha] },
+	{ id: person:jaime, name: 'Jaime', friends: [person:mary] },
+	{ id: person:micha, name: 'Micha', friends: [person:john] },
+	{ id: person:john, name: 'John' },
+	{ id: person:mary, name: 'Mary' },
+	{ id: person:tim, name: 'Tim' },
+];
+
+INSERT RELATION INTO knows [
+	{ id: knows:1, in: person:tobie, out: person:jaime },
+	{ id: knows:2, in: person:tobie, out: person:micha },
+	{ id: knows:3, in: person:micha, out: person:john },
+	{ id: knows:4, in: person:jaime, out: person:mary },
+	{ id: knows:5, in: person:mary, out: person:tim },
+];
+
 -- Any depth
 person:tobie.{..}(->knows->person).name;
 
@@ -1042,6 +1121,51 @@ Recursive queries follow a few rules to determine how far to traverse and what t
 * If it has already passed the minimum depth, it returns the last valid value.
 * During each iteration, if it encounters an array value, all dead end values are automatically filtered out, ensuring no empty paths are included.
 
+#### Filtering recursive fields
+
+Recursive syntax is not just useful in creating recursive queries, but parsing them as well. Take the following example that creates some `person` records, gives each of them two friends, and then traverses the `friends_with` graph for the first `person` records to find its friends, friends of friends, and friends of friends of friends. Since every level except the last contains another `connections` field, adding a `.{some_number}.connections` to a `RETURN` statement is all that is needed to drill down to a certain depth.
+
+```surql
+CREATE |person:1..20| SET name = id.id() RETURN NONE;
+FOR $person IN SELECT * FROM person {
+    LET $friends = (SELECT * FROM person WHERE id != $person.id ORDER BY rand() LIMIT 2);
+    RELATE $person->friends_with->$friends;
+};
+
+LET $third_degree = person:1.{..3}.{ id, connections: ->friends_with->person.@ };
+// Object containing array of arrays of arrays of 'person'
+RETURN $third_degree;
+// All connections: an array of arrays of arrays of 'person'
+RETURN $third_degree.connections;
+// Secondary connections: an array of arrays of 'person'
+RETURN $third_degree.{2}.connections;
+// Tertiary connections: an array of 'person'
+RETURN $third_degree.{3}.connections;
+// Tertiary connections with aliased fields and original 'person' info
+RETURN $third_degree.{
+		original_person: id, 
+		third_degree_friends: connections.{2}.connections
+};
+```
+
+Possible output of the final query:
+
+```surql title="Output for third_degree_friends query"
+{
+	original_person: person:1,
+	third_degree_friends: [
+		person:13,
+		person:3,
+		person:14,
+		person:10,
+		person:8,
+		person:3,
+		person:3,
+		person:14
+	]
+}
+```
+
 ## Combining Idiom Parts
 
 Idioms can combine multiple parts to navigate complex data structures seamlessly.
diff --git a/src/content/doc-surrealql/datamodel/ids.mdx b/src/content/doc-surrealql/datamodel/ids.mdx
index 41fe1c785..d9bcef4d1 100644
--- a/src/content/doc-surrealql/datamodel/ids.mdx
+++ b/src/content/doc-surrealql/datamodel/ids.mdx
@@ -18,7 +18,7 @@ An example of a record ID can look like this: `table:record_identifier`.
 
 ## Types of Record IDs
 
-Record IDs can be constructed using a number of different types of values, including text, numbers, objects, and arrays. For example, by default when you [create a table](/docs/surrealql/statements/create), `create internet`, a random id is assigned. This differs from the traditional default of auto-increment or serial IDs you might be used to.
+Record IDs can be constructed using a number of different types of values, including text, numbers, objects, and arrays. For example, by default when you [create a table](/docs/surrealql/statements/create), `create internet`, a random id is assigned. This differs from the traditional default of auto-increment or serial IDs many developers are used to.
 
 
 > [!NOTE]
@@ -86,13 +86,18 @@ CREATE temperature:['London', $now] SET
 ```
 
 ### Generating Record IDs
+
 Record IDs can be generated with a number of built-in ID generation functions. These allow for record IDs to be generated using cryptographically-secure randomly-generated identifiers (which are suitable for dispersion across a distributed datastore), sequentially incrementing `ULID` Record identifiers, and `UUID` version 7 Record idenfitifiers.
 
 ```surql
 // Generate a random record ID
 // Charset: `abcdefghijklmnopqrstuvwxyz0123456789`
 // ID Length: 20 characters long
+CREATE temperature SET time = time::now(), celsius = 37.5;
+// :rand() is the default random ID format, so this
+// is identical to the above CREATE statement
 CREATE temperature:rand() SET time = time::now(), celsius = 37.5;
+
 // Generate a ULID-based record ID
 CREATE temperature:ulid() SET time = time::now(), celsius = 37.5;
 // Generate a UUIDv7-based record ID
@@ -209,6 +214,46 @@ FROM { temps: [-5, 8, 9] };
 ]
 ```
 
+### Auto-incrementing IDs
+
+While SurrealDB does not use auto-incrementing IDs by default, this behaviour can be achieved in a number of ways. One is to use the [`record::id()`](/docs/surrealql/functions/database/record#recordid) function on the latest record, which returns the latter part of a record ID (the '1' in the record ID `person:1`). This can then be followed up with the [`type::thing()`](/docs/surrealql/functions/database/type#typething) function to create a new record ID.
+
+```surql
+-- Create records from person:1 to person:10
+CREATE |person:1..10|;
+LET $latest = SELECT VALUE id FROM ONLY person ORDER BY id DESC LIMIT 1;
+CREATE type::thing("person", $latest.id() + 1);
+```
+
+```surql title="Output"
+[
+	{
+		id: person:11
+	}
+]
+```
+
+When dealing with a large number of records, a more performant option is to use a separate record that holds a single value representing the latest ID. An [`UPSERT`](/docs/surrealql/statements/upsert) statement is best here, which will allow the counter to be initialized if it does not yet exist, and updated otherwise. This is best done [inside a manual transaction](/docs/surrealql/statements/begin) so that the latest ID will be rolled back if any failures occur when creating the next record.
+
+```surql
+BEGIN TRANSACTION;
+UPSERT person_id:counter SET num += 1;
+-- Creates a person:1
+CREATE type::thing("person", person_id:counter.num);
+COMMIT TRANSACTION;
+
+BEGIN TRANSACTION;
+-- Latest ID is now 2
+UPSERT person_id:counter SET num += 1;
+-- Whoops, invalid datetime format
+-- Transaction fails and all changes are rolled back
+CREATE type::thing("person", person_id:counter.num) SET created_at = <datetime>'2025_01+01';
+COMMIT TRANSACTION;
+
+-- Latest ID is still 1
+RETURN person_id:counter.num;
+```
+
 ## Learn more 
 
-Learn more about Record IDs [in this blogpost](https://surrealdb.com/blog/the-life-changing-magic-of-surrealdb-record-ids#the-performance-at-scale) and on this [youtube video](https://www.youtube.com/watch?v=c0cqmWRYP8c).
+Learn more about Record IDs [in this blogpost](/blog/the-life-changing-magic-of-surrealdb-record-ids#the-performance-at-scale) and on this [youtube video](https://www.youtube.com/watch?v=c0cqmWRYP8c).
diff --git a/src/content/doc-surrealql/functions/database/array.mdx b/src/content/doc-surrealql/functions/database/array.mdx
index 792d41cb5..f207ca8db 100644
--- a/src/content/doc-surrealql/functions/database/array.mdx
+++ b/src/content/doc-surrealql/functions/database/array.mdx
@@ -830,7 +830,7 @@ RETURN array::flatten([ [1, 2], [3, 4], 'SurrealDB', [5, 6, [7, 8]] ]);
 
 <Since v="v2.1.0" />
 
-The `array::fold` function applies an operation on an initial value plus every element in the array, returning the final result. To use `array::fold`, pass in an initial value, followed by parameter names for the current value and the next value and an operation to perform on them. If you only want to perform an operation on each item and do not need an initial value, use the [`array::reduce`](/docs/surrealql/functions/database/array#arrayreduce) function.
+The `array::fold` function returns a final value from the elements of an array by allowing an operation to be performed at each step of the way as each subsequent item in the array is encountered. To use `array::fold`, pass in an initial value, followed by parameter names for the current value and the next value and an operation to perform on them. If you only want to perform an operation on each item and do not need an initial value, use the [`array::reduce`](/docs/surrealql/functions/database/array#arrayreduce) function instead.
 
 ```surql title="API DEFINITION"
 array::fold(array, initial_value, @closure) -> value
@@ -886,6 +886,20 @@ As the output above shows, it is often nice to know which item of the array one
 "I_don't_like_whitespace"
 ```
 
+The `array::fold()` function can be used to generate an array of values that can then be passed on to statements like [`INSERT`](/docs/surrealql/statements/insert) for bulk insertion.
+
+```surql
+INSERT INTO person (
+  -- Create 1000 objects with a random ULID and incrementing number
+    (<array>0..1000).fold([], |$v, $_, $i| {
+    $v.append( { 
+      id: rand::ulid(),
+      person_num: $i
+      });
+    })
+);
+```
+
 This function is also useful for aggregating the results of graph queries. The following shows a graph table called `to` that holds the distance from one city to another. The `array::fold()` function can then be used to pass an object along that tracks the first and last city, while accumulating the distance and number of trips along the way.
 
 ```surql
@@ -1253,6 +1267,13 @@ The `array::map` function also allows access to the index of each item if a seco
 ]
 ```
 
+The `array::map()` function can be used to generate an array of values that can then be passed on to statements like [`INSERT`](/docs/surrealql/statements/insert) for bulk insertion.
+
+```surql
+-- Create 1000 objects with a random ULID
+INSERT INTO person ((<array>0..=1000).map(|| {id: rand::ulid()}));
+```
+
 For a similar function that allows using a closure on entire values instead of each item in an array, see the [chain](/docs/surrealql/functions/database/value#chain) method.
 
 ## `array::max`
@@ -1399,7 +1420,7 @@ RETURN array::range(3, 2);
 
 <Since v="v2.1.0" />
 
-The `array::reduce` function applies an operation on every element in the array, returning the final result. To use `array::reduce`, pass in parameter names for the current value and the next value and an operation to perform on them. If you want to have an initial value to pass in before the other items are operated on, use the [`array::fold`](/docs/surrealql/functions/database/array#arrayfold) function.
+The `array::reduce` function reduces the elements of an array to a single final value by allowing an operation to be performed at each step of the way as each subsequent item in the array is encountered. To use `array::reduce`, pass in parameter names for the current value and the next value and an operation to perform on them. If you need an initial value to pass in before the other items are operated on, use the [`array::fold`](/docs/surrealql/functions/database/array#arrayfold) function instead.
 
 ```surql title="API DEFINITION"
 array::reduce(array, @closure) -> value
diff --git a/src/content/doc-surrealql/functions/database/geo.mdx b/src/content/doc-surrealql/functions/database/geo.mdx
index cf3b44eec..b5f0af301 100644
--- a/src/content/doc-surrealql/functions/database/geo.mdx
+++ b/src/content/doc-surrealql/functions/database/geo.mdx
@@ -313,7 +313,7 @@ each `Point` coordinates are in the range of -180° to 180° for longitude and -
 ```surql title="API DEFINITION"
 geo::is::valid(geometry) -> bool
 ```
-The following examples show this function, and its output, when used in a [`RETURN`](/docs/surrealdb/surrealql/statements/return) statement:
+The following examples show this function, and its output, when used in a [`RETURN`](/docs/surrealql/statements/return) statement:
 
 ```surql title="A valid geography point"
 RETURN geo::is::valid( (51.509865, -0.118092) );
diff --git a/src/content/doc-surrealql/functions/database/index.mdx b/src/content/doc-surrealql/functions/database/index.mdx
index 0038b4efe..a89f4de5f 100644
--- a/src/content/doc-surrealql/functions/database/index.mdx
+++ b/src/content/doc-surrealql/functions/database/index.mdx
@@ -49,7 +49,7 @@ SurrealDB has many built-in functions designed to handle many common database ta
     </tr>
     <tr>
       <td scope="row" data-label="Function"><a href="/docs/surrealql/functions/database/http"><code>HTTP</code></a></td>
-      <td scope="row" data-label="Description and Example">These functions can be used when opening and submitting remote web requests, and webhooks.<br/>Example: <code>http::get('https://surrealdb.com')</code></td>
+      <td scope="row" data-label="Description and Example">These functions can be used when opening and submitting remote web requests, and webhooks.<br/>Example: `http::get('https://surrealdb.com')`</td>
     </tr>
     <tr>
       <td scope="row" data-label="Function"><a href="/docs/surrealql/functions/database/math"><code>Math</code></a></td>
diff --git a/src/content/doc-surrealql/functions/database/meta.mdx b/src/content/doc-surrealql/functions/database/meta.mdx
index d384cae2f..7746e7545 100644
--- a/src/content/doc-surrealql/functions/database/meta.mdx
+++ b/src/content/doc-surrealql/functions/database/meta.mdx
@@ -9,7 +9,7 @@ import Since from '@components/shared/Since.astro'
 
 # Meta functions
 
-> [!WARNING]
+> [!NOTE]
 > As of version 2.0, these functions are now part of SurrealDB's [record](/docs/surrealql/functions/database/record) functions.
 
 
diff --git a/src/content/doc-surrealql/functions/database/record.mdx b/src/content/doc-surrealql/functions/database/record.mdx
index b9fb4bda6..469156c87 100644
--- a/src/content/doc-surrealql/functions/database/record.mdx
+++ b/src/content/doc-surrealql/functions/database/record.mdx
@@ -9,10 +9,8 @@ import Since from '@components/shared/Since.astro'
 
 # Record functions
 
-Record functions before SurrealDB 2.0 were located inside the module [meta](/docs/surrealql/functions/database/meta).
-
-> [!WARNING]
-> This function was known as `record::exists` in versions of SurrrealDB before 2.0. The behaviour has not changed.
+> [!NOTE]
+> Record functions before SurrealDB 2.0 were located inside the module [meta](/docs/surrealql/functions/database/meta). Their behaviour has not changed.
 
 These functions can be used to retrieve specific metadata from a SurrealDB Record ID.
 
diff --git a/src/content/doc-surrealql/functions/database/type.mdx b/src/content/doc-surrealql/functions/database/type.mdx
index 14c3b27ae..e6a90f000 100644
--- a/src/content/doc-surrealql/functions/database/type.mdx
+++ b/src/content/doc-surrealql/functions/database/type.mdx
@@ -600,6 +600,7 @@ The `type::thing` function converts a value into a record pointer definition.
 ```surql title="API DEFINITION"
 type::thing(any, any) -> record
 ```
+
 The following example shows this function, and its output, when used in a [`RETURN`](/docs/surrealql/statements/return) statement:
 
 ```surql
@@ -607,7 +608,43 @@ LET $tb = "person";
 LET $id = "tobie";
 RETURN type::thing($tb, $id);
 ```
-<br />
+
+An example of this function being used to turn an array of objects into records to be created or upserted:
+
+```surql
+FOR $data IN [
+	{
+		id: 9,
+		name: 'Billy'
+	},
+	{
+		id: 10,
+		name: 'Bobby'
+	}
+] {
+	UPSERT type::thing('person', $data.id) CONTENT $data;
+};
+```
+
+An example of the same except in which the `num` field is to be used as the record's ID. In this case, it can be mapped with the [`array::map()`](/docs/surrealql/functions/database/array#arraymap) function to rename `num` as `id` so that the following `CONTENT` clause does not create both a `num` and an `id` with the same value.
+
+```surql
+FOR $data IN [
+	{
+		name: 'Billy',
+		num: 9
+	},
+    {
+		name: 'Bobby',
+		num: 10
+	},
+].map(|$o| {
+    id: $o.num,
+    name: $o.name
+}) {
+    UPSERT type::thing('person', $data.id) CONTENT $data;
+};
+```
 
 ## `type::uuid`
 
diff --git a/src/content/doc-surrealql/statements/create.mdx b/src/content/doc-surrealql/statements/create.mdx
index e07ecbe96..fd22e104f 100644
--- a/src/content/doc-surrealql/statements/create.mdx
+++ b/src/content/doc-surrealql/statements/create.mdx
@@ -21,7 +21,7 @@ CREATE [ ONLY ] @targets
 	[ CONTENT @value
 	  | SET @field = @value ...
 	]
-	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... ]
+	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... | RETURN VALUE @statement_param ]
 	[ TIMEOUT @duration ]
 	[ PARALLEL ]
 ;
@@ -317,7 +317,7 @@ CREATE person SET age = 46, username = "john-smith" RETURN BEFORE;
 CREATE person SET age = 46, username = "john-smith" RETURN AFTER;
 ```
 
-You can also return specific fields from a created record, as well as ad-hoc fields to modify the output as needed.
+You can also return specific fields from a created record, the value of a single field using `VALUE`, as well as ad-hoc fields to modify the output as needed.
 
 ```surql
 CREATE person
@@ -328,9 +328,15 @@ RETURN
     age,
     interests,
     age + 1 AS age_next_year;
+
+CREATE |person:5|
+    SET age = 20
+RETURN VALUE age;
 ```
 
 ```surql title="Response"
+-------- Query --------
+
 [
 	{
 		age: 46,
@@ -341,6 +347,16 @@ RETURN
 		]
 	}
 ]
+
+-------- Query --------
+
+[
+	20,
+	20,
+	20,
+	20,
+	20
+]
 ```
 
 ### Timeout
diff --git a/src/content/doc-surrealql/statements/define/access/jwt.mdx b/src/content/doc-surrealql/statements/define/access/jwt.mdx
index 8fffc6143..5e619b399 100644
--- a/src/content/doc-surrealql/statements/define/access/jwt.mdx
+++ b/src/content/doc-surrealql/statements/define/access/jwt.mdx
@@ -100,7 +100,7 @@ iCTjhbIDEBHySSSc/pQ4ftHQmhToTlQeOdEy4LYiaEIgl1X+hzRH1hBYvWlNKe4EY1nMCKcjgt0=
 With JWKS, a set of JWK (JSON Web Key) objects will be dynamically fetched from a remote location and used to verify tokens following the [RFC 7517](https://datatracker.ietf.org/doc/html/rfc7517) specification. When defining a JWKS token verification method, its value should contain a valid URL that is reachable by SurrealDB and allowed by the configured network [capabilities](/docs/surrealdb/security/capabilities). This URL should point to a valid JWKS object (as described in [Section 5 of RFC 7517](https://datatracker.ietf.org/doc/html/rfc7517#section-5)) in the form of a JSON document. This is the recommended method to integrate with authentication providers that support JWKS. Providers like [Google](https://developers.google.com/identity/openid-connect/openid-connect#discovery), [AWS Cognito](https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-user-pools-using-tokens-verifying-a-jwt.html#amazon-cognito-user-pools-using-tokens-manually-inspect), [Azure Active Directory](https://azure.github.io/azure-workload-identity/docs/installation/self-managed-clusters/oidc-issuer/jwks.html), [Auth0](https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets), [Keycloak](https://documentation.cloud-iam.com/how-to-guides/configure-remote-jkws.html) or [OneLogin](https://developers.onelogin.com/authentication/tools/jwt) provide JWKS endpoints to verify tokens issued by their services.
 
 > [!NOTE: Before you start]
-> As the JWKS functionality requires establishing a network connection in order to download the JWKS object, you will require running the SurrealDB server with the network <a href="/docs/security/capabilities">capability</a>. For the strongest security, provide the specific hostname hosting the JWKS object when starting SurrealDB with <code>--allow-net</code>. For example: <code>--allow-net example.com</code>.
+> As the JWKS functionality requires establishing a network connection in order to download the JWKS object, you will require running the SurrealDB server with the network <a href="/docs/surrealdb/security/capabilities">capability</a>. For the strongest security, provide the specific hostname hosting the JWKS object when starting SurrealDB with <code>--allow-net</code>. For example: <code>--allow-net example.com</code>.
 
 
 The following example shows the definition of a token using a JWKS.
diff --git a/src/content/doc-surrealql/statements/define/event.mdx b/src/content/doc-surrealql/statements/define/event.mdx
index 00e1716e5..6afe52ce7 100644
--- a/src/content/doc-surrealql/statements/define/event.mdx
+++ b/src/content/doc-surrealql/statements/define/event.mdx
@@ -17,7 +17,9 @@ Events allow you to define custom logic that is executed when a record is create
 ### Key Concepts
 
 - **Events**: Triggered after changes (create, update, delete) to records in a table.
+* **$event**: A preset parameter containing the type of event as a string, will always be one of "CREATE", "UPDATE", or "DELETE".
 - **$before / $after**: Refer to the record state before and after the modification. Learn more about the `$before` and `$after` parameters in the [parameters documentation](/docs/surrealql/parameters#before-after).
+- **$value**: The record in question. For a `CREATE` or `UPDATE` event, this will be the record after the changes were made. For a `DELETE` statement, this will be the record before it was deleted.
 - **WHEN condition**: Determines when the event should be triggered.
 
 ## Requirements
@@ -31,7 +33,7 @@ Events allow you to define custom logic that is executed when a record is create
 DEFINE EVENT [ OVERWRITE | IF NOT EXISTS ] @name ON [ TABLE ] @table [ WHEN @expression ] THEN @expression [ COMMENT @string ]
 ```
 
-### Parameters:
+### Clauses:
 
 - **OVERWRITE**: Replaces the existing event if it already exists.
 - **IF NOT EXISTS**: Only creates the event if it doesn't already exist.
@@ -39,25 +41,61 @@ DEFINE EVENT [ OVERWRITE | IF NOT EXISTS ] @name ON [ TABLE ] @table [ WHEN @exp
 - **THEN**: Specifies the action(s) to execute when the event is triggered.
 - **COMMENT**: Optional comment for describing the event.
 
-
 ## Example usage
 
 -  **Email Change Detection**: Create an event that logs whenever a user's email is updated.
 
+In this example:
+- The `WHEN` clause checks if the email has changed.
+- The `THEN` clause records this change in a `log` table.
+
 ```surql
 -- Create a new event whenever a user changes their email address
 -- One-statement event
-DEFINE EVENT test ON TABLE user WHEN $before.email != $after.email THEN (
-        CREATE log SET user = $this, action = 'email_changed', old_email = $before.email, new_email = $after.email
-    );
-    UPSERT user:test SET email = 'old_email@test.com';
-    UPSERT user:test SET email = 'new_email@test.com';
-    SELECT count() FROM log WHERE action = 'email_changed';
+DEFINE EVENT OVERWRITE test ON TABLE user WHEN $before.email != $after.email THEN (
+    CREATE log SET 
+        user       = $value.id,
+        // Turn events like "CREATE" into string "email created"
+        action     = 'email' + ' ' + $event.lowercase() + 'd',
+        // `email` field may be NONE, log as '' if so
+        old_email  = $before.email ?? '',
+        new_email  = $after.email  ?? '',
+        at         = time::now()
+);
+UPSERT user:test SET email = 'old_email@test.com';
+UPSERT user:test SET email = 'new_email@test.com';
+DELETE user:test;
+SELECT * FROM log ORDER BY at ASC;
 ```
 
-In this example:
-- The `WHEN` clause checks if the email has changed.
-- The `THEN` clause records this change in a `log` table.
+```surql title="Output"
+[
+	{
+		action: 'email created',
+		at: d'2024-11-25T02:59:41.003Z',
+		id: log:e3thw1l0q7xiapznar1f,
+		new_email: 'old_email@test.com',
+		old_email: '',
+		user: user:test
+	},
+	{
+		action: 'email updated',
+		at: d'2024-11-25T02:59:41.003Z',
+		id: log:uaarfyk191jgod06xobm,
+		new_email: 'new_email@test.com',
+		old_email: 'old_email@test.com',
+		user: user:test
+	},
+	{
+		action: 'email deleted',
+		at: d'2024-11-25T02:59:41.003Z',
+		id: log:mlkag8h1xotglpz9wt2i,
+		new_email: '',
+		old_email: 'new_email@test.com',
+		user: user:test
+	}
+]
+```
 
 ### More Complex Logic:
 
diff --git a/src/content/doc-surrealql/statements/define/table.mdx b/src/content/doc-surrealql/statements/define/table.mdx
index bf01521ee..c5ea5b23b 100644
--- a/src/content/doc-surrealql/statements/define/table.mdx
+++ b/src/content/doc-surrealql/statements/define/table.mdx
@@ -8,7 +8,10 @@ import Since from '@components/shared/Since.astro'
 
 # `DEFINE TABLE` statement
 
-The `DEFINE TABLE` statement allows you to declare your table by name, enabling you to apply strict controls to a table's schema by making it `SCHEMAFULL`, create a foreign table view, and set permissions specifying what operations can be performed on the field.
+The `DEFINE TABLE` statement allows you to declare your table by name, enabling you to apply strict controls to a table's schema by making it `SCHEMAFULL`, create a foreign table view, and set permissions specifying what operations can be performed on the table.
+
+> [!NOTE]
+> The fields of a table are not defined using `DEFINE TABLE`, but via individual [`DEFINE FIELD`](/docs/surrealql/statements/define/field) statements.
 
 ## Requirements
 
@@ -38,6 +41,7 @@ DEFINE TABLE [ OVERWRITE | IF NOT EXISTS ] @name
 ```
 
 ## Example usage
+
 Below shows how you can create a table using the `DEFINE TABLE` statement.
 
 ```surql
@@ -371,7 +375,6 @@ With `TYPE NORMAL`, you can specify a table to only store "normal" records, and
 ```surql
 -- Since it's default, we can also omit the TYPE clause
 DEFINE TABLE person TYPE NORMAL;
-
 ```
 
 With `TYPE RELATION`, you can specify a table to only store relational type content, and restrict what kind of relations can be stored.
@@ -387,7 +390,6 @@ DEFINE TABLE likes TYPE RELATION IN user OUT post;
 -- To allow a link to one of a possible set of record types, use the | operator
 DEFINE TABLE likes TYPE RELATION FROM user TO post|video;
 DEFINE TABLE likes TYPE RELATION IN user OUT post|video;
-
 ```
 
 ```surql
diff --git a/src/content/doc-surrealql/statements/info.mdx b/src/content/doc-surrealql/statements/info.mdx
index acb377d24..259c5d2e2 100644
--- a/src/content/doc-surrealql/statements/info.mdx
+++ b/src/content/doc-surrealql/statements/info.mdx
@@ -22,6 +22,9 @@ INFO FOR [
 
 The information returned from an `INFO` command is an object containing items that almost always correspond to a matching [DEFINE](/docs/surrealql/statements/define) statement. For example, the `INFO FOR NS` command returns the information on the access methods, databases and users of a namespace, which are defined with `DEFINE ACCESS`, `DEFINE DATABASE` and `DEFINE USER` statements.
 
+> [!NOTE]
+> The output of an `INFO FOR` command currently can only be used on its own and not in a dynamic context, such as inside other queries or as the value of a parameter.
+
 ## Example usage
 
 There are a number of different `INFO` commands for retrieving the configuration at the different levels of the database.
diff --git a/src/content/doc-surrealql/statements/insert.mdx b/src/content/doc-surrealql/statements/insert.mdx
index 892d77329..6a8d54767 100644
--- a/src/content/doc-surrealql/statements/insert.mdx
+++ b/src/content/doc-surrealql/statements/insert.mdx
@@ -18,7 +18,7 @@ INSERT [ IGNORE | RELATION ] INTO @what
 	  | (@fields) VALUES (@values)
 		[ ON DUPLICATE KEY UPDATE @field = @value ... ]
 	]
-	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... ]
+	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... | RETURN VALUE @statement_param ]
 ;
 ```
 
@@ -157,7 +157,7 @@ INSERT INTO company {
 } RETURN AFTER;
 ```
 
-You can also return specific fields from a created record, as well as ad-hoc fields to modify the output as needed.
+You can also return specific fields from a created record, the value of a single field using `VALUE`, as well as ad-hoc fields to modify the output as needed.
 
 ```surql
 INSERT INTO person {
@@ -168,9 +168,24 @@ RETURN
     age,
     interests,
     age + 1 AS age_next_year;
+
+INSERT INTO planet [
+	{
+		name: 'Venus',
+        surface_temp: 462,
+        temp_55_km_up: 27
+	},
+	{
+		name: 'Earth',
+        surface_temp: 15,
+        temp_55_km_up: -55
+	}
+] RETURN VALUE temp_55_km_up;
 ```
 
 ```surql title="Response"
+-------- Query --------
+
 [
 	{
 		age: 46,
@@ -181,6 +196,13 @@ RETURN
 		]
 	}
 ]
+
+-------- Query --------
+
+[
+	27,
+	-55
+]
 ```
 
 ## Bulk insert
diff --git a/src/content/doc-surrealql/statements/relate.mdx b/src/content/doc-surrealql/statements/relate.mdx
index bc8a784b5..43263ac4b 100644
--- a/src/content/doc-surrealql/statements/relate.mdx
+++ b/src/content/doc-surrealql/statements/relate.mdx
@@ -8,22 +8,18 @@ import Since from '@components/shared/Since.astro'
 
 # `RELATE` statement
 
-The `RELATE` statement can be used to generate graph edges between two records in the database.
+The `RELATE` statement can be used to generate graph edges between two records in the database. This allows you to traverse related records efficiently without needing to pull data from multiple tables and merging that data together using SQL JOINs.
 
-This allows you to traverse related records efficiently without needing to pull data from multiple tables and merging that data together using SQL JOINs.
-
-Edges created using the RELATE statement are nearly identical to tables created using other statements, and can contain data.
-
-The key differences are that:
+Edges created using the RELATE statement are nearly identical to tables created using other statements, and can contain data. The key differences are that:
 
 - Edge tables are deleted once there are no existing relationships left.
-- Edge tables have two required fields `in` and `out`, which specify the directions of the relationships. These cannot be modified in schema declarations except to specify that they must be of a certain record type or to add assertions.
+- Edge tables have two required fields `in` and `out`, which specify the directions of the relationships. These cannot be modified in schema declarations except to specify that they must be of a certain record type or to [add assertions](/docs/surrealql/statements/define/field#asserting-rules-on-fields).
 
 Otherwise, edge tables behave like normal tables in terms of [updating](/docs/surrealql/statements/update), [defining a schema](/docs/surrealql/statements/define/table) or [indexes](/docs/surrealql/statements/define/indexes).
 
-[Record links](/docs/surrealql/datamodel/records) are the alternative option when connecting data, and simply consist of a field with record IDs that serve as uni-directional links. The key differences are that graph relations
+Another option for connecting data is using [record links](/docs/surrealql/datamodel/records). Record links consist of a field with record IDs that serve as uni-directional links. The key differences are that graph relations have the following benefits over record links:
 
-- Are kept in a separate table as opposed to a field inside a record.
+- They are kept in a separate table as opposed to a field inside a record.
 - Offer bi-directional querying.
 - Offer referential integrity.
 - Allow you to store data alongside the relationship.
@@ -35,41 +31,105 @@ RELATE [ ONLY ] @from_record -> @table -> @to_record
 	[ CONTENT @value
 	  | SET @field = @value ...
 	]
-	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... ]
+	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... | RETURN VALUE @statement_param ]
 	[ TIMEOUT @duration ]
 	[ PARALLEL ]
 ;
 ```
 
 > [!NOTE]
-> `RELATE` will create a relation regardless of whether the records to relate to exist or not. As such, it is advisable to create the records you want to relate to before using `RELATE`, or to at least ensure that they exist before making a query on the relation. You can do this using the [CREATE statement](/docs/surrealql/statements/create). If the records to relate to don't exist, a query on the relation will still work without an error but will return an empty array. To override this default behaviour and return an error if no records exist to relate, you can add the `ENFORCED` keyword to a [`DEFINE TABLE`](/docs/surrealql/statements/define/table) statement.
+> `RELATE` will create a relation regardless of whether the records to relate to exist or not. As such, it is advisable to [create the records](/docs/surrealql/statements/create) you want to relate to before using `RELATE`, or to at least ensure that they exist before making a query on the relation. If the records to relate to don't exist, a query on the relation will still work but will return an empty array. To override this behaviour and return an error if no records exist to relate, you can use a [`DEFINE TABLE`](/docs/surrealql/statements/define/table) statement that includes the `ENFORCED` keyword.
+
+### Example usage
+
+#### Basic usage
+
+The following query shows the basic structure of the `RELATE` statement, which creates a relationship between a record in the `person` table and a record in the `article` table.
+
+```surql
+CREATE person:aristotle, article:on_sleep_and_sleeplessness;
+RELATE person:aristotle->wrote->article:on_sleep_and_sleeplessness;
+```
+
+```surql title="Response"
+[
+	{
+		id: wrote:bpbrj5kd7smu3ahlf55r,
+		in: person:aristotle,
+		out: article:on_sleep_and_sleeplessness
+	}
+]
+```
 
+There is no relationship information stored in either the `person` or `article` table.
 
-## Example usage
+```surql
+SELECT * FROM person, article;
+```
 
-### Basic usage
+```surql title="Response"
+[
+	{
+		id: person:aristotle
+	},
+	{
+		id: article:on_sleep_and_sleeplessness
+	}
+]
+```
 
-The following query shows the basic structure of the `RELATE` statement, which creates a relationship between a record in the person table and a record in the article table.
+Instead, an edge table (in this case a table called `wrote`) stores the relationship information.
 
 ```surql
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm;
+SELECT * FROM wrote;
 ```
 
+The structure `in -> id -> out` mirrors the record IDs from the `RELATE` statement, with the addition of the automatically generated ID for the `wrote` edge table.
+
 ```surql title="Response"
 [
 	{
-		"id": "wrote:ctwsll49k37a7rmqz9rr",
-		"in": "person:l19zjikkw1p1h9o6ixrg",
-		"out": "article:8nkk6uj4yprt49z7y3zm"
+		id: wrote:bpbrj5kd7smu3ahlf55r,
+		in: person:aristotle,
+		out: article:on_sleep_and_sleeplessness
 	}
 ]
 ```
 
-There is no relationship information stored in either the person or article table.
+The same structure can be used in a `SELECT` query, as well as directly from a record ID.
+
+```surql
+-- Aristotle's id and the articles he wrote
+SELECT id, ->wrote->article FROM person:aristotle;
+-- Every `person`'s id and written articles
+-- Same output as above as the database has a single `person` record
+SELECT id, ->wrote->article FROM person;
+-- Directly follow the path from Aristotle to his written articles
+RETURN person:aristotle->wrote->article;
+```
+
+```surql title="Response"
+-------- Query --------
 
-Instead, an edge table (in this case a table called `wrote`) stores the relationship information. The structure `in -> id -> out` mirrors the record IDs from the `RELATE` statement, with the addition of the automatically generated ID for the `wrote` edge table.
+[
+	{
+		"->wrote": {
+			"->article": [
+				article:on_sleep_and_sleeplessness
+			]
+		},
+		id: person:aristotle
+	}
+]
 
-By default, the edge table gets created as a schemaless table when you execute the `RELATE` statement. You can however make the table schemafull by either [defining a schema](/docs/surrealql/statements/define/table) before or after executing the RELATE statement.
+-------- Query --------
+
+[
+	article:on_sleep_and_sleeplessness
+]
+```
+
+By default, the edge table gets created as a schemaless table when you execute the `RELATE` statement. You can make the table schemafull by [defining a schema](/docs/surrealql/statements/define/table).
 
 A common use case is to make sure only unique relationships get created. You can do that by [defining an index](/docs/surrealql/statements/define/indexes).
 
@@ -78,16 +138,23 @@ DEFINE INDEX unique_relationships
     ON TABLE wrote
     COLUMNS in, out UNIQUE;
 ```
-Edge tables are bi-directional by default. To enforce unidirectional relationships, you can restrict the type definition using field definition.
+
+As edge tables are bi-directional by default, there is nothing stopping a query like the following in which an article writes a person instead of the other way around.
+
+```surql
+RELATE article:on_sleep_and_sleeplessness->wrote->person:aristotle;
+```
+
+To enforce unidirectional relationships, you can restrict the type definition using a [`DEFINE FIELD`](/docs/surrealql/statements/define/field) definition.
 
 ```surql
 DEFINE FIELD in  ON TABLE wrote TYPE record<person>;
 DEFINE FIELD out ON TABLE wrote TYPE record<article>;
 ```
 
-### Always two there are - no more, no less
+#### Always two there are - no more, no less
 
-A `RELATE` statement that involves an array instead of a single id will not fail. Instead, it will create a graph edge for each record in the array:
+A `RELATE` statement that involves an array instead of a single id will not fail. Instead, it will create a graph edge for each record in the array.
 
 ```surql
 INSERT INTO cat (id) VALUES ("mr_meow"), ("mrs_meow"), ("kitten");
@@ -96,20 +163,20 @@ RELATE [cat:mr_meow, cat:mrs_meow]->parent_of->cat:kitten;
 
 ```surql title="Response"
 [
-    {
-        "id": "parent_of:7ypx27tgoa9lrsa4s6fm",
-        "in": "cat:mr_meow",
-        "out": "cat:kitten"
-    },
-    {
-        "id": "parent_of:mw08ri5e1jgh78wp1c1p",
-        "in": "cat:mrs_meow",
-        "out": "cat:kitten"
-    }
+	{
+		id: parent_of:uahudi4qr68k640fcjbg,
+		in: cat:mr_meow,
+		out: cat:kitten
+	},
+	{
+		id: parent_of:hi79yfazjppv8b3kyi36,
+		in: cat:mrs_meow,
+		out: cat:kitten
+	}
 ]
 ```
 
-Similarly, a `RELATE` statement that involves two arrays will return a number of graph edges equal to their product (in this case 2 * 2):
+Similarly, a `RELATE` statement that involves two arrays will return a number of graph edges equal to their product (2 * 2 in this case):
 
 ```surql
 CREATE cat:kitten2;
@@ -118,30 +185,30 @@ RELATE [cat:mr_meow, cat:mrs_meow]->parent_of->[cat:kitten, cat:kitten2];
 
 ```surql title="Response"
 [
-    {
-        "id": "parent_of:kvgu19yulq347b8xksxw",
-        "in": "cat:mr_meow",
-        "out": "cat:kitten"
-    },
-    {
-        "id": "parent_of:xxvj5pkxci3k9bqm6br9",
-        "in": "cat:mr_meow",
-        "out": "cat:kitten2"
-    },
-    {
-        "id": "parent_of:e4xwvecwwm6sxq1xe0yr",
-        "in": "cat:mrs_meow",
-        "out": "cat:kitten"
-    },
-    {
-        "id": "parent_of:ub9t2mm948jfuup6r6c4",
-        "in": "cat:mrs_meow",
-        "out": "cat:kitten2"
-    }
+	{
+		id: parent_of:ysbab20nv5568ogba6ns,
+		in: cat:mr_meow,
+		out: cat:kitten
+	},
+	{
+		id: parent_of:0ltm6xr94pkblyxf0m6c,
+		in: cat:mr_meow,
+		out: cat:kitten2
+	},
+	{
+		id: parent_of:71cfl0nvj5frve0r1npv,
+		in: cat:mrs_meow,
+		out: cat:kitten
+	},
+	{
+		id: parent_of:4gbid7nzo6cwr1t8k090,
+		in: cat:mrs_meow,
+		out: cat:kitten2
+	}
 ]
 ```
 
-## Adding data using `SET` and `CONTENT`
+### Adding data using `SET` and `CONTENT`
 
 Graph edges are standalone tables that can hold other fields besides the default `in`, `out`, and `id`. These can be added during a `RELATE` statement or during an `UPDATE` in the same manner as any other SurrealDB table.
 
@@ -149,32 +216,55 @@ Let's look at the two ways you can add record data in the `RELATE` statement. Bo
 
 ```surql
 RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now();
+    SET 
+		metadata.time_written = time::now(),
+		metadata.location = "Tallinn";
 
 
 RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
 	CONTENT {
-		time: {
-			written: time::now()
+		metadata: {
+			time_written: time::now(),
+			location: "Tallinn"
 		}
 	};
 ```
 
-Here is an example of a graph edge being updated in the same way as any other SurrealDB record:
+```surql title="Response"
+[
+	{
+		id: wrote:rva8hentypdu8lcgwjmf,
+		in: person:l19zjikkw1p1h9o6ixrg,
+		metadata: {
+			location: 'Tallinn',
+			time_written: d'2024-11-26T01:52:01.169Z'
+		},
+		out: article:8nkk6uj4yprt49z7y3zm
+	}
+]
+```
+
+Here is an example of the graph edge being updated in the same way as any other SurrealDB record:
 
 ```surql
 -- Add a small synopsis composed of the table name and article ID
 UPDATE wrote SET
-    description = meta::tb(out) + ' written by ' + <string>in;
+    metadata.description = meta::tb(out) + ' written by ' + <string>in;
 ```
 
 ```surql title="Response"
-    {
-        "id": "wrote:s51jjewpw953ahysbhak",
-        "in": "person:l19zjikkw1p1h9o6ixrg",
-        "out": "article:8nkk6uj4yprt49z7y3zm",
-        "description": "article written by person:l19zjikkw1p1h9o6ixrg"
-    }
+[
+	{
+		id: wrote:k9d8ynbfxgb8jqjv2ob5,
+		in: person:l19zjikkw1p1h9o6ixrg,
+		metadata: {
+			description: 'article written by person:l19zjikkw1p1h9o6ixrg',
+			location: 'Tallinn',
+			time_written: d'2024-11-26T01:53:51.350Z'
+		},
+		out: article:8nkk6uj4yprt49z7y3zm
+	}
+]
 ```
 
 ### Passing variables in `CONTENT` and `SET`
@@ -224,29 +314,252 @@ RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
     }
 ```
 
-## Creating a single relation with the `ONLY` keyword
+
+### Creating a single relation with the `ONLY` keyword
+
 Using the ONLY keyword, just an object for the relation in question will be returned. This, instead of an array with a single object.
 
 ```surql
 RELATE ONLY person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm;
 ```
 
-## Basics of querying graphs
+```surql title="Response"
+{
+	id: wrote:k9f1rqn3oikolr1560u3,
+	in: person:l19zjikkw1p1h9o6ixrg,
+	out: article:8nkk6uj4yprt49z7y3zm
+}
+```
+
+### Using [`LET`](/docs/surrealql/statements/let) parameters in RELATE statements
+
+You can also use [parameters](/docs/surrealql/parameters) to specify the record IDs.
+
+```surql
+-- These two statements store the result of the subquery in a parameter
+-- The subquery returns an array of IDs
+LET $person =  (SELECT VALUE id FROM person);
+LET $article = (SELECT VALUE id FROM article);
+
+-- This statement creates a relationship record for every combination of Record IDs
+-- Such that if we have 10 records each in the person and article table
+-- We get 100 records in the wrote edge table (10*10 = 100)
+-- In this case it would mean that each article would have 10 authors
+RELATE $person->wrote->$article SET time.written = time::now();
+```
+
+### Modifying output with the [`RETURN`](/docs/surrealql/statements/return) clause
+
+By default, the relate statement returns the record value once the changes have been made. To change the return value of each record, specify a RETURN clause, specifying either `NONE`, `BEFORE`, `AFTER`, `DIFF`, or a comma-separated list of specific fields to return.
 
-Let's look at how the above gets queried, for more examples see the [SELECT docs](/docs/surrealql/statements/select).
+```surql
+-- Don't return any result
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN NONE;
+
+-- Return the changeset diff
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN DIFF;
 
-For the questions below, each of the queries will give you the same answer. Note that whether `->` and `<-` are parsed as `in` or `out` depends on their direction in relation to the graph edge `wrote`. An arrow pointing towards `wrote` corresponds to `in`, and vice versa.
+-- Return the record before changes were applied
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN BEFORE;
 
-The following examples show how to make similar queries in a number of different ways, in the context of `person` records that `wrote` one or more `article`s.
+-- Return the record after changes were applied (the default)
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN AFTER;
+
+-- Return a specific field only from the updated records
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN time;
+
+-- Return only the value of a specific field without the field name
+RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
+    SET time.written = time::now()
+    RETURN VALUE time;
+```
+
+### Using the `TIMEOUT` clause
+
+Adding the `TIMEOUT` keyword to specify a timeout duration for the statement can be useful when processing a large result set with many interconnected records. If the statement continues beyond this duration, then the transaction will fail, and the statement will return an error.
+
+```surql
+-- Cancel this conditional filtering based on graph edge properties
+-- if not finished within 5 seconds
+SELECT * FROM person WHERE ->knows->person->(knows WHERE influencer = true) TIMEOUT 5s;
+```
+
+Using a `TIMEOUT` is particularly useful when experimenting with complex queries with an extent that is difficult to imagine, especially if the query [is recursive](#recursive-graph-queries).
+
+### Using the `PARALLEL` clause
+
+When processing a large result set with many interconnected records, it may be desirable to use the `PARALLEL` keyword to signify that edges and remote records should be fetched and processed concurrently, rather than sequentially. This can be useful when you want to process a large result set in a short amount of time.
+
+```surql
+-- Fetch and process the person, purchased and product targets in parallel
+-- Select every product that was purchased by a person that purchased a product that person tobie also purchased
+SELECT ->purchased->product<-purchased<-person->purchased->product FROM person:tobie PARALLEL;
+```
+
+### Deleting graph edges
+
+You can also delete graph edges between two records in the database by using the [DELETE statement](/docs/surrealql/statements/delete).
+
+For example the graph edge below:
+
+```surql
+RELATE person:tobie->bought->product:iphone;
+```
+
+```surql title="Response"
+
+[
+	{
+		id: bought:ctwsll49k37a7rmqz9rr,
+		in: person:tobie,
+		out: product:iphone
+	}
+]
+```
+
+Can be deleted by:
+
+```surql
+DELETE person:tobie->bought WHERE out=product:iphone RETURN BEFORE;
+```
+
+As mentioned above, a graph edge will also automatically be deleted if it is no longer connected to a record at both `in` and `out`.
+
+```surql
+-- Create three people
+CREATE person:one, person:two, person:three;
+
+-- And a love triangle involving them all
+RELATE person:one  ->likes->person:two;
+RELATE person:two  ->likes->person:three;
+RELATE person:three->likes->person:one;
+
+-- Person two moves to Venus permanently, so delete
+DELETE person:two;
+
+-- Only one `likes` relationship is left
+SELECT * FROM likes;
+```
+
+```surql title="Output"
+[
+	{
+		id: likes:55szjin5yfqwl4sbmy1f,
+		in: person:three,
+		out: person:one
+	}
+]
+```
+
+
+### Using RELATE on non-existent records
+
+As mentioned at the top of the page, `RELATE` can be used for records that do not yet exist. While this behaviour can be overridden by using the `ENFORCED` keyword, it can be useful in certain situations.
+
+For example, the `VALUE` clause inside a [`DEFINE FIELD`](/docs/surrealql/statements/define/field) statement is calculated every time a record is altered (that is, every time it is created or updated). If this value depends on a graph edge, creating the record first will cause `VALUE` to calculate it based on a nonexistent path.
+
+In the following example, a `house` table has a field called `has_road_access` that depends on whether any `->has_road` paths return an output that is not empty. Meanwhile, the city has a new road under construction but no houses are present and their details have not been set yet.
+
+```surql
+-- Returns true if $this->has_road path is not empty
+DEFINE FIELD has_road_access ON TABLE house VALUE !!$this->has_road->road;
+CREATE road SET name = "Dalhurst Way", length = 10.5;
+```
+
+As the addresses of the upcoming houses have been decided, the `->has_road` path can be set ahead of time by giving the `house` records an ID based on their exact address.
+
+```surql
+LET $road = SELECT * FROM ONLY road WHERE name = "Dalhurst Way" LIMIT 1;
+RELATE [
+    house:[218, "Dalhurst Way"],
+    house:[222, "Dalhurst Way"],
+    house:[226, "Dalhurst Way"],
+]->has_road->$road;
+```
+
+Later on, two new houses are completed in the city and registered in the database. As the path to `house:[218, "Dalhurst Way"]` has already been set up, the `has_road_access` field will evaluate to `true`, while the other house in the middle of nowhere will evaluate to `false`.
+
+```surql
+CREATE house:[218, "Dalhurst Way"] SET floors = 2, bedrooms = 5;
+CREATE house:[0, "Middle of nowhere"] SET floors = 4, bedrooms = 12;
+```
+
+```surql
+-------- Query --------
+
+[
+	{
+		bedrooms: 5,
+		floors: 2,
+		has_road_access: true,
+		id: house:[
+			218,
+			'Dalhurst Way'
+		]
+	}
+]
+
+-------- Query --------
+
+[
+	{
+		bedrooms: 12,
+		floors: 4,
+		has_road_access: false,
+		id: house:[
+			0,
+			'Middle of nowhere'
+		]
+	}
+]
+```
+
+## Querying graphs
+
+### Different ways to reach similar results
+
+For the questions below, each of the queries will give you largely the same answer. Note that whether `->` and `<-` are parsed as `in` or `out` depends on their direction in relation to the graph edge `wrote`. An arrow pointing towards `wrote` corresponds to `in`, and vice versa.
+
+The following examples show how to make similar queries in a number of different ways, in the context of a database with one person who wrote two articles.
+
+```surql
+CREATE 
+	person:aristotle,
+	article:on_sleep_and_sleeplessness,
+	article:on_dreams;
+RELATE person:aristotle->wrote->[
+		article:on_sleep_and_sleeplessness,
+		article:on_dreams
+	]
+	// Written sometime around the year 330 BC
+	SET time_written = d"-0330-01-01";
+```
 
 Who wrote the articles?
 
 ```surql
+-- All queries lead to `person:artistotle` twice,
+-- via different paths and thus different field names
+-- and/or structure
+
+-- Directly from the `wrote` table
 SELECT in FROM wrote;
 
+-- From a single `person` record
 SELECT ->wrote.in FROM person;
 SELECT ->wrote<-person FROM person;
 
+-- From two `article` records
 SELECT <-wrote.in FROM article;
 SELECT <-wrote<-person FROM article;
 ```
@@ -266,11 +579,13 @@ SELECT <-wrote->article FROM article;
 When was the article written?
 
 ```surql
-SELECT time.written as time_written FROM wrote;
-SELECT ->wrote.time.written as time_written FROM person;
-SELECT <-wrote.time.written as time_written FROM article;
+SELECT time_written FROM wrote;
+SELECT ->wrote.time_written as time_written FROM person;
+SELECT <-wrote.time_written as time_written FROM article;
 ```
 
+### Parsing graph queries
+
 For a more complicated query like the one below you can use a simple rule of thumb:
 Place the subject in front of the graph selection, then read it backward.
 
@@ -282,53 +597,207 @@ SELECT ->purchased->product<-purchased<-person->purchased->product FROM person:t
 person:tobie->purchased->product<-purchased<-person->purchased->product SELECT
 ```
 
-Reading this backwards then makes more sense: <br/>
+Reading this backwards then makes more sense:
+
+> Select every product that was purchased by a person who purchased a product that was also purchased by person Tobie.
+
+Alternatively, you can break it down into steps over multiple lines.
+
+```surql
+-- Starting with Tobie
+person:tobie
+-- move on to his purchased products
+->purchased->product
+-- that were also purchased by persons...
+<-purchased<-person
+-- what are all of those persons' purchased products?
+->purchased->product
+```
+
+Putting it all together it would be: based on all the products Tobie purchased, which person also purchased those products and what did they purchase? This sort of query could be used on a social network site to recommend to the user `person:tobie` a list of people that have similar interests.
+
+### Using parentheses to refine graph query logic
+
+Parentheses can be added at any step of a graph query to refine the logic, such as filtering relations based on specific conditions using the `WHERE` clause.
+
+For example, suppose we want to limit the query to only take recent purchases into account. We can filter `purchased` graph edge to only include purchases made in last 3 weeks:
+
+```surql
+-- Select products purchased by people in the last 3 weeks who have purchased the same products that tobie purchased
+SELECT 
+	->purchased->product
+	<-purchased<-person->(purchased WHERE created_at > time::now() - 3w)
+	->purchased->product
+FROM person:tobie;
+```
+
+If the `purchased` graph table can lead to both a `product` or a `subscription`, they can both be added to the query.
+
+```surql
+SELECT 
+	->purchased->(product, subscription)
+	<-purchased<-person
+	->purchased->(product, subscription)
+FROM person:tobie;
+```
 
-Select every product that was purchased by a person who purchased a product that was also purchased by person Tobie.
+The `?` wildcard operator can also be used to search for any and all linked records. The following query will allow purchased `product`, `subscription`, `insurance`, or any other linked records to show up.
+
+```surql
+SELECT 
+	->purchased->(?)
+	<-purchased<-person
+	->purchased->(?)
+FROM person:tobie;
+```
+
+The `?` operator on its own can thus be used to see all of the relations that a record has.
+
+```surql
+CREATE person:hermann_hesse, person:abigail, city:calw, book:demian;
+RELATE person:hermann_hesse->wrote->book:demian SET written_in = d'1919-01-01';
+RELATE person:hermann_hesse->born_in->city:calw;
+RELATE person:abigail->likes->person:hermann_hesse;
+
+SELECT 
+	-- all tables in which the record is at `in`
+    ->(?).* AS what_hesse_did,
+	-- all tables in which the record is at `out`
+    <-(?).* AS what_others_did_to_hesse
+FROM person:hermann_hesse;
+```
+
+```surql title="Output"
+[
+	{
+		what_hesse_did: [
+			{
+				id: born_in:k3adylof24a2r5kio8l5,
+				in: person:hermann_hesse,
+				out: city:calw
+			},
+			{
+				id: wrote:ncbo9w0d8t3xd7lvl4dx,
+				in: person:hermann_hesse,
+				out: book:demian,
+				written_in: d'1919-01-01T00:00:00Z'
+			}
+		],
+		what_others_did_to_hesse: [
+			{
+				id: likes:6gubmldm14gzasoyypay,
+				in: person:abigail,
+				out: person:hermann_hesse
+			}
+		]
+	}
+]
+```
 
-Alternatively, you can break it down into steps.
+Parentheses can be used at each point of a graph query. The example below includes `person` records (authors) connected to `book` records by the `wrote` table. As both the `person` and `book` tables have fields that can be useful when filtering, they can be isolated with parentheses at this point of the graph query in order to filter using the `WHERE` clause.
 
 ```surql
--- Starting with Tobie
-person:tobie
-
--- and his purchased products
-->purchased->product
-
--- that were also purchased by persons
-<-purchased<-person
-
--- what are all of those persons' purchased products?
-->purchased->product
+CREATE person:j_r_r_tolkien SET
+	name = "J.R.R. Tolkien",
+	born = d'1891-01-03';
+-- Very approximate date of birth
+CREATE person:plato SET 
+	name = "Plato", 
+	born = "-0428-06-01";
+
+CREATE book:fotr SET 
+	name = "The Fellowship of the Ring";
+CREATE book:republic SET 
+	name = "The Republic",
+	original_name = "Πολιτεία";
+
+RELATE person:j_r_r_tolkien->wrote->book:fotr SET written_at = "North Oxford";
+RELATE person:plato->wrote->book:republic SET written_at = "Athens";
+
+SELECT 
+	name,
+	-- Isolate 'wrote' to use WHERE
+	->(wrote WHERE written_at = "Athens")->book.* AS books_written_in_athens
+FROM person;
+
+SELECT 
+	name, 
+	-- Isolate 'book' to use WHERE
+	->wrote->(book WHERE "Ring" IN name).* AS books_about_rings
+FROM person;
 ```
 
-Putting it all together it would be: based on all the products Tobie purchased, which person also purchased those products and what did they purchase?
+```surql title="Output"
+-------- Query --------
+
+[
+	{
+		books_written_in_athens: [],
+		name: 'J.R.R. Tolkien'
+	},
+	{
+		books_written_in_athens: [
+			{
+				id: book:republic,
+				name: 'The Republic',
+				original_name: 'Πολιτεία'
+			}
+		],
+		name: 'Plato'
+	}
+]
 
-## Using expressions in graph queries
+-------- Query --------
 
-You can use expressions to filter relations based on specific conditions using the `WHERE` clause.
+[
+	{
+		books_about_rings: [
+			{
+				id: book:fotr,
+				name: 'The Fellowship of the Ring'
+			}
+		],
+		name: 'J.R.R. Tolkien'
+	},
+	{
+		books_about_rings: [],
+		name: 'Plato'
+	}
+]
+```
 
-For example, suppose we want to limit the query to only take recent purchases into account. We can filter `purchased` graph edge to only include purchases made in last 3 weeks:
+As of SurrealDB 2.0, [destructuring](/docs/surrealql/datamodel/idioms#destructuring) can also be used to pick and choose which fields to access inside a graph query. The following query will return the same output as above, except that `original_name: 'Πολιτεία'` will no longer show up.
 
 ```surql
--- Select products purchased by people in the last 3 weeks who have purchased the same products that tobie purchased
-SELECT ->purchased->product<-purchased<-person->(purchased WHERE created_at > time::now() - 3w)->product FROM person:tobie;
+SELECT 
+	name, 
+	->(wrote WHERE written_at = "Athens")->book.{ name, id } AS books_written_in_athens
+FROM person;
 ```
 
-## Bidirectional relation querying
+### Bidirectional relation querying
+
+All of the queries up to now have been clear about what sort of record is found at the `in` and `out` fields: `in` is the record that is doing something, while `out` is the record that has something done to it:
 
-Sometimes a relation is such that it is impossible to determine which record is located at the `in` part of a graph table, and which is located at the `out` part. This is the case when a relationship is truly bidirectional and equal, such as a friendship, marriage, or sister cities:
+* A `person` who writes an `article`: the person **writes**, the article **is written**.
+* A `person` who purchases a `product`: the person **purchases**, the product **is purchased**.
+
+However, sometimes a relation is such that it is impossible to determine which record is located at the `in` part of a graph table, and which is located at the `out` part. This is the case when a relationship is truly bidirectional and equal, such as a friendship, marriage, or sister cities:
 
 ```surql
 CREATE city:calgary, city:daejeon;
 RELATE city:calgary->sister_of->city:daejeon;
-
-SELECT id, ->sister_of->city AS sister_cities FROM city;
 ```
 
+This relation could just as well have been established with the statement `RELATE city:daejeon->sister_of->city:calgary`.
+
 In such a case, a query on the relationship makes it appear as if one city has a twin city but the other does not.
 
 ```surql
+SELECT id, ->sister_of->city AS sister_cities FROM city;
+```
+
+```surql title="Response"
 [
 	{
 		id: city:calgary,
@@ -393,7 +862,7 @@ SELECT id, array::complement(<->sister_of<->city, [id]) AS sister_cities FROM ci
 ]
 ```
 
-When using `RELATE` for this sort of relationship, you may want to [define a field](/docs/surrealql/statements/define/field) as a unique key based on the ordered record IDs involved.
+Adding a unique key is a good practice for this sort of relation, as it will prevent it from being created twice. This can be done by [defining a field](/docs/surrealql/statements/define/field) as a unique key based on the ordered record IDs involved, followed by a [`DEFINE INDEX`](/docs/surrealql/statements/define/field) statement.
 
 ```surql
 DEFINE FIELD key ON TABLE sister_of VALUE <string>array::sort([in, out]);
@@ -408,7 +877,7 @@ RELATE city:daejeon->sister_of->city:calgary;
 -- "Database index `only_one_sister_city` already contains '[city:calgary, city:daejeon]', with record `sister_of:npab0uoxogmrvpwsvfoa`"
 ```
 
-## Refining the `in` and `out` fields of a relation
+### Refining the `in` and `out` fields of a relation
 
 As mentioned above, the `in` and `out` fields of a graph table are mandatory but can be modified to specify their record type or make assertions.
 
@@ -419,7 +888,7 @@ DEFINE FIELD in ON TABLE wrote TYPE record<author>;
 DEFINE FIELD out ON TABLE wrote TYPE record<book>;
 ```
 
-But this will be ignored:
+But any attempt to outright redefine the `in` or `out` fields as a different type will be ignored.
 
 ```surql
 DEFINE FIELD in ON TABLE wrote TYPE string;
@@ -441,8 +910,7 @@ RELATE author:hesse->wrote->book:demian;
 "Found book:demian for field `out`, with record `wrote:le3ntnyv2lb943km9gxk`, but field must conform to: $value.language = 'English'"
 ```
 
-
-## Structure of queries on relations
+### Structure of queries on relations
 
 Using an alias is a common practice in both regular and relation queries in SurrealDB to make output more readable and collapse nested structures. You can create an alias using the `AS` clause.
 
@@ -531,6 +999,17 @@ SELECT
 FROM country:usa;
 ```
 
+If using SurrealDB versions 2.0 and above, [destructuring syntax](/docs/surrealql/datamodel/idioms#destructuring) can be used to reduce some typing. Here is the same query as the last using destructuring syntax instead of one line for each field.
+
+```surql
+SELECT
+    id,
+	-- access id and population on a single line
+    ->contains->state.{id, population},
+    ->contains->state->contains->city.id
+FROM country:usa;
+```
+
 ```surql title="Output"
 [
 	{
@@ -563,191 +1042,336 @@ FROM country:usa;
 
 As the query that uses aliases does not maintain the original graph structure, adding `population` would require clever renaming such as `->contains->state.population AS state_populations` to make it clear that the numbers represent state and not city populations.
 
-## Using [`LET`](/docs/surrealql/statements/let) parameters in RELATE statements
+### Multiple graph tables vs. fields
 
-You can also use [parameters](/docs/surrealql/parameters) to specify the record IDs.
+Being able to set fields on graph tables opens up a large variety of custom query methods, one of which is explored here.
 
-```surql
--- These two statements store the result of the subquery in a parameter
--- The subquery returns an array of IDs
-LET $person = (SELECT VALUE id FROM person);
-LET $article = (SELECT VALUE id FROM article);
+Imagine a database that holds detailed information on the relations between NPCs in a game that are made to be as realistic as possible. Two of the characters have a rocky past but finally end up married. During this period, we might have tracked their relationship by adding and removing graph edges between the two of them as they move from a stage of being friends, to dating, to hating each other, to finally ending up married.
 
--- This statement creates a relationship record for every combination of Record IDs
--- Such that if we have 10 records each in the person and article table
--- We get 100 records in the wrote edge table (10*10 = 100)
--- In this case it would mean that each article would have 10 authors
-RELATE $person->wrote->$article SET time.written = time::now();
+```surql
+CREATE person:one, person:two;
+-- These three relations would end up deleted
+RELATE person:one->friends_with->person:two;
+RELATE person:one->dating->person:two;
+RELATE person:one->hates->person:two;
+-- Finally this would be the graph edge connecting the two
+RELATE person:one->married->person:two;
 ```
 
-## Modifying output with the [`RETURN`](/docs/surrealql/statements/return) clause
-
-By default, the relate statement returns the record value once the changes have been made. To change the return value of each record, specify a RETURN clause, specifying either `NONE`, `BEFORE`, `AFTER`, `DIFF`, or a comma-separated list of specific fields to return.
+This works well to track the current state of the relationship, but creating a more general table such as `knows` along with a number of fields can be a better method to track the changing relationship over time. The following shows the relationship between the two `person` records, along with a third record called `person:three` who went to the same school and once dated `person:one`.
 
 ```surql
--- Don't return any result
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now()
-    RETURN NONE;
+CREATE person:one, person:two, person:three;
+RELATE person:one->knows->person:two SET
+    has_been_friends = true,
+    has_dated = true,
+    has_hated = true,
+    married_to = true;
 
--- Return the changeset diff
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now()
-    RETURN DIFF;
+RELATE person:one->knows->person:three SET
+    same_high_school = true,
+    has_dated = true;
+```
 
--- Return the record before changes were applied
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now()
-    RETURN BEFORE;
+With these fields in place, it is possible to use a `WHERE` clause to do refined searches on relationships of a certain type.
 
--- Return the record after changes were applied (the default)
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now()
-    RETURN AFTER;
+```surql
+SELECT 
+	->knows->person AS knows,
+	->knows[WHERE has_dated]->person AS has_dated,
+	->knows[WHERE same_high_school AND has_dated]->person AS dated_and_same_school
+ FROM person:one;
+```
 
--- Return a specific field only from the updated records
-RELATE person:l19zjikkw1p1h9o6ixrg->wrote->article:8nkk6uj4yprt49z7y3zm
-    SET time.written = time::now()
-    RETURN time;
+```surql title="Response"
+[
+	{
+		dated_and_same_school: [
+			person:three
+		],
+		has_dated: [
+			person:two,
+			person:three
+		],
+		knows: [
+			person:two,
+			person:three
+		]
+	}
+]
 ```
-## Using `TIMEOUT` clause
 
-When processing a large result set with many interconnected records, it is possible to use the `TIMEOUT` keyword to specify a timeout duration for the statement. If the statement continues beyond this duration, then the transaction will fail, and the statement will return an error.
+Because the `WHERE` clause simply checks for [truthiness](/docs/surrealql/datamodel/values#values-and-truthiness) (whether a value is present and not empty), these fields do not necessarily need to be booleans and can even be complex objects.
 
 ```surql
--- Cancel this conditional filtering based on graph edge properties
--- if it's not finished within 5 seconds
-SELECT * FROM person WHERE ->knows->person->(knows WHERE influencer = true) TIMEOUT 5s;
-```
+RELATE person:one->knows->person:two SET
+	same_high_school = false,
+    has_been_friends = true,
+    has_dated = {
+		from: d'2020-12-25',
+		to: d'2023-12-25'
+	},
+    has_hated = {
+		from: d'2023-12-25',
+		to: d'2024-03-01'
+	},
+    married_to = {
+		since: d'2024-03-01'
+	};
 
-## Using `PARALLEL` clause
+RELATE person:one->knows->person:three SET
+    same_high_school = true,
+    has_dated = {
+		from: d'2019-09-10',
+		to: d'2020-12-31'
+	};
+```
 
-When processing a large result set with many interconnected records, it is possible to use the `PARALLEL` keyword to signify that edges and remote records should be fetched and processed concurrently, rather than sequentially. This can be useful when you want to process a large result set in a short amount of time.
+With these objects, a jealous `person:two` could do a check on `person:one` to see how many relationships with `has_dated` have an end time that overlaps with the `has_dated` period of `person:one` and `person:two`.
 
 ```surql
--- Fetch and process the person, purchased and product targets in parallel
--- Select every product that was purchased by a person that purchased a product that person tobie also purchased
-SELECT ->purchased->product<-purchased<-person->purchased->product FROM person:tobie PARALLEL;
+SELECT id, ->knows[WHERE same_high_school AND has_dated.to > d'2020-12-25']->person FROM person:one;
 ```
 
-## Deleting graph edges
+### Recursive graph queries
 
-You can also delete graph edges between two records in the database by using the [DELETE statement](/docs/surrealql/statements/delete).
+<Since v="v2.1.0" />
 
-For example the graph edge below:
+Graph edges can also be queried recursively. For a full explanation of this syntax, see the page on [recursive paths](/docs/surrealql/datamodel/idioms#recursive-paths).
+
+Take the following example which creates five cities, each of which is connected to the next by some type of road of random length.
 
 ```surql
-RELATE person:tobie->bought->product:iphone;
+CREATE |city:1..5| SET name = <string>id.id() + 'ville';
+FOR $pair IN (<array>(1..=5)).windows(2) {
+  	LET $city1 = type::thing("city", $pair[0]);
+    LET $city2 = type::thing("city", $pair[1]);
+    RELATE $city1->to->$city2 SET 
+        type = rand::enum(["train", "road", "bike path"]),
+        distance = <int>(rand::float() * 100).ceil()
+};
 ```
 
-```surql title="Response"
+While it is possible to manually move three levels down this road network, it involves a good deal of manual typing.
+
+```surql
+SELECT ->to->city->to->city->to->city AS fourth_city FROM city:1;
+```
 
+```surql title="Response"
 [
 	{
-		"id": "bought:ctwsll49k37a7rmqz9rr",
-		"in": "person:tobie",
-		"out": "product:iphone"
+		fourth_city: [
+			city:4
+		]
 	}
 ]
 ```
 
-Can be deleted by:
+This can be replaced by a `@` to refer to the current record, followed by `.{3}` to represent three levels down the `to` graph edge. A level between 1 and 256 can be specified here.
 
 ```surql
-DELETE person:tobie->bought WHERE out=product:iphone;
+SELECT @.{3}->to->city AS fourth_city FROM city:1;
 ```
 
-As mentioned above, a graph edge will also automatically be deleted if it is no longer connected to a record at both `in` and `out`.
+A traditional query to show the final road info from `city:1` to the city three stops away would look like this.
 
 ```surql
--- Create three people
-CREATE person:one, person:two, person:three;
-
--- And a love triangle involving them all
-RELATE person:one->likes->person:two;
-RELATE person:two->likes->person:three;
-RELATE person:three->likes->person:one;
-
--- Person two moves to Venus permanently, so delete
-DELETE person:two;
-
--- Only one `likes` relationship is left
-SELECT * FROM likes;
+SELECT ->to->city->to->city->to.* AS third_journey FROM city:1;
 ```
 
-```surql title="Output"
+```surql title="Response"
 [
 	{
-		id: likes:55szjin5yfqwl4sbmy1f,
-		in: person:three,
-		out: person:one
+		fourth_city: [
+			[
+				{
+					distance: 80,
+					id: to:sw2pery99jomfhibzfrh,
+					in: city:3,
+					out: city:4,
+					type: 'train'
+				}
+			]
+		]
 	}
 ]
 ```
 
-## Multiple graph tables vs. fields
-
-Imagine a database that holds detailed information on the relations between NPCs in a game that are made to be as realistic as possible. Two of the characters have a rocky past but finally a happy conclusion in which they end up married. During this period, we might have tracked their relationship by adding and removing graph edges between the two of them as they move from a stage of being friends, to dating, to hating each other, to finally ending up married.
+To use the same query recursively, wrap the part that must be repeated (`->to->city`) inside parentheses. This will ensure that the `.{2}` part of the query only repeats `->to->city` twice, and not the final `->to.*` portion.
 
 ```surql
--- These three relations would end up deleted
-RELATE person:one->friends_with->person:two;
-RELATE person:one->dating->person:two;
-RELATE person:one->hates->person:two;
--- Finally this would be the graph edge connecting the two
-RELATE person:one->married->person:two;
+SELECT @.{2}(->to->city)->to.* AS third_journey FROM city:1;
 ```
 
-This works well to track the current state of the relationship, but creating a more general table such as `knows` along with a number of fields can be a better method to track the changing relationship over time. The following shows the relationship between the two `person` records, along with a third record called `person:three` who went to the same school and once dated `person:one`.
+A range can be added inside the `{}` braces. The following query that uses a range of 1 to 20 will follow the `->to->city` path up to 20 times, but will stop at the 5th and final depth because the next level returns an empty array.
 
 ```surql
-RELATE person:one->knows->person:two SET
-    has_been_friends = true,
-    has_dated = true,
-    has_hated = true,
-    married_to = true;
+city:1.{1..20}->to->city;
+```
 
-RELATE person:one->knows->person:three SET
-    same_high_school = true,
-    has_dated = true;
+```surql title="Response"
+[
+	city:5
+]
 ```
 
-With these fields in place, it is possible to use a `WHERE` clause to do refined searches on relationships of a certain type.
+Ranges can be followed with the destructuring operator to collect fields on each depth, returning them in a single response. The following query goes five depths down the `to` graph table, returning each city and road along the way.
 
 ```surql
-SELECT id, ->knows->person FROM person:one;
-SELECT id, ->knows[WHERE has_dated]->person FROM person:one;
-SELECT id, ->knows[WHERE same_high_school AND has_dated]->person FROM person:one;
+SELECT @.{1..5}.{ 
+    id, 
+    next_roads: ->to.*,
+    next_cities: ->to->city
+} FROM city;
 ```
 
-Because the `WHERE` clause simply checks for [truthiness](/docs/surrealql/datamodel/values#values-and-truthiness) (whether a value is present and not empty), these fields do not necessarily need to be booleans and can even be complex objects.
-
-```surql
-RELATE person:one->knows->person:two SET
-	same_high_school = false,
-    has_been_friends = true,
-    has_dated = {
-		from: d'2020-12-25',
-		to: d'2023-12-25'
+```surql title="Response"
+[
+	{
+		id: city:1,
+		next_cities: [
+			city:2
+		],
+		next_roads: [
+			{
+				distance: 33,
+				id: to:bl6i9djau0pg24pqrwd9,
+				in: city:1,
+				out: city:2,
+				type: 'road'
+			}
+		]
 	},
-    has_hated = {
-		from: d'2023-12-25',
-		to: d'2024-03-01'
+	{
+		id: city:2,
+		next_cities: [
+			city:3
+		],
+		next_roads: [
+			{
+				distance: 45,
+				id: to:ybugfnlzv6kcrkaj49ig,
+				in: city:2,
+				out: city:3,
+				type: 'road'
+			}
+		]
 	},
-    married_to = {
-		since: d'2024-03-01'
-	};
+	{
+		id: city:3,
+		next_cities: [
+			city:4
+		],
+		next_roads: [
+			{
+				distance: 80,
+				id: to:sw2pery99jomfhibzfrh,
+				in: city:3,
+				out: city:4,
+				type: 'train'
+			}
+		]
+	},
+	{
+		id: city:4,
+		next_cities: [
+			city:5
+		],
+		next_roads: [
+			{
+				distance: 29,
+				id: to:42hlspf4z5lpqceyv68p,
+				in: city:4,
+				out: city:5,
+				type: 'train'
+			}
+		]
+	},
+	{
+		id: city:5,
+		next_cities: [],
+		next_roads: []
+	}
+]
+```
 
-RELATE person:one->knows->person:three SET
-    same_high_school = true,
-    has_dated = {
-		from: d'2019-09-10',
-		to: d'2020-12-31'
-	};
+As noted above, a `TIMEOUT` can be set for queries that may be computationally expensive. This is particularly useful when experimenting with recursive queries, which, if care is not taken, can run all the way to the maximum possible depth of 256.
+
+Take the following example with two `person` records that like each other. Following the `likes` edge will run until the query recurses 256 times and gives up.
+
+```surql
+CREATE person:one, person:two;
+RELATE person:one->likes->person:two;
+RELATE person:two->likes->person:one;
+-- Open-ended range
+person:one.{..}->likes->person;
 ```
 
-With these objects, a jealous `person:two` could do a check on `person:one` to see how many relationships with `has_dated` have an end time that overlaps with the `has_dated` period of `person:one` and `person:two`.
+```surql title="Response"
+'Exceeded the idiom recursion limit of 256.'
+```
+
+Take the following example in which three `person` records of created, each of which likes the other two `person` records. A query on the `->likes->person` path shows that the number of records doubles each time.
 
 ```surql
-SELECT id, ->knows[WHERE same_high_school AND has_dated.to > d'2020-12-25']->person FROM person:one;
+CREATE |person:1..3|;
+FOR $person IN (SELECT * FROM person) {
+  LET $others = (SELECT * FROM person WHERE id != $person.id);
+    FOR $other IN $others {
+        RELATE $person->likes->$other;
+    }
+};
+RETURN [
+	person:1.{2}->likes->person,
+	person:1.{3}->likes->person,
+	person:1.{4}->likes->person
+];
+```
+
+```surql title="Response"
+[
+	[
+		person:1,
+		person:2,
+		person:1,
+		person:3
+	],
+	[
+		person:3,
+		person:2,
+		person:1,
+		person:3,
+		person:3,
+		person:2,
+		person:1,
+		person:2
+	],
+	[
+		person:1,
+		person:2,
+		person:1,
+		person:3,
+		person:3,
+		person:2,
+		person:1,
+		person:2,
+		person:1,
+		person:2,
+		person:1,
+		person:3,
+		person:3,
+		person:2,
+		person:1,
+		person:3
+	]
+]
 ```
+
+Since an open-ended range can be specified in a recursive query, this would result in a full 256 attempts to recurse, multiplying the number of results by two each time for a total of 115792089237316195423570985008687907853269984665640564039457584007913129639936 records by the end.
+
+When experimenting with recursive queries, especially open-ended ranges, it is thus recommended to use a timeout.
+
+```surql
+SELECT @.{..}.{ id, likes: ->likes->person.@ } FROM person TIMEOUT 1s;
+```
\ No newline at end of file
diff --git a/src/content/doc-surrealql/statements/show.mdx b/src/content/doc-surrealql/statements/show.mdx
index 29fbcfd28..39b3fd589 100644
--- a/src/content/doc-surrealql/statements/show.mdx
+++ b/src/content/doc-surrealql/statements/show.mdx
@@ -10,7 +10,7 @@ description: The SHOW statement can be used to replay changes made to a table.
 The `SHOW` statement can be used to replay changes made to a table.
 
 ## Requirements
-- You must first [`DEFINE`](/docs/surrealql/statements/define/table#example-usage) a [Change Feed](https://surrealdb.com/products/change-data-capture).
+- You must first [`DEFINE`](/docs/surrealql/statements/define/table#example-usage) a [Change Feed](/features/change-data-capture).
 
 ### Statement syntax
 
diff --git a/src/content/doc-surrealql/statements/update.mdx b/src/content/doc-surrealql/statements/update.mdx
index 07a8e2ab4..e4f080d97 100644
--- a/src/content/doc-surrealql/statements/update.mdx
+++ b/src/content/doc-surrealql/statements/update.mdx
@@ -29,7 +29,7 @@ UPDATE [ ONLY ] @targets
 	  | [ SET @field = @value, ... | UNSET @field, ... ]
 	]
 	[ WHERE @condition ]
-	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... ]
+	[ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... | RETURN VALUE @statement_param ]
 	[ TIMEOUT @duration ]
 	[ PARALLEL ]
 ;
@@ -439,7 +439,7 @@ UPDATE person:tobie PATCH [
 
 ## Alter the `RETURN` value
 
-By default, the update statement returns the record value once the changes have been made. To change the return value of each record, specify a `RETURN` clause, specifying either `NONE`, `BEFORE`, `AFTER`, `DIFF`, or a comma-separated list of specific fields to return.
+By default, the update statement returns the record value once the changes have been made. To change the return value of each record, use the `RETURN` clause, specifying `NONE`, `BEFORE`, `AFTER`, `DIFF`, a comma-separated list of specific fields or ad-hoc fields, or `VALUE` for a single field without its key name.
 
 ```surql
 -- Don't return any result
@@ -454,6 +454,9 @@ UPDATE person SET skills += 'reading' RETURN BEFORE;
 -- Return the record after changes were applied (the default)
 UPDATE person SET skills += 'reading' RETURN AFTER;
 
+-- Return the value of the 'skills' field without the field name
+UPDATE person SET skills += 'reading' RETURN VALUE skills;
+
 -- Return a specific field only from the updated records
 UPDATE person:tobie SET skills = ['skiing', 'music'] RETURN name, interests;
 ```
diff --git a/src/content/doc-surrealql/statements/upsert.mdx b/src/content/doc-surrealql/statements/upsert.mdx
index 1827086f7..13290ddff 100644
--- a/src/content/doc-surrealql/statements/upsert.mdx
+++ b/src/content/doc-surrealql/statements/upsert.mdx
@@ -28,7 +28,7 @@ UPSERT [ ONLY ] @targets
       | [ SET @field = @value, ... | UNSET @field, ... ]
     ]
     [ WHERE @condition ]
-    [ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... ]
+    [ RETURN NONE | RETURN BEFORE | RETURN AFTER | RETURN DIFF | RETURN @statement_param, ... | RETURN VALUE @statement_param ]
     [ TIMEOUT @duration ]
     [ PARALLEL ]
 ;
diff --git a/src/content/doc-surrealql/transactions.mdx b/src/content/doc-surrealql/transactions.mdx
index 67f4e0e4f..2e5a55510 100644
--- a/src/content/doc-surrealql/transactions.mdx
+++ b/src/content/doc-surrealql/transactions.mdx
@@ -130,3 +130,49 @@ SELECT * FROM account;
 ]
 ```
 
+## Using transactions to test code for errors
+
+As failed transactions automatically roll back any changes made, a transaction with a final `THROW` statement can be used as a confirmation that no errors have taken place inside a group of queries.
+
+Take the following example that creates a unique index and then inserts some records to make sure that the database logic is functioning as expected. However, as names are not necessarily unique, the index soon gives an error and cancels the transaction before `THROW` can be reached.
+
+```surql
+BEGIN TRANSACTION;
+DEFINE INDEX unique_name ON TABLE person FIELDS name UNIQUE;
+
+INSERT INTO person [
+    { name: 'Agatha Christie', born: d'1890-09-15' },
+    { name: 'Billy Billerson', born: d'1979-09-11' },
+	-- Pretend there are is 10,000 more objects here
+    { name: 'Agatha Christie', born: d'1955-05-15' },
+];
+
+THROW "Reached the end";
+COMMIT TRANSACTION;
+```
+
+The output is not the expected 'An error occurred: Reached the end' message, showing that not all queries were successful.
+
+```surql title="Output"
+"Database index `unique_name` already contains 'Agatha Christie', with record `person:qs4bpvl96sf9x40b3567`"
+```
+
+If the index is redefined to be less strict, the statetements will work and the expected output will be reached, confirming that no errors occurred during the test.
+
+```surql
+BEGIN TRANSACTION;
+DEFINE INDEX OVERWRITE unique_person ON TABLE person FIELDS name, born UNIQUE;
+
+INSERT INTO person [
+    { name: 'Agatha Christie', born: d'1890-09-15' },
+    { name: 'Billy Billerson', born: d'1979-09-11' },
+    { name: 'Agatha Christie', born: d'1955-05-15' },
+];
+
+THROW "Reached the end";
+COMMIT TRANSACTION;
+```
+
+```surql title="Expected output"
+'An error occurred: Reached the end'
+```
\ No newline at end of file
diff --git a/src/content/doc-tutorials/integrate-auth0-as-authentication-provider.mdx b/src/content/doc-tutorials/integrate-auth0-as-authentication-provider.mdx
index 2186eee44..c1bb0facc 100644
--- a/src/content/doc-tutorials/integrate-auth0-as-authentication-provider.mdx
+++ b/src/content/doc-tutorials/integrate-auth0-as-authentication-provider.mdx
@@ -237,7 +237,7 @@ In the example above, replace the placeholder with the domain value defined for
 
 
 > [!IMPORTANT]
-> In order to allow SurrealDB to establish a connection with Auth0 to download the JWKS object, you will require running it with the network <a href="/docs/security/capabilities">capability</a>. For the strongest security, provide your specific Auth0 domain when starting SurrealDB with <code>--allow-net</code>. For example: <code>--allow-net example.eu.auth0.com</code>.
+> In order to allow SurrealDB to establish a connection with Auth0 to download the JWKS object, you will require running it with the network <a href="/docs/surrealdb/security/capabilities">capability</a>. For the strongest security, provide your specific Auth0 domain when starting SurrealDB with <code>--allow-net</code>. For example: <code>--allow-net example.eu.auth0.com</code>.
 
 #### Defining authorization criteria in SurrealDB
 For this simple example, we will create a single table named “user”, where any user that authenticates through Auth0 using your application with a verified email address will be able to register, view and update their data. For this to work as intended, we will need to verify some information in the token claims.
diff --git a/src/content/doc-tutorials/using-github-actions.mdx b/src/content/doc-tutorials/using-github-actions.mdx
index 0a6e1eb1b..26eafa20b 100644
--- a/src/content/doc-tutorials/using-github-actions.mdx
+++ b/src/content/doc-tutorials/using-github-actions.mdx
@@ -25,16 +25,17 @@ jobs:
     - name: Git checkout
       uses: actions/checkout@v4
     - name: Start SurrealDB
-      uses: surrealdb/setup-surreal@v1
+      uses: surrealdb/setup-surreal@v2
       with:
         surrealdb_version: latest
         surrealdb_port: 8000
         surrealdb_username: root
         surrealdb_password: root
-        surrealdb_auth: true
-        surrealdb_strict: true
+        surrealdb_auth: false
+        surrealdb_strict: false
         surrealdb_log: info
         surrealdb_additional_args: --allow-all
+        surrealdb_retry_count: 30
 ```
 
 ## Step 2: Customize Workflow Arguments
@@ -62,7 +63,7 @@ The official SurrealDB GitHub Action accepts several arguments to configure the
                 latest
             </td>
             <td scope="row" data-label="Value">
-                latest, v1.x.x
+                latest, v2.x.x
             </td>
         </tr>
         <tr>
@@ -183,21 +184,22 @@ jobs:
     - name: Git checkout
       uses: actions/checkout@v4
     - name: Start SurrealDB
-      uses: surrealdb/setup-surreal@v1
+      uses: surrealdb/setup-surreal@v2
       with:
         surrealdb_version: latest
         surrealdb_port: 8000
         surrealdb_username: root
         surrealdb_password: root
-        surrealdb_auth: true
-        surrealdb_strict: true
-        surrealdb_log: debug
-        surrealdb_additional_args: --strict-mode --other-arg
+        surrealdb_auth: false
+        surrealdb_strict: false
+        surrealdb_log: info
+        surrealdb_additional_args: --allow-all
+        surrealdb_retry_count: 30
 ```
 
 ### Tips for Customization
 
-1. **Version Control**: Use specific versions to avoid unexpected changes. Example: surrealdb_version: v1.0.0.
+1. **Version Control**: Use specific versions to avoid unexpected changes. Example: surrealdb_version: v2.0.0.
 2. **Security**: Always use strong passwords for surrealdb_password and avoid using default credentials in production.
 3. **Logs**: Set an appropriate log level based on your needs. For debugging, use debug or trace.
 4. **Additional Arguments**: Utilise surrealdb_additional_args to pass any additional CLI arguments required by your setup.
@@ -218,4 +220,3 @@ Go to your repository on GitHub and navigate to the "Actions" tab. You should se
 ## Conclusion
 
 Using the official GitHub Action for SurrealDB simplifies the process of setting up and running SurrealDB in your CI/CD pipeline. Customise the workflow as per your project requirements, and ensure you follow best practices for security and version control. Happy coding!
-
diff --git a/src/pages/index.astro b/src/pages/index.astro
index 9234c4d1c..938d1fd80 100644
--- a/src/pages/index.astro
+++ b/src/pages/index.astro
@@ -14,6 +14,9 @@ import LightRust from '@img/icon/light/rust.png';
 import LightTypescript from '@img/icon/light/typescript.png';
 import LightWasm from '@img/icon/light/webassembly.png';
 
+import LightCloud from '@img/image/cloud/surrealcloud.png';
+import DarkCloud from '@img/image/cloud/surrealcloud.png';
+
 import DarkDotnet from '@img/icon/dark/dotnet.png';
 import DarkGolang from '@img/icon/dark/golang.png';
 import DarkJava from '@img/icon/dark/java.png';
@@ -117,6 +120,12 @@ import DarkSurrealQL from '@img/icon/dark/surrealql.png';
                         href="/docs/surrealdb"
                         icon={{ light: LightSurrealDB, dark: DarkSurrealDB }}
                     />
+                    <IconBox
+                        title="Surreal Cloud (Beta)"
+                        description="Surreal Cloud (Beta) redefines the database experience, offering the power and flexibility of SurrealDB without the pain of managing infrastructure. Elevate your business to unparalleled levels of scale and resilience. Focus on building tomorrow's applications. Let us take care of the rest."
+                        href="/docs/cloud"
+                        icon={{ light: LightCloud, dark: DarkCloud }}
+                    />
                     <IconBox
                         title="Surrealist"
                         description="Surrealist is a user interface for interacting with your SurrealDB database visually. It enables you to seamlessly connect to any SurrealDB instance, allowing you to execute queries, explore your tables, design your schemas, and much more."
@@ -145,13 +154,13 @@ import DarkSurrealQL from '@img/icon/dark/surrealql.png';
                     <IconBox
                         title="SurrealDB University"
                         description="Dive into our collection of recorded videos, live streams, and expert talks. Enhance your learning experience by accessing a variety of video content that covers essential SurrealDB topics and industry insights."
-                        href="https://surrealdb.com/learn"
+                        href="/learn"
                         icon={{ light: LightUniversity, dark: DarkUniversity }}
                     />
                     <IconBox
                         title="The SurrealDB Book"
                         description="Embark on a journey through the ins and outs of SurrealDB as you follow an immersive story crafted to make learning a new database feel as enjoyable as sitting back and watching your favourite movie."
-                        href="https://surrealdb.com/learn/book"
+                        href="/learn/book"
                         icon={{ light: LightBook, dark: DarkBook }}
                     />
                 </Boxes>
diff --git a/src/util/doc.ts b/src/util/doc.ts
index 8bafc9fbf..2349f1918 100644
--- a/src/util/doc.ts
+++ b/src/util/doc.ts
@@ -197,3 +197,32 @@ export function getTitle(
 ): string {
     return meta.sidebar_label ?? meta.title ?? titleFromSlug(slug);
 }
+
+export function findPreviousPage(
+    items: Item[],
+    index: number
+): Item | undefined {
+    if (index === -1) {
+        return undefined;
+    }
+
+    for (let i = index - 1; i >= 0; i--) {
+        const item = items[i];
+        if ('isPage' in item ? item.isPage : true) {
+            return item;
+        }
+    }
+}
+
+export function findNextPage(items: Item[], index: number): Item | undefined {
+    if (index === -1) {
+        return undefined;
+    }
+
+    for (let i = index + 1; i < items.length; i++) {
+        const item = items[i];
+        if ('isPage' in item ? item.isPage : true) {
+            return item;
+        }
+    }
+}