Fix container name for verification step

Signed-off-by: Dan Barr <[email protected]>

Author: danbarr

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