Fix documentation inconsistency in sub-models example

[Copilot]

This PR fixes the inconsistency in the sub-models documentation where the example showed a sub-model with order 2 ({ PLATFORM, CPUS, RAM, HDD } @ 2), but the explanation and diagram that followed referenced using PICT with order 3 (/o:3).

The inconsistency made the documentation confusing and could lead readers to misunderstand how sub-models function, as noted in issue #95.

Changes made:

• Updated all references to /o:3 in the explanation to /o:2 to match the example
• Updated the diagram to show order = 2 instead of order = 3
• Updated the statistics about test case counts to reflect the correct numbers with /o:2 (approximately 40 test cases with sub-model vs. 17 without)

These changes make the documentation consistent and clearer for readers to understand the impact of using sub-models with PICT.

Fixes #95.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.