diff --git a/apps/docs/content/docs/ai/install-and-connect.mdx b/apps/docs/content/docs/ai/install-and-connect.mdx
index ee820158..126f2268 100644
--- a/apps/docs/content/docs/ai/install-and-connect.mdx
+++ b/apps/docs/content/docs/ai/install-and-connect.mdx
@@ -17,13 +17,13 @@ ProofKit installs several pieces that work together: a FileMaker add-on, a FileM
**Download and run the installer.**
- Before you run it, **fully quit both FileMaker Pro and your coding agent** (Claude Desktop, Cursor, etc.). They must be closed during installation so the new plug-in and integrations register correctly. Then get the installer for your platform:
+ Get the installer for your platform:
The installer sets up the local ProofKit tools and registers integrations for supported coding agents.
- After the installer finishes, **restart both FileMaker Pro and your coding agent** (Claude Desktop, Cursor, etc.) so they load the new ProofKit plug-in and integrations. Skipping this restart is the most common cause of connection failures.
+ When it finishes, **fully restart both FileMaker Pro and your coding agent** (Claude Desktop, Cursor, etc.) so they pick up the new plug-in and integrations. Skipping this restart is the most common cause of connection failures.