Fix final long sentences in best practice and context engineering docs

- Line 107 in best-practice/README.md (27 → 19 + 10 words)
- Line 116 in best-practice/README.md (27 → 12 + 18 words)
- Line 69 in context-enginerring.md (27 → 11 + 20 words)

All sentences now under 25 words for improved readability.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: Phil Whittaker

16/umbraco-cms/reference/developer-mcp/best-practice/README.md

@@ -104,7 +104,7 @@ Use:
 Update the Document Type to include a new "SEO Description" property and apply it to all "Blog Post" nodes.
 
 - **Mention tools or entities by name**
-If you've enabled tools like ```document-type, media, or data-type```, refer to them directly in your prompt to help the model understand what it can access.
+If you've enabled tools like ```document-type, media, or data-type```, refer to them directly in your prompt. This helps the model understand what it can access.
 
 - **Use system instructions or context files for background**  
 Offload rules, terminology, or structural constraints into a dedicated instruction file. This keeps prompts cleaner and context more focused.
@@ -113,5 +113,5 @@ Offload rules, terminology, or structural constraints into a dedicated instructi
 Don’t try to do everything in one prompt. Sequence multi-step operations (e.g., create types → add content → apply relations) across multiple turns for better results.
 
 {% hint style="info" %}
-If a prompt fails or produces a weak result, try these approaches: simplify it, restate it with clearer intent, or reduce the number of active tools.
+If a prompt fails or produces a weak result, try these approaches. Simplify it, restate it with clearer intent, or reduce the number of active tools.
 {% endhint %}

16/umbraco-cms/reference/developer-mcp/concepts/context-enginerring.md

@@ -38,11 +38,11 @@ It’s about curating and managing what gets sent to the model:
 ## Why Context Engineering Is So Important
 
 In the early days of large language models (LLMs), the context of a conversation was straightforward — only your messages and the model's responses.
-Conversations were short and easy to follow, but even then, you could see context drift. As earlier parts of the discussion faded, the model's memory weakened and response quality declined.
+Conversations were short and straightforward to follow, but even then, you could see context drift. As earlier parts of the discussion faded, the model's memory weakened and response quality declined.
 
 Today, however, the landscape has changed dramatically.
 
-Modern AI systems rely on increasingly **complex and layered contexts**, which include far more than just the user conversation. A single MCP-driven interaction may now contain:
+Modern AI systems rely on increasingly **complex and layered context**, which include far more than only the user conversation. A single MCP-driven interaction may now contain:
 
 - A **system prompt** (the invisible instructions defining the model’s role and tone).
 - **Rules or instruction** files that constrain or enhance model behavior.
@@ -66,7 +66,7 @@ In the Umbraco CMS Developer MCP (Model Context Protocol), context engineering i
 This makes requests more effective, efficient, and more likely to succeed. It also makes prompts easier to write, reuse, and maintain.
 
 {% hint style="info" %}
-Think of context engineering as the art of precision storytelling: every piece of information you include should help the model stay on track and deliver value.
+Think of context engineering as the art of precision storytelling. Every piece of information you include should help the model stay on track and deliver value.
 {% endhint %}
 
 Your choice of enabled tools directly shapes the quality of your context.