diff --git a/docs/toolhive/guides-k8s/deploy-operator-helm.md b/docs/toolhive/guides-k8s/deploy-operator-helm.md
index 6c0ef88f..d8686e5d 100644
--- a/docs/toolhive/guides-k8s/deploy-operator-helm.md
+++ b/docs/toolhive/guides-k8s/deploy-operator-helm.md
@@ -33,7 +33,7 @@ chart. To install a specific version, append `--version <VERSION>` to the
 command, for example:
 
 ```bash
-helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds --version 0.0.7
+helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds --version 0.0.21
 ```
 
 ## Install the operator
@@ -52,7 +52,7 @@ chart. To install a specific version, append `--version <VERSION>` to the
 command, for example:
 
 ```bash
-helm upgrade -i toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --create-namespace --version 0.1.1
+helm upgrade -i toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --create-namespace --version 0.2.10
 ```
 
 Verify the installation:
@@ -81,7 +81,7 @@ and set a specific ToolHive version, create a `values.yaml` file:
 ```yaml title="values.yaml"
 operator:
   replicaCount: 2
-  toolhiveRunnerImage: ghcr.io/stacklok/toolhive:v0.1.8 # or `latest`
+  toolhiveRunnerImage: ghcr.io/stacklok/toolhive:v0.2.17 # or `latest`
 ```
 
 Install the operator with your custom values:
@@ -222,8 +222,14 @@ kubectl logs -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
 
 ## Upgrade the operator
 
-To upgrade the ToolHive operator to a new version, use the same command you used
-to install it:
+To upgrade the ToolHive operator to a new version, use the same commands you
+used to install it. First, upgrade the CRDs if a new version is available:
+
+```bash
+helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-operator-crds
+```
+
+Then upgrade the operator itself:
 
 ```bash
 helm upgrade toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-operator -n toolhive-system --reuse-values
diff --git a/docs/toolhive/tutorials/vault-integration.mdx b/docs/toolhive/tutorials/vault-integration.mdx
index ff689579..767a2bf0 100644
--- a/docs/toolhive/tutorials/vault-integration.mdx
+++ b/docs/toolhive/tutorials/vault-integration.mdx
@@ -6,11 +6,13 @@ description:
 ---
 
 This tutorial shows how to integrate HashiCorp Vault with the ToolHive
-Kubernetes Operator to securely manage secrets for your MCP servers. Using
-Vault's Agent Injector, you can automatically provision secrets into MCP server
-pods without exposing sensitive data in your Kubernetes manifests.
+Kubernetes Operator to securely manage secrets for your MCP servers. Using the
+[Vault Agent Injector](https://developer.hashicorp.com/vault/docs/deploy/kubernetes/injector),
+you can automatically provision secrets into MCP server pods without exposing
+sensitive data in your Kubernetes manifests.
 
-As an example, we'll be deploying a GitHub MCP server.
+To demonstrate this integration, you will deploy a GitHub MCP server that
+retrieves a GitHub personal access token (PAT) from Vault.
 
 :::info[Prerequisites]
 
@@ -255,7 +257,7 @@ MCP_POD_NAME=$(kubectl get pods -ntoolhive-system \
      -ojsonpath='{.items[0].metadata.name}')
 
 # Verify the Vault Agent wrote the secret file
-kubectl exec -n toolhive-system "$PROXY_POD_NAME" -c toolhive -- \
+kubectl exec -n toolhive-system "$PROXY_POD_NAME" -c vault-agent -- \
     cat /vault/secrets/github-config
 
 # Check that the environment variable is available to the MCP server