--- url: /foundations/content-design/global-writing/word-choice.md description: >- Global writing is easier to read, understand, and translate. This guidance is for all American English that is localized. --- # Global writing Global writing is easier to read, understand, and translate. This guidance is for all American English that is localized. [Overview](overview.md) · **Word choice** ## Word choice ### Use global examples & explain local references References to local places, holidays, and companies won’t always make sense to global audiences. ::: tip Do ![Empty wishlist screen that references the holidays](/assets/6840f6fe-lvuo362u-1_do.mdAmQqzU.webp) Use generalized, global examples. Most countries and cultures have holidays. ::: ::: danger Don't ![Empty wishlist screen that references Christmas](/assets/4103594c-lvuo41ao-2_don-t.Bz5_NzU_.webp) Don’t call out a specific country or culture’s holiday ::: If it doesn’t make sense to use a global example, explain the reference in the message description so the translator can substitute a locale-specific example. Some instances where local references should be called out include: * Locations * Names (common first names and nicknames) * Currencies * Temperatures * Date formats * Providers (internet and cable) ::: warning Caution ![Empty state that references New York with message description about replacing New York with a well-known city in other languages](/assets/ace8d898-lvuo4v88-3.D0Mv3z8L.webp) Help translators understand the context by adding message descriptions ::: ### Use short, simple sentences Break text into shorter sentences. Use bullets or separate content into sections with headings.  Other languages average at 1.5 times longer than English, so text that’s short may be long when translated. ![2 screens side by side, in English and German](/assets/5255338f-lvuo5uis-4.BN8tKcqP.webp) Many languages, like German, are longer than English ### Avoid abbreviations Abbreviations don’t translate well and can be confusing out of context. Spell things out whenever possible. However, common abbreviations for time are acceptable. ::: tip Do ![Dialog with options that aren’t abbreviated](/assets/11fd0cc2-lvuo6t6b-5_do.B2P0Gypv.webp) Use clear names to refer to things ::: ::: warning Caution ![Dialog with options that are abbreviated](/assets/320f4495-lvuo82rh-6.C-92lqD2.webp) Avoid abbreviations. If they're used, provide their meaning in message descriptions. ::: ### Clarify pronouns Using pronouns, like “it,” can get tricky when translators are working with small, unconnected strings of text and when nouns have genders in many languages. Repeat the noun, or clarify the noun in a message description. ::: tip Do ![Photo app with snackbar that reads “Couldn’t move photo”](/assets/e3514e33-lvuo92qu-7_do.BkKLECaY.webp) Using nouns instead of, or in addition to, pronouns can help clarify future and past user actions ::: ::: danger Don't ![Photo app with snackbar that reads “Couldn’t move it to ‘Travel’ folder because it’s unavailable”](/assets/7c5b5713-lvuoacju-8_don-t.B_cqRhOk.webp) Avoid using pronouns when it’s unclear what nouns they’re referring to, especially when explaining user actions ::: ### Clarify “this” and “that” Don’t start a sentence with "this" or "that" unless it's immediately followed by the noun. When the noun is unclear, the sentence is more difficult to translate. ::: tip Do ![Form with clear writing that doesn’t use “this” or “that”](/assets/7e46a218-lvuobsfb-9_do.CafLnbi8.webp) Make sure it’s clear who text is referring to ::: ::: danger Don't ![Form with a subhead that reads “This can be seen by your IT administrator.” It’s not clear what “this” refers to.](/assets/f2fbefb6-lvuocbnw-10_don-t.0-t6Ry3v.webp) Avoid using “this” and “that” ::: ### Avoid idiomatic, colloquial, and polite expressions Idiomatic or colloquial phrases can be confusing if the meaning isn’t clear. If you use them, clarify the purpose and context of the phrase to help the translator choose an appropriate alternative. Avoid polite expressions, such as “Please,” “Sorry,” and “Thank you,” especially in error messages. However, "please" may be used when asking the user to do something inconvenient. ::: tip Do ![Empty state with illustration that reads “Let’s go”](/assets/d1f23101-m48wnsm6-11_do.OaRMpSFf.webp) Clear, everyday language can be used in an expressive and whimsical way when paired with imagery ::: ::: danger Don't ![Empty state with illustration that reads “Let’s get this party started”](/assets/170bc438-m48wp6t5-12_don-t.BJqTpFhN.webp) Idiomatic phrases can be difficult for everyone to understand and for translators to localize ::: ### Reduce technical jargon Technical terms don't always translate. Descriptions should be simple, and in some cases literal, to avoid confusion when translating. ::: tip Do ![Dialog that prompts people to sign up to try new products](/assets/ba620d07-lvuoeiu1-13_do.CR4rJluN.webp) Plain language is easier for everyone to understand ::: ::: danger Don't ![Wordy and confusing dialog that prompts people to sign up for new communication preferences](/assets/0be50355-lvuoexnd-14_don-t.BWWvE2TS.webp) Confusing language makes it difficult for people to understand the actions they’re taking ::: ### Clarify ambiguities Some words have multiple meanings. For example, “traffic,” “filter,” and “change” can be used as either nouns or verbs. Avoid using both meanings of the word in the same string or body of text. If a word has the potential to be confusing, provide as much context as possible in the message description so the translation will be accurate. ![Screen displaying devices and speakers at home, next to bottom app bar with “home” button](/assets/cf19afb4-lvuoff5i-15.CCcfDLs-.webp) Clarify words that have multiple meanings. “Home” could reference a homepage or where someone lives.