Merge pull request #1340 from juliavs85/prodwriting13

[Docs] Updating content principles and grammar, and index

Author: sarjona

general/contentguidelines/01-productwriting/contentprinciples.md

@@ -6,33 +6,49 @@ tags:
 - UX Writing
 ---
 
-Our content principles help us understand and reinforce our personality, tone and voice. They also help us provide a consistent experience across all our products, services output and any other way we interact with people.
+## Our vision
 
-With everything we write, we aim to:
+We design content experiences that support educators and learners in focusing on what matters most: teaching and learning. We make Moodle feel clear, human, and easy to use, no matter who you are, where you're from, or what you're trying to do.
 
-**Empower** our users to achieve their goals.<br/>
-**Guide** them to make the most out of our products and services.<br/>
-**Educate** them by giving them the exact information they need, plus opportunities to learn more.<br/>
-**Respect** our users, their sensitivity, and time by showing integrity and not patronising them.
+We do this by:
 
-To achieve this, we follow these principles:
+- Making complex functionality feel intuitive and human
+- Designing with accessibility and internationalisation at the core
+- Bringing clarity, consistency, and care to every interaction
+- Embedding content design into product decisions and design
+
+## Our goal
+
+Our content helps users feel confident, supported, and respected. With everything we write, we aim to:
+
+- **Empower** our users to achieve their goals<br/>
+- **Guide** them to get the most from our products and services<br/>
+- **Support** their understanding with just the right information without overwhelming them, plus clear paths to learn more<br/>
+- **Respect** their time, attention, and differences, through integrity, clarity, and care
+
+## Our content principles:
+
+These principles guide every content decision we make. They help us stay consistent, accessible, and aligned across products, services, and all user interactions.
 
 ### Keep it simple
 
-We write in English for a global audience, and want to make our content accessible to everyone.
+We write in plain English for a global audience. Our goal is to make Moodle accessible to everyone.
 
-- Use short sentences and everyday words that our users understand and use.
-- Keep your words direct and to the point.
-- Avoid jargon and idioms that may be difficult to understand with no context.
-- Make instructions clear, actionable and concise.
+- Use short sentences and everyday words that our users understand and use
+- Get straight to the point
+- Avoid jargon, idioms, and culture-specific references
+- Make instructions clear, actionable, and concise
 
 ### Be relevant
 
-Communicate the correct details for a specific situation and no more. Get rid of complicated words and excess information. When we help users focus on the task at hand, they feel safe and empowered.
+We give users the information they need to perform their task and make informed decisions: no more, no less. When users get the right details at the right time, they can stay focused, feel confident, and move forward smoothly.
+
+### Be positive and supportive
 
-### Be positive
+Use language that helps users move forward. Be constructive and encouraging, especially when guiding users through difficult moments.
 
-Tell people what they can or should do instead of what they can't or shouldn't do. If you see lots of 'can't' or 'don't', you may be using negative language.
+- Tell people what they *can* or *should* do
+- Reframe errors and restrictions as helpful guidance
 
 <ValidExample title="Do">
 
@@ -48,7 +64,7 @@ You can't complete this section until you submit your final assignment.
 
 ### Use active voice
 
-Active voice eliminates ambiguity.
+Active voice is clearer and easier to follow.
 
 <ValidExample title="Do">
 
@@ -62,51 +78,17 @@ A deadline can be set by teachers.
 
 </InvalidExample>
 
-### Limit your exclamation points
-
-*When everything is exciting, nothing is exciting*. We save exclamation points for key moments in the user journey; for example when we welcome them on board one of our products for the first time.
-
-### Spell out acronyms the first time you use them
-
-Example: Branded Moodle App (BMA)
-
-### Use sentence case
-
-Use capital letters only at the beginning of sentences and for proper nouns. For headings, subheadings and calls to action, we use sentence case and not Title Case.
-
-<ValidExample title="Do">
-
-Read the full article.
-
-</ValidExample>
-
-<InvalidExample title="Don't">
-
-Read the Full Article.
-
-</InvalidExample>
-
-### Follow the rules of UK/Australian English
-
-Although we have global headquarters, we default to UK/Australian spelling. (Except for communications from Moodle US, which use American spelling to suit their market.)
-
-### Avoid regionally specific date formats
-
-Don't use 13/02/2022 or 02/13/2022. To avoid confusion, write the date as 13 February 2022.
-
-### Words and phrases to avoid
-
-We write with accessibility, inclusivity and diversity in mind. That's why we avoid:
+### Write for inclusion
 
-- Language that reinforces racial, ethnic or religious stereotypes, for example: Use *allowlist* and *denylist* instead of *whitelist* and *blacklist*.
-- Ableist language, for example: Say *amazing*, *awesome*, *shocking* or *intense* instead of *insane* or *crazy*. Say *final check* instead of *sanity check*.
-- Unnecessarily gendered words, for example: Say *people* or *humanity* instead of *mankind*. Say *chairperson* or *chair* instead of *chairman*.
-- Figures of speech that refer to war or violence, for example: Say *try* instead of *take a shot*. Say *near miss* instead of *dodged bullet*
+We write with accessibility, diversity, and respect in mind.
 
-### Use diverse examples
+- Avoid stereotypes, ableist language, and unnecessary gendering. For example, use *final check* instead of *sanity check*, *allowlist* instead of *whitelist*, or *chairperson* instead of *chairman*
+- Choose examples that reflect different cultures, names, and ages
+- Avoid metaphors tied to violence
 
-If you're inventing people or situations, choose different genders and ages. Don't stick to English names.
+### Work together
 
-### Ask for a quick review
+Good content design is a team effort. We share early, welcome feedback, and learn from each other.
 
-If English is not your first language and you feel unsure about the clarity of something you're writing, reach out to a native English speaking team member for support.
+- If you're unsure, especially if English is not your first language, ask a teammate to review your work
+- We support one another in writing clearly and inclusively