Address PR feedback for Virtual MCP documentation

- Change title from "Virtual MCP architecture" to "Understanding Virtual
  MCP Server" to better reflect user-focused content
- Remove specific percentages (90%, 87%) that sound LLM-generated
- Simplify authentication section: reference MCP spec mechanism instead
  of specific implementation details like token exchange
- Update related links to match new title

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: JAORMX

docs/toolhive/concepts/vmcp-architecture.mdx

@@ -1,7 +1,7 @@
 ---
-title: Virtual MCP architecture
+title: Understanding Virtual MCP Server
 description:
-  Understanding what Virtual MCP Server does, why it exists, and when to use it.
+  Learn what Virtual MCP Server does, why it exists, and when to use it.
 ---
 
 This document explains Virtual MCP Server (vMCP), why it exists, and when you
@@ -22,10 +22,10 @@ tools with sensible defaults.
 
 Virtual MCP Server delivers four key benefits:
 
-1. **Reduce complexity**: 10 connections become 1 connection (90% reduction in
-   configuration)
-2. **Speed up workflows**: Parallel execution makes multi-system tasks 5-10x
-   faster
+1. **Reduce complexity**: Many connections become one, dramatically simplifying
+   configuration
+2. **Speed up workflows**: Parallel execution across systems instead of
+   sequential calls
 3. **Improve security**: Centralized authentication and authorization with a
    two-boundary model
 4. **Enable reusability**: Define workflows once, use them everywhere
@@ -39,10 +39,10 @@ own configuration, authentication, and maintenance. vMCP aggregates all backends
 into one endpoint with automatic conflict resolution.
 
 **Example scenario**: An engineering team needs access to 8 backend servers
-(GitHub, Jira, Slack, Confluence, PagerDuty, DataDog, AWS, Internal Docs).
+(GitHub, Jira, Slack, Confluence, PagerDuty, Datadog, AWS, Internal Docs).
 Instead of configuring 8 separate connections, they configure one vMCP
-connection with SSO. The result is 87% less configuration complexity and easier
-onboarding for new team members.
+connection with SSO. This significantly reduces configuration complexity and
+makes onboarding new team members much easier.
 
 When multiple backends have tools with the same name (for example, both GitHub
 and Jira have `create_issue`), vMCP automatically prefixes them:
@@ -100,16 +100,15 @@ are centralized in the vMCP configuration.
 
 Different auth is needed for clients versus backends, and managing credentials
 across multiple systems is complex. vMCP implements a two-boundary auth model
-where clients use SSO and vMCP handles per-backend authentication.
+that separates these concerns.
 
-**How it works**: Engineers authenticate once with your identity provider (Okta,
-Google, Microsoft Entra ID). vMCP exchanges their token for backend-specific
-tokens (GitHub, Jira, Slack), each with appropriate scopes. Revoking access is
-simple: disable the user in your IdP and all backend access is revoked
-instantly.
+**How it works**: Clients authenticate to vMCP using the mechanism defined in
+the MCP specification. vMCP then handles authentication to each backend MCP
+server independently. Revoking access is simple: disable the user in your
+identity provider and all backend access is revoked instantly.
 
-This approach provides single sign-on for users, least-privilege token scoping
-per backend, centralized access control, and a complete audit trail.
+This approach provides single sign-on for users, centralized access control, and
+a complete audit trail.
 
 ## When to use vMCP
 
@@ -130,9 +129,9 @@ per backend, centralized access control, and a complete audit trail.
 ## Summary
 
 Virtual MCP Server transforms MCP from individual servers into a unified
-orchestration platform. The use cases range from simple aggregation (90% less
-configuration) to complex workflows with approval gates (5-10x faster
-execution), making it valuable for organizations at any scale.
+orchestration platform. The use cases range from simple aggregation to complex
+workflows with approval gates, making it valuable for teams managing multiple
+MCP servers.
 
 ## Related information
 

docs/toolhive/guides-vmcp/intro.mdx

@@ -60,5 +60,5 @@ flowchart TB
 
 ## Related information
 
-- [Virtual MCP architecture](../concepts/vmcp-architecture.mdx)
+- [Understanding Virtual MCP Server](../concepts/vmcp-architecture.mdx)
 - [Quickstart: Virtual MCP](../tutorials/quickstart-vmcp.mdx)

docs/toolhive/tutorials/quickstart-vmcp.mdx

@@ -151,7 +151,7 @@ Next steps:
 - [Configure authentication](../guides-vmcp/authentication.mdx) for production
 - [Customize tool aggregation](../guides-vmcp/tool-aggregation.mdx) with
   filtering and overrides
-- [Learn about Virtual MCP architecture](../concepts/vmcp-architecture.mdx)
+- [Understanding Virtual MCP Server](../concepts/vmcp-architecture.mdx)
 
 ## Troubleshooting