If the term you're looking for isn't on this page, then consult the resources on our Other editorial resources page. Closed compounds and prefixesIn 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. Word listSome 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& (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.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-DAa and anUse 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 testingabnormalDon't use to refer to a person. OK to use to refer to a condition of a computer system.abortAvoid 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 onWhen 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.aboveDon'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 tokenaccount nameDon't use. Instead, use username.actionableAvoid 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 barIn Android documentation, don't use. Instead, use app bar.ad techWrite out on first mention: advertising technology (ad tech). Don't use adtech or ad-tech.add-in; not addinadd-on; not addonaddress barUse to refer to the URL bar or the combined URL bar and search box in a browser. Don't use omnibox.ad hocOkay 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.adminWrite out administrator. Only use admin in Android documentation or if it's the name of a UI label or other element. administratorIn Android documentation, don't use. Instead, use admin.advertised route priorityOkay to also use base advertised route priority when discussing region-to-region costs.Do not shorten or use variations of these terms.agnosticDon'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 screenallowlist (verb), allowlisted, allowlistingDon't use as a verb. Instead, rewrite to improve clarity.OK to use allowlist as a noun.For more information, see blacklist.allows you toDon't use. Instead, use lets you. For more information, see enable. alphaLowercase except when part of a product name.Recommended: PRODUCT_NAME AlphaRecommended: PRODUCT_NAME is currently in alpha.America, AmericanUse 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.amongSee between versus among.AM, PMTo be consistent with Material Design, use all caps, no periods, and a space before.Recommended: 9:00 AMRecommended: 10:30 PMand/orSometimes 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 deviceand so onAvoid 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.APIUse 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 consoleShort for Google API Console. Use the before the tool name. For more information, see console.API Console keyIn 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 keyAPIs; not API'sAPIs Explorer; not API explorer or other variantsAPK; not .apkappIn 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 barFormerly action bar.appendixUse the plural appendixes, not appendices.applicationSee app.argument (command-line context)For general usage, use option. Some command-line tools, such as thegcloud CLI, use argument. For details, see Documenting command-line syntax.asIf 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 writingAvoid 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-scaleIn 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, authZDon't use. Instead, use authentication or authorization.auto*See
Closed compounds and prefixes.autohealing; not auto-healingauto mode VPC network; not auto mode networkautonomous system (AS)autonomous system number (ASN)autopopulate; not auto populate or auto-populateautoscaling;
not auto-scalingautotagging; not auto-taggingautoupdateDon't use. Instead, use automatically update.-awareAvoid 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 endbackoff (noun), back off (verb), back-off (adjective)backup (noun), back up (verb), backup (adjective)backward compatible; not backwards compatiblebarAvoid when possible. For more information, see foo.bare metalbase64Except 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.bazAvoid when possible. For more information, see foo.belowDon'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 effortAvoid where possible. Instead, use more specific wording. After providing a description, you can add a phrase like "sometimes referred to as best effort."betaLowercase except when part of a product name.Recommended: PRODUCT_NAME BetaRecommended: PRODUCT_NAME is currently in beta.between versus amongIt'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.BGPWrite out on first mention: Border Gateway Protocol (BGP).big dataLowercase. 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-endianUse 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 chargesAvoid 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-boxAvoid using black-box, blackbox, or black box to describe monitoring and testing. Consider using a more precise term for clarity.
dos.yaml file.Not recommended: To denylist an IP address, add it to the dos.yaml file.Don't use: To blacklist an IP address, add it to the dos.yaml
file.If the command or code that you're documenting uses one of these words, then use these words only in direct reference to the code items (formatted as code), and make it clear what you're referring to.Recommended: Add a user to the allowlist (whitelist) by entering the following: whitelist
adduser EMAIL_ADDRESS.Not recommended: Add a user to the whitelist by entering the following:
whitelist adduser
EMAIL_ADDRESS.For more information, see the inclusive documentation page.blacklisted, black listed, black-listedSee blacklist.blacklisting, black
listing, black-listingDon't use. See blacklist.blast radiusDon't use. Instead, use a more precise term like affected area or spatial impact.blindAvoid using blind to or blind eye to. Instead, use more precise terms like ignore, unaware of, disregard, avoid,
or reject.Avoid using blind writes. Instead, use a more precise phrase, such as a write operation without a read operation.Avoid using blind change or change blindly. Instead, use a more precise phrase such as change without first confirming the value.When referring to people, use terms like person who is blind, screen reader user (if applicable), person who is visually impaired, person who is
low-vision, magnification user (if applicable).blue-greenWrite blue-green with a hyphen, not blue/green or blue green.BMaaSWrite out on first mention: bare metal as a service (BMaaS).booleanIn most contexts, you're talking about a specific data type in a specific programming language, in which case use code font and the exact spelling and capitalization of the
programming keyword. But when referring to the abstract data type, use lowercase. (In the unlikely event that you refer to Boolean mathematics or Boolean logic, use uppercase.)branding informationIn the API Console and the Google Cloud console, the phrase branding information refers to the information that Google shows to users when the client asks them to authorize access: specifically, the project's name and logo, and the
developer's Google Account. This information is set in the Consent screen page.break-glassDon't use. This phrase is idiomatic.
CcanUse 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.canaryDon'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, cancelledEither spelling is OK. For more information about spelling variations, see Spelling.cell phone, cellphoneDon'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 dataDon't use. Instead, use mobile data.cellular networkDon't use. Instead, use mobile network.chapterWhen 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.checkDon'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 boxchubbyDon't use. Instead, use a word that clearly explains what you mean, such as unused or overextended.clearUse (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.CLIDon't use CLI generically to refer to a command-line interface. Instead, refer to the specific command-line interface, such as thegcloud CLI.click; not click onWhen 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 hereDon't use. For details and alternatives, see Link text.clickthrough (noun), click through (verb)clientIn 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 IDclient secretCloudDon't use as short for Google Cloud. For generic references such as the cloud or hybrid cloud, use the lowercase form.Cloud consoleDon'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 SDKco*See Closed compounds and
prefixes.codebase; not code basecodelab; not code labFor more information, see documentation.coldWhen 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 colocombo box (noun), combo-box (adjective)command line (noun), command-line (adjective)compile time (noun), compile-time (adjective)compliant, complianceUse with caution. A claim that a product or its output is compliant with a standard is
a strong statement.compriseDon't use. Instead, use consist of, contain, or include.configAvoid 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.consDon't use. Instead,
use something like disadvantages.consoleDon'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 EngineDon'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 typeDon'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-STo 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 pasteAvoid 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.couldAvoid 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.CPUAll caps. No need to expand the abbreviation on first mention.crazy, bonkers, mad, lunatic, insane, loonyDon'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 projectcrippleDon'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 forgeryCSVDon'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 rolesDon'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 networkCyber MondayAvoid unless explicitly referring to an event in the US. Instead use peak scale event.DdashA 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.dashboardDon'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.dataIn 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 datacenterdata center campusUse when referring to an entire physical location, which can encompass one or more data centers.
data cleaning; not data cleansingdata 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 setdata source; not datasourcedatastore; not data storedata type; not datatypedead-letter queue, dead letterDefine on first use, for example dead-letter queue (unprocessed messages queue).deep linking; not deep-linkingHowever, if it would work to replace with linking, then do that.deficientDon't use to refer to a person. OK to use to
refer to a condition of a computer system.deformedDon'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.denigrateDon't use. Instead, use disparage.denylist (verb),
denylisted, denylistingDon't use as a verb. Instead, rewrite to improve clarity.OK to use denylist as a noun.For more information, see blacklist.deprecateTo 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.deselectDon'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,
desiredDon'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 ConsoleDon't use. For more information, see console.Developer's Guide; not Developer Guide or Developers' GuideDevOpsShort for
development operations. No need to spell out on first mention unless the audience requires it. For more information, see DevOps.dialogUse dialog for the UI element sometimes called a dialog box. Use dialogue only for verbal interaction between people.directory, folderIf 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.disableDon'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 recoveryLowercase 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 policyDNSKEYdocumentation or
document or documents; not doc, docs, article, or topicWithin 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 docsetdoes not yetAvoid 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.dojoDon't use. Instead, use a precise term that is accurate for the context, such as training or workshop.domain
name registrarDomain Name System Security Extensions (DNSSEC)double-tapdownscope; not down scope or down-scopeConsider 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.dragUse 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 dropdownIn 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 downDon't use. Instead, use a word or phrase what's happening, such as simplify or remove technical jargon.dummy variableDon'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.EeachEach 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.earlierUse 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, easilyWhat 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.ECMPWrite 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-commerceedge availability domainDon'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.egressWhen referring to the networking term, use lowercase.eitherUsage 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.elementIn 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-mailAs 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.emojiUse 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?enableIn 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)fatDon'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 adapterDon't use. Instead, use a genderless word like socket.filename; not file namefile system; not filesystemfill in; fill outUse 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 solutionDon't use. Instead, use solution as a stand-alone term or, depending on the context, definitive, optimal, best, or last solution.fintechWrite out on first mention: financial technology (fintech). Don't use FinTech or fin-tech.firewallsDon'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 classDon'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.followingIt'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: ...fooAvoid when possible even though it's a common term in the developer community. Instead, use a clearer and more meaningful placeholder name.for instanceAvoid when possible. Instead, use for example or such as.frontendfunctionalityUse 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 futureAvoid in timeless documentation because this word or phrase can become outdated.See also eventually and soon. For more information, see Timeless documentation.GGBpsShort for gigabytes per second. By convention, we don't use GB/s. For more information, see Units of measurement.GbpsShort for gigabits per second. By convention, we don't use Gb/s. For more information, see Units of measurement.gcloud CLIAfter 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.GFEWrite 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.ghettoDon't use. Instead use more precise terms like clumsy, workaround, or inelegant to refer to code that isn't in a production-ready state.GIFDon'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, gimpyDon'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.GKEWrite out on first mention: Google Kubernetes Engine (GKE).
GKE nodeUse 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 ConsoleOK 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 CloudGoogle Cloud consoleIf 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 IDYou can also shorten to project ID, but be aware that that term is ambiguous in some contexts.Google Developers ConsoleDon't use. For more
information, see console.Google I/O; not I-O or IOGoogle Play servicesGoogle Play services SDKgoogle.devLowercase in all contexts, even at the beginning of a sentence.grandfather clause, grand-father clause, grand father
clauseDon't use. See grandfathered.grandfatheredDon'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-boxAvoid 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 outDon't use. Instead, use unavailable.grayhat, greyhat, gray hat, grey hatDon'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-listDon't use. See blacklist.graylisted, greylisted, gray listed, grey listed, gray-listed, grey-listedDon't use. See blacklist.graylisting,
greylisting, gray listing, grey listing, gray-listing, grey-listingDon't use. See blacklist.gsutilUse code font for both the name of the command-line utility and the command.guruIf possible, use a more precise term. For example, if you mean expert or teacher, use those terms.guys,
you guysWhen referring to a group of people use non-gendered language, such as everyone or folks.gypsyDon'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-thonhamburger, hamburger menuDon't use. Instead use thearia-label for that particular icon. For example, Menu. For more information, see Buttons and icons.hands off, hands-offUse 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-onUse a less figurative phrase, such as customizable, or write a description of the activity.hang, hungDon'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 satisfactionUse 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, hisDon'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-carehealth checkUse 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.healthyDon'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.higherDon'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.hitDon'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 holidaysDon't use to refer to the end of the year. Instead, refer to specific quarters or months.home screenhostname; not host namehotWhen 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-keepingDon't use. Instead, use less figurative and more precise terms, such as maintenance and cleanup.hoverDon't use. Instead use hold the pointer over.HTTPS; not HTTPsIIaaSWrite out on first mention: infrastructure as a service (IaaS).IAMWhen 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.IDNot 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.IfWondering whether to use if or whether? See whether.impactUse 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.indexUse the plural indexes unless there is a domain-specific reason (for example, a mathematical or financial context) to use indices.ingestAvoid in most cases when referring to data. Instead, use import or load.ingressWhen referring to the networking term, use lowercase. When referring to the GKE term or API, capitalize Ingress.in order toIf 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.inlineOne word as an adjective, inline, not in line or in-line.instance groupDon't abbreviate to IG. See also managed instance group.interclusterUse unhyphenated intercluster, not inter-cluster.interconnectAttachmentUse when referring to the API. Otherwise, use VLAN attachment.Interconnect connectionOnly use Interconnect connection relative to a product as follows:
Okay to use connection on subsequent mentions. JjankUse only to refer to a glitch or problem with graphics that is caused by a loss of data. Avoid using otherwise.jankyUse a less figurative term to refer to something of poor or unreliable quality.JPEGDon'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.justAvoid. 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 aSELECT 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. Kk8sDon't use. Instead, use Kubernetes.KBpsShort for kilobytes per second. By convention, we don't use KB/s. For more information, see Units of measurement.KbpsShort for kilobits per second. By convention, we don't use Kb/s. For more information, see Units of measurement.kebab, kabob, kebab menu, kabob menuDon't use. Instead use thearia-label for that particular icon. For example, More. For more information, see Buttons and icons.kebab case,
kabob case, kebab-case, kabob-caseDon't use. Instead, use dash-case.keyDon'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 pairA 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 ringUse instead of keyring (without the space) when referring to a grouping of Cloud KMS keys.key-value pairUse instead of key/value pair or key value pair.killAvoid when possible. Instead, use words like stop, exit, cancel, or end. For exceptions to this rule, see
Documenting command-line syntax.LlameDon't use. Instead, use precise, non-figurative language to refer to a deficiency in a component.laterUse 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.latestAvoid 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.LayerUse 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)learningsDon't use.left-nav, right-navDon'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) leverageAvoid 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-cyclelifetime; not life time or life-timelift and shift; not rehosting or the forklift approachTo 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 asIt's okay to use like or such as for comparisons or examples.limitsIn 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.lintWrite both command-line tool name and command in lowercase. Use code font except where inappropriate.little-endianUse 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 streamload balancing (noun), load-balancing (adjective)lock-in (noun), lock in (verb)lock screenlogin (noun or adjective), log in (verb)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 pressIn Android documentation, don't use. Instead, use touch & hold. (Not touch and hold.)lowerDon'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.MmacOSThe 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 adapterDon't use. Instead, use a genderless word like plug.man hours, manhours, man-hoursAvoid 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 madeAvoid using gendered terms. Instead use a word like artificial, manufactured, or synthetic.mannedAvoid using gendered terms. Instead use terms like staffed or crewed.manpower, man power, man-powerAvoid using gendered terms. Instead use terms like staff or workforce.MarkdownAlways capitalized, even when you're referring to a nonstandard version.markup (noun), mark up (verb)No hyphen. As a verb, it's two words.masterUse 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 NASpell out as not available or not applicable on first reference.name server; not nameservernamespace; not name spacenativeAvoid 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.navigation barDon't use to refer to a navigation menu. For more information, see Navigation menu.neitherSay 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 addressDon't use. Instead, use internal IP address.new, newerAvoid 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.ninjaDon'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.NLUWrite out on first mention: natural-language understanding (NLU).non*See Closed compounds and prefixes.nonceUse 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-fatalnon-keyAn exception to our usual preference for closed forms.NoOpsDon'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. NoSQLnotification drawernowAvoid 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.nukeDon'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 Okayold, olderDon'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.omniboxDon't use. Instead, use address bar.onceIf you mean after, then use after instead of once.onlineOne word as an adjective, online, not on line or on-line.on-premises; not on prem or on premise or on-premiseUse 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 databaseRecommended: The database runs on-premisesOK: Moving data from on-premises to Google Cloudopen source (no hyphen, not even as an adjective or verb)option (in command-line context); not argument or flag or parameterFor exceptions to this rule, see Documenting command-line syntaxOSOkay to use as a shortening of "operating system."outpostDon't use. Instead, use channel.Recommended: social media channelsoutside the box, out of the box, out-of-the-boxAvoid using in a figurative way. OK to use literally.overview screenIn Android documentation, don't use. Instead, use recents screen.PPaaSWrite out on first mention: platform as a service (PaaS).pagePreferred term when referring to a web page in general, and to a sub-page of a console in particular.parameterIn our API documentation, parameter is usually short for query parameter; it's aNAME=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—childpath
Avoid using filepath, file path, pathname, or path name if possible.PDFDon'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 gatewayDon'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 networkDon'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 zoneperTo 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 dayRecommended: create a policy for each PodRecommended: according to the style guideRecommended: in response to your requestNot recommended: requests/dayNot
recommended: create a policy per PodNot recommended: per the style guideNot recommended: as per your requestperformantAvoid where possible. Instead, use more specific wording.Recommended: an accurate machine learning modelNot recommended: a performant machine learning modelpersistDon'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 PDLowercase 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. cattleDon'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)pleaseDon'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.PNGDon'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 toUse 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.POJOIf 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.PoPAcronym for point of presence.Recommended: point of presence (PoP)Not recommended: point of presence (POP)pop-up, popupDon'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.populateOK 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 ...portUse listen on (not to).portalDon't use to refer to the Google Cloud console. For more information, see console.possibleDon'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.postmortemAvoid in general usage. Instead, use retrospective. In disaster recovery (DR) and DevOps context, use blameless postmortem.practitionerAvoid 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-builtprecapture; not pre-captureprecedingRecommended:
... in the preceding example ...precondition; not pre-conditionpredefined; not pre-definedpreemptible; not pre-emptible or pre-emptivepre-existing; not preexistingpreferred pronounsDon't use. Instead, use pronouns.prerecorded; not pre-recordedpre-shared key; not preshared keypresently, at presentAvoid 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.pressUse 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-submitprimitiveUse with caution. Don't use primitive in a disparaging sense.projectIn 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.propertyIn our API documentation, a property is an element in a resource. For example, a Task resource has properties like kind, id, and title.prosDon't use. Instead, use something else, such as advantages.
Qquick, quicklyWhat 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.quotaIn 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 wareRDPDon'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 onlyAlways 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-brandingrecents screen; not overview screenredlineDon'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.repoDon't use. Instead, use repository.Representational State TransferDon'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 theDon't use.resource record set; not resource recordsetresponse policy zone (RPZ)retardedDon't use. If you are referring to a system or component being slowed, use the word slowed.retriable, triableDon't use retriable or triable, unless a code item uses that spelling. Outside of code font, write around the term.retryable, tryableWhere possible, write around retryable and tryable. For example, write out can be tried again or you can try it again.reviewIf 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.RFCWhen referencing an RFC specification, use a space between RFC and the number (for example, RFC 2318).roll outDon'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)RTFMDon't use. Instead, use something like For more information, see....runbook; not run bookruntime, run timeUse 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.SSaaSWrite out on first mention: software as a service (SaaS).saneDon't use. Instead use a word like valid or sensible.sanity checkDon't use. Instead, use a term like quick check, confidence check, preliminary check or coherence check.SAPPronounced 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 screensnapDon't use as a verb; instead, use take a screenshot.scrollOK 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 ConsoleseeOK 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. selectUse 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.serviceIt'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 agreementLowercase 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 indicatorOK to abbreviate as SLI after first use.service level objectiveOK to abbreviate as SLO after first use.setup (noun or adjective), set up (verb)sexyDon't use. Instead, use precise, positive words, such as fast, powerful, or elegant.SHA-1Not SHA1, except in string literals/enums and in hyphenated phrases such as HSA-SHA1.shallAvoid shall except under advice from a lawyer. For more information, see should.she, her, hersDon't use a gendered pronoun except for a specific individual of known gender. Use they and their for the general singular pronoun.sherpaIf possible, use a more precise term. For example, if you mean guide, use that term.shift leftIn 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 beGenerally 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.
slave) process directly when debugging issues between the primary and secondary processes.See
master.slice and diceDon't use the phrase slice and dice. Instead, use specific terms appropriate to the task at hand. Some possible options include: segment data for analysis, break information into smaller parts.smartphone, smart phoneDon't use. Instead, use
mobile phone or phone. 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.soonAvoid in timeless documentation because this word can become outdated. The word can also prematurely disclose product or feature strategy or inappropriately imply that a product or
feature might change.See also eventually and future.Recommended: This setting is optional.Not recommended: This setting is optional for existing applications but will soon be required for all applications.For more information, see
Timeless documentation.source network address translation (SNAT)Also okay to use source NAT after first mention. If you do this, include it in the first mention parenthetical: (SNAT or source NAT). See also NAT.spin upAs in spin up an
instance. Avoid using spin up unless you're referring to a hard disk; instead, use a less colloquial term like create or start.SQLRefer to a SQL, not an SQL.ssh and SSHDon't use ssh or SSH as a verb. SSH is a secure communications protocol; ssh is a utility.Recommended: To establish an SSH connection, use the ssh command.Not recommended: ssh
into your remote shell.ssh'ingDon't use.Recommended: When you use ssh to log in…startup (noun or adjective), start up (verb)static external IP addressDo not use static IP address or external IP address to refer to static external IP addresses.status barSTONITH, STOMITHAvoid
using graphically violent terms. This acronym's letters stand for an extremely graphic and violent act. Instead, explain the relevant feature, such as fence failed nodes.style sheet; not stylesheetThis is the official spelling, per the World Wide Web Consortium (W3C).subclass; not sub-class; noun or verb
sub-command; not subcommandsub-elementsubnetOK to use as a shortening of subnetwork. Use the same term consistently throughout your document. For more information, see Subnets vs. subnetworks.subtree; not sub-treesubzone; not sub-zone or sub zone
such as versus likeSee like versus such as.surfaceAvoid as a transitive verb; instead, use a more specific term, such as make people aware of or expose. Recommended: To make the audit logs available, you must configure the monitoring system.Not recommended: To surface audit logs, you must configure
the monitoring system. sync (noun, verb); not synchRecommended: in syncRecommended: sync, syncing, syncedTtabWhen referring to the sub-pages of a console, use page instead of tab.table nameTwo words. Set specific table names in code font.tabletTablet is OK. If you don't know whether it's a tablet or a phone, use device.tag See element.tapIn 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.)tarballDon't use. Instead, use tar file.tar fileDon'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.targetAvoid 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.terminateAvoid 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, textboxDon'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, thatWhere 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 frameAvoid 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 stamptime to live; not time-to-liveAbbreviate as TTL after first use.time zone (noun), time-zone (adjective)tl;drDon't use. Instead, use something like To summarize, or revise the sentence.touchIn Android documentation, don't use. Instead, use tap. However, touch & hold is OK to use."touch & hold"; not touch and holdtouchscreen; not touch screentraditionalIf 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 transcompiletribal knowledge, tribal wisdomDon't use. Instead, use a less figurative term to indicate knowledge held by a group of people.trojanLowercase when referring to malware. turn onIn 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.tutorialOkay to use. See documentation.typeIn 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).typicallyUse 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.UUIDon't use generically to refer to a page or dashboard. Use a more specific term like page or console.Recommended: In the Google Cloud consoleRecommended: On the Cloud Tasks pageNot recommended: In the Cloud Tasks UIunarchiveDon't use. Instead, use extract.uncheckDon'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.uncompressDon't use. Instead, use extract.underDon'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.UnicodeDon't capitalize as UNICODE.Unix-likeUnix epoch timeUse 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. unselectDon't use. Instead, use clear for checkboxes, and deselect for other UI elements.unsightedDon't use. See blind.untarDon't use. Instead, use extract.unzip Don't use. Instead, use extract.URLAll 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.USOK 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 userbaseusername; not user nameusingWhere 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.UTFInclude the hyphen in the names of Unicode encodings, such as UTF-8, UTF-16, and UTF-32. utilize, utilizationUse 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.Vv (abbreviating version)Use lowercase.viaDon't use.vice versaDon'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) instanceUse 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 attachmentDon't use the following: interconnect attachment (VLAN), Interconnect attachment, Cloud Interconnect attachment, or any variation thereof. See also interconnectAttachment.voilaDon't use.voodooDon'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.Wwake lock (noun), wake-lock (adjective)walkthrough; not walk-throughwar room, warroom, war-roomDon'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.warmWhen 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 masterDon'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 webpageBut where possible, avoid both by using page.web server; not webserverwebsite (lowercase w); not web sitewhether
YYAMLDon't use a filename extension to refer to a type of file. For example, use YAML file rather than .yaml file. For details, see Referring to file types.ymmvDon't use. Instead, use something like Your results might vary.ZzipDon't use a filename extension to refer to a type of file. For example, use zip file rather than .zip file. For details, see Referring to file types.zippyDon't use to refer to expander arrows, unless you're specifically referring to the Zippy widget in Closure.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-21 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" }] |
General non descriptive terms such as normal, abnormal or poor should be used when documenting data
zusammenhängende Posts
Urheberrechte © © 2024 ketiadaan Inc.
