Expand on inclusive language and framing in style guide

Author: nimble-turtle

src/content/docs/writing/style.mdx

@@ -124,7 +124,26 @@ But almost every security step also has a usability cost. We never hide that. Na
 "Downsides to using a VPN: You will encounter more CAPTCHAs on websites. Some websites may block VPN access."
 </GoodBad>
 
-### 6. Use plain language
+### 6. Write for everyone in our movements
+
+Our readers are not a monolith. They include undocumented folks, trans and queer organizers, disabled people, parents, elders (lots of folks joining our movements right now are retirees), and people across different races, classes, and religions. Write as if all of them are in the room — not just the reader you most easily picture.
+
+A few concrete habits:
+
+- **Default to "they/them."** Avoid "he/she," "guys," "manpower," "mankind." When using a hypothetical name, vary it rather than defaulting to one kind of person.
+- **Don't assume a single reader profile.** Not every reader is a citizen, has a stable address, uses a newer phone, has reliable internet, or can afford paid tools. Offer free or low-cost paths alongside paid ones.
+- **Name when risks hit some people harder.** A phone search, a border stop, or a doxxing incident carries different weight depending on someone's immigration status, disability, or who they're out to. Call it out where it matters instead of writing a generic "activist."
+- **Check your own assumptions before publishing.** Ask: who is this written for, and who might it accidentally leave out?
+
+<GoodBad tone="good" type="blockquote">
+"If an organizer loses their phone, they should change their passwords right away."
+</GoodBad>
+
+<GoodBad tone="good" type="blockquote">
+"Biometric unlock (like Face ID) can be legally compelled in more situations than a passcode. This matters especially for undocumented folks and anyone attending high-risk actions."
+</GoodBad>
+
+### 7. Use plain language
 
 We use short sentences and everyday language. If a technical term is necessary, we define it immediately, in context. We use contractions ("don't," "won't," "you'll") and parenthetical asides ("yes, we hate Amazon too"). Conversational but not sloppy.
 
@@ -168,7 +187,7 @@ We choose the clearest term as our default — "people search sites" instead of
 - Condescending framings ("it's easy," "simply do X," "just follow these steps")
 - Corporate security language ("implement," "deploy," "leverage," "utilize")
 - Passive voice when describing threats
-- Gendered language
+- Gendered language, or assumptions that don't apply to all readers (citizenship status, income, tech access, ability — see principle 6)
 
 
 ## Content Standards