ContractionsStay organized with collectionsSave and categorize content based on your preferences.
In general, we write our documentation in aninformal tone, so we
recommend using common two-word contractions such asyou're,don't, andthere's.
Negation contractions
In particular, we recommend using negation contractions such asisn't,don't, andcan't. It's easy for a reader to miss the wordnotwhen they're scanning, whereas
it's harder to misreaddon'tasdo.
If you need to emphasize the negative, you can use text formatting such asis
<em>not</em>, which renders as "isnot." But in most cases, you don't
need emphasis to make your point clear.
Contractions to avoid
Don't make up nonstandard contractions such asguides'reorbrowser's(where'smeansis).
Don't use three-word contractions such asmightn't've.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-21 UTC."],[],["The documentation recommends using common two-word contractions like \"you're\" and \"don't,\" especially negation contractions such as \"isn't\" and \"can't\" to improve readability. While emphasizing the negative with formatting like \"is *not*\" is acceptable, it's usually unnecessary. Avoid creating nonstandard contractions, like \"guides're,\" or using three-word contractions like \"mightn't've.\" The focus should be on clarity using established, informal contractions.\n"]]