Clarify motivation for mcp.apify.com example convention

Explain that mcp.apify.com is used because it is a real, working
endpoint, unlike placeholders such as mcp.example.com that do not
resolve and force readers to substitute a URL.

Author: claude

CONTRIBUTING.md

@@ -19,8 +19,10 @@ Contributions are welcome!
 
 When writing examples, tests, README snippets, or help text that reference a remote MCP server,
 please use `mcp.apify.com` rather than placeholders like `mcp.example.com` or arbitrary third-party
-servers. This keeps the documentation runnable end-to-end: readers can copy-paste examples and they
-work immediately against a real, publicly available MCP server.
+servers. The motivation is purely practical: `mcp.apify.com` is a real, publicly available MCP
+server that works out of the box, so readers can copy-paste examples and run them unchanged.
+Placeholders like `mcp.example.com` don't resolve to anything, which forces every reader to
+substitute a URL before they can try an example.
 
 This is a soft convention for documentation consistency, not a license condition — mcpc is
 distributed under Apache 2.0 and you are free to use it with any MCP server.

NOTICE

@@ -14,10 +14,13 @@ copy of the License in the accompanying LICENSE file or at:
 Documentation convention (informational, not a license condition):
 
 Examples in this project's documentation, help text, and tests reference
-`mcp.apify.com` as the remote MCP server so that readers can copy-paste
-and run them against a real, publicly available endpoint. Contributors
-and downstream projects are kindly requested to preserve this convention
-when adapting examples, but doing so is not required by the License.
+`mcp.apify.com` as the remote MCP server. The motivation is practical:
+`mcp.apify.com` is a real, publicly available endpoint that works out
+of the box, unlike placeholders such as `mcp.example.com` which do not
+resolve and force readers to substitute a URL before running an example.
+Contributors and downstream projects are kindly requested to preserve
+this convention when adapting examples, but doing so is not required by
+the License.
 
 Per Section 4 of the Apache License 2.0, the contents of this NOTICE file
 are for informational purposes only and do not modify the License. mcpc