Note: This document includes references to terms that Google considers disrespectful or offensive. The terms are listed here to provide usage guidance and alternative terms. If the term you're looking for isn't on this page, then consult the resources on our Other editorial resources page. In general, use the closed form of compound words and words with prefixes; that is, write them without a space or a hyphen. We've included
some common examples of the closed form in the word list, such as dataset, metadata, and predefined, as well as our exceptions for well-established terms that commonly use a hyphen or a space, such as multi-region and style sheet. Additionally, in cases where the noun, verb, and adjective versions of a word are treated differently, we explicitly note the differences. As always, it's fine to deviate from this guidance if that serves your users better. For example, if you determine that the hyphenated version of a term in your domain is more appropriate for your users, it's fine to use that instead. We acknowledge that sometimes there are competing forms of the same word in wide use, especially as new terms emerge, and you might have good reasons for deviating from our guidance. Use the same term consistently throughout your document. Some word list entries include guidance to avoid or don't use a term. Apply this guidance as follows:
Numbers and Symbols+ OK to use + with numbers in text, such as customer records with 300+ demographic attributes, except in formal contexts. +1's, +1'ing, +1'ed 2-Step Verification When referring to Google's 2-Step Verification, use initial caps. When referring to generic 2-step verification, use lowercase. 3D; not 3-DSymbols& (ampersand) Don't use & instead of and in headings, text, navigation, or tables of contents; however, it's OK to use & when referencing UI elements that use &, or in table headings and diagram labels where space constraints require abbreviation. And of course, it's fine to use & for technical purposes in code. For more information, see Headings and titles.Aa and an Use a when the next word starts with a consonant sound, regardless of what letter it starts with. For more information, see Articles (a, an, the). A/B testing abnormal Don't use to refer to a person. OK to use to refer to a condition of a computer system. abort Avoid in general usage. Instead, use words like stop, exit, cancel, or end. In Linux, abort refers to a type of signal that terminates an abnormal process. about versus on When a cross-reference includes information that describes what the cross-reference links to, use about instead of on. Recommended: For more information about indexes, see Managing indexes. Not recommended: For more information on indexes, see Managing indexes. above Don't use for a range of version numbers. Instead, use later. Don't use to refer to a position in a document. Instead, use earlier or preceding. Don't use to refer to a position in the UI. Instead, write instructions that avoid directional language. For more information, see Writing accessible documentation. access (verb) Avoid when you can. Instead, use friendlier words like see, edit, find, use, or view. access token account name Don't use. Instead, use username. actionable Avoid unless it's the clearest and simplest phrasing for your audience. Instead of using it, leave it out or replace it with a phrase like that you can act on or useful. Don't use it in the legal sense without consulting a lawyer. action bar In Android documentation, don't use. Instead, use app bar. ad tech Write out on first mention: advertising technology (ad tech). Don't use adtech or ad-tech. 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 browser. Don't use omnibox. ad hoc Okay to use in database and analytics contexts to mean "free-form" or "user-written" (for example, ad hoc queries or an ad hoc chart). Don't hyphenate or italicize the term. For other contexts, try to find a more specific English equivalent. admin Write out administrator. Only use admin in Android documentation or if it's the name of a UI label or other element. administrator In Android documentation, don't use. Instead, use admin. Okay to also use base advertised route priority when discussing region-to-region costs. Do not shorten or use variations of these terms. agnostic Don't use. Instead, use a precise term like platform-independent. aka Don't use. Instead, write out also known as, or present an alternative term using parentheses or the word or. You can also write out a definition. Recommended: Geographic data, also known as geospatial data, is ... Recommended: Geographic data (geospatial data) is ... Recommended: Geographic data, or geospatial data, is ... all apps screen allowlist (verb), allowlisted, allowlisting Don't use as a verb. Instead, rewrite to improve clarity. OK to use allowlist as a noun. For more information, see blacklist. allows you to Don't use. Instead, use lets you. For more information, see enable. alpha Lowercase except when part of a product name. Recommended: PRODUCT_NAME Alpha Recommended: PRODUCT_NAME is currently in alpha. America, American Use only to refer to the Americas or the American continent. Don't use to refer to the United States. Instead, use a more precise term like the US or the United States, and people in the US. For more information, see US. among See between versus among. AM, PM To be consistent with Material Design, use all caps, no periods, and a space before. Recommended: 9:00 AM Recommended: 10:30 PM and/or Sometimes and/or is the clearest and most efficient way to express something. It's worth considering whether there's a good way to write around it, but it's not worth rewriting so that the text is harder to understand. Android (never android) Android-powered device; not Android device and so on Avoid using and so on whenever possible. For more information, see etc. anti* See Closed compounds and prefixes. any time (noun), anytime (adverb) Recommended: You can change this setting at any time. Recommended: Anytime you want a good video, you can watch YouTube. API Use API to refer to either a web API or a language-specific API. Don't use it when referring to a method or a class. For example, don't write This resource has one API to mean "This resource has one method." API Console; not APIs console or developer console or dev console Short for Google API Console. Use the before the tool name. For more information, see console. API Console key In most contexts, use API key instead of API Console key. In Apps admin APIs, however, it's okay to use API Console key to distinguish from other API keys. API key; not developer key or dev key APIs; not API's APIs Explorer; not API explorer or other variants APK; not .apk app In general, use app instead of application when referring to programs for end users, especially in the context of mobile or web software. In some contexts, such as enterprise software, it's OK to use application to convey a sense of greater complexity. Use application in standard phrases such as application programming interface. app bar Formerly action bar. appendix Use the plural appendixes, not appendices. application See app. argument (command-line context) For general usage, use option. Some command-line tools, such as the gcloud CLI, use argument. For details, see Documenting command-line syntax. as If you mean because, then use because instead of as. As is ambiguous; it can refer to the passage of time. Because refers to causation or the reason for something. as of this writing Avoid because this phrase is implied. The phrase can also prematurely disclose product or feature strategy or inappropriately imply that a product or feature might change. See also currently and presently. Recommended: BigQuery doesn't support that function. Not recommended: As of this writing, BigQuery doesn't support that function. For more information, see Timeless documentation. at scale; not at-scale authentication and authorization In general, use the word authenticated only to refer to users, and authorized only to refer to requests that are sent by a client app on behalf of an authenticated user. A user authenticates that they are who they say they are by entering their password (or giving some other proof of identity). The authenticated user then authorizes the client app to send an authorized request to the server on the user's behalf. When you want to use a preposition with authenticate, use against. authN, authZ Don't use. Instead, use authentication or authorization. auto* See Closed compounds and prefixes. autohealing; not auto-healing auto mode VPC network; not auto mode network autonomous system (AS) autonomous system number (ASN) autopopulate; not auto populate or auto-populate autoscaling; not auto-scaling autotagging; not auto-tagging autoupdate Don't use. Instead, use automatically update. -aware Avoid using as a compound modifier, as in healthcare-aware. OK to use when it is part of a product name, such as Identity-Aware Proxy.Bbackend; not back-end or back end backoff (noun), back off (verb), back-off (adjective) backup (noun), back up (verb), backup (adjective) backward compatible; not backwards compatible bar Avoid when possible. For more information, see foo. base64 Except where it starts a sentence or heading, in which case it's init-capped; or where it's part of a name where it's init-capped. Generally not in code font. However, it is in code font if and only if it's a string literal or otherwise quoted from code. baz Avoid when possible. For more information, see foo. below Don't use for a range of version numbers. Instead, use earlier. Don't use to refer to a position in a document. Instead, use later or following. Don't use to refer to a position in the UI. Instead, write instructions that avoid directional language. For more information, see Writing accessible documentation. It's OK to use below in set phrases such as below (the) average, below the mean, below zero. best effort Avoid where possible. Instead, use more specific wording. After providing a description, you can add a phrase like "sometimes referred to as best effort." beta Lowercase except when part of a product name. Recommended: PRODUCT_NAME Beta Recommended: PRODUCT_NAME is currently in beta. between versus among It's fine to use between when talking about more than two things; however, between isn't interchangeable with among. In particular, use between when you're talking about two or more distinct things: Recommended: JavaScript introduces dependencies between the DOM, the CSSOM, and JavaScript execution. Use among when you're talking about things that are part of a group or things that aren't distinct: Recommended: ... a conventional SQL database that can be shared among multiple apps. More examples: Recommended: Because screen dimensions vary widely among devices (for example, between phones and tablets, and even among different phones), you should configure the viewport so that your pages render correctly on many different devices. Not recommended: Because screen dimensions vary widely between devices (for example, between phones and tablets, and even between different phones), you should configure the viewport so that your pages render correctly on many different devices. Recommended: You can share services among multiple clients. Not recommended: You can share services between multiple clients. See also Grammar Girl's discussion of between and among. BGP Write out on first mention: Border Gateway Protocol (BGP). big data Lowercase. Hyphenate if necessary for clarity. Recommended: MyPlatform is a powerful big-data platform. Not recommended: MyPlatform is a powerful Big Data platform. Not recommended: MyPlatform is a powerful big data platform. big-endian Use lowercase for both words. Hyphenate. Recommended: The codebase currently assumes big-endian byte ordering. Not recommended: The codebase currently assumes Big Endian byte ordering. Not recommended: The codebase currently assumes Big-endian byte ordering. Not recommended: The codebase currently assumes big endian byte ordering. billing charges Avoid using billing charges to mean charges that appear on a bill. Instead, use billed charges. Billing charges means the cost of creating the bill. black-box Avoid using black-box, blackbox, or black box to describe monitoring and testing. Consider using a more precise term for clarity.
Don't use. This phrase is idiomatic.
Ccan Use to convey permission, to refer to an optional action (for example, You can also view logs with the Log Viewer), or to refer to a possible outcome (for example, The process can take 30 minutes). See also could, may, might, must, should, and would. For more about clarifying who's doing what, see Active voice. canary Don't use canary as a verb, and don't use canarying. When possible, avoid jargon like canary and canary testing. If you use one of these phrases, define it on first use or provide a link to the definition, and use it consistently throughout the document. canceled, cancelled Either spelling is OK. For more information about spelling variations, see Spelling. cell phone, cellphone Don't use. Instead, use mobile phone, or if you're talking about more than phones, then use mobile device. It's OK to use phone (without mobile) when the context is clear. cellular data Don't use. Instead, use mobile data. cellular network Don't use. Instead, use mobile network. chapter When referring to documentation that isn't in the form of a book, don't use the term chapter. Instead, refer to documents, pages, or sections. check Don't use to refer to marking a checkbox. Instead, use select. Recommended: Select Automatically check for updates. Not recommended: Check Automatically check for updates. checkbox; not check box chubby Don't use. Instead, use a word that clearly explains what you mean, such as unused or overextended. clear Use (as a verb) to refer to clearing a check mark from a checkbox. Recommended: Clear Automatically check for updates. Not recommended: Uncheck Automatically check for updates. Not recommended: Deselect Automatically check for updates. CLI Don't use CLI generically to refer to a command-line interface. Instead, refer to the specific command-line interface, such as the gcloud CLI. click; not click on When the environment is a desktop with a mouse, use click for most targets, such as buttons, links, list items, and radio buttons. Recommended: Click OK. Not recommended: Click on OK. Hyphenate right-click, left-click, and double-click. When a click or tap action reveals a collapsed list, you can write click to expand or simply expand. It's okay to write click in when referring to a region that needs focus (for example: click in the window), but not when referring to a control or a link. For Android apps, don't use click. Instead, use tap. click here Don't use. For details and alternatives, see Link text. clickthrough (noun), click through (verb) client In REST and RPC API documentation, client is short for client app—that is, the app that the developer is writing. Don't use client as an abbreviation for client library; instead, use library. client ID client secret Cloud Don't use as short for Google Cloud. For generic references such as the cloud or hybrid cloud, use the lowercase form. Cloud console Don't use. Instead, refer to the full name Google Cloud console, or if you aren't discussing any other console (such as the Google Admin console), you can abbreviate to the console after first mention. Use the before the tool name. For more information, see console. Cloud SDK; not Google Cloud SDK co* See Closed compounds and prefixes. codebase; not code base codelab; not code lab For more information, see documentation. cold When possible, avoid jargon like cold failover, cold standby, and cold spare. If you use one of these phrases, define it on first use and use it consistently throughout the document. colocate; not co-locate or colo combo box (noun), combo-box (adjective) command line (noun), command-line (adjective) compile time (noun), compile-time (adjective) compliant, compliance Use with caution. A claim that a product or its output is compliant with a standard is a strong statement. comprise Don't use. Instead, use consist of, contain, or include. config Avoid when possible. Instead, spell out the full word when it's used in a non-code sense: configuration or configuring. Use the verbatim code item name when referring to, for example, a data structure or file with that name. cons Don't use. Instead, use something like disadvantages. console Don't use in isolation. Instead, use the name of the specific console, such as the Google Cloud console or the Google Admin console. Use the before the tool name. After giving a console's full name, you can use a shortened version of the name, such as the Admin console. If you're only discussing the Google Cloud console, after giving the full name you can refer to the console. To refer to a sub-page of a console, use the term page. Container Engine Don't use. Instead, use Google Kubernetes Engine. contents (noun) In its singular form, content can be a noun, adjective, or verb. In its plural form, it's nearly always a noun. In our documentation, we use the noun, so keep it plural. content type Don't use when referring to types such as application/json; instead, use media type. Control+S, Command+S, etc.; not Ctl-S or Cmd-S or Cloverleaf-S To refer to a Control character, use Control+CHARACTER. (In most cases, use an uppercase letter for CHARACTER.) Note that in macOS, many keyboard commands use the Command key instead of the Control key, and there's an Option key instead of an Alt key. If your audience includes macOS users as well as Windows or Linux users, then mention both keyboard commands. Recommended: Control+S (Command+S on Macintosh) Copy and paste Avoid using. Instead explain what to enter into a field and not how. Recommended: Enter the output from the previous step in the Query field. Not recommended: Copy the output from the previous step and paste into the Query field. could Avoid using. Instead, use can where possible. See also can, may, might, must, should and would. For more about clarifying who's doing what, see Active voice. For more information about tenses, see Present tense. CPU All caps. No need to expand the abbreviation on first mention. crazy, bonkers, mad, lunatic, insane, loony Don't use. Instead, use complicated, complex, baffling, strange, or unexpected, and only for inanimate objects. Create a new ... Avoid using unless you need to distinguish the item from another recently created item. Instead, use Create a ... Recommended: Create a project. Not recommended: Create a new project cripple Don't use. Instead, use more precise language. For example, instead of it crippled the server, write it slowed the server down. When referring to people, use terms that specifically describe a physical impairment, such as person with a motor disability; person with a mobility impairment (refers to walking or moving about); person with dexterity impairment (refers to using a standard mouse or keyboard); person who uses a wheelchair, walker, or cane; wheelchair user; person with restricted or limited mobility. cross-site request forgery CSV Don't use a filename extension to refer to a type of file. For example, use CSV file rather than .csv file. For details, see Referring to file types. curated roles Don't use. Instead, use predefined roles. currently Avoid because this word is implied. The word can also prematurely disclose product or feature strategy or inappropriately imply that a product or feature might change. See also as of this writing and presently. Recommended: Windows isn't supported. Not recommended: Windows isn't currently supported. For more information, see Timeless documentation. custom mode VPC network; not custom mode network Cyber Monday Avoid unless explicitly referring to an event in the US. Instead use peak scale event.Ddash A dash (—) is not the same character as a hyphen (-). The characters are used for different purposes. Therefore, don't use the word dash to refer to a hyphen. dashboard Don't use to refer to the Google Cloud console. For more information, see console. Use dashboard not Dashboard unless it's officially part of a product name. data In our usage, data is singular, not plural. Say the data is, not the data are. Also, in our usage, data is a mass noun, not a count noun; for example, say less data rather than fewer data. data center; not datacenter data center campus Use when referring to an entire physical location, which can encompass one or more data centers. data cleaning; not data cleansing data flow (noun); dataflow (noun) If it's possible to replace with the phrase flow of data, then use two words: data flow. If that's not possible, such as when referring to something like stream processing or reactive programming, then use one word: dataflow. dataset; not data set data source; not datasource datastore; not data store data type; not datatype dead-letter queue, dead letter Define on first use, for example dead-letter queue (unprocessed messages queue). deep linking; not deep-linking However, if it would work to replace with linking, then do that. deficient Don't use to refer to a person. OK to use to refer to a condition of a computer system. deformed Don't use to refer to a person. OK to use to refer to a condition of a computer system or inanimate object. demilitarized zone (DMZ) Don't use. Instead, use a more precise term like perimeter network. denigrate Don't use. Instead, use disparage. denylist (verb), denylisted, denylisting Don't use as a verb. Instead, rewrite to improve clarity. OK to use denylist as a noun. For more information, see blacklist. deprecate To deprecate an item is to recommend against the item's use, typically as a warning that the item will soon be unavailable or unsupported. Don't use deprecated to mean removed, deleted, shut down, or turned down. deselect Don't use to refer to clearing a check mark from a checkbox. Instead, use clear. Recommended: Clear Automatically check for updates. Not recommended: Deselect Automatically check for updates. Not recommended: Uncheck Automatically check for updates. desire, desired Don't use. Instead, use a word like want or need. Recommended: Set the value to the size that you want. Not recommended: Set the value to the size that you desire. Not recommended: Set the value to the desired size. destination network address translation (DNAT) Also okay to use destination NAT after first mention. If you do this, include it in the first mention parenthetical: (DNAT or destination NAT). See also NAT. Developers Console Don't use. For more information, see console. Developer's Guide; not Developer Guide or Developers' Guide DevOps Short for development operations. No need to spell out on first mention unless the audience requires it. For more information, see DevOps. dialog Use dialog for the UI element sometimes called a dialog box. Use dialogue only for verbal interaction between people. directory, folder If the context you're documenting (such as an IDE's GUI) uses one term or the other, use that term. If not, then use directory in a command-line context, and folder in a GUI context. When in doubt, default to directory. disable Don't use disable or disabled to describe something that's broken. When describing a user action or the state of a UI element, use a more precise term where possible. You can use inactive, unavailable, deactivate, turn off, or deselect, depending on the context. Use the same term consistently throughout your document. See also enable. disaster recovery Lowercase except when part of a product name, but OK to abbreviate as DR after first use. disclosure triangle, disclosure widget Don't use. Instead, use expander arrow. display (verb) Don't use as an intransitive verb. Display is a transitive verb; therefore, it requires an object. It is often misused in technical documentation, as demonstrated by the following example: Recommended: The Output Directories area appears. Recommended: The Output Directories area is displayed. Not recommended: The Output Directories area displays. The following example demonstrates correct usage of the verb display but means something quite different from the preceding examples. Recommended: The Output Directories area displays the vector image. distributed denial-of-service (DDoS) Hyphenate as shown. On subsequent mention, use DDoS. DNS server policy DNSKEY documentation or document or documents; not doc, docs, article, or topic Within a document, use in this document, and not in this article or in this topic. It's okay to use in this tutorial, in this quickstart, or in this codelab. Recommended: You can find many examples in this document. Not recommended: You can find many examples in this article. Recommended: This document provides guidance about creating tables. Not recommended: This topic provides guidance about creating tables. documentation set; not doc set or docset does not yet Avoid in timeless documentation because this phrase can become outdated. The phrase can also prematurely disclose product or feature strategy or inappropriately imply that a product or feature might change. Recommended: The Google Cloud console doesn't support this IAM role. Not recommended: The Google Cloud console does not yet support this IAM role. For more information, see Timeless documentation. dojo Don't use. Instead, use a precise term that is accurate for the context, such as training or workshop. domain name registrar Domain Name System Security Extensions (DNSSEC) double-tap downscope; not down scope or down-scope Consider using a more descriptive term like constrain scope or reduce scope. Because downscope might not be broadly understood, if you use the term, make sure to define it on first use. Recommended: Reducing the scope of a token helps you follow the principle of least privilege. Recommended (first use): The IAM recommender helps you downscope (reduce the permissions) that are available to your users. drag Use drag, not click and drag and not drag and drop, although you can use drag-and-drop as an adjective. Recommended: Drag the USER to the Authorized box. drop-down; not dropdown In most cases, you can omit drop-down in favor of list or menu. If the omission results in ambiguity, then include drop-down as a modifier. dumb down Don't use. Instead, use a word or phrase what's happening, such as simplify or remove technical jargon. dummy variable Don't use to refer to placeholders. Instead, use placeholder. Also don't use if referring to the concept in statistics known as a dummy variable. Instead, use alternate terms such as indicator variable, design variable, one-hot encoding, Boolean indicator, binary variable, or qualitative variable.Eeach Each refers to every individual item taken individually, not a group of items taken collectively. In other words, each is not a synonym for all. For example, a list of each item is ambiguous; a list of all the items or a list of the items is generally clearer. earlier Use for a range of version numbers, not lower. Recommended: Use version 2.2 or earlier. Not recommended: Use version 2.2 or lower. In Android documentation, don't use earlier for a range of version numbers. Instead, use lower. When referring to a position in a document, use earlier or preceding, not higher. easy, easily What might be easy for you might not be easy for others. Try eliminating this word from the sentence because usually the same meaning can be conveyed without it. ECMP Write out on first mention: equal-cost multipath (ECMP). Do not use as a verb. Recommended: Cloud Router uses ECMP across routes. Not recommended: Cloud Router ECMPs traffic across routes. ecommerce; not e-commerce edge availability domain Don't use edge availability zone, metro availability domain, or metro availability zone. Don't shorten to EAD. e.g. Don't use. Instead, use phrases like for example or such as. Too many people mix up e.g. and i.e. egress When referring to the networking term, use lowercase. either Usage note 1: When using either, use parallel syntax. It's fine to write Do either option 1 or option 2 or Either do option 1 or do option 2, but don't write Either do option 1 or option 2. Usage note 2: We recommend using either only for a choice between two things, not for a choice among multiple things; however, this is a weak recommendation rather than a firm rule. Writing either A or B or C will annoy and distract some readers, but if it's the best phrasing for your situation, then use it. element In HTML and XML, a tag is a component of an element that indicates the start or end of the element. (For example, the <i> start tag indicates the beginning of the <i>example</i> element.) In general, don't use the term tag to refer to an entire element. email; not e-mail or Email or E-mail As of mid-2017, Merriam-Webster dictionaries still prefer e-mail to email. But the AP style manual switched to email in March 2011, and the New York Times switched to email in October 2013. In some contexts, mail is a better choice. Don't use as a verb. Use a specific verb in front of the word. For example, send email. This construction is better for translation and a global audience. emoji Use emoji for both singular and plural forms. See Don't know the difference between emoji and emoticons? Let me explain and What's the Plural of Emoji? enable In procedures, use the appropriate label and action for the UI element that the user interacts with. For turning on or activating an option or feature, use enable or turn on consistently:
Ffail over (verb), failover (noun, adjective) fat Don't use. Instead, use a precise modifier that conveys the appropriate meaning. For example, use high-capacity network connection instead of fat connection or full-featured client instead of fat client. Instead of using fat in a negative sense, such as trim the fat, refer in a more concrete manner to the removal of unused items. OK to use as an acronym when referring to file allocation table (FAT). female adapter Don't use. Instead, use a genderless word like socket. filename; not file name file system; not filesystem fill in; fill out Use fill in when referring to entering information in individual fields. Use fill out when referring to completing an entire form. Recommended: Fill out the questionnaire. Be sure to fill in the required fields. final solution Don't use. Instead, use solution as a stand-alone term or, depending on the context, definitive, optimal, best, or last solution. fintech Write out on first mention: financial technology (fintech). Don't use FinTech or fin-tech. firewalls Don't use in Compute Engine or networking documentation. Instead, use firewall rules. Exception: If you are explaining how firewall rules work, you can explain that every network has an implied virtual distributed firewall. Outside of Compute Engine or networking documentation, the term firewalls is acceptable. first-class, first-class citizen, first class Don't use socially-charged terms for technical concepts where possible. Instead, consider terms such as core feature, built-in, top-level. flag (command-line context) Don't use. Instead, use option. For exceptions to this rule, see Documenting command-line syntax. following It's not necessary to use a noun after following unless it helps provide clarity and enables accessibility. See Tables. Recommended: ... in the following code sample ... Recommended: ... in the following table ... Recommended: ... do the following: ... foo Avoid when possible even though it's a common term in the developer community. Instead, use a clearer and more meaningful placeholder name. for instance Avoid when possible. Instead, use for example or such as. frontend functionality Use with caution. With respect to hardware or software, functionality refers to the set of associated functions or capabilities and how they work. However, the word is sometimes overused, especially when the intended meaning is capabilities or features. future, in the future Avoid in timeless documentation because this word or phrase can become outdated. See also eventually and soon. For more information, see Timeless documentation.GGBps Short for gigabytes per second. By convention, we don't use GB/s. For more information, see Units of measurement. Gbps Short for gigabits per second. By convention, we don't use Gb/s. For more information, see Units of measurement. gcloud CLI After first use of Google Cloud CLI on a page, it's okay to refer to the gcloud CLI, but not simply gcloud. The name is always lowercase, and gcloud is always set in code font. gender-neutral he, him, or his (or she or her) Don't use. Instead, use the singular they (see Jane Austen and other famous authors violate what everyone learned in their English class). Don't use he/she or (s)he or other such punctuational approaches. For more information, see Pronouns. GFE Write out on first mention: Google Front End (GFE). The GFE is an infrastructure service. Okay to use the article the before the term and the abbreviation, and to use the plural (GFEs). For an example in documentation, see Google Front End service. ghetto Don't use. Instead use more precise terms like clumsy, workaround, or inelegant to refer to code that isn't in a production-ready state. GIF Don't use a filetype extension to refer to a type of file. For example, use GIF file rather than .gif file. For details, see Referring to file types. gimp, gimpy Don't use. Instead, use precise, non-figurative language to refer to a deficiency in a component. OK to use in reference to companies, tools, software packages, and other entities that use the term in their names. GKE Write out on first mention: Google Kubernetes Engine (GKE). GKE node Use when first introducing GKE nodes on a given page. For subsequent mentions, you can use node. A GKE node is a worker machine that runs containerized applications and other workloads. The machine is a Compute Engine VM that GKE creates during cluster creation. See also virtual machine (VM) instance. Google, Googling Don't use as a verb or gerund. Instead, use search with Google. Google Account, Google Accounts (capital A) Google API Client Library for LANGUAGE (Java, .NET, etc.) On second and subsequent use, you can abbreviate to LANGUAGE client library. Google API Console; not Google APIs Console OK to shorten to API Console after first use on a given page. Use the before the tool name. For more information, see console. Google Cloud; not GCP, Cloud Platform, or Cloud Google Cloud console If you're only discussing the Google Cloud console, it's OK to shorten to the console after first use on a given page. Use the before the tool name. For more information, see console. Google Cloud project ID; not Cloud project ID or GCP project ID You can also shorten to project ID, but be aware that that term is ambiguous in some contexts. Google Developers Console Don't use. For more information, see console. Google I/O; not I-O or IO Google Play services Google Play services SDK google.dev Lowercase in all contexts, even at the beginning of a sentence. grandfather clause, grand-father clause, grand father clause Don't use. See grandfathered. grandfathered Don't use to refer to something that is allowed to violate a rule because it predates the rule. Instead, use an adjective like legacy or exempt or a verb like made an exception. Recommended: The app is exempt because it was released before the new requirements were announced. Not recommended: The app is grandfathered in because it was released before the new requirements were announced. gray-box Avoid using gray-box, graybox, or gray box to describe testing. To refer to testing that's a combination of clear and opaque testing methods, describe exactly what it's doing. If you need to refer to this type of testing after you describe it, consider using a more precise term for clarity, such as translucent-box testing. grayed-out, greyed-out, gray out, grey out Don't use. Instead, use unavailable. grayhat, greyhat, gray hat, grey hat Don't use. Follow the guidance for black hat when referring to someone violating rules or laws. graylist, greylist, gray list, grey list, gray-list, grey-list Don't use. See blacklist. graylisted, greylisted, gray listed, grey listed, gray-listed, grey-listed Don't use. See blacklist. graylisting, greylisting, gray listing, grey listing, gray-listing, grey-listing Don't use. See blacklist. gsutil Use code font for both the name of the command-line utility and the command. guru If possible, use a more precise term. For example, if you mean expert or teacher, use those terms. guys, you guys When referring to a group of people use non-gendered language, such as everyone or folks. gypsy Don't use. To refer to the people, use Romani, Roma, or Traveller, as appropriate for the specific group you're referring to. In place of metaphorical uses of the term, use more precise phrases.Hhackathon; not hack-a-thon hamburger, hamburger menu Don't use. Instead use the aria-label for that particular icon. For example, menu Menu. For more information, see Buttons and icons. hands off, hands-off Use a less figurative phrase, such as automated. If you're referring to a group that doesn't do anything during a process, write a description. hands on, hands-on Use a less figurative phrase, such as customizable, or write a description of the activity. hang, hung Don't use to refer to a computer or system that is not responding. Instead, use stop responding or not responding. For more information, see Avoid unnecessarily violent language. happiness and satisfaction Use happiness when referring to a customer's perception of a site's reliability. Use satisfaction when referring to whether the site meets the customer's needs. Site reliability engineering (SRE) content generally refers to measuring customer happiness instead of customer satisfaction. The two phrases are not equivalent. The distinction the SRE docs make is between satisfying a need (a dispassionate act) and establishing an emotional response (creating happiness). Although it is difficult to measure happiness precisely, SRE uses service level indicators (SLIs) to quantify user perception. For example, a customer might feel a "need" to watch a show on TV. If the show is available, the customer's need is satisfied. But if playback is slow or choppy, the customer might not be happy. For more information about SRE and measuring reliability, see The Happiness Test. hardcode (verb), hardcoded (adjective) he, him, his Don't use a gendered pronoun except for a specific individual of known gender. Use they and their for the general singular pronoun. healthcare; not health care or health-care health check Use with caution. When describing an action taken for a computer system, only use the term health check if this is the term that appears in the interface. Be certain to remove any ambiguity regarding whether the term refers to health in the medical sense. Use detailed, non-figurative language as much as possible, such as referring to a node being responsive instead of referring to a node being healthy. healthy Don't use. See health check. high availability (noun), high-availability (adjective) Lowercase except when part of a product name, but OK to abbreviate as HA after first use. higher Don't use for a range of version numbers. Instead, use later. Don't use to refer to a position in a document. Use earlier or preceding. Don't use to refer to a position in the UI. Instead, write instructions that avoid directional language. For more information, see Writing accessible documentation. In Android documentation, use higher for a range of version numbers, not later. A release with the highest version number might not be the latest version. For example, if version 2.0 of an operating system receives a bug-fix update after version 3.0 has been released, then version 2.0.1 might be the latest version, even though its version number is lower than 3.0. high performance computing (HPC) Lowercase and no hyphen. hit Don't use as a synonym for click, press, or type. hold the pointer overOnly use this verb phrase in the following cases:
The phrase point to is more common. See also point to. Recommended: In the Admin menu, hold the pointer over File, and then click New. Not recommended: In the Admin menu, hover over File, and then click New. holiday, the holidays Don't use to refer to the end of the year. Instead, refer to specific quarters or months. home screen hostname; not host name hot When possible, avoid jargon like hot failover, hot standby, and hot spare. If you use one of these phrases, define it on first use and use it consistently throughout the document. housekeeping, house keeping, house-keeping Don't use. Instead, use less figurative and more precise terms, such as maintenance and cleanup. hover Don't use. Instead use hold the pointer over. HTTPS; not HTTPsIIaaS Write out on first mention: infrastructure as a service (IaaS). IAM When referring to the Google Cloud product, spell it out on first use: Identity and Access Management (IAM). When referring to UI text, write this term the way it's written in the UI. When referring to the general practice of identity and access management, spell it out in lowercase on first use and include a parenthetical comment: Recommended: Identity and access management (generally referred to as IAM) is the practice of granting the right individuals access to the right resources for the right reasons. ID Not Id or id, except in string literals or enums. In some contexts, best to spell out as identifier or identification. i.e. Don't use. Instead, use phrases like that is. Too many people mix up e.g. and i.e. If Wondering whether to use if or whether? See whether. impact Use only as a noun. Recommended: This issue affects user experience. Acceptable: This issue has an impact on user experience. Not recommended: This issue impacts user experience. index Use the plural indexes unless there is a domain-specific reason (for example, a mathematical or financial context) to use indices. ingest Avoid in most cases when referring to data. Instead, use import or load. ingress When referring to the networking term, use lowercase. When referring to the GKE term or API, capitalize Ingress. in order to If at all possible, don't use in order to; instead, use to. Very occasionally, in order to does clarify meaning or make something easier to read. inline One word as an adjective, inline, not in line or in-line. instance group Don't abbreviate to IG. See also managed instance group. intercluster Use unhyphenated intercluster, not inter-cluster. interconnectAttachment Use when referring to the API. Otherwise, use VLAN attachment. Interconnect connection Only use Interconnect connection relative to a product as follows:
Okay to use connection on subsequent mentions. Jjank Use only to refer to a glitch or problem with graphics that is caused by a loss of data. Avoid using otherwise. janky Use a less figurative term to refer to something of poor or unreliable quality. JPEG Don't use a filename extension to refer to a type of file. For example, use JPEG file rather than .jpg file. For details, see Referring to file types. just Avoid. Usually, just is a filler word that you can delete without affecting your meaning. Recommended: BigQuery skips the row. Not recommended: BigQuery just skips the row. If your meaning is unclear without just, then use a more specific term such as only, instead, or previously, or revise your language to be more specific. (Even if one of these replacement terms fits, you often don't need it.) Recommended: You can execute DML statements in the same way that you'd execute a SELECT statement. Not recommended: You can execute DML statements just as you'd execute a SELECT statement. Recommended: Let a user query only the table without full dataset access. Recommended: Let a user query the table without full dataset access. Not recommended: Let a user query just the table without full dataset access. Sometimes, just is useful for conveying that one approach is simpler than another. In those cases, use just instead of simply. Recommended: Use the namespace ID namespace:example-kind or just example-kind.Kk8s Don't use. Instead, use Kubernetes. KBps Short for kilobytes per second. By convention, we don't use KB/s. For more information, see Units of measurement. Kbps Short for kilobits per second. By convention, we don't use Kb/s. For more information, see Units of measurement. kebab, kabob, kebab menu, kabob menu Don't use. Instead use the aria-label for that particular icon. For example, more_vert More. For more information, see Buttons and icons. kebab case, kabob case, kebab-case, kabob-case Don't use. Instead, use dash-case. key Don't use as an adjective in the sense of crucial or important. If you use key as a noun, specify which kind of key you're referring to on first mention, because there are many kinds of keys in technical contexts. key pair A pair of keys, such as a public key and a private key. Contrast with key-value pair, which refers to a pairing that specifies a value for a variable (as in configuration files). key ring Use instead of keyring (without the space) when referring to a grouping of Cloud KMS keys. key-value pair Use instead of key/value pair or key value pair. kill Avoid when possible. Instead, use words like stop, exit, cancel, or end. For exceptions to this rule, see Documenting command-line syntax.Llame Don't use. Instead, use precise, non-figurative language to refer to a deficiency in a component. later Use for a range of version numbers, not higher. Recommended: Use version 2.2 or later. Not recommended: Use version 2.2 or higher. Not recommended: Use version 2.2+. A release with the highest version number might not be the latest version. For example, if version 2.0 of an operating system receives a bug-fix update after version 3.0 has been released, then version 2.0.1 might be the latest version, even though its version number is lower than 3.0. In Android documentation, don't use later for a range of version numbers. Instead, use higher. When referring to a position in a document, use later or following, not below. latest Avoid in timeless documentation because this word can become outdated. If you must use latest, give the reader a reference point—for example, a version number or release date. Recommended: To help keep your system secure, install the latest version of the tools. Recommended: The June 2021 release includes the latest tools that help secure your system. Not recommended: The product includes the latest tools that help secure your system. For more information, see Timeless documentation. Layer Use capital L; for example, Layer 2, Layer 3, Layer 4, or Layer 7. Don't shorten to L2, L3, and so on. lead-in (noun) learnings Don't use. Don't use directional language. Instead, use navigation menu if referring to applications, and use content navigation menu if referring to navigational elements for documentation. legacy If possible, use a more precise term. If you do use legacy, include or point to a definition to clarify what you mean in the current context. Do not use legacy with any sort of pejorative connotation. let's (as a contraction of let us) Don't use if at all possible. Not recommended: Let's click the OK button now. Letter of Authorization and Connecting Facility Assignment (LOA-CFA) leverage Avoid using if you mean use. If possible, use a more precise term. For example, use, build on, or take advantage of. lifecycle; not life cycle or life-cycle lifetime; not life time or life-time lift and shift; not rehosting or the forklift approach To refer to the idea of migrating an app or workload with no changes or minimal changes, use lift and shift and write an inline definition. For more information and an example, see lift and shift in the Cloud Architecture Center. like versus such as It's okay to use like or such as for comparisons or examples. limits In an API context, often refers to usage limits (number of queries allowed per second or per day). Where possible, best to specify the kind of limit you mean, using terms like usage limit or service limit; the word limit can refer to many different kinds of limits, including rules about acceptable use. See also quota. lint Write both command-line tool name and command in lowercase. Use code font except where inappropriate. little-endian Use lowercase for both words. Hyphenate. Recommended: The codebase currently assumes little-endian byte ordering. Not recommended: The codebase currently assumes Little Endian byte ordering. Not recommended: The codebase currently assumes Little-endian byte ordering. Not recommended: The codebase currently assumes little endian byte ordering. livestream; not live stream load balancing (noun), load-balancing (adjective) lock-in (noun), lock in (verb) lock screen For the verb form, sign in is generally better, but if you're documenting a tool that uses the term log in, then use the term that the tool uses. long press In Android documentation, don't use. Instead, use touch & hold. (Not touch and hold.) lower Don't use for a range of version numbers. Instead, use earlier. Don't use to refer to a position in a document. Instead, use later or following. Don't use to refer to a position in the UI. Instead, write instructions that avoid directional language. For more information, see Writing accessible documentation. In Android documentation, use lower for a range of version numbers, not earlier.MmacOS The operating system formerly known as OS X has been rebranded as macOS. If you're referring to a specific version of the Apple operating system, then use its official name at the time of its release (such as OS X 10.11); but if you're referring to the operating system in general, use macOS. male adapter Don't use. Instead, use a genderless word like plug. man hours, manhours, man-hours Avoid using gendered terms. Instead use terms like person hours. man-in-the-middle (MITM) Avoid using gendered terms. Instead use terms like on-path attacker, person-in-the-middle (PITM). managed instance group (MIG) Okay to abbreviate to MIG on subsequent mention. See also instance group. manmade, man made Avoid using gendered terms. Instead use a word like artificial, manufactured, or synthetic. manned Avoid using gendered terms. Instead use terms like staffed or crewed. manpower, man power, man-power Avoid using gendered terms. Instead use terms like staff or workforce. Markdown Always capitalized, even when you're referring to a nonstandard version. markup (noun), mark up (verb) No hyphen. As a verb, it's two words. master Use with caution. Never use in conjunction with slave. Where possible, replace master with a specific term that is accurate for the context, such as primary, main, original, parent, initiator, driver, controller, manager, mixer, aggregator, publisher, leader, or active.
NN/A; not NA Spell out as not available or not applicable on first reference. name server; not nameserver namespace; not name space native Avoid using native to refer to people. When referring to software products, try to use a more precise term—for example, use built-in to describe a feature that's part of a product. The term native isn't necessarily clear—for example, cloud-native could mean that something was written for the cloud, or that it's built in to a cloud platform, or that it currently exists in a cloud platform. Alternatives to a term like cloud-native could include: modern cloud, born in the cloud, cloud first, and cloud-born. Don't use to refer to a navigation menu. For more information, see Navigation menu. neither Say neither A nor B, not neither A or B. network address translation (NAT) Spell out on first mention. To turn into an adjective, use NAT-translated, or rephrase. Don't use NATted or NAT-ted. See also DNAT and SNAT. network endpoint group (NEG) network interface controller (NIC) network IP address Don't use. Instead, use internal IP address. new, newer Avoid in timeless documentation because this word can become outdated. New also implies that the reader knows the older product and that labeling something as new is therefore meaningful. If you must use new, give the reader a reference point—for example, a version number or release date. Don't use newer to refer to a specific version of a product. Instead, use later. Make sure that you provide a version number or release date by which to understand later. For Android documentation, use higher instead of later. Recommended: The service's network analysis feature reports on network health. Not recommended: Network analysis, a new feature in the service, reports on network health. For more information, see Timeless documentation. ninja Don't use to refer to a person. Instead, use a term such as expert. OK to use in reference to companies, tools, software packages, and other entities that use the term in their names. NLU Write out on first mention: natural-language understanding (NLU). non* See Closed compounds and prefixes. nonce Use with caution: this term has a secondary slang meaning that can cause confusion for global readers. Always define the term on first use, and only use it in specific technical contexts such as authentication and blockchain. In end-user documentation and other contexts, use a more descriptive phrase, such as a number that will be used only once. nonfatal; not non-fatal non-key An exception to our usual preference for closed forms. NoOps Don't use. Instead, use fully managed. If you must include the term, define it at first use with language such as fully managed or no operations, but not non-operational. Do not use noops.For an instruction that does nothing, use no-op or the specific instruction name for your context. NoSQL notification drawer now Avoid when describing features of products or services because this word is implied. If the intent of the text is a comparison between past and present, you can use now—for example, In versions of the tool earlier than 1.10, you could use only the default value, but now you can assign a custom value. Recommended: This feature lets you use combinations of user properties. Not recommended: This feature now lets you use combinations of user properties. For more information, see Timeless documentation. nuke Don't use. Instead use remove or attack. For example, a denial-of-service attack.OOAuth 2.0; not OAuth 2 or OAuth2 or Oauth off-the-shelf, commercial off-the-shelf (COTS) Use more widely understood terms like ready-made, pre-built, standard, or default. OK or okay; not ok or Okay old, older Don't use to refer to a previous version of a product. Instead, use earlier. Make sure that you provide a version number by which to understand earlier. For Android documentation, use lower instead of earlier. Recommended: This functionality doesn't work in versions earlier than 1.17.0. Not recommended: This functionality doesn't work in older versions. For more information, see Timeless documentation. omnibox Don't use. Instead, use address bar. once If you mean after, then use after instead of once. online One word as an adjective, online, not on line or on-line. on-premises; not on prem or on premise or on-premise Use to refer to a customer's resources that they manage in their own facilities. Don't use peer. Hyphenate when used as any part of speech. It can be acceptable to use on-premises as a noun when it would be awkward to repeatedly write out a full phrase like an on-premises environment. However, it's preferable to use the more complete phrase whenever possible. Recommended: An on-premises database Recommended: The database runs on-premises OK: Moving data from on-premises to Google Cloud open source (no hyphen, not even as an adjective or verb) option (in command-line context); not argument or flag or parameter For exceptions to this rule, see Documenting command-line syntax OS Okay to use as a shortening of "operating system." outpost Don't use. Instead, use channel. Recommended: social media channels outside the box, out of the box, out-of-the-box Avoid using in a figurative way. OK to use literally. overview screen In Android documentation, don't use. Instead, use recents screen.PPaaS Write out on first mention: platform as a service (PaaS). page Preferred term when referring to a web page in general, and to a sub-page of a console in particular. parameter In our API documentation, parameter is usually short for query parameter; it's a NAME=VALUE pair that's appended to a URL in an HTTP GET request. In some contexts, however, the term can have other meanings. parent-child or parent/child; not parent – child or parent—child path Avoid using filepath, file path, pathname, or path name if possible. PDF Don't use a filename extension to refer to a type of file. For example, use PDF file rather than .pdf file. For details, see Referring to file types. peer gateway Don't use on-premises gateway when you mean a peer gateway. A peer gateway can be an on-premises device or service or another cloud gateway. peer network Don't use on-premises network when you mean a peer network. A peer network can be an on-premises network or another cloud network. peering zone; not peer zone per To express a rate, use per instead of the division slash (/), unless space constraints require the use of the slash. For more information, see Units of measurement. Avoid per in contexts other than rate units. Recommended: requests per day Recommended: create a policy for each Pod Recommended: according to the style guide Recommended: in response to your request Not recommended: requests/day Not recommended: create a policy per Pod Not recommended: per the style guide Not recommended: as per your request performant Avoid where possible. Instead, use more specific wording. Recommended: an accurate machine learning model Not recommended: a performant machine learning model persist Don't use as a transitive verb, and best to avoid using as a verb at all, especially in passive voice. Recommended: To make the token persistent ... OK: To make the token persist ... Not recommended: The token is persisted ... Not recommended: To persist the token ... persistent disk; not PD Lowercase except at the start of a sentence. personally identifiable information (PII) Some government agencies use the less common term personally identifying information; use this alternate term only in contexts where you are referring to a document that uses this term. pets versus cattle, pets vs. cattle, pets v. cattle Don't use. Instead, use more precise terms like persistent versus dynamic or manually configured versus automated. For more information, see Avoid unnecessarily violent language. plain text (but plaintext in cryptography context) please Don't use please in the normal course of explaining how to use a product, even if you're explaining a difficult task. Also don't use the phrase please note. Use please only when you're asking for permission or forgiveness—for example, when what you're asking for benefits us, inconveniences a reader, or suggests a potential issue with a product. Recommended: If the issue persists, please contact your account representative. For more information, see the style and tone page. plugin (noun), plug-in (adjective), plug in (verb) PM See AM, PM. PNG Don't use a filetype extension to refer to a type of file. For example, use PNG file rather than .png file. For details, see Referring to file types. point to Use to refer to the action of pointing the mouse pointer (focus). This action doesn't imply a length of time waiting for the UI to react to user action. This is similar to the action hold the pointer over (hover). In most cases, it's better to use the verb phrase hold the pointer over because we want the user to wait for the UI to react. POJO If you're not actually writing about a Plain Old Java Object for a Java audience, use simple object. It's acceptable to write a simple object, similar to a POJO in Java if that helps your audience. PoP Acronym for point of presence. Recommended: point of presence (PoP) Not recommended: point of presence (POP) pop-up, popup Don't use. Instead, use dialog to describe a window that appears and asks for, or presents, additional information. Use menu for menus that rise from an interface. populate OK to use if you're writing about a process populating a table or other entity. If you're writing about a person, use fill in. Recommended: The SQL command populates the table with sample data. Recommended: When you have finished filling in the form ... Not recommended: When you have finished populating the form ... port Use listen on (not to). portal Don't use to refer to the Google Cloud console. For more information, see console. possible Don't use possible or impossible to mean you can or you can't. PostgreSQL If the UI uses the name Postgres, it's OK to match the UI. Don't use PostgresSQL. postmortem Avoid in general usage. Instead, use retrospective. In disaster recovery (DR) and DevOps context, use blameless postmortem. practitioner Avoid using without any supporting information to define the roles that you're referring to. Recommended: The framework describes best practices for architects, developers, administrators, and other cloud practitioners. Not recommended: The framework describes best practices for cloud practitioners. pre* See Closed compounds and prefixes. prebuilt; not pre-built precapture; not pre-capture preceding Recommended: ... in the preceding example ... precondition; not pre-condition predefined; not pre-defined preemptible; not pre-emptible or pre-emptive pre-existing; not preexisting preferred pronouns Don't use. Instead, use pronouns. prerecorded; not pre-recorded presently, at present Avoid because this word or phrase is implied. The word or phrase can also prematurely disclose product or feature strategy or inappropriately imply that a product or feature might change. See also as of this writing and currently. Recommended: This setting is required. Not recommended: At present, this setting is required. For more information, see Timeless documentation. press Use when referring to pressing a key or a key combination to cause an action to occur. Also use for mechanical buttons. Use tap for on-screen and soft (capacitive) buttons. Recommended: Press Control+C (or Command+C on Mac). presubmit; not pre-submit primitive Use with caution. Don't use primitive in a disparaging sense. project In Google Cloud documentation, use Google Cloud project on first mention and in any context in which there might be ambiguity about what kind of project you're referring to. property In our API documentation, a property is an element in a resource. For example, a Task resource has properties like kind, id, and title. pros Don't use. Instead, use something else, such as advantages.Qquick, quickly What might be quick for you might not be quick for others. Try eliminating this word from the sentence because usually the same meaning can be conveyed without it. quota In API contexts, often refers to API usage limits. Where possible, best to use a more specific term than quota, such as usage limit; the word quota means many different things to many different people. But in some contexts, such as Google Cloud documentation, the standard term is quota, so use that.Rransomware; not ransom ware RDP Don't use as a verb. Instead, use connect using RDP. Or, if it's clear from context that they're using RDP, then use connect. re* See Closed compounds and prefixes. read-only, not read only Always hyphenate read-only. real time (noun), real-time (adjective), Realtime (as part of product name) Recommended: We report on system health in real time. Recommended: We offer real-time reporting. rebranding, not re-branding recents screen; not overview screen redline Don't use as a verb. Instead, use precise terms appropriate to the context. In the context of editing or providing a review, refer to those actions or to tracking changes. In the context of setting priorities and planning work, refer to those actions or to priority lining. regex Don't use. Instead, use regular expression. repo Don't use. Instead, use repository. Representational State Transfer Don't use. To people unfamiliar with REST, this acronym expansion is meaningless; it's better to refer to it as REST and not bother trying to explain what it theoretically stands for. reservation, off the Don't use. resource record set; not resource recordset response policy zone (RPZ) retarded Don't use. If you are referring to a system or component being slowed, use the word slowed. retriable, triable Don't use retriable or triable, unless a code item uses that spelling. Outside of code font, write around the term. retryable, tryable Where possible, write around retryable and tryable. For example, write out can be tried again or you can try it again. review If you mean "read, potentially for the first time," then use read instead of review. If you mean "read critically, commenting on problems" (as in code review), then review is fine; the usage to avoid is phrasing like If you've never heard of OAuth, then review the OAuth documentation. RFC When referencing an RFC specification, use a space between RFC and the number (for example, RFC 2318). roll out Don't use to mean a sudden or instantaneous launch. If you use roll out, define what you mean. When possible, use a more precise, non-figurative term like gradual, in stages, phases, or progressive. round-trip delay (RTD) round-trip time (RTT) RTFM Don't use. Instead, use something like For more information, see.... runbook; not run book runtime, run time Use the noun runtime when referring to the environment in which software runs, such as a Ruby or Java runtime. Use the noun phrase run time when referring to the time during program execution when something occurs, as contrasted with compile time, for example. Recommended: The profiler collects data at run time, and the scheduler uses this data at compile time to improve performance for subsequent runs. Recommended: The App Engine standard environment has two generations of runtime environments. The second-generation runtimes significantly improve the capabilities of App Engine.SSaaS Write out on first mention: software as a service (SaaS). sane Don't use. Instead use a word like valid or sensible. sanity check Don't use. Instead, use a term like quick check, confidence check, preliminary check or coherence check. SAP Pronounced as the individual letters S, A, P, so write an SAP system, not a SAP system. scale Don't use scale alone to say that something is large or increasing. Include supporting words to indicate magnitude or direction of change in magnitude, whether scaling up or down, such as when you change a machine type to add or remove CPUs or RAM, or scaling out or in, such as adding or removing instances from a group. Recommended: The system performs better at a larger scale. Not recommended: The system performs better at scale. Recommended: The system scales up quickly, but it scales down more slowly. Not recommended: The system scales quickly. screenshot (noun); not screen shot or screensnap Don't use as a verb; instead, use take a screenshot. scroll OK to use scroll as a verb, but if possible, instead use a term that isn't specific to implementation. For example, write go to the section, instead of scroll to the section. If you use scroll, don't use directional language like scroll up. For more information, see Accessibility. Search (as part of product name) Search Console see OK as a general term and when referring to links and cross-references. Our research indicates that language relating to sight is OK for a wide range of readers. For more information, see Link text and cross-references. select Use to describe choosing an item from among multiple options, selecting text, or marking a checkbox. Recommended: Select Automatically check for updates. Not recommended: Check Automatically check for updates. service It's OK to refer to Google products, such as Google Kubernetes Engine or Compute Engine, as services. However, if the term services leads to ambiguity, then use the product names. service level agreement Lowercase when referring to service level agreements in general. It's OK to use title case (Service Level Agreement) when referring to a specific document. OK to abbreviate as SLA after first use. service level indicator OK to abbreviate as SLI after first use. service level objective OK to abbreviate as SLO after first use. setup (noun or adjective), set up (verb) sexy Don't use. Instead, use precise, positive words, such as fast, powerful, or elegant. SHA-1 Not SHA1, except in string literals/enums and in hyphenated phrases such as HSA-SHA1. shall Avoid shall except under advice from a lawyer. For more information, see should. she, her, hers Don't use a gendered pronoun except for a specific individual of known gender. Use they and their for the general singular pronoun. sherpa If possible, use a more precise term. For example, if you mean guide, use that term. shift left In general, avoid using this term to mean moving something earlier in time. Instead, use a less figurative phrase, such as shift earlier or move to an earlier phase. This figurative term relies on the non-universal assumption that the natural flow is from left to right. It's OK to use shift left and shift right in the context of binary multiplication and division. should, should be Generally avoid. Because should is ambiguous by definition, it can be problematic. For example, if you're telling the reader what to do, should implies that the action is recommended but optional, leaving the reader unsure about what to do. Clarify what you mean. Determine if an action is required versus optional, an outcome is expected versus possible, or a state is actual versus recommended.
Ttab When referring to the sub-pages of a console, use page instead of tab. table name Two words. Set specific table names in code font. tablet Tablet is OK. If you don't know whether it's a tablet or a phone, use device. tag See element. tap In Android documentation, use for on-screen and soft (capacitive) buttons. Use instead of click when the environment is definitely a touch device. For mechanical buttons, use press. Use instead of touch. However, touch & hold (not touch and hold) is OK to use. "tap & hold" or "tap and hold" In Android documentation, don't use. Instead, use touch & hold. (Not touch and hold.) tarball Don't use. Instead, use tar file. tar file Don't use a filename extension to refer to a type of file. For example, use tar file rather than .tar file. For details, see Referring to file types. target Avoid using as a verb when possible, especially in reference to people. For some readers, has aggressive connotations. Instead of "targeting" audiences, we try to attract them or appeal to them or make their lives easier. (Using it as an adjective, as in target audience, is probably fine.) Alternatives include terms such as intended for, looking for, focused on, and interacting with. terminate Avoid using as a synonym for stop. Instead, use words like stop, exit, cancel, or end. For a specific context where you can use terminate as a synonym for stop, see Documenting command-line syntax. In some contexts, such as telephony and networking, terminate has specific technical meanings that aren't synonyms for stop; in those contexts, you can use terminate. text box, textbox Don't use. Instead, use box. For more information, see Text box. In Google Cloud documentation, use field instead of box. For example, In the Instance field, specify a value less than 64 characters long. their (singular) they (singular) This is our preferred gender-neutral pronoun. Whether used as singular or plural, it always takes the plural verb. For example, A user authenticates that they are who they say they are by entering their password. See also gender-neutral he. this, that Where possible, put a noun after this or that for clarity. If doing so results in clunky prose, then don't do it; but even then, try thinking about what the noun would be. If you aren't sure what noun this or that refers to, then consider rephrasing. timeframe; not time frame Avoid where possible, or use an alternative such as period, schedule, deadline, or when. But if you do use it, then write it without a space in the middle. timeout (noun), time out (verb) timestamp; not time stamp time to live; not time-to-live Abbreviate as TTL after first use. time zone (noun), time-zone (adjective) tl;dr Don't use. Instead, use something like To summarize, or revise the sentence. touch In Android documentation, don't use. Instead, use tap. However, touch & hold is OK to use. "touch & hold"; not touch and hold touchscreen; not touch screen traditional If possible, use a more precise term. Recommended: Conventionally, Python function names are lowercase, with words separated by underscores. Not recommended: Traditionally, Python function names are lowercase, with words separated by underscores. Recommended: This tutorial explains how to migrate from an on-premises data warehouse to BigQuery. Not recommended: This tutorial explains how to migrate from a traditional data warehouse to BigQuery. transpile; not transcompile tribal knowledge, tribal wisdom Don't use. Instead, use a less figurative term to indicate knowledge held by a group of people. trojan Lowercase when referring to malware. turn on In procedures, use the appropriate label and action for the UI element that the user interacts with. For turning on or activating an option or feature, use turn on or enable consistently. Use the same term consistently throughout your document. Recommended: To turn on Magic Mode, follow these steps. Recommended: You can toggle Magic Mode in the Settings window. tutorial Okay to use. See documentation. type In general, use enter instead of type because there is typically more than one way to enter text than typing (such as pasting text or speaking). typically Use to describe what is usual or expected under normal circumstances. Don't use as the first word in a sentence, as doing so can leave the meaning open to misinterpretation.UUI Don't use generically to refer to a page or dashboard. Use a more specific term like page or console. Recommended: In the Google Cloud console Recommended: On the Cloud Tasks page Not recommended: In the Cloud Tasks UI unarchive Don't use. Instead, use extract. uncheck Don't use to refer to clearing a check mark from a checkbox. Instead, use clear. Recommended: Clear Automatically check for updates. Not recommended: Uncheck Automatically check for updates. Not recommended: Deselect Automatically check for updates. uncompress Don't use. Instead, use extract. under Don't use for a range of version numbers. Instead, use earlier. Don't use to refer to a position in the UI. Recommended: In the Service account ID field, enter a name. Recommended: For Service account ID, enter a name. Not recommended: Under Service account ID, enter a name. Unicode Don't capitalize as UNICODE. Unix-like Unix epoch time Use rather than Unix time or epoch time to refer to a point in time represented as a number of seconds since the Unix epoch (00:00:00 UTC on January 1, 1970), ignoring leap seconds. unselect Don't use. Instead, use clear for checkboxes, and deselect for other UI elements. unsighted Don't use. See blind. untar Don't use. Instead, use extract. unzip Don't use. Instead, use extract. URL All caps. Plural is URLs. Write a URL rather than an URL, because the most common pronunciation starts with a consonant sound. For more information, see a and an. For information about how to style URLs, see the Code in text page. US OK to use as an abbreviation for United States. Don't use U.S. or U.S.A. For more information, see Periods with abbreviations. user base; not userbase username; not user name using Where using might have more than one interpretation, use by using to help clarify the logic of the sentence. Recommended: You can filter for data with specific attributes by using custom filters. Not recommended: You can filter for data with specific attributes using custom filters. UTF Include the hyphen in the names of Unicode encodings, such as UTF-8, UTF-16, and UTF-32. utilize, utilization Use with caution. Don't use utilize when you mean use. It's OK to use utilize or utilization when referring to the quantity of a resource being used. Recommended: When CPU utilization exceeds 75%, the autoscaler adds more CPU resources. Recommended: To distribute network traffic, use a load balancer. Not recommended: To distribute network traffic, utilize a load balancer. v (abbreviating version) Use lowercase. via Don't use. vice versa Don't use. Instead, use a phrase like the other way around, conversely, or otherwise. In some contexts, vice versa is unclear or imprecise because in a complex sentence it's hard to know which two things are swapped with each other. In such cases, make it explicitly clear what two things are swapped. virtual machine (VM) instance Use when first introducing virtual machines on a given page. For subsequent mentions, you can use VM instance or VM. See also GKE node. visually challenged See blind. VLAN attachment Don't use the following: interconnect attachment (VLAN), Interconnect attachment, Cloud Interconnect attachment, or any variation thereof. See also interconnectAttachment. voila Don't use. voodoo Don't use. Instead, use a term like mysterious, complicated, or nondeterministic. vs. Don't use vs. as an abbreviation for versus; instead, use the unabbreviated versus. wake lock (noun), wake-lock (adjective) walkthrough; not walk-through war room, warroom, war-room Don't use. Instead, use a more precise term to describe the activity or team. Depending on context, possible alternatives include rapid response team, situation response team, situation room, incident-management team, or media monitoring room. warm When possible, avoid jargon like warm failover, warm standby, and warm spare. If you use one of these phrases, define it on first use and use it consistently throughout the document. web (lowercase) web application firewall (lowercase) webmaster, web master Don't use. Instead, use a more precise term to describe the specific role, such as website owner, website administrator, web content manager, owner of a site. web page; not webpage But where possible, avoid both by using page. web server; not webserver website (lowercase w); not web site whether while Don't use to indicate a contrast. Instead, use a more precise term, such as although. OK to use to refer to a period of time. white-box Avoid using white-box, whitebox, or white box to describe monitoring and testing. Consider using a more precise term for clarity.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates. Last updated 2022-09-02 UTC. [{ "type": "thumb-down", "id": "missingTheInformationINeed", "label":"Missing the information I need" },{ "type": "thumb-down", "id": "tooComplicatedTooManySteps", "label":"Too complicated / too many steps" },{ "type": "thumb-down", "id": "outOfDate", "label":"Out of date" },{ "type": "thumb-down", "id": "samplesCodeIssue", "label":"Samples / code issue" },{ "type": "thumb-down", "id": "otherDown", "label":"Other" }] [{ "type": "thumb-up", "id": "easyToUnderstand", "label":"Easy to understand" },{ "type": "thumb-up", "id": "solvedMyProblem", "label":"Solved my problem" },{ "type": "thumb-up", "id": "otherUp", "label":"Other" }] |
Use the key terms list to complete the sentences that follow: a an is not used for hosts on the internet.
Postagens relacionadas
direito autoral © 2024 temalgum Inc.
