Issue

Technical terms in prompt files (e.g., FastMCP, @mcp.tool) were inconsistently formatted with single quotes instead of markdown backticks, leading to improper rendering and pronunciation issues. Single-quoted terms appeared as plain text rather than highlighted code, causing visual inconsistencies and mispronunciation during text-to-speech processing.

Culprit

The use of single quotes for technical terms violated markdown standards, where backticks are required for inline code formatting. This discrepancy caused terms to render incorrectly in markdown viewers and introduced inconsistencies with the rest of the generated documentation.

Solution

A standardized update was applied to replace single-quoted technical terms with backtick-wrapped terms across all prompt files. This ensured consistent rendering and improved readability while maintaining the intended semantic meaning of highlighted code components.