- Rewrite/ write the (following) content in a Friendly Professional style.
- Use approachable, inclusive, and clear language that balances warmth with professionalism.
- Write for a mixed audience (developers, designers, QAs, and non-IT staff) — avoid jargon where possible, but do not oversimplify technical details.
- Always use the active voice and direct phrasing.
- Focus on helping the reader succeed by offering practical advice and actionable steps.
- Use short to medium length sentences (avoid long, complex structures).
- Keep the tone welcoming and collaborative, without being casual or playful.
- Avoid slang, sarcasm, or heavy humour.
- Ensure consistency, readability, and accessibility for all users.
- Always follow Oxford English spelling (e.g., organise, recognise, analyse).
- Only use lists or bullet points when the content is naturally a list(e.g., steps, rules, dos/don'ts).
- Friendly but professional — Use clear, warm, approachable language that welcomes and supports the reader, not casual language.
- Inclusive — use language that makes everyone feel welcome. Address the reader directly when appropriate, using “you” and “we” to foster connection.
- Use positive, constructive phrasing to guide and motivate.
- Avoid slang, sarcasm, or heavy humour.
- Active voice (“Do X”, not “X should be done”).
- Short to medium sentences — avoid long or overly complex structures.
- Only use bullet points or lists when the content is naturally a list(e.g., steps, dos, don'ts, comparisons).
- Structure content with clear headings, lists, and logical flow.
- Review for clarity, accuracy, and tone; ensure every sentence adds value.
- Use clear, direct phrasing (no jargon unless explained).
- Keep formatting consistent (headings, lists, code snippets).
- Ensure accessibility (plain language, logical flow).
- Always use Oxford English spelling (e.g., organise, recognise, analyse).
- Use correct grammar and punctuation throughout.
- Overly casual tone (slang, memes, excessive emojis).
- Long, dense paragraphs that are hard to scan.
- Jargon or abbreviations without explanation.
- Switching between styles — keep one consistent voice.
- Does this sound warm and professional at the same time?
- Could someone outside of IT still understand it?
- Are the sentences clear, active, and scannable?
- Am I following Oxford English spelling?