AI Preview contact form (#834)

Simran-B · web-flow · commit d79eb5fcbf52 · 2025-11-15T13:01:48.000+01:00
* Link AI preview form instead of contact us in AI Suite admonitions

* ArangoDB -&gt; Arango sales/support
diff --git a/site/content/ai-suite/_index.md b/site/content/ai-suite/_index.md
@@ -16,7 +16,7 @@ aliases:
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/graphml/_index.md b/site/content/ai-suite/graphml/_index.md
@@ -12,7 +12,7 @@ aliases:
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/graphrag/_index.md b/site/content/ai-suite/graphrag/_index.md
@@ -13,7 +13,7 @@ aliases:
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/graphrag/technical-overview.md b/site/content/ai-suite/graphrag/technical-overview.md
@@ -8,7 +8,7 @@ description: >-
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/graphrag/tutorial-notebook.md b/site/content/ai-suite/graphrag/tutorial-notebook.md
@@ -7,7 +7,7 @@ weight: 25
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/graphrag/web-interface.md b/site/content/ai-suite/graphrag/web-interface.md
@@ -7,7 +7,7 @@ description: >-
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/notebook-servers.md b/site/content/ai-suite/notebook-servers.md
@@ -7,7 +7,7 @@ description: >-
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/reference/ai-orchestrator.md b/site/content/ai-suite/reference/ai-orchestrator.md
@@ -8,7 +8,7 @@ weight: 5
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/reference/importer.md b/site/content/ai-suite/reference/importer.md
@@ -8,7 +8,7 @@ weight: 10
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/reference/mlflow.md b/site/content/ai-suite/reference/mlflow.md
@@ -8,7 +8,7 @@ weight: 25
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/reference/retriever.md b/site/content/ai-suite/reference/retriever.md
@@ -8,7 +8,7 @@ weight: 15
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/reference/triton-inference-server.md b/site/content/ai-suite/reference/triton-inference-server.md
@@ -7,7 +7,7 @@ weight: 30
 ---
 {{< tip >}}
 The Arango AI Data Platform is available as a pre-release. To get
-exclusive early access, [get in touch](https://arango.ai/contact-us/) with
+exclusive early access, [get in touch](https://arango.ai/ai-preview/) with
 the Arango team.
 {{< /tip >}}
 
diff --git a/site/content/ai-suite/release-notes.md b/site/content/ai-suite/release-notes.md
@@ -7,7 +7,7 @@ description: >-
 ---
 {{< tip >}}
 The AI Suite is available as a pre-release. To get exclusive early access,
-[get in touch](https://arango.ai/contact-us/) with the Arango team.
+[get in touch](https://arango.ai/ai-preview/) with the Arango team.
 {{< /tip >}}
 
 ## October 2024 (pre-release)
diff --git a/site/content/amp/organizations/_index.md b/site/content/amp/organizations/_index.md
@@ -63,7 +63,7 @@ In addition, you gain access to:
 - ArangoDB Professional Services Engagements
 - Ability to transact via the AWS and GCP marketplaces
 
-To take advantage of this, you need to get in touch with the ArangoDB
+To take advantage of this, you need to get in touch with the Arango
 team. [Contact us](https://arango.ai/contact-us/) for more details.
 
 ## How to unlock all features
diff --git a/site/content/arangodb/3.10/operations/administration/license-management.md b/site/content/arangodb/3.10/operations/administration/license-management.md
@@ -63,18 +63,18 @@ can have the following values:
 
 - `good`: Your license is valid for more than another 1 week.
 - `expiring`: Your license is about to expire shortly. Please contact
-  your ArangoDB sales representative to acquire a new license or
+  your Arango sales representative to acquire a new license or
   extend your old license.
 - `read-only`: Your license has expired at which
   point the deployment will be in read-only mode. All read operations to the
   instance will keep functioning. However, no data or data definition changes
-  can be made. Please contact your ArangoDB sales representative immediately.
+  can be made. Please contact your Arango sales representative immediately.
 
 The attribute `expires` in `features` denotes the expiry date as Unix timestamp
 (in seconds since January 1st, 1970 UTC).
 
 The `license` field holds an encrypted and base64-encoded version of the
-applied license for reference and support from ArangoDB.
+applied license for reference and support from Arango.
 
 ## Monitoring
 
diff --git a/site/content/arangodb/3.10/operations/troubleshooting/cluster/agency-dump.md b/site/content/arangodb/3.10/operations/troubleshooting/cluster/agency-dump.md
@@ -35,6 +35,6 @@ curl -k --username root https://<any-coordinator>:<port>/_api/cluster/agency-dum
 ```
 
 Should the _Agency_ be down, an _Agency_ dump can still be created
-starting from the database directory of (one of) the _Agents_. Contact
-ArangoDB Support, in this case, to obtain more detailed guidelines on
+starting from the database directory of (one of) the _Agents_. Contact the
+Arango support in this case, to obtain more detailed guidelines on
 how to produce the dump.
diff --git a/site/content/arangodb/3.10/operations/upgrading/starter-deployments.md b/site/content/arangodb/3.10/operations/upgrading/starter-deployments.md
@@ -203,7 +203,7 @@ If you have connected clusters across multiple datacenter
 (DC2DC deployment), then you need to update each of the clusters.
 
 If the upgrade command fails, please try again. If the upgrade command continues
-to fail, please contact the ArangoDB support.
+to fail, please contact the Arango support.
 
 #### Deployment mode `single`
 
@@ -282,7 +282,7 @@ upgraded.
 ## Going back to the previous version in case of failure
 
 In case the upgrade cannot be carried out (i.e. the upgrade command continues 
-to fail with an error message) please contact the ArangoDB support.
+to fail with an error message) please contact the Arango support.
 
 Until then, the not yet upgraded instances will still be running the previous
 version of ArangoDB. When instances are restarted, they will be starting
diff --git a/site/content/arangodb/3.11/operations/administration/license-management.md b/site/content/arangodb/3.11/operations/administration/license-management.md
@@ -64,18 +64,18 @@ can have the following values:
 
 - `good`: Your license is valid for more than another 1 week.
 - `expiring`: Your license is about to expire shortly. Please contact
-  your ArangoDB sales representative to acquire a new license or
+  your Arango sales representative to acquire a new license or
   extend your old license.
 - `read-only`: Your license has expired at which
   point the deployment will be in read-only mode. All read operations to the
   instance will keep functioning. However, no data or data definition changes
-  can be made. Please contact your ArangoDB sales representative immediately.
+  can be made. Please contact your Arango sales representative immediately.
 
 The attribute `expires` in `features` denotes the expiry date as Unix timestamp
 (in seconds since January 1st, 1970 UTC).
 
 The `license` field holds an encrypted and base64-encoded version of the
-applied license for reference and support from ArangoDB.
+applied license for reference and support from Arango.
 
 ## Monitoring
 
diff --git a/site/content/arangodb/3.11/operations/troubleshooting/cluster/agency-dump.md b/site/content/arangodb/3.11/operations/troubleshooting/cluster/agency-dump.md
@@ -35,6 +35,6 @@ curl -k --username root https://<any-coordinator>:<port>/_api/cluster/agency-dum
 ```
 
 Should the _Agency_ be down, an _Agency_ dump can still be created
-starting from the database directory of (one of) the _Agents_. Contact
-ArangoDB Support, in this case, to obtain more detailed guidelines on
+starting from the database directory of (one of) the _Agents_. Contact the
+Arango support in this case, to obtain more detailed guidelines on
 how to produce the dump.
diff --git a/site/content/arangodb/3.11/operations/upgrading/starter-deployments.md b/site/content/arangodb/3.11/operations/upgrading/starter-deployments.md
@@ -203,7 +203,7 @@ If you have connected clusters across multiple datacenter
 (DC2DC deployment), then you need to update each of the clusters.
 
 If the upgrade command fails, please try again. If the upgrade command continues
-to fail, please contact the ArangoDB support.
+to fail, please contact the Arango support.
 
 #### Deployment mode `single`
 
@@ -282,7 +282,7 @@ upgraded.
 ## Going back to the previous version in case of failure
 
 In case the upgrade cannot be carried out (i.e. the upgrade command continues 
-to fail with an error message) please contact the ArangoDB support.
+to fail with an error message) please contact the Arango support.
 
 Until then, the not yet upgraded instances will still be running the previous
 version of ArangoDB. When instances are restarted, they will be starting
diff --git a/site/content/arangodb/3.12/aql/execution-and-performance/explaining-queries.md b/site/content/arangodb/3.12/aql/execution-and-performance/explaining-queries.md
@@ -196,7 +196,7 @@ directly, focusing on the most important information.
 ## Gathering debug information about a query
 
 If an explain provides no suitable insight into why a query does not perform as
-expected, it may be reported to the ArangoDB support. In order to make this as easy
+expected, it may be reported to the Arango support. In order to make this as easy
 as possible, there is a built-in command in ArangoShell for packaging the query, its
 bind parameters, and all data required to execute the query elsewhere.
 
diff --git a/site/content/arangodb/3.12/operations/administration/license-management.md b/site/content/arangodb/3.12/operations/administration/license-management.md
@@ -241,18 +241,18 @@ can have the following values:
 
 - `good`: Your license is valid for more than another 1 week.
 - `expiring`: Your license is about to expire shortly. Please contact
-  your ArangoDB sales representative to acquire a new license or
+  your Arango sales representative to acquire a new license or
   extend your old license.
 - `read-only`: Your license has expired at which
   point the deployment will be in read-only mode. All read operations to the
   instance will keep functioning. However, no data or data definition changes
-  can be made. Please contact your ArangoDB sales representative immediately.
+  can be made. Please contact your Arango sales representative immediately.
 
 The attribute `expires` in `features` denotes the expiry date as Unix timestamp
 (in seconds since January 1st, 1970 UTC).
 
 The `license` field holds an encrypted and base64-encoded version of the
-applied license for reference and support from ArangoDB.
+applied license for reference and support from Arango.
 {{< /tab >}}
 
 {{< /tabs >}}
diff --git a/site/content/arangodb/3.12/operations/troubleshooting/cluster/agency-dump.md b/site/content/arangodb/3.12/operations/troubleshooting/cluster/agency-dump.md
@@ -35,6 +35,6 @@ curl -k --username root https://<any-coordinator>:<port>/_api/cluster/agency-dum
 ```
 
 Should the _Agency_ be down, an _Agency_ dump can still be created
-starting from the database directory of (one of) the _Agents_. Contact
-ArangoDB Support, in this case, to obtain more detailed guidelines on
+starting from the database directory of (one of) the _Agents_. Contact the
+Arango support, in this case, to obtain more detailed guidelines on
 how to produce the dump.
diff --git a/site/content/arangodb/3.12/operations/upgrading/starter-deployments.md b/site/content/arangodb/3.12/operations/upgrading/starter-deployments.md
@@ -198,7 +198,7 @@ arangodb upgrade --starter.endpoint=<endpoint-of-a-starter>
 ```
 
 If the upgrade command fails, please try again. If the upgrade command continues
-to fail, please contact the ArangoDB support.
+to fail, please contact the Arango support.
 
 #### Deployment mode `single`
 
@@ -277,7 +277,7 @@ upgraded.
 ## Going back to the previous version in case of failure
 
 In case the upgrade cannot be carried out (i.e. the upgrade command continues 
-to fail with an error message) please contact the ArangoDB support.
+to fail with an error message) please contact the Arango support.
 
 Until then, the not yet upgraded instances will still be running the previous
 version of ArangoDB. When instances are restarted, they will be starting
diff --git a/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md
@@ -870,7 +870,7 @@ created with v3.12.4 or any later version.
    **production deployment** to 3.12.4 (or later) and then recreate the indexes
    you dropped once the deployment is on the new version.
 
-   If there are still affected indexes, contact the ArangoDB support.
+   If there are still affected indexes, contact the Arango support.
 
 ### Upgrade a Community Edition deployment
 
diff --git a/site/content/arangodb/4.0/aql/execution-and-performance/explaining-queries.md b/site/content/arangodb/4.0/aql/execution-and-performance/explaining-queries.md
@@ -196,7 +196,7 @@ directly, focusing on the most important information.
 ## Gathering debug information about a query
 
 If an explain provides no suitable insight into why a query does not perform as
-expected, it may be reported to the ArangoDB support. In order to make this as easy
+expected, it may be reported to the Arango support. In order to make this as easy
 as possible, there is a built-in command in ArangoShell for packaging the query, its
 bind parameters, and all data required to execute the query elsewhere.
 
diff --git a/site/content/arangodb/4.0/operations/administration/license-management.md b/site/content/arangodb/4.0/operations/administration/license-management.md
@@ -243,18 +243,18 @@ can have the following values:
 
 - `good`: Your license is valid for more than another 1 week.
 - `expiring`: Your license is about to expire shortly. Please contact
-  your ArangoDB sales representative to acquire a new license or
+  your Arango sales representative to acquire a new license or
   extend your old license.
 - `read-only`: Your license has expired at which
   point the deployment will be in read-only mode. All read operations to the
   instance will keep functioning. However, no data or data definition changes
-  can be made. Please contact your ArangoDB sales representative immediately.
+  can be made. Please contact your Arango sales representative immediately.
 
 The attribute `expires` in `features` denotes the expiry date as Unix timestamp
 (in seconds since January 1st, 1970 UTC).
 
 The `license` field holds an encrypted and base64-encoded version of the
-applied license for reference and support from ArangoDB.
+applied license for reference and support from Arango.
 {{< /tab >}}
 
 {{< /tabs >}}
diff --git a/site/content/arangodb/4.0/operations/troubleshooting/cluster/agency-dump.md b/site/content/arangodb/4.0/operations/troubleshooting/cluster/agency-dump.md
@@ -35,6 +35,6 @@ curl -k --username root https://<any-coordinator>:<port>/_api/cluster/agency-dum
 ```
 
 Should the _Agency_ be down, an _Agency_ dump can still be created
-starting from the database directory of (one of) the _Agents_. Contact
-ArangoDB Support, in this case, to obtain more detailed guidelines on
+starting from the database directory of (one of) the _Agents_. Contact the
+Arango support, in this case, to obtain more detailed guidelines on
 how to produce the dump.
diff --git a/site/content/arangodb/4.0/operations/upgrading/starter-deployments.md b/site/content/arangodb/4.0/operations/upgrading/starter-deployments.md
@@ -198,7 +198,7 @@ arangodb upgrade --starter.endpoint=<endpoint-of-a-starter>
 ```
 
 If the upgrade command fails, please try again. If the upgrade command continues
-to fail, please contact the ArangoDB support.
+to fail, please contact the Arango support.
 
 #### Deployment mode `single`
 
@@ -277,7 +277,7 @@ upgraded.
 ## Going back to the previous version in case of failure
 
 In case the upgrade cannot be carried out (i.e. the upgrade command continues 
-to fail with an error message) please contact the ArangoDB support.
+to fail with an error message) please contact the Arango support.
 
 Until then, the not yet upgraded instances will still be running the previous
 version of ArangoDB. When instances are restarted, they will be starting
diff --git a/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md
@@ -870,7 +870,7 @@ created with v3.12.4 or any later version.
    **production deployment** to 3.12.4 (or later) and then recreate the indexes
    you dropped once the deployment is on the new version.
 
-   If there are still affected indexes, contact the ArangoDB support.
+   If there are still affected indexes, contact the Arango support.
 
 ### Upgrade a Community Edition deployment
 
