Fix editorial issues across index and intro pages

danbarr · claude · danbarr · commit 58d5e04db0d7 · 2026-03-27T10:06:20.000-04:00
Standardize capitalization of "ToolHive Kubernetes Operator" and
"ToolHive Registry Server" as product names throughout the docs.
Consolidate intro page titles from "Overview" to "Introduction" and
rename redundant "Overview" H2s. Shorten duplicate registry
disambiguation admonition on index page. Fix import placement,
first-person voice, and other minor issues.

Co-Authored-By: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/docs/toolhive/guides-cli/api-server.mdx b/docs/toolhive/guides-cli/api-server.mdx
@@ -13,7 +13,7 @@ The API server isn't intended for production use. It's designed for local
 automation and UI development, and doesn't implement any authentication or
 authorization mechanisms.
 
-For production use cases, consider using the ToolHive Kubernetes operator, which
+For production use cases, consider using the ToolHive Kubernetes Operator, which
 provides a more robust and secure way to manage ToolHive instances in a
 multi-user environment.
 
diff --git a/docs/toolhive/guides-k8s/index.mdx b/docs/toolhive/guides-k8s/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Using the ToolHive Kubernetes Operator
 description:
-  How-to guides for using the ToolHive Kubernetes operator to run and manage MCP
+  How-to guides for using the ToolHive Kubernetes Operator to run and manage MCP
   servers.
 ---
 
diff --git a/docs/toolhive/guides-k8s/intro.mdx b/docs/toolhive/guides-k8s/intro.mdx
@@ -1,21 +1,22 @@
 ---
-title: Overview
-description: How to manage MCP servers in Kubernetes with the ToolHive operator
+title: Introduction
+description:
+  How to manage MCP servers in Kubernetes with the ToolHive Kubernetes Operator
 ---
 
-The ToolHive Kubernetes operator manages MCP servers in Kubernetes clusters. It
+The ToolHive Kubernetes Operator manages MCP servers in Kubernetes clusters. It
 lets you define MCP servers as Kubernetes resources and automates their
 deployment and management.
 
 :::info
 
 See the [ToolHive Operator quickstart tutorial](./quickstart.mdx) to get started
-quickly using a local kind cluster. We'd love for you to try it out and send
-feedback!
+quickly using a local kind cluster. Try it out and
+[share your feedback](https://discord.gg/stacklok)!
 
 :::
 
-## Overview
+## How the operator works
 
 The operator introduces new Custom Resource Definitions (CRDs) into your
 Kubernetes cluster. The primary CRDs for MCP server workloads are `MCPServer`,
diff --git a/docs/toolhive/guides-k8s/quickstart.mdx b/docs/toolhive/guides-k8s/quickstart.mdx
@@ -2,14 +2,14 @@
 title: 'Quickstart: ToolHive Kubernetes Operator'
 sidebar_label: Quickstart
 description:
-  Learn how to deploy the ToolHive Kubernetes operator and use it to manage MCP
+  Learn how to deploy the ToolHive Kubernetes Operator and use it to manage MCP
   servers in a Kubernetes cluster.
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import ThemedImage from '@theme/ThemedImage';
 
-In this tutorial, you'll learn how to deploy the ToolHive Kubernetes operator
+In this tutorial, you'll learn how to deploy the ToolHive Kubernetes Operator
 and use it to manage MCP servers in a Kubernetes cluster. By the end, you'll
 have a working operator deployment that automatically manages MCP servers using
 Kubernetes resources.
diff --git a/docs/toolhive/guides-mcp/notion-remote.mdx b/docs/toolhive/guides-mcp/notion-remote.mdx
@@ -84,7 +84,7 @@ thv restart notion-remote
 
 :::note
 
-The ToolHive Kubernetes operator does not currently support remote MCP servers
+The ToolHive Kubernetes Operator does not currently support remote MCP servers
 using dynamic OAuth authentication. Instead, you can run the
 [local Notion MCP server](https://github.com/makenotion/notion-mcp-server) in
 Kubernetes using a static integration key.
diff --git a/docs/toolhive/guides-registry/index.mdx b/docs/toolhive/guides-registry/index.mdx
@@ -15,11 +15,11 @@ It provides a standardized REST API for discovering and accessing MCP servers
 from multiple backend sources, including Kubernetes clusters, Git repositories,
 API endpoints, and local files.
 
-:::note[Registry Server vs. built-in registry]
+:::note
 
-This is the **Registry Server** — a standalone service for hosting and curating
-your own MCP server catalog. For the built-in registry that ships with ToolHive,
-see [Explore the registry](../guides-cli/registry.mdx) (CLI) or
+This section covers the **Registry Server**, a standalone service you deploy
+yourself. Looking for the built-in registry instead? See
+[Explore the registry](../guides-cli/registry.mdx) (CLI) or
 [Explore the registry](../guides-ui/registry.mdx) (UI).
 
 :::
diff --git a/docs/toolhive/guides-registry/intro.mdx b/docs/toolhive/guides-registry/intro.mdx
@@ -1,12 +1,11 @@
 ---
-title: Overview
-sidebar_label: Introduction
+title: Introduction
 description:
-  How to use the ToolHive Registry server to discover and access MCP servers and
+  How to use the ToolHive Registry Server to discover and access MCP servers and
   skills
 ---
 
-The ToolHive Registry server is a standards-compliant implementation of the MCP
+The ToolHive Registry Server is a standards-compliant implementation of the MCP
 Registry API specification. It provides a REST API for discovering and accessing
 MCP servers from multiple backend sources.
 
@@ -22,7 +21,7 @@ MCP servers from the default catalog. That's a different feature: see
 
 :::
 
-## Overview
+## How the Registry Server works
 
 The Registry server aggregates MCP server metadata from various sources and
 exposes it through a standardized API. When you start the server, it:
diff --git a/docs/toolhive/guides-vmcp/index.mdx b/docs/toolhive/guides-vmcp/index.mdx
@@ -3,6 +3,8 @@ title: Virtual MCP Server
 description: Aggregate multiple MCP servers into a single unified endpoint.
 ---
 
+import DocCardList from '@theme/DocCardList';
+
 ## Introduction
 
 Virtual MCP Server (vMCP) is ToolHive's MCP gateway. It aggregates multiple
@@ -22,6 +24,4 @@ connection.
 
 ## Contents
 
-import DocCardList from '@theme/DocCardList';
-
 <DocCardList />
diff --git a/docs/toolhive/guides-vmcp/intro.mdx b/docs/toolhive/guides-vmcp/intro.mdx
@@ -3,7 +3,7 @@ title: Introduction to vMCP
 description: Understand what Virtual MCP Server (vMCP) does and when to use it.
 ---
 
-## Overview
+## What is vMCP?
 
 Virtual MCP Server (vMCP) is a feature of the ToolHive Kubernetes Operator that
 acts as an aggregation proxy, consolidating multiple backend MCP servers into a
diff --git a/docs/toolhive/integrations/opentelemetry.mdx b/docs/toolhive/integrations/opentelemetry.mdx
@@ -52,7 +52,7 @@ running in Docker containers. This approach is perfect for:
 
 **ToolHive Kubernetes Operator + in-cluster observability**
 
-Use the ToolHive Kubernetes operator to manage MCP servers in a cluster, with
+Use the ToolHive Kubernetes Operator to manage MCP servers in a cluster, with
 Jaeger and Prometheus deployed inside Kubernetes. This approach is ideal for:
 
 - Production-like environments
