diff --git a/docs-site/content/kagent/latest/operations/operational-considerations.md b/docs-site/content/kagent/latest/operations/operational-considerations.md
index a6b66513..d72c6c97 100644
--- a/docs-site/content/kagent/latest/operations/operational-considerations.md
+++ b/docs-site/content/kagent/latest/operations/operational-considerations.md
@@ -119,7 +119,7 @@ Connections to this database do not use a password. `kagent install` sets `datab
 
 For production, run PostgreSQL outside the cluster's lifecycle so that a kagent uninstall cannot delete the data. kagent requires a new, empty database, and the roles and the schema must exist before the controller starts. kagent ships a `psql` script that creates them.
 
-Agent Substrate connects to the same database with its own owner and read/write logins. The Agent Substrate setup script creates these logins. The Agent Substrate chart reads the connection strings for those logins from the Secrets that its `postgres.ownerConnectionStringSecretRef` and `postgres.readWriteConnectionStringSecretRef` values reference. For a procedure that prepares the database for both, see [Install kagent 1.0]({{< link path="operations/upgrade-from-0x#install-kagent-10" >}}).
+Agent Substrate connects to the same database with its own owner and read/write logins. The Agent Substrate setup script creates these logins. The Agent Substrate chart reads the connection strings for those logins from the Secrets that its `postgres.ownerConnectionStringSecretRef` and `postgres.readWriteConnectionStringSecretRef` values reference. For a procedure that prepares the database for both, see [Install kagent 1.0]({{< link path="operations/upgrade-from-0x#install" >}}).
 
 1. Download the setup script for your kagent version.
 
diff --git a/docs-site/content/kagent/latest/operations/upgrade-from-0x.md b/docs-site/content/kagent/latest/operations/upgrade-from-0x.md
index 1beb7d51..53eedd5e 100644
--- a/docs-site/content/kagent/latest/operations/upgrade-from-0x.md
+++ b/docs-site/content/kagent/latest/operations/upgrade-from-0x.md
@@ -62,7 +62,7 @@ Export your resources before you uninstall 0.10.x. Some resources convert to 1.0
 
 3. If you install 1.0 on the same cluster, uninstall 0.10.x now. For the steps, see [Uninstall kagent]({{< link path="operations/uninstall#uninstall-with-helm" version="0.x" >}}) in the 0.x documentation.
 
-## Install kagent 1.0
+## Install kagent 1.0 {#install}
 
 Install 1.0 against the empty database that you provisioned. kagent and Agent Substrate both store their state in that database, each with an owner login that applies migrations and a read/write login that serves runtime queries. `kagent install` normally creates a development database for both. When you pass `--skip-database-setup`, `kagent install` does not create the development database. The kagent and Agent Substrate charts then read the connection Secrets that you create in this section.
 
diff --git a/docs-site/content/kagent/main/operations/operational-considerations.md b/docs-site/content/kagent/main/operations/operational-considerations.md
index a6b66513..d72c6c97 100644
--- a/docs-site/content/kagent/main/operations/operational-considerations.md
+++ b/docs-site/content/kagent/main/operations/operational-considerations.md
@@ -119,7 +119,7 @@ Connections to this database do not use a password. `kagent install` sets `datab
 
 For production, run PostgreSQL outside the cluster's lifecycle so that a kagent uninstall cannot delete the data. kagent requires a new, empty database, and the roles and the schema must exist before the controller starts. kagent ships a `psql` script that creates them.
 
-Agent Substrate connects to the same database with its own owner and read/write logins. The Agent Substrate setup script creates these logins. The Agent Substrate chart reads the connection strings for those logins from the Secrets that its `postgres.ownerConnectionStringSecretRef` and `postgres.readWriteConnectionStringSecretRef` values reference. For a procedure that prepares the database for both, see [Install kagent 1.0]({{< link path="operations/upgrade-from-0x#install-kagent-10" >}}).
+Agent Substrate connects to the same database with its own owner and read/write logins. The Agent Substrate setup script creates these logins. The Agent Substrate chart reads the connection strings for those logins from the Secrets that its `postgres.ownerConnectionStringSecretRef` and `postgres.readWriteConnectionStringSecretRef` values reference. For a procedure that prepares the database for both, see [Install kagent 1.0]({{< link path="operations/upgrade-from-0x#install" >}}).
 
 1. Download the setup script for your kagent version.
 
diff --git a/docs-site/content/kagent/main/operations/upgrade-from-0x.md b/docs-site/content/kagent/main/operations/upgrade-from-0x.md
index 1beb7d51..53eedd5e 100644
--- a/docs-site/content/kagent/main/operations/upgrade-from-0x.md
+++ b/docs-site/content/kagent/main/operations/upgrade-from-0x.md
@@ -62,7 +62,7 @@ Export your resources before you uninstall 0.10.x. Some resources convert to 1.0
 
 3. If you install 1.0 on the same cluster, uninstall 0.10.x now. For the steps, see [Uninstall kagent]({{< link path="operations/uninstall#uninstall-with-helm" version="0.x" >}}) in the 0.x documentation.
 
-## Install kagent 1.0
+## Install kagent 1.0 {#install}
 
 Install 1.0 against the empty database that you provisioned. kagent and Agent Substrate both store their state in that database, each with an owner login that applies migrations and a read/write login that serves runtime queries. `kagent install` normally creates a development database for both. When you pass `--skip-database-setup`, `kagent install` does not create the development database. The kagent and Agent Substrate charts then read the connection Secrets that you create in this section.