Update docs/toolhive/tutorials/custom-registry.mdx

Co-authored-by: Dan Barr <[email protected]>

Author: rdimitrov

docs/toolhive/tutorials/custom-registry.mdx

@@ -110,20 +110,19 @@ Create a new file called `registry.json` and add the following content:
 }
 ```
 
-This registry defines:
+This registry contains two types of server configurations:
 
-- A single MCP server called `my-fetch` in the top-level `servers` section
-- A group called `dev-toolkit` with its own independent server called
-  `fetch-tool`
+- A standalone MCP server called `my-fetch` in the top-level `servers` section
+- A group called `dev-toolkit` containing a `fetch-tool` server
 
-Groups are optional - you can omit the entire `groups` section if you only need
-individual servers. Groups are independent entities that contain their own
-complete server definitions. The `dev-toolkit` group includes a `fetch-tool`
-server that's similar to the top-level `my-fetch` server but with different
-configuration (different user agent, different allowed hosts for development
-purposes).
+The `dev-toolkit` group demonstrates how you can organize related servers
+together. When you run this group later, you'll be able to start multiple
+servers as a single unit—perfect for development workflows or team-specific
+toolsets. Notice how the `fetch-tool` server has a different user agent and
+network permissions than `my-fetch`, showing how you can customize servers
+within groups for specific purposes.
 
-Each server definition includes:
+Your server configurations include everything ToolHive needs to run them:
 
 - A description explaining its purpose
 - The container image to use