The division 2 hack lingering menus
"user-written" (for example, ad hoc queries or an ad hoc chart).ĭon't hyphenate or italicize the term. ad hoc Okay to use in database and analytics contexts to mean "free-form" or
add-in not addin add-on not addon address bar Use to refer to the URL bar or the combined URL bar and search box in aīrowser. ad tech Write out on first mention: advertising technology (ad tech).ĭon't use adtech or ad-tech.
#THE DIVISION 2 HACK LINGERING MENUS ANDROID#
action bar In Android documentation, don't use. Instead of using it, leave it out or replace it with a phrase like actionable Avoid unless it's the clearest and simplest phrasing for your audience. Instead, use friendlier words like see,Įdit, find, use, or view. Instead, write instructions that avoidĭirectional language. Don't use to refer to a position in the UI. Don't use to refer to a position in a document. above Don't use for a range of version numbers. about versus on When a cross-reference includes information that describes what theĬross-reference links to, use about instead of on. Signal that terminates an abnormal process. Instead, use words like stop, exit,Ĭancel, or end. OK to use to refer to a condition of a computer system. A/B testing abnormal Don't use to refer to a person. For more information, see Articles (a, an, the). Regardless of what letter it starts with. A a and an Use a when the next word starts with a consonant sound, And of course, it's fine to use &įor technical purposes in code. Tables of contents however, it's OK to use & when referencing UIĮlements that use &, or in table headings and diagram labels where spaceĬonstraints require abbreviation. 3D not 3-D Symbols & (ampersand) Don't use & instead of and in headings, text, navigation, or When referring to generic 2-step verification, use lowercase.
#THE DIVISION 2 HACK LINGERING MENUS VERIFICATION#
Word list # +1's, +1'ing, +1'ed 2-Step Verification When referring to Google's 2-Step Verification, use Make sure to be internally consistent and use the same form throughout yourĭocumentation. Either way, whichever form of a word you choose, Use, especially as new terms emerge, and you might have good reasons forĭeviating from our guidance. We acknowledge that sometimes there are competing forms of the same word in wide Your domain is more appropriate for your users, it's fine to use that instead. For example, if you determine that the hyphenated version of a term in Noun, verb, and adjective versions of a word are treated differently, weĪs always, it's fine to deviate from this guidance if that serves your usersīetter. Well-established terms that commonly use a hyphen or a space, such as Metadata, and predefined, as well as our exceptions for
We've included some commonĮxamples of the closed form in the word list, such as dataset, That is, write them without a space or a hyphen. In general, use the closed form of compound words and words with prefixes If the term you're looking for isn't on this page, then consult the resources Provide usage guidance and alternative terms. Google considers disrespectful or offensive. Note: This document includes references to terms that