Instead, use a precise term like platform-independent. Do not shorten or use variations of these terms. advertised route priority Okay to also use base advertised route priority when discussing If it's the name of a UI label or other element.Īdministrator In Android documentation, don't use. ![]() Only use admin in Android documentation or "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 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. 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, When referring to generic 2-step verification, use lowercase. 2-Step Verification When referring to Google's 2-Step Verification, use For more information, see Headings and titles. 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. +1's, +1'ing, +1'ed & (ampersand) Don't use & instead of and in headings, text, navigation, or Numbers and Symbols + OK to use + with numbers in text, such as customer records with 300+ demographicĪttributes, except in formal contexts. If such a term appears in code, we recommend that Term might be particularly ambiguous or it might have an offensive or
0 Comments
Leave a Reply. |