diff --git a/docs-site/src/content/docs/getting-started/installation.mdx b/docs-site/src/content/docs/getting-started/installation.mdx
index 369e8fe..714712c 100644
--- a/docs-site/src/content/docs/getting-started/installation.mdx
+++ b/docs-site/src/content/docs/getting-started/installation.mdx
@@ -41,7 +41,7 @@ Install the MCP server, then let it install `ilspycmd` for you. The `install_ils
 pip install mcilspy
 ```
 
-Then ask your AI assistant:
+Then ask your assistant:
 
 > *"Install ilspycmd for me"*
 
@@ -113,7 +113,7 @@ Install the .NET SDK and `ilspycmd` yourself:
 
 ## Verify Installation
 
-Ask your AI assistant to run the installation check:
+Ask your assistant to run the installation check:
 
 > *"Check if ilspycmd is installed correctly"*
 
diff --git a/docs-site/src/content/docs/getting-started/overview.mdx b/docs-site/src/content/docs/getting-started/overview.mdx
index ee027e7..f7d9673 100644
--- a/docs-site/src/content/docs/getting-started/overview.mdx
+++ b/docs-site/src/content/docs/getting-started/overview.mdx
@@ -5,7 +5,7 @@ description: What mcilspy is, how it works, and who it's for.
 
 import { Aside } from "@astrojs/starlight/components";
 
-mcilspy is a [Model Context Protocol](https://modelcontextprotocol.io/) server that gives AI assistants the power to reverse-engineer .NET binaries. It wraps the [ILSpy](https://github.com/icsharpcode/ILSpy) decompiler and [dnfile](https://github.com/malwarefrank/dnfile) metadata parser behind a clean tool interface, letting Claude (or any MCP client) decompile assemblies, search for hardcoded secrets, explore type hierarchies, and recover lost source code.
+mcilspy is a [Model Context Protocol](https://modelcontextprotocol.io/) server for reverse-engineering .NET binaries. It wraps the [ILSpy](https://github.com/icsharpcode/ILSpy) decompiler and [dnfile](https://github.com/malwarefrank/dnfile) metadata parser behind a clean tool interface, letting Claude (or any MCP client) decompile assemblies, search for hardcoded secrets, explore type hierarchies, and recover lost source code.
 
 ## Two Engines, One Interface
 
@@ -24,13 +24,13 @@ mcilspy operates with two complementary backends:
 
 ## What Is MCP?
 
-The [Model Context Protocol](https://modelcontextprotocol.io/) is an open standard for connecting AI assistants to external tools and data sources. Instead of copying output between terminals, you describe what you want in natural language and the AI calls the right tools automatically.
+The [Model Context Protocol](https://modelcontextprotocol.io/) is an open standard for connecting language models to external tools and data sources. Instead of copying output between terminals, you describe what you want in natural language and the right tools are called automatically.
 
 mcilspy exposes 16 tools and 2 prompts through MCP, making .NET reverse engineering a conversational workflow:
 
 > *"Search for any hardcoded API keys in MyApp.dll"*
 
-The AI calls `search_strings` and `search_fields` with the right parameters, aggregates the results, and explains what it found — no manual CLI invocation needed.
+The assistant calls `search_strings` and `search_fields` with the right parameters, aggregates the results, and explains what it found — no manual CLI invocation needed.
 
 ## Supported Formats
 
diff --git a/docs-site/src/content/docs/getting-started/quick-start.mdx b/docs-site/src/content/docs/getting-started/quick-start.mdx
index 3d170e8..0c795fa 100644
--- a/docs-site/src/content/docs/getting-started/quick-start.mdx
+++ b/docs-site/src/content/docs/getting-started/quick-start.mdx
@@ -12,7 +12,7 @@ Once mcilspy is installed and configured with your MCP client, you're ready to a
 <Steps>
 1. **Point at an assembly**
 
-   Give your AI assistant a path to any `.dll` or `.exe`:
+   Give your assistant a path to any `.dll` or `.exe`:
 
    > *"Analyze the assembly at /path/to/MyApp.dll"*
 
diff --git a/docs-site/src/content/docs/index.mdx b/docs-site/src/content/docs/index.mdx
index 30de6d8..5f35472 100644
--- a/docs-site/src/content/docs/index.mdx
+++ b/docs-site/src/content/docs/index.mdx
@@ -1,9 +1,9 @@
 ---
 title: mcilspy
-description: Decompile, search, and analyze .NET assemblies with AI assistance via the Model Context Protocol.
+description: Decompile, search, and analyze .NET assemblies through the Model Context Protocol.
 template: splash
 hero:
-  tagline: Decompile, search, and analyze .NET assemblies with AI assistance.
+  tagline: Decompile, search, and analyze .NET assemblies through natural language.
   image:
     file: ../../assets/hero-decompiler.svg
   actions:
@@ -74,7 +74,7 @@ import { Card, CardGrid, Tabs, TabItem } from "@astrojs/starlight/components";
   </TabItem>
 </Tabs>
 
-Then ask your AI assistant:
+Then ask your assistant:
 
 > *"Decompile the LoginService class from this assembly and explain what it does"*
 
diff --git a/docs-site/src/content/docs/reference/prompts.mdx b/docs-site/src/content/docs/reference/prompts.mdx
index f9f0d86..12fddd5 100644
--- a/docs-site/src/content/docs/reference/prompts.mdx
+++ b/docs-site/src/content/docs/reference/prompts.mdx
@@ -5,7 +5,7 @@ description: Two MCP prompts for structured assembly analysis workflows.
 
 import { Aside, Tabs, TabItem } from "@astrojs/starlight/components";
 
-mcilspy includes two [MCP prompts](https://modelcontextprotocol.io/docs/concepts/prompts) that provide structured analysis workflows. Prompts are templates that MCP clients can invoke to guide multi-step analysis -- they tell the AI assistant what tools to call and in what order.
+mcilspy includes two [MCP prompts](https://modelcontextprotocol.io/docs/concepts/prompts) that provide structured analysis workflows. Prompts are templates that MCP clients can invoke to guide multi-step analysis -- they tell the assistant what tools to call and in what order.
 
 ## analyze_assembly