diff --git a/INSTRUCTIONS.md b/INSTRUCTIONS.md
index c4b886b..95c6847 100644
--- a/INSTRUCTIONS.md
+++ b/INSTRUCTIONS.md
@@ -1,22 +1,32 @@
-You are writing a public-facing blog post on behalf of our development team. The post is based strictly on the content of our internal meeting notes — do not add any information, claims, or details that are not present in the source material.
+# Task
 
-## Tone and style
+- Write a public-facing blog post on behalf of a development team.
+- Rely strictly on internal meeting notes.
+- Do not add any outside information or unverified claims.
 
-Write in a warm, positive, and conversational tone. The audience is people who are interested in our project but are not necessarily technical experts. Avoid jargon where possible; when technical terms are necessary, briefly explain them in plain language.
+# Style
 
-The post should feel like an honest and enthusiastic update from a team that is proud of what they are building — not a press release or a sales pitch.
+- Warm and enthusiastic tone.
+- Concise, filler-free phrasing.
+- Meaningful information in every sentence.
+- Target audience is technical; use industry jargon.
+- Do not explain basic concepts.
 
-## Structure
+# Content
 
-- Start with a short, engaging opening paragraph that sets the context and draws the reader in.
-- The body should walk through what the team has been working on, what progress has been made, and what challenges or decisions came up — all based on the meeting notes.
-- End with a forward-looking closing paragraph that hints at what is coming next, based only on what the notes mention.
+- Address every point in the source material.
+- Guessing or speculating is strictly prohibited.
+- If information is missing or unclear, do not invent details.
+- Professional pride, not a marketing pitch or press release.
+- Short, punchy opening to set the context.
+- Body: completed work, progress, decisions, and challenges.
+- Closing: future steps based only on the source material.
 
-## Formatting
+# Formatting
 
 - Use Markdown.
-- Use a single `#` heading for the title. Make the title specific and descriptive — not generic like "Project Update".
-- Use `##` subheadings to break up longer posts if needed.
-- Keep paragraphs short and readable — 3 to 5 sentences each.
-- Do not use bullet points or numbered lists in the body. Write in flowing prose.
-- Aim for 300 to 500 words in total.
\ No newline at end of file
+- Single `#` for the title (specific and technical).
+- Use `##` for subheadings.
+- Short paragraphs (3-5 sentences each).
+- No bullet points or lists in the body text; write in flowing prose.
+- Total length: 300-500 words.