Correct wording about client compatibility

Fixed the description to accurately reflect:
- Structured Content: For older clients with structured content display and MCP protocol compliance
- Embedded JSON in Text: For newer clients with structured content display issues

This matches the actual technical situation where older clients properly display structured content while newer clients have display issues with structured content.

Author: xplusplusai

CHANGELOG.md

@@ -16,8 +16,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Technical Details
 - Maintains backward compatibility with both older and newer Cursor IDE versions
-- Structured content available for MCP-compliant clients
-- Embedded JSON in text content for clients with structured content display issues
+- Structured content available for older clients with structured content display and MCP protocol compliance
+- Embedded JSON in text content for newer clients with structured content display issues
 - Fixed fullLocalPath usage instructions
 
 ### ⚠️ Compatibility Note

README.md

@@ -33,8 +33,8 @@ Transform your F&O development workflow with AI-powered semantic search over 50,
 
 **Cursor IDE Compatibility**: This version temporarily returns search results in **two formats simultaneously** to ensure compatibility across all Cursor IDE versions:
 
-1. **Structured Content** - For MCP protocol compliance and newer clients
-2. **Embedded JSON in Text** - For older clients with structured content display issues
+1. **Structured Content** - For older clients with structured content display and MCP protocol compliance
+2. **Embedded JSON in Text** - For newer clients with structured content display issues
 
 This dual-format approach ensures the MCP server works reliably with both legacy and current Cursor IDE installations. Future versions may optimize this once MCP client standardization improves.