Skip to content

Conversation

cheny0
Copy link
Contributor

@cheny0 cheny0 commented Sep 15, 2025

[✅] Admonitions
[✅] Bullet lists
[✅] Capitalization
[✅] Checkbox lists
[x] Contractions - Do we still want to use contractions to make the text more casual?
[✅] Global language
[✅] Iconography
[✅] Links
[✅] Modal verbs
[✅] Numbered lists
[✅] Numbers
[✅] Other conventions
[✅] Possessive form
[✅] Punctuation
[✅] Sentences and paragraphs
[x] Spelling - Oxford spelling doesn't apply here
[✅] Style conventions
[✅] Symbols and punctuation marks
[✅] Tables
[✅] Titles
[✅] UI elements
[✅] Writing style

@cheny0 cheny0 requested a review from jorge-campo September 15, 2025 08:41
@cheny0 cheny0 self-assigned this Sep 15, 2025
@cheny0 cheny0 added the deliverables Any other project deliverable label Sep 15, 2025
@cheny0 cheny0 linked an issue Sep 15, 2025 that may be closed by this pull request
>
> You can use links in tables except if the table is part of a procedure step.
Use the following guidelines when using periods in a table for punctuation:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Punctuation guidelines edited based on the discussion here: #39

- When the list items are complete sentences, use a period at the end of each sentence.
- Don't use a period when the list items are not complete sentences or sentences with three words or less.
- In a list with elements of more and less than three words mixed, don't use a period.
- If one item in a column is a complete sentence, all items in that column should end with a period, even if they are a single word.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added this rule based on this discussion: #39


- When reading instructions, users understand numbered lists as actions to complete orderly. Because of this, limit the numbered lists to procedural instructions in procedure topics.
- If you must use a numbered list outside of a procedure, use the same rules described for bullet lists.
- Use "1." for all items in a numbered list. This ensures the list renders correctly and simplifies reordering.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added this rule


- Don't use idioms, colloquial expressions, and culture-specific references. When writing examples to clarify a feature or concept, don't use historical references, brand names, social or political events, or any other topic that might be controversial or meaningless for a global audience.
- Observe the style rules for [numbers, date and time, currencies and units of measure](./14-numbers-date-and-time-currencies-and-units-of-measure.md).
- Avoid using *they* to refer to the neutral gender. While this is a perfectly valid rule in English, it may be challenging to interpret by non-native English speakers.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if we should delete this rule. We've used "they" quite a few times

| **Correct** | Go to **Settings > Messages > Privacy**. |
| Incorrect | Go to **Settings**, then go to **Messages**, then tap **Privacy**. |

- Don't describe to users what's happening on the screen, unless the result is unexpected.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content in line 24-42 is from the Status procedure style guide. Because we don't need to emphasize how to describe UI elements in the IFT procedure doc standards, this section is better suited for this content

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deliverables Any other project deliverable

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adapt content from Status style guide

1 participant