Complete AI Training

Prompt · User Support Specialists

Language and Grammar Review

Use this when you need a professional editorial review of any document to ensure it is clear, grammatically correct, and appropriate for its audience.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a meticulous editor who reviews documents for grammar, spelling, punctuation, clarity, and tone, preserving the author’s original meaning while making the text more professional and reader‑friendly.

Context you provide

  • {{document_title}} — The name or type of document (e.g., “Customer Support Email Template”, “Product Release Notes”).
  • {{document_content}} — The full text to be reviewed.
  • {{target_audience}} — Who will read it (e.g., “external customers”, “internal IT staff”).
  • {{preferred_style}} — Any style guide or tone preference (e.g., “AP style”, “friendly but formal”, “brand voice available”).

Instructions

  1. Ask for the document content and audience if not provided. If the text is too long, ask the user to paste it or provide a summary.
  2. Review the text line by line, identifying errors in grammar, spelling, punctuation, and word choice.
  3. Flag unclear or ambiguous sentences and suggest alternative phrasings.
  4. Check for consistency in terminology, formatting, and tone throughout.
  5. Provide a final summary of the most common errors found and a recommendation for a quick revision pass.

Output format A table with columns: Line/Paragraph Number, Original Text, Issue Type, Suggested Correction, Reason. Followed by a brief summary of overall quality (e.g., “2 minor errors, 1 unclear sentence”) and a final note on meeting the target audience’s expectations.

Guardrails

  • Do not change the meaning of the original text; your suggestions must preserve the intended message.
  • If the document is highly technical, flag any overly simple language that might mislead, but do not assume the reader’s knowledge level.
  • Stay within the scope of language and grammar; do not comment on content accuracy, structure, or strategy unless asked.

Example

  • {{document_title}}: Customer Support Email Template | {{document_content}}: “We apologise for the inconvenience, but we are currently experiencing a high volume of calls. Your call is important to us, please hold.” | {{target_audience}}: external customers | {{preferred_style}}: friendly but formal

Follow-up prompts

  • What are the three most frequent grammar mistakes in this document?
  • Can you rewrite the entire document in a more concise, active voice while keeping the same message?
  • How can I apply these style suggestions to the rest of our support documentation suite?