> [!NOTE]
> **Note**: This document includes references to potentially disrespectful or offensive terms. These terms are listed here to provide usage guidance and alternative terms.
This word list covers style and usage guidelines that are specific to developer documentation.
If the term that you're looking for isn't on this list, check our other
[editorial resources](https://developers.google.com/style#editorial-resources), including our preferred
dictionary,
[Merriam-Webster](https://www.merriam-webster.com/). If there are multiple spellings in
the Merriam-Webster word entry, use the first form listed, which is the most common spelling. For
example, in the
[entry for *cancel*](https://www.merriam-webster.com/dictionary/canceled),
the first form listed for the past tense is *canceled*, indicating that it's more common than
*cancelled*.
If you're looking for a technical definition, then it's often a good idea to check the
authoritative documentation on the topic.
Terminology decisions, including how and when to define or contextualize
terms, often require judgments based on factors like your product area,
your audience, and prevailing convention. Here are some other pages of this
guide that can help you make those types of judgments:
- [Jargon](https://developers.google.com/style/jargon)
- [Inclusive language](https://developers.google.com/style/inclusive-documentation)
- [Write for a global audience](https://developers.google.com/style/translation)
- [Hyphens](https://developers.google.com/style/hyphens)
- [Capitalization](https://developers.google.com/style/capitalization)
As always, it's fine to deviate from our guidance if that serves your readers
better. For more information, see [Break the rules](https://developers.google.com/style#rules).
## Word list
All word list entries have a link
icon next to them. To link directly to an entry, you can right-click and
copy the link address, or click and copy the URL from your address bar.
Some word list entries include guidance to *avoid* or *don't use* a
term. Apply this guidance as follows:
- **Use with caution** . A recommendation to avoid using the term *when possible*, or to use the term with caution. The term might be ambiguous or obscure, so we provide alternative term suggestions or suggest that you use a more specific term. However, you can use the term if needed. Where appropriate, define the term or use it only once, as explained on the [Jargon](https://developers.google.com/style/jargon) page.
- **Don't use** . In all cases, we prefer to *not use the term*. The term might be particularly ambiguous or it might have an offensive or non-inclusive association. If such a term appears in code, we recommend that you [replace or write around the term](https://developers.google.com/style/inclusive-documentation#replace-or-write-around-non-inclusive-terms).
- **Android**. Applies only to Android documentation.
- **Google Cloud**. Applies only to Google Cloud documentation.
- **Google Workspace**. Applies only to Google Workspace documentation.
### Numbers and Symbols
+ [](https://developers.google.com/style/word-list#+)
:
OK to use *+* with numbers in text, such as *customer records with 300+ demographic attributes*, except in formal contexts.
\& (ampersand)
[](https://developers.google.com/style/word-list#ampersand)
:
Don't use *\&* instead of *and* in headings, text, navigation, or
tables of contents.
:
It's OK to use *\&* when referencing UI elements that use *\&*, or
in table headings and diagram labels where space constraints require
abbreviation.
: It's OK to use `&` for technical purposes in code.
2-Step Verification
[](https://developers.google.com/style/word-list#2-step-verification)
:
When referring to Google's
[2-Step Verification](https://www.google.com/landing/2step/),
use initial caps.
:
When referring to
[generic 2-step verification](http://searchsecurity.techtarget.com/definition/two-step-verification),
use lowercase.
### A
a and an [](https://developers.google.com/style/word-list#a-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)](https://developers.google.com/style/articles).
A/B testing [](https://developers.google.com/style/word-list#ab)
: Capitalize and use slash notation for *A/B*.
abnormal [](https://developers.google.com/style/word-list#abnormal)
: Don't use to refer to a person.
: OK to use to refer to a condition of a computer system.
abort [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#about-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](https://cloud.google.com/firestore/docs/query-data/indexing).
:
Not recommended: For more information
on indexes, see [Managing
indexes](https://cloud.google.com/firestore/docs/query-data/indexing).
above [](https://developers.google.com/style/word-list#above)
:
Don't use for a range of version numbers. Instead, use
[*later*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/accessibility).
:
It's OK to use *above* in a non-directional way, such as when describing a hierarchy.
access (verb) [](https://developers.google.com/style/word-list#access)
:
Avoid when you can. Instead, use friendlier words like *see*,
*edit*, *find*, *use*, or *view*.
access token [](https://developers.google.com/style/word-list#access-token)
: Lowercase except at the beginning of a sentence,
heading, or list item.
account name [](https://developers.google.com/style/word-list#account-name)
: Don't use. Instead, use [*username*](https://developers.google.com/style/word-list#username).
actionable [](https://developers.google.com/style/word-list#actionable)
:
Avoid unless it's the clearest and simplest phrasing for your audience.
Instead, leave it out or replace it with a phrase like *that you can act on* or *useful*.
:
Don't use *actionable* in the legal sense without consulting a
lawyer.
action bar
[](https://developers.google.com/style/word-list#action-bar)
:
In Android documentation, don't use. Instead, use
[*app bar*](https://developers.google.com/style/word-list#app-bar).
ad tech [](https://developers.google.com/style/word-list#ad-tech)
:
Write out on first mention: *advertising technology (ad tech)*.
: Don't use *adtech* or *ad-tech*.
address bar [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#ad-hoc)
:
OK to use in database and analytics contexts to mean "free-form" or
"user-written" (for example, *ad hoc queries* or *an ad hoc chart*). For other contexts, try to find a more specific English
equivalent.
:
Don't hyphenate or italicize the term.
admin [](https://developers.google.com/style/word-list#admin)
:
Write out *administrator* unless it's the name of a UI label or other
element.
:
It's OK to use *admin* in Android
documentation.
administrator
[](https://developers.google.com/style/word-list#administrator)
: In Android documentation, don't use. Instead, use *admin*.
advertised route priority [](https://developers.google.com/style/word-list#advertised-route-priority)
:
OK to also use *base advertised route priority* when discussing
region-to-region costs.
: Don't shorten or use variations of these terms.
agnostic [](https://developers.google.com/style/word-list#agnostic)
:
Don't use. Instead, use a more precise term like
*platform-independent*.
AI [](https://developers.google.com/style/word-list#ai)
:
In general, you can use *AI* without spelling out *artificial intelligence*.
:
Most readers are familiar with the abbreviation *AI*. If you think your audience isn't
familiar with the term, spell it out on first use.
aka [](https://developers.google.com/style/word-list#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
[](https://developers.google.com/style/word-list#all-apps-screen)
: In Android documentation: Lowercase except at the beginning of a sentence,
heading, or list item.
allowlist (verb), allowlisted, allowlisting
[](https://developers.google.com/style/word-list#allowlist)
: Don't use as a verb. Instead, rewrite to improve clarity.
: OK to use *allowlist* as a noun.
: For more information, see [blacklist](https://developers.google.com/style/word-list#blacklist).
allows you to [](https://developers.google.com/style/word-list#allows-you-to)
:
Don't use. Instead, use *lets you*. For more information, see [enable](https://developers.google.com/style/word-list#enable).
alpha [](https://developers.google.com/style/word-list#alpha)
: Lowercase except when part of a product name.
:
Recommended: PRODUCT_NAME
Alpha
:
Recommended: PRODUCT_NAME
is in alpha.
America, American [](https://developers.google.com/style/word-list#america)
:
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](https://developers.google.com/style/word-list#us).
among [](https://developers.google.com/style/word-list#among)
: See [between versus among](https://developers.google.com/style/word-list#between).
AM, PM [](https://developers.google.com/style/word-list#am-pm)
:
To be consistent with [Material Design](https://material.io/design/communication/data-formats.html#date-and-time),
use all caps, no periods, and a space before.
:
Recommended: 9:00 AM
:
Recommended: 10:30 PM
and/or [](https://developers.google.com/style/word-list#and-or)
:
Don't use unless space is limited, such as in a table. For more
information, see [Slashes](https://developers.google.com/style/slashes#and-or).
Android [](https://developers.google.com/style/word-list#android)
: When referring to the operating system, capitalize *Android*.
Android-powered device
[](https://developers.google.com/style/word-list#android-powered)
: Not *Android device*.
and so on [](https://developers.google.com/style/word-list#and-so-on)
:
Avoid using *and so on* whenever possible. For more information,
see [etc.](https://developers.google.com/style/word-list#etc)
anti\* [](https://developers.google.com/style/word-list#anti)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
anti-pattern [](https://developers.google.com/style/word-list#anti-pattern)
:
Avoid using *anti-pattern*, particularly as a standalone heading.
Instead, consider using a more specific and broadly understood term.
:
Recommended: Avoid these five SQL
errors.
:
Recommended: Avoid these five
programming practices that make SQL queries inefficient.
:
Not recommended: Avoid these five SQL
anti-patterns.
API [](https://developers.google.com/style/word-list#api)
:
Use *API* to refer to either a web API or a language-specific API.
:
Don't use *API* 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, APIs console,
developer console, dev console, or Google API Console
[](https://developers.google.com/style/word-list#api-console)
:
Don't use. Instead, refer to the *Google APIs Explorer* or to the
*Google Cloud console*. For more information, see
[console](https://developers.google.com/style/word-list#console).
API Console key [](https://developers.google.com/style/word-list#api-console-key)
:
In most contexts, use *API key* instead of *API Console key*.
:
In Apps admin APIs, it's OK to use *API Console key* to distinguish
from other API keys.
API key [](https://developers.google.com/style/word-list#api-key)
: Not *developer key* or *dev key*.
APIs Explorer [](https://developers.google.com/style/word-list#apis-explorer)
: Not *API explorer* or other variants.
app [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#app-bar)
: In Android contexts, formerly *action bar*.
appendix [](https://developers.google.com/style/word-list#appendix)
: Use the plural *appendixes*, not *appendices*.
application [](https://developers.google.com/style/word-list#application)
: See [app](https://developers.google.com/style/word-list#app).
as [](https://developers.google.com/style/word-list#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
[](https://developers.google.com/style/word-list#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](https://developers.google.com/style/word-list#currently) and [presently](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
authentication and authorization
[](https://developers.google.com/style/word-list#authentication-and-authorization)
:
In general, use the word *authenticated* only to refer to users,
and use *authorized* only to refer to requests that are sent by a
client app on behalf of an authenticated user.
A user *authenticates* their identity 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 [](https://developers.google.com/style/word-list#authn-authz)
:
Don't use. Instead, use *authentication* or *authorization*.
auto\* [](https://developers.google.com/style/word-list#auto)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
autohealing [](https://developers.google.com/style/word-list#autohealing)
: Not *auto-healing*.
auto mode VPC network [](https://developers.google.com/style/word-list#auto-mode-vpc)
: Not *auto mode network*.
autopopulate [](https://developers.google.com/style/word-list#autopopulate)
: Not *auto populate* or *auto-populate*.
autoscaling [](https://developers.google.com/style/word-list#autoscaling)
: Not *auto-scaling*.
autotagging [](https://developers.google.com/style/word-list#autotagging)
: Not *auto-tagging*.
autoupdate [](https://developers.google.com/style/word-list#autoupdate)
: Don't use. Instead, use *automatically update*.
-aware [](https://developers.google.com/style/word-list#aware)
: Avoid using as a compound modifier, as in *healthcare-aware*.
:
OK to use when it's part of a product name, such as *Identity-Aware Proxy*.
### B
backend [](https://developers.google.com/style/word-list#backend)
: Not *back-end* or *back end*.
bar [](https://developers.google.com/style/word-list#bar)
:
Avoid when possible. For more information, see [foo](https://developers.google.com/style/word-list#foo).
bare metal [](https://developers.google.com/style/word-list#bare-metal)
: Lowercase except at the beginning of a sentence,
heading, or list item.
:
Hyphenate when used as a compound modifier, such as *bare-metal server*.
base64 [](https://developers.google.com/style/word-list#base64)
:
Lowercase except at the beginning of a sentence,
heading, or list item. Otherwise, capitalize *Base64* only if it's part of a
formal name.
:
Write *base64* in code font *only* if it's a string literal or
otherwise quoted from code.
baz [](https://developers.google.com/style/word-list#baz)
:
Avoid when possible. For more information, see [foo](https://developers.google.com/style/word-list#foo).
below [](https://developers.google.com/style/word-list#below)
:
Don't use for a range of version numbers. Instead, use
[*earlier*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/accessibility).
:
It's OK to use *below* in set phrases such as *below (the) average*, *below the mean*, *below zero*.
:
It's OK to use *below* in a non-directional way, such as when describing a hierarchy.
best effort [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#beta)
: Lowercase except when part of a product name.
:
Recommended: PRODUCT_NAME
Beta
:
Recommended: PRODUCT_NAME
is currently in beta.
between versus among [](https://developers.google.com/style/word-list#between)
:
It's fine to use *between* when talking about more than two things;
however, *between* isn't interchangeable with *among*.
: 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*](http://www.quickanddirtytips.com/education/grammar/between-versus-among).
big-endian [](https://developers.google.com/style/word-list#big-endian)
: Hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
:
Recommended: The codebase assumes
big-endian byte ordering.
:
Not recommended: The codebase assumes
Big Endian byte ordering.
:
Not recommended: The codebase assumes
Big-endian byte ordering.
:
Not recommended: The codebase assumes big
endian byte ordering.
billing charges [](https://developers.google.com/style/word-list#billing-charges)
:
Don't use *billing charges* to mean charges that appear on a bill.
Instead, use *billed charges*.
:
Use *billing charges* to describe the cost of creating the bill.
black-box [](https://developers.google.com/style/word-list#black-box)
:
Avoid using *black-box*, *blackbox*, or *black box* to
describe monitoring and testing. Consider using a more precise term for
clarity.
- For monitoring, use *synthetic monitoring*.
- For testing, use *opaque-box testing*.
Black Friday [](https://developers.google.com/style/word-list#black-friday)
:
Avoid unless explicitly referring to an event in the US. Instead use
*peak scale event*.
blackhat, black hat, black-hat
[](https://developers.google.com/style/word-list#blackhat)
:
Don't use. Instead, use precise terms for the kind of violation or
practice, such as *illegal*, *unethical*, or *in violation of rules*.
blackhole (verb), blackholed (adjective)
[](https://developers.google.com/style/word-list#blackhole)
:
Don't use. Instead, use a more descriptive term or phrase, such as
*dropped without notification*.
blacklist, black list, black-list
[](https://developers.google.com/style/word-list#blacklist)
:
Don't use *blacklist*, *whitelist*, and *graylist*.
Instead, use more precise terms that are appropriate for your domain.
:
- For the noun *blacklist*, consider using a replacement such as *denylist*, *excludelist*, or *blocklist*.
- For the noun *whitelist*, consider using a replacement such as *allowlist*, *trustlist*, or *safelist*.
- For the noun *graylist* (*greylist*), consider using a replacement such as *provisional list*.
:
In all of these cases, consider that there might not actually be a list
involved. When replacing problematic terms, be sure to be technically
accurate for the specific context.
:
For the verb forms of these words, a simple word-for-word replacement
typically isn't the best solution. Instead, replace verbs such as
*blacklisted* with phrases that accurately convey the relevant
action. For example:
:
Recommended: To deny requests from
an IP address, add it to the `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 the words only in direct reference to the code items
([formatted as code](https://developers.google.com/style/code-in-text)), 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](https://developers.google.com/style/inclusive-documentation) page.
blacklisted, black listed, black-listed
[](https://developers.google.com/style/word-list#blacklisted)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
blacklisting, black listing, black-listing
[](https://developers.google.com/style/word-list#blacklisting)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
blast radius [](https://developers.google.com/style/word-list#blast-radius)
:
Don't use. Instead, use a more precise term like *affected area* or
*spatial impact*.
blind [](https://developers.google.com/style/word-list#blind)
:
Avoid 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-green [](https://developers.google.com/style/word-list#blue-green)
: Not *blue/green* or *blue green*.
boolean [](https://developers.google.com/style/word-list#boolean)
:
In most contexts, *boolean* refers to a specific data type in a
specific programming language. In such cases, use code font and the exact
spelling and capitalization of the programming keyword.
: When referring to the abstract data type, use lowercase.
:
If you refer to *Boolean mathematics* or *Boolean logic*, use
uppercase.
branding information [](https://developers.google.com/style/word-list#branding-information)
:
In 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-glass [](https://developers.google.com/style/word-list#break-glass)
: Don't use. Instead, use a more precise term depending on context:
- To describe a general emergency or procedure that grants emergency access, use *emergency access*.
- To describe a fallback procedure, use *manual fallback* or *preplanned procedure*.
brown bag, brown-bag [](https://developers.google.com/style/word-list#brown-bag)
:
Don't use. Instead, use a more precise term like *learning session*,
*lunch and learn*, *lunchtime learning session*,
*casual training*, or *informal training*.
build cop, build sheriff
[](https://developers.google.com/style/word-list#build-cop)
:
Don't use. Instead, use a more precise term like *build monitor*.
button [](https://developers.google.com/style/word-list#button)
:
In a UI, a link isn't the same as a button; don't use the term
*button* to refer to a link.
:
Use *button* to refer to mechanical buttons (like the volume control
buttons on the side of a phone) and capacitive touch buttons on a phone
(like the Home button). You *press* mechanical buttons, and
*tap* capacitive and on-screen buttons.
### C
can [](https://developers.google.com/style/word-list#can)
: Use *can* in the following ways:
- To convey permission or ability (for example, "You can access the server").
- To refer to an optional action (for example, "You can also view logs with the Log Viewer").
- To describe a possible outcome (for example, "The process can take 30 minutes").
:
See also [could](https://developers.google.com/style/word-list#could), [may](https://developers.google.com/style/word-list#may),
[might](https://developers.google.com/style/word-list#might), [must](https://developers.google.com/style/word-list#must),
[should](https://developers.google.com/style/word-list#should), and [would](https://developers.google.com/style/word-list#would).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
canary [](https://developers.google.com/style/word-list#canary)
: Don't use *canary* as a verb, and don't use *canarying*.
:
When possible, avoid [jargon](https://developers.google.com/style/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.
careful, carefully [](https://developers.google.com/style/word-list#careful)
:
Avoid telling a user to perform an action *carefully*, which can sound condescending or
imply that other steps don't require much attention. For more information, see [Use precise, objective language](https://developers.google.com/style/inclusive-documentation#subjective-language).
:
Recommended: Enter the API key that
appears in the console.
:
Not recommended: Make sure to enter the API key carefully.
cell phone, cellphone
[](https://developers.google.com/style/word-list#cell-phone)
:
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 [](https://developers.google.com/style/word-list#cellular-data)
: Don't use. Instead, use *mobile data*.
cellular network [](https://developers.google.com/style/word-list#cellular-network)
: Don't use. Instead, use *mobile network*.
chapter [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#checkbox)
: Not *check box*.
choose [](https://developers.google.com/style/word-list#choose)
: *Choose* is fine to use for generic contexts. For UI elements, use
[select](https://developers.google.com/style/word-list#select).
chubby [](https://developers.google.com/style/word-list#chubby)
:
Don't use. Instead, use a word that clearly explains what you mean, such
as *unused* or *overextended*.
clear [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#cli)
:
Don't use *CLI* generically to refer to a command-line interface.
Instead, refer to the specific command-line interface, such as the
[Google Cloud CLI](https://developers.google.com/style/word-list#gcloud).
click [](https://developers.google.com/style/word-list#click)
:
When the environment is a desktop with a mouse, use *click* for most
targets, such as buttons, links, list items, and radio buttons. Don't use
*click on*.
:
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 OK 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](https://developers.google.com/style/word-list#tap).
click here [](https://developers.google.com/style/word-list#click-here)
:
Don't use. For information and alternatives, see
[Avoid vague link text](https://developers.google.com/style/cross-references#vague-link-text).
clickthrough (noun), click through (verb) [](https://developers.google.com/style/word-list#clickthrough)
client [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#client-id)
: Lowercase except at the beginning of a sentence,
heading, or list item.
client secret [](https://developers.google.com/style/word-list#client-secret)
: Lowercase except at the beginning of a sentence,
heading, or list item.
Cloud
[](https://developers.google.com/style/word-list#cloud)
: Don't use as short for *Google Cloud*.
:
For generic references such as *the cloud* or *hybrid cloud*,
use lowercase.
Cloud
console
[](https://developers.google.com/style/word-list#gcp-console)
:
Don't use. Instead, refer to the full name *Google Cloud console*.
:
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](https://developers.google.com/style/word-list#console).
Cloud SDK [](https://developers.google.com/style/word-list#cloud-sdk)
: Not *Google Cloud SDK*.
co\* [](https://developers.google.com/style/word-list#co)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
codebase [](https://developers.google.com/style/word-list#codebase)
: Not *code base*.
codelab [](https://developers.google.com/style/word-list#codelab)
:
Not *code lab* or *code-lab*. For more information, see
[documentation](https://developers.google.com/style/word-list#documentation).
cold [](https://developers.google.com/style/word-list#cold)
:
When possible, avoid [jargon](https://developers.google.com/style/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 [](https://developers.google.com/style/word-list#colocate)
: Not *co-locate* or *colo*.
compliant, compliance [](https://developers.google.com/style/word-list#compliant)
:
Use with caution. A claim that a product or its output is *compliant*
with a standard is a strong statement.
comprise [](https://developers.google.com/style/word-list#comprise)
:
Don't use. Instead, use *consist of*, *contain*, or
*include*.
config [](https://developers.google.com/style/word-list#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 a file with that name.
confidential [](https://developers.google.com/style/word-list#confidential)
:
*Confidential* data is data that is protected to prevent unauthorized access. See
[sensitive](https://developers.google.com/style/word-list#sensitive).
cons [](https://developers.google.com/style/word-list#cons)
:
Don't use. Instead, use a more precise term, such as *disadvantages*.
console [](https://developers.google.com/style/word-list#console)
:
Don't use in isolation. Instead, use the name of the specific console,
such as the [Google Cloud
console](https://console.cloud.google.com/) or the Google Admin console.
: Use *the* before the name of a console.
:
After giving the full name of a console, 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*.
:
If a specific term for a browser-based interface is unavailable, use
*web interface*.
content type [](https://developers.google.com/style/word-list#content-type)
:
Be as specific as possible when writing about a content type, and use the term only when applicable.
For example, you can use this term if you're referring to the value of the `Content-Type` HTTP header.
Also see [media type](https://developers.google.com/style/word-list#media-type).
Control+S, Command+S, and other keyboard commands [](https://developers.google.com/style/word-list#control-keys)
:
To refer to a Control character, use
Control+CHARACTER.
: Don't use *Ctl-S*, *Cmd-S*, or *Cloverleaf-S*.
: In most cases, use an uppercase letter for CHARACTER.
:
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 and
Windows or Linux users, then mention both keyboard commands.
:
Recommended: Control+S
(Command+S on macOS)
Copy and paste [](https://developers.google.com/style/word-list#copy-paste)
:
Avoid using. Instead, explain what to enter into a field and not how.
:
Recommended: In the
**Query** field, enter the output from the previous step.
:
Not recommended: Copy the output from
the previous step and paste into the **Query** field.
could [](https://developers.google.com/style/word-list#could)
: Avoid using. Instead, use *can* where possible.
:
See also [can](https://developers.google.com/style/word-list#can), [may](https://developers.google.com/style/word-list#may),
[might](https://developers.google.com/style/word-list#might), [must](https://developers.google.com/style/word-list#must),
[should](https://developers.google.com/style/word-list#should) and [would](https://developers.google.com/style/word-list#would).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
:
For information about tenses, see [Present
tense](https://developers.google.com/style/tense).
CPU [](https://developers.google.com/style/word-list#cpu)
: All caps. No need to expand the abbreviation on first mention.
crazy, bonkers, mad, lunatic, insane,
loony
[](https://developers.google.com/style/word-list#crazy)
:
Don't use. Instead, use *complicated*, *complex*,
*baffling*, *strange*, or *unexpected*, and only for
inanimate objects.
Create a new ... [](https://developers.google.com/style/word-list#create-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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#cross-site-request-forgery)
: Lowercase except at the beginning of a sentence,
heading, or list item.
curated roles [](https://developers.google.com/style/word-list#curated-roles)
: Don't use. Instead, use *predefined roles*.
currently [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/word-list#as-of-this-writing) and
[presently](https://developers.google.com/style/word-list#presently).
:
Recommended: Windows isn't supported.
:
Not recommended: Windows isn't
currently supported.
:
For more information, see
[Timeless documentation](https://developers.google.com/style/timeless-documentation).
custom mode VPC network [](https://developers.google.com/style/word-list#custom-mode-vpc-network)
: Not *custom mode network*.
curl [](https://developers.google.com/style/word-list#curl)
: Not *cURL*.
: For information about when to use code format, see
[Items that are sometimes in code font](https://developers.google.com/style/code-in-text#items-that-are-sometimes-in-code-font).
Cyber Monday [](https://developers.google.com/style/word-list#cyber-monday)
: Avoid unless explicitly referring to an event in the US. Instead use
*peak scale event*.
### D
dash [](https://developers.google.com/style/word-list#dash)
:
A dash (`---`) isn't 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 [](https://developers.google.com/style/word-list#dashboard)
:
Don't use to refer to the Google Cloud console. For more information, see
[console](https://developers.google.com/style/word-list#console).
:
Use *dashboard* not *Dashboard* unless it's officially part of a
product name.
data [](https://developers.google.com/style/word-list#data)
:
Use *data* as singular, not plural; *the data is*, not
*the data are*.
:
Use data as a mass noun, not a count noun; *less data*, not
*fewer data*.
data center [](https://developers.google.com/style/word-list#data-center)
: Not *datacenter*.
data center campus [](https://developers.google.com/style/word-list#data-center-campus)
:
Use when referring to an entire physical location, which can encompass one
or more data centers.
data cleaning [](https://developers.google.com/style/word-list#data-cleaning)
: Not *data cleansing*.
data flow (noun); dataflow (noun) [](https://developers.google.com/style/word-list#dataflow)
:
If it's possible to replace with the phrase *flow of data*, then use
two words: *data flow*.
:
If that replacement doesn't work, such as when referring to something like
stream processing or reactive programming, then use one word:
*dataflow*.
data source [](https://developers.google.com/style/word-list#data-source)
: Not *datasource*.
datastore [](https://developers.google.com/style/word-list#datastore)
: Not *data store*.
data type [](https://developers.google.com/style/word-list#data-type)
: Not *datatype*.
dead-letter queue, dead letter [](https://developers.google.com/style/word-list#dead-letter)
:
Define on first use, for example *dead-letter queue (unprocessed messages queue)*.
deep linking [](https://developers.google.com/style/word-list#deep-linking)
:
Not *deep-linking*. However, if you can replace with
*linking*, then do so.
deficient [](https://developers.google.com/style/word-list#deficient)
: Don't use to refer to a person.
: OK to use to refer to a condition of a computer system.
deformed [](https://developers.google.com/style/word-list#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) [](https://developers.google.com/style/word-list#dmz)
:
Don't use. Instead, use a more precise term like *perimeter network*.
denigrate [](https://developers.google.com/style/word-list#denigrate)
: Don't use. Instead, use *disparage*.
denylist (verb), denylisted, denylisting
[](https://developers.google.com/style/word-list#denylisted)
: Don't use as a verb. Instead, rewrite to improve clarity.
: OK to use *denylist* as a noun.
: For more information, see [blacklist](https://developers.google.com/style/word-list#blacklist).
deprecate [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#desire)
: 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.
Developers Console
[](https://developers.google.com/style/word-list#developers-console)
:
Don't use. For more information, see [console](https://developers.google.com/style/word-list#console).
DevOps [](https://developers.google.com/style/word-list#devops)
:
Short for *development operations*. No need to spell out on first
mention unless the audience requires it. For more information, see [DevOps](https://wikipedia.org/wiki/DevOps).
dialog [](https://developers.google.com/style/word-list#dialog)
:
Use *dialog* for the UI element sometimes called a [dialog box](http://wikipedia.org/wiki/Dialog_box).
:
Use *dialogue* only for verbal interaction between people.
directory, folder [](https://developers.google.com/style/word-list#directory)
:
If the context that 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 [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/word-list#enable).
disclosure triangle, disclosure widget
[](https://developers.google.com/style/word-list#disclosure-triangle)
: Don't use. Instead, use *expander arrow*.
display (verb) [](https://developers.google.com/style/word-list#display)
:
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) [](https://developers.google.com/style/word-list#ddos)
: Hyphenate as shown. On subsequent mention, use *DDoS*.
DNS server policy [](https://developers.google.com/style/word-list#dns-server-policy)
: Lowercase *server policy*.
DNSKEY [](https://developers.google.com/style/word-list#dnskey)
: One word, all capital letters.
documentation or document or documents [](https://developers.google.com/style/word-list#documentation)
: To refer specifically to the text on a page that explains a product, feature, or service,
use *this document*, and not *this article*, *this topic*, *this doc*, or
*this page*. It's OK to use *this tutorial*, *this quickstart*, or *this codelab* for those specific documentation types.
Always spell out *documentation* except in cases where space is limited, such as in
tabs and URLs.
See also
[page](https://developers.google.com/style/word-list#page).
:
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 page provides
guidance about creating tables.
documentation set [](https://developers.google.com/style/word-list#docset)
: Not *doc set* or *docset*.
does not yet [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
dojo [](https://developers.google.com/style/word-list#dojo)
:
Don't use. Instead, use a precise term that is accurate for the context,
such as *training* or *workshop*.
domain name registrar [](https://developers.google.com/style/word-list#domain-name-registrar)
: Lowercase except at the beginning of a sentence,
heading, or list item.
Domain Name System Security Extensions (DNSSEC) [](https://developers.google.com/style/word-list#dnssec)
:
Write out and capitalize each word on first use. OK to abbreviate as
*DNSSEC* after first use.
double-tap [](https://developers.google.com/style/word-list#double-tap)
: Hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
downscope [](https://developers.google.com/style/word-list#downscope)
:
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.
:
: Don't use *down scope* or *down-scope*
:
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 [](https://developers.google.com/style/word-list#drag)
:
Use *drag*, not *click and drag* and not *drag and drop*.
: OK to use *drag-and-drop* as an adjective.
:
Recommended: Drag the USER
to the **Authorized** box.
drop-down [](https://developers.google.com/style/word-list#drop-down)
:
In most cases, you can omit *drop-down* from phrases like *drop-down list* or
*drop-down menu*, and just use *list* or *menu*. Include *drop-down* as a
modifier only if the omission would cause ambiguity. Don't use *drop-down* as a
standalone noun.
dumb down [](https://developers.google.com/style/word-list#dumb-down)
:
Don't use. Instead, use a word or phrase what's happening, such as
*simplify* or *remove technical jargon*.
dummy variable [](https://developers.google.com/style/word-list#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](https://en.wikipedia.org/wiki/Dummy_variable_(statistics)).
Instead, use alternate terms such as
*indicator variable*, *design variable*, *one-hot encoding*, *Boolean indicator*, *binary variable*, or
*qualitative variable*.
### E
each [](https://developers.google.com/style/word-list#each)
:
*Each* refers to every individual item taken individually, not to a
group of items taken collectively. In other words, *each* isn't 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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#easy)
:
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. For more information, see
[Use precise, objective
language](https://developers.google.com/style/inclusive-documentation#subjective-language).
ecommerce [](https://developers.google.com/style/word-list#ecommerce)
: Not *e-commerce*.
edge availability domain [](https://developers.google.com/style/word-list#edge-availability-domain)
:
Don't use *edge availability zone*, *metro availability domain*,
or *metro availability zone*. Don't shorten to *EAD*.
e.g. [](https://developers.google.com/style/word-list#eg)
:
Don't use. Instead, use phrases like *for example* or *such as*.
Many people confuse *e.g.* and *i.e.*
egress [](https://developers.google.com/style/word-list#egress)
: When referring to the networking term, use lowercase.
either [](https://developers.google.com/style/word-list#either)
: When using *either*, use parallel syntax.
:
Recommended: Do either option 1 or
option 2.
:
Recommended: Either do option 1 or
do option 2.
:
Not recommended: Either do option 1
or option 2.
:
In general, use *either* only for a choice between two things, not
for a choice among multiple things. Writing *either A or B or C* will
distract some readers, but if it's the best phrasing for your situation,
then use it.
element [](https://developers.google.com/style/word-list#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
`` start tag indicates the beginning of the
`example` element.) In general, don't use
the term *tag* to refer to an entire element.
email [](https://developers.google.com/style/word-list#email)
: Not *e-mail*, *Email*, or *E-mail*.
: 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](https://developers.google.com/style/translation).
emoji [](https://developers.google.com/style/word-list#emoji)
:
Use *emoji* for both singular and plural forms. See [Don't
know the difference between emoji and emoticons? Let me explain](https://www.theguardian.com/technology/2015/feb/06/difference-between-emoji-and-emoticons-explained) and [What's the Plural of Emoji?](http://www.theatlantic.com/technology/archive/2016/01/whats-the-plural-of-emoji-emojis/422763/)
enable [](https://developers.google.com/style/word-list#enable)
:
In procedures, use the appropriate label and action for the
[UI element](https://developers.google.com/style/ui-elements) that the user interacts with. When describing a
user action or the state of a UI element, use a more precise term where possible. It's OK to
use *enable* when not referring to a person.
:
For turning on or activating an option or feature, use *enable* or
*[turn on](https://developers.google.com/style/word-list#turn-on)* consistently:
- Use the same term in introductory text as described in the procedure.
- Use the same term throughout the document unless there's a difference in the UI elements for different procedures.
:
Recommended: To enable the API,
click the toggle.
:
Recommended: Enable the API for your
project.
: For making it feasible to do something, use *lets you*.
:
Recommended: The API lets you detect
features in images.
:
Not recommended: The API enables you
to detect features in images.
:
Not recommended: The API allows you
to detect features in images.
: In Google Workspace documentation, if possible, use
*turn on* or *on* instead. If referring to the state of a UI element, use
*available*.
endpoint [](https://developers.google.com/style/word-list#endpoint)
: Not *end point*.
enter [](https://developers.google.com/style/word-list#enter)
:
Use *enter* to refer to the user entering text. If it's important to
not press Enter, explicitly say so. See also
[*type*](https://developers.google.com/style/word-list#type).
:
Recommended: In the **Owner** box,
enter your name.
:
Recommended: In the **Size** box,
type a font size.
ephemeral external IP address [](https://developers.google.com/style/word-list#ephemeral-external-ip-address)
:
Don't use *ephemeral IP address* or *external IP address* to
refer to ephemeral external IP addresses.
error-prone (adjective) [](https://developers.google.com/style/word-list#error-prone)
: Hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
etc. [](https://developers.google.com/style/word-list#etc)
:
Avoid using *etc.*, *and so forth*, and *and so on*
wherever possible. If you really need to use one, use *etc.*
Always include the period, even if a comma follows immediately after.
:
Recommended: Your app might experience
problems such as instability or high latency.
:
Recommended: Your app might experience
problems, including instability or high latency.
:
Not recommended: Your app might
experience instability, high latency, and so on.
:
Not recommended: Your app might
experience instability, high latency, etc.
:
Not recommended: If your app
experiences instability, high latency, etc., follow these steps:
eventually [](https://developers.google.com/style/word-list#eventually)
:
Avoid 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
[future](https://developers.google.com/style/word-list#future) and [soon](https://developers.google.com/style/word-list#soon).
:
Recommended: This version of the SDK
is deprecated.
:
Not recommended: This version of the
SDK is deprecated and eventually will be no longer supported.
:
For more information, see
[Timeless documentation](https://developers.google.com/style/timeless-documentation).
execute [](https://developers.google.com/style/word-list#execute)
:
Verb commonly used to refer to function calls, SQL queries, and other processes. When the meaning
is the same, use the simpler word *run* instead. If you need to use a more precise term
for your context, use that term.
expander arrow [](https://developers.google.com/style/word-list#expander-arrow)
:
The UI element used to expand or collapse a section of navigation or
content. If you describe this element, use the terms *expander arrow*
and *expandable section*
: Don't use terms like *expando* or *zippy*.
exploit [](https://developers.google.com/style/word-list#exploit)
: Don't use *exploit* to mean "use."
:
Only use *exploit* in the negative sense, such as to describe
*exploiting a security vulnerability*.
external VPN gateway [](https://developers.google.com/style/word-list#external-vpn-gateway)
:
Write *external* and *gateway* all lowercase except at the
beginning of a sentence, heading or list item.
extract [](https://developers.google.com/style/word-list#extract)
: Use instead of *unarchive*, *uncompress*, *untar*, or *unzip*.
### F
fail over (verb), failover (noun, adjective) [](https://developers.google.com/style/word-list#failover)
fat [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#female-adapter)
: Don't use. Instead, use a genderless word like *socket*.
Fast Healthcare Interoperability Resources (FHIR) [](https://developers.google.com/style/word-list#fhir)
: Refer to *a FHIR* (pronounced "a fire," as in "a FHIR store"), not *an FHIR*.
For more information, see
[Indefinite articles before abbreviations](https://developers.google.com/style/abbreviations#articles).
filename [](https://developers.google.com/style/word-list#filename)
: Not *file name*
file system [](https://developers.google.com/style/word-list#file-system)
: Not *filesystem*.
fill in; fill out [](https://developers.google.com/style/word-list#fill-in)
:
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 [](https://developers.google.com/style/word-list#final-solution)
:
Don't use. Instead, use *solution* as a standalone term or, depending
on the context, *definitive*, *optimal*, *best*, or *last solution*.
fintech [](https://developers.google.com/style/word-list#fintech)
:
Write out on first mention: *financial technology (fintech)*. Don't
use *FinTech* or *fin-tech*.
firewalls [](https://developers.google.com/style/word-list#firewalls)
:
Don't use in Compute Engine or networking documentation. Instead, use
*firewall rules*.
:
Exception: If you're 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, first-class citizen
[](https://developers.google.com/style/word-list#first-class)
:
Don't use *first class* or *first-class citizen*. Instead, use
another term that's appropriate for the context, such as *higher-order*,
*anonymous*, or *nested*, or loosely describe the specific
characteristics or features of the entity, resource, language, or framework.
:
Recommended: These widgets have full access to the event system and lifecycle hooks.
:
Not recommended: The widgets are first-class components in the UI framework.
:
Recommended: Virtual machines are higher-order resources that can participate in resource groups and are integrated in a variety of identity, networking, and storage services.
:
Not recommended: Virtual machines are treated as first-class resources across the identity, networking, and storage services.
:
For more information, see
[Write inclusive documentation](https://developers.google.com/style/inclusive-documentation).
following [](https://developers.google.com/style/word-list#following)
:
It's not necessary to use a noun after *following* unless it helps
provide clarity and enables accessibility. See [Tables](https://developers.google.com/style/tables#table-placement).
:
Recommended: ... in the following
code sample ...
:
Recommended: ... in the following
table ...
:
Recommended: ... do the following:
...
foo [](https://developers.google.com/style/word-list#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 example [](https://developers.google.com/style/word-list#for-example)
:
When you introduce an example using the phrase *for example*, follow the phrase by a comma. For clarity, when
introducing an example, separate the example using dashes, commas, or parentheses from the
rest of the sentence as appropriate, or introduce the example in a separate sentence.
:
Recommended: Enter a name for the instance---for example, `my-instance-99`.
:
Recommended: Enter a six-digit hex number (for example, `228B22`), and then click **OK**.
:
Recommended: Enter a six-digit hex number, and then click **OK** . For example, if you want the color forest
green, enter `228B22`.
:
For more information, see [Format examples](https://developers.google.com/style/format-examples).
for instance [](https://developers.google.com/style/word-list#for-instance)
:
Don't use the phrase *for instance* to introduce examples to avoid confusion with the
noun *instance*. Instead, use *for example*, *like*, or *such as*. For
more information, see [for example](https://developers.google.com/style/word-list#for-example).
frontend [](https://developers.google.com/style/word-list#frontend)
: Not *front-end* or *front end*.
functionality [](https://developers.google.com/style/word-list#functionality)
:
Use with caution. With respect to hardware or software,
*functionality* refers to a 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 [](https://developers.google.com/style/word-list#future)
:
Avoid in timeless documentation because this word or phrase can become
outdated.
:
See also [eventually](https://developers.google.com/style/word-list#eventually) and [soon](https://developers.google.com/style/word-list#soon). For more
information, see [Timeless
documentation](https://developers.google.com/style/timeless-documentation).
### G
GBps [](https://developers.google.com/style/word-list#gigabytes-per-second)
:
Short for *gigabytes per second*. By convention, we don't use
*GB/s*. For more information, see [Units of measurement](https://developers.google.com/style/units-of-measure).
Gbps [](https://developers.google.com/style/word-list#gbps)
:
Short for *gigabits per second*. By convention, we don't use
*Gb/s*. For more information, see [Units of measurement](https://developers.google.com/style/units-of-measure).
`gcloud` CLI [](https://developers.google.com/style/word-list#gcloud)
:
Use the full name *Google Cloud CLI* the first time that you mention
the product on a page.
gender-neutral he, him, or his (or she or
her)
[](https://developers.google.com/style/word-list#gender)
:
Don't use. Instead, use the singular *they* (see [Jane Austen and other famous authors violate what everyone learned in
their English class](http://www.pemberley.com/janeinfo/austheir.html)). Don't use *he/she* or *(s)he* or other
such punctuational approaches. For more information, see
[Pronouns](https://developers.google.com/style/pronouns).
generative AI [](https://developers.google.com/style/word-list#generative-ai)
:
Spell out *generative*. Use sentence case.
:
Don't use *gen AI* or *Gen AI*.
:
Don't hyphenate *generative AI* as an adjective unless you must do
so for clarity. See also [AI](https://developers.google.com/style/word-list#ai).
ghetto [](https://developers.google.com/style/word-list#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.
gimp, gimpy [](https://developers.google.com/style/word-list#gimp)
:
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 node [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/word-list#virtual-machine-instance).
Google, Googling [](https://developers.google.com/style/word-list#google)
:
Don't use as a verb or gerund. Instead, use *search with Google*.
Google Account, Google Accounts [](https://developers.google.com/style/word-list#google-account)
: Capitalize *Account*.
Google API Client Library for LANGUAGE (Java, .NET, etc.)
[](https://developers.google.com/style/word-list#google-api-client-library)
:
On second and subsequent use, you can abbreviate to
*LANGUAGE client library*.
Google API Console, Google APIs Console
[](https://developers.google.com/style/word-list#google-api-console)
:
Don't use. For more information, see [console](https://developers.google.com/style/word-list#console).
Google Cloud [](https://developers.google.com/style/word-list#gcp)
: Not *GCP*, *Cloud Platform*, or *Cloud*.
Google Cloud console [](https://developers.google.com/style/word-list#google-cloud-platform-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 console name. For more information, see [console](https://developers.google.com/style/word-list#console).
Google Cloud project ID [](https://developers.google.com/style/word-list#gcp-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
[](https://developers.google.com/style/word-list#google-developers-console)
:
Don't use. For more information, see [console](https://developers.google.com/style/word-list#console).
Google I/O [](https://developers.google.com/style/word-list#google-io)
: Not *I-O* or *IO*.
Google Play services [](https://developers.google.com/style/word-list#google-play-services)
: Write *services* in lowercase.
Google Play services SDK [](https://developers.google.com/style/word-list#google-play-services-SDK)
: Write *services* in lowercase.
grandfather clause, grand-father clause,
grand father clause
[](https://developers.google.com/style/word-list#grandfather-clause)
: Don't use. See [grandfathered](https://developers.google.com/style/word-list#grandfathered).
grandfathered [](https://developers.google.com/style/word-list#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, grey-box [](https://developers.google.com/style/word-list#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
[](https://developers.google.com/style/word-list#grayed-out)
: Don't use. Instead, use *unavailable*.
grayhat, greyhat, gray hat, grey hat
[](https://developers.google.com/style/word-list#grayhat)
:
Don't use. Follow the guidance for [black hat](https://developers.google.com/style/word-list#blackhat) when
referring to someone violating rules or laws.
graylist, greylist, gray list, grey list,
gray-list, grey-list
[](https://developers.google.com/style/word-list#graylist)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
graylisted, greylisted, gray listed, grey
listed, gray-listed, grey-listed
[](https://developers.google.com/style/word-list#graylisted)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
graylisting, greylisting, gray listing,
grey listing, gray-listing, grey-listing
[](https://developers.google.com/style/word-list#graylisting)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
`gsutil` [](https://developers.google.com/style/word-list#gsutil)
:
In the Google Cloud context, use code font for both the name of the
command-line utility and the command.
guru [](https://developers.google.com/style/word-list#guru)
:
If possible, use a more precise term. For example, if you mean
*expert* or *teacher*, use those terms.
guys, you guys [](https://developers.google.com/style/word-list#guys)
:
When referring to a group of people use non-gendered language, such as
*everyone* or *folks*.
gypsy [](https://developers.google.com/style/word-list#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.
### H
hamburger, hamburger menu
[](https://developers.google.com/style/word-list#hamburger)
:
Don't use. Instead use the `aria-label` for that particular
icon. For example, **Menu** .
For more information, see
[Buttons and icons](https://developers.google.com/style/ui-elements#buttons).
hands off, hands-off [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#hands-on)
:
Use a less figurative phrase, such as *customizable*, or write a
description of the activity.
hang, hung [](https://developers.google.com/style/word-list#hang)
:
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 figurative
language](https://developers.google.com/style/inclusive-documentation#figurative-language).
happiness and satisfaction [](https://developers.google.com/style/word-list#happiness)
:
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 documentation makes 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)](https://developers.google.com/style/word-list#service-level-indicator) 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](https://www.coursera.org/lecture/site-reliability-engineering-slos/the-happiness-test-ELmSr).
hardcode (verb), hardcoded (adjective) [](https://developers.google.com/style/word-list#hardcode)
:
Don't hyphenate.
he, him, his [](https://developers.google.com/style/word-list#he)
:
Don't use a gendered pronoun except for a specific individual of known
gender. Use *they* and *their* for the general singular pronoun.
healthcare [](https://developers.google.com/style/word-list#healthcare)
: Not *health care* or *health-care*.
health check [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#healthy)
: Don't use. See [health check](https://developers.google.com/style/word-list#health-check).
high availability (noun), high-availability (adjective)
[](https://developers.google.com/style/word-list#high-availability)
:
Spell as *high availability* when used as a noun and as *high-availability* when
used as an adjective. See also [load balancing (noun), load-balancing (adjective)](https://developers.google.com/style/word-list#load-balancing).
:
Lowercase except when part of a product name, but OK to abbreviate as
*HA* after first use.
higher [](https://developers.google.com/style/word-list#higher)
:
Don't use for a range of version numbers. Instead, use [*later*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/accessibility).
:
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) [](https://developers.google.com/style/word-list#high-performance-computing)
: Don't hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
hit [](https://developers.google.com/style/word-list#hit)
:
Don't use as a synonym for *click*, *press*, or *type*.
hold the pointer over [](https://developers.google.com/style/word-list#hold-the-pointer-over)
: Only use this verb phrase in the following cases:
- When the user needs to hold their mouse over a UI element, but not click the UI element. This action involves waiting for the UI to react---for example, waiting for a tooltip to open or waiting for a submenu to open.
- When the duration of time is important.
The phrase *point to* is more common.
: See also [point to](https://developers.google.com/style/word-list#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
[](https://developers.google.com/style/word-list#holiday)
:
Don't use to refer to the end of the year. Instead, refer to specific
quarters or months.
home screen [](https://developers.google.com/style/word-list#home-screen)
:
Two words in Android contexts; not *homescreen* or
*home-screen*.
hostname [](https://developers.google.com/style/word-list#hostname)
: Not *host name*.
hot [](https://developers.google.com/style/word-list#hot)
:
When possible, avoid [jargon](https://developers.google.com/style/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. However, see
[hotspot](https://developers.google.com/style/word-list#hotspot).
hotspot[](https://developers.google.com/style/word-list#hotspot)
:
In databases, *hotspots* occur when a small number of nearby rows are
accessed frequently in a short period of time, causing CPU spikes and
affecting performance. Use *hotspot* and *hotspots* as nouns.
Don't use verb and gerund forms such as *hotspotting*, because they
translate less consistently.
:
When you use *hotspot*, define it the first time that you use it on
a page as you normally do with jargon.
:
Recommended: Hotspots in one table
can affect the performance of other tables.
:
Not recommended: Hotspotting in one
table can affect the performance of other tables.
housekeeping, house keeping, house-keeping
[](https://developers.google.com/style/word-list#housekeeping)
:
Don't use. Instead, use less figurative and more precise terms, such as
*maintenance* and *cleanup*.
hover [](https://developers.google.com/style/word-list#hover)
:
Don't use. Instead use [*hold the pointer over*](https://developers.google.com/style/word-list#hold-the-pointer-over).
HTTPS [](https://developers.google.com/style/word-list#https)
: Not *HTTPs*.
### I
IaaS [](https://developers.google.com/style/word-list#iaas)
:
Write out on first mention: *infrastructure as a service (IaaS)*.
IAM [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#id)
: Not *Id* or *id,* except in string literals or enums.
:
In some contexts, it's best to spell out as *identifier* or
*identification*.
i.e. [](https://developers.google.com/style/word-list#ie)
:
Don't use. Instead, use phrases like *that is*. Many people confuse
*e.g.* and *i.e.*
if [](https://developers.google.com/style/word-list#if)
:
Wondering whether to use *if* or *whether*? See [whether](https://developers.google.com/style/word-list#whether).
:
Although it is common in casual usage to omit the word *then* in *if...then*
statements, you should include helper words like *then* in technical documentation. For
more information, see
[Use clear, precise, and unambiguous language](https://developers.google.com/style/translation#clear-language).
image [](https://developers.google.com/style/word-list#image)
:
*Image* by itself doesn't localize well because of its many meanings. Consider adding
context---for example, *disk image* or *container image*.
impact [](https://developers.google.com/style/word-list#impact)
:
Use only as a noun. Instead of writing that something *has an impact*, use the word *affect*.
:
Recommended: This issue affects
user experience.
:
Acceptable: This issue has an impact
on user experience.
:
Not recommended: This issue impacts
user experience.
index [](https://developers.google.com/style/word-list#index)
:
Use the plural *indexes* unless there is a domain-specific reason
(for example, a mathematical or financial context) to use *indices*.
ingest [](https://developers.google.com/style/word-list#ingest)
:
Use *import*, *load*, or *copy* when referring to simple movement of data. Use
*ingest* only when referring to such operations that also involve significant processing
of the data.
ingress [](https://developers.google.com/style/word-list#ingress)
:
When referring to the networking term, use lowercase. When referring
to the GKE term or API, capitalize *Ingress*.
in order to [](https://developers.google.com/style/word-list#in-order-to)
: Avoid *in order to*; instead, use *to*.
:
Use *in order to* when needed to clarify meaning or to make
something easier to read.
:
Recommended: You can use
monitoring to help identify issues.
:
Not recommended: You can use
monitoring in order to help identify issues.
:
Recommended: The infrastructure is
required in order to support search.
:
Not recommended: The infrastructure
is required to support search.
inline [](https://developers.google.com/style/word-list#inline)
:
One word as an adjective, *inline*, not *in line* or
*in-line*.
instance group [](https://developers.google.com/style/word-list#instance-group)
:
Don't abbreviate to *IG*. See also [managed instance
group](https://developers.google.com/style/word-list#mig).
intercluster [](https://developers.google.com/style/word-list#intercluster)
: Use unhyphenated *intercluster*, not *inter-cluster*.
interconnectAttachment [](https://developers.google.com/style/word-list#interconnect-attachment)
:
Use when referring to the API. Otherwise, use [*VLAN attachment*](https://developers.google.com/style/word-list#vlan).
Interconnect connection [](https://developers.google.com/style/word-list#interconnect-connection)
:
Only use *Interconnect connection* relative to a product as follows:
- CDN Interconnect connection
- Cloud Interconnect connection
- Dedicated Interconnect connection
- Partner Interconnect connection
OK to use *connection* on subsequent mentions.
:
When you're referring to a Google Cloud product, always specify the
product name. Don't use *Interconnect* or *interconnect* as
standalone terms, and don't use generic terms like *cloud interconnect connection* or *cross-connect*.
Interconnect connection location
[](https://developers.google.com/style/word-list#interconnect-connection-location)
:
Only refer to an *Interconnect connection location* in context of a
specific product, for example *CDN Interconnect*.
: OK to also use *colocation facility*.
interconnect type
[](https://developers.google.com/style/word-list#interconnect-type)
:
Don't use. Instead, use *connection type*. Examples of connection
types are a *dedicated connection* or a *connection provided by a service provider*.
interface [](https://developers.google.com/style/word-list#interface)
: OK to use as a noun.
:
Don't use as a verb. Instead, use *interact*, *talk*,
*speak*, *communicate*, or other similar terms.
internal DNS [](https://developers.google.com/style/word-list#internal-dns)
:
Write *internal* all lowercase except at the beginning of a
sentence, heading, or list item.
Internationalized Domain Name (IDN) [](https://developers.google.com/style/word-list#idn)
:
Write out and capitalize each word on first use. OK to abbreviate as
*IDN* after first use.
internet [](https://developers.google.com/style/word-list#internet)
: Lowercase except at the beginning of a sentence,
heading, or list item.
Internet Key Exchange (IKE) [](https://developers.google.com/style/word-list#ike)
:
Write out and capitalize each word on first use. OK to abbreviate
*IKE* after first use.
I/O (see also [Google I/O](https://developers.google.com/style/word-list#google-io)) [](https://developers.google.com/style/word-list#io)
: Not *I-O* or *IO*.
IoT [](https://developers.google.com/style/word-list#iot)
:
OK to use as an abbreviation for *Internet of Things*. Note
the lowercase *o*.
IPsec [](https://developers.google.com/style/word-list#ipsec)
: Not *IPSec* or *IPSECShort*.
:
Short for *Internet Protocol Security*. No need to spell out on
first mention.
### J
jank, janky [](https://developers.google.com/style/word-list#jank)
:
Use only to refer to a glitch or problem with graphics that is caused by a loss of data or
inadequate refresh rate. Don't use otherwise. Use a less figurative term to refer to something
of poor or unreliable quality.
just [](https://developers.google.com/style/word-list#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 run DML
statements in the same way that you'd run a `SELECT`
statement.
:
Not recommended: You can run DML
statements just as you'd run 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*](https://developers.google.com/style/word-list#simple).
:
Recommended: Use the namespace ID
`namespace:example-kind` or just `example-kind`.
### K
k8s [](https://developers.google.com/style/word-list#k8s)
: Don't use. Instead, use *Kubernetes*.
KBps [](https://developers.google.com/style/word-list#kilobytes-per-second)
:
Short for *kilobytes per second*. By convention, we don't use
*KB/s*. For more information, see [Units of measurement](https://developers.google.com/style/units-of-measure).
Kbps [](https://developers.google.com/style/word-list#kbps)
:
Short for *kilobits per second*. By convention, we don't use
*Kb/s*. For more information, see [Units of measurement](https://developers.google.com/style/units-of-measure).
kebab, kabob, kebab menu, kabob menu
[](https://developers.google.com/style/word-list#kebab)
:
Don't use. Instead use the `aria-label` for that particular
icon. For example,
**More** . For more information, see
[Buttons and icons](https://developers.google.com/style/ui-elements#buttons).
kebab case, kabob case, kebab-case,
kabob-case
[](https://developers.google.com/style/word-list#kebab-case)
: Don't use. Instead, use *dash-case*.
key [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#key-ring)
:
Use instead of *keyring* (without the space) when referring to a
grouping of Cloud KMS keys.
key-value pair [](https://developers.google.com/style/word-list#key-value)
: Use instead of *key/value pair* or *key value pair*.
kill [](https://developers.google.com/style/word-list#kill)
:
Avoid when possible. Instead, use words like *stop*, *exit*,
*cancel*, or *end*. For exceptions to this rule, see
[Documenting command-line
syntax](https://developers.google.com/style/code-syntax#linux-signals).
### L
lame [](https://developers.google.com/style/word-list#lame)
:
Don't use. Instead, use precise, non-figurative language to refer to a
deficiency in a component.
later [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
learnings [](https://developers.google.com/style/word-list#learnings)
:
Don't use. Instead, refer to *knowledge* or *things that you learned*.
left-nav, right-nav [](https://developers.google.com/style/word-list#left-nav)
: Don't use directional language. For more information, see
[Writing accessible documentation](https://developers.google.com/style/accessibility).
:
If referring to applications, use *[navigation menu](https://developers.google.com/style/ui-elements#term-navigation-menu)*.
:
If referring to navigational elements for documentation, use *content navigation menu*.
legacy [](https://developers.google.com/style/word-list#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. Don't use *legacy* with any sort of pejorative
connotation.
let's (as a contraction of *let us*)
[](https://developers.google.com/style/word-list#lets)
: 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)
[](https://developers.google.com/style/word-list#loa-cfa)
:
Write out and capitalize each word on first use. OK to abbreviate as
*LOA-CFA* after first use.
leverage [](https://developers.google.com/style/word-list#leverage)
:
Avoid using if you mean *use*. If possible, use a more precise term.
For example, *use*, *build on*, or *take advantage of*.
lifecycle [](https://developers.google.com/style/word-list#lifecycle)
: Not *life cycle* or *life-cycle*.
lift and shift [](https://developers.google.com/style/word-list#lift-and-shift)
:
See [rehost](https://developers.google.com/style/word-list#rehost).
like [](https://developers.google.com/style/word-list#like)
:
It's OK to use *like* for either drawing comparisons (in the sense of *similar to*)
or introducing examples (in the sense of *such as*).
:
Recommended: Common I/O operations, like reading files or
making network requests, can be asynchronous.
:
Recommended: The new compression algorithm works like a
dictionary encoder, replacing repeated strings with shorter codes.
:
See also [such as](https://developers.google.com/style/word-list#such-as). For more information, see [Format examples](https://developers.google.com/style/format-examples).
limits [](https://developers.google.com/style/word-list#limits)
:
In an API context, *limit* often refers to usage limits (number of
queries allowed per second or per day). Where possible, specify the kind
of limit that you mean, such as *usage limit* or *service limit*; the word *limit* can refer to many different kinds of
limits, including rules about acceptable use. See also [quota](https://developers.google.com/style/word-list#quota).
lint [](https://developers.google.com/style/word-list#lint)
:
Write both command-line tool name and command in lowercase. Use code font
except where inappropriate.
little-endian [](https://developers.google.com/style/word-list#little-endian)
: Hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
:
Recommended: The codebase assumes
little-endian byte ordering.
:
Not recommended: The codebase assumes
Little Endian byte ordering.
:
Not recommended: The codebase assumes
Little-endian byte ordering.
:
Not recommended: The codebase assumes
little endian byte ordering.
livestream [](https://developers.google.com/style/word-list#livestream)
: Not *live stream*.
load balancing (noun), load-balancing (adjective) [](https://developers.google.com/style/word-list#load-balancing)
:
Spell as *load balancing* when used as a noun and as *load-balancing* when
used as an adjective. See also [high availability (noun),
high-availability (adjective)](https://developers.google.com/style/word-list#high-availability).
lock screen [](https://developers.google.com/style/word-list#lock-screen)
:
Two words in Android contexts; not *lockscreen* or
*lock-screen*.
login (noun or adjective), log in (verb) [](https://developers.google.com/style/word-list#login)
: For the verb form, *sign in* is generally better.
:
If you're documenting a tool that uses the term *log in*, then use
that term.
long press
[](https://developers.google.com/style/word-list#long-press)
:
In Android documentation, don't use. Instead, use *touch \& hold*.
(Not *touch and hold*.)
long-running operation [](https://developers.google.com/style/word-list#lro)
: Not *long running operation*.
: OK to abbreviate as *LRO* after the first use.
lower [](https://developers.google.com/style/word-list#lower)
:
Don't use for a range of version numbers. Instead, use [*earlier*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/accessibility).
:
In Android documentation, use
*lower* for a range of version numbers, not *earlier*.
### M
male adapter [](https://developers.google.com/style/word-list#male-adapter)
: Don't use. Instead, use a genderless word like *plug*.
man hours, manhours, man-hours
[](https://developers.google.com/style/word-list#man-hours)
:
Avoid using gendered terms. Instead use terms like *person hours*.
man-in-the-middle (MITM) [](https://developers.google.com/style/word-list#mitm)
:
Avoid using gendered terms. Instead use terms like *on-path attacker* or *person-in-the-middle (PITM)*.
managed instance group (MIG) [](https://developers.google.com/style/word-list#mig)
:
OK to abbreviate to *MIG* on subsequent mention. See also
[instance group](https://developers.google.com/style/word-list#instance-group).
manmade, man made [](https://developers.google.com/style/word-list#manmade)
:
Avoid using gendered terms. Instead use a word like *artificial*,
*manufactured*, or *synthetic*.
manned [](https://developers.google.com/style/word-list#manned)
:
Avoid using gendered terms. Instead use terms like *staffed* or
*crewed*.
manpower, man power, man-power
[](https://developers.google.com/style/word-list#manpower)
:
Avoid using gendered terms. Instead use terms like *staff* or
*workforce*.
Markdown [](https://developers.google.com/style/word-list#markdown)
:
Always capitalized, even when you're referring to a nonstandard version.
master [](https://developers.google.com/style/word-list#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*.
| Guidance | Recommended | Not recommended |
|---|---|---|
| Don't use *master* in conjunction with *slave* in any context. | Cloud SQL primary/replica | Cloud SQL master/slave |
| Avoid using *master* where possible. | - GKE control plane - Jenkins controller - root key (in security) - primary key (in databases) | - GKE master plane - Jenkins master - master key (in security) - master key (in databases) |
:
If the command or code that you're documenting uses the literal word
*master*, then use this word only in direct reference to the code
item ([formatted as code](https://developers.google.com/style/code-in-text)), make it clear
what you're referring to, and use the new term thereafter.
: See also [*slave*](https://developers.google.com/style/word-list#slave).
Material Design [](https://developers.google.com/style/word-list#material-design)
: Capitalize each word in *Material Design*.
matrix [](https://developers.google.com/style/word-list#matrix)
:
Use the plural *matrixes* unless there is a domain-specific reason
(for example, a mathematical context) to use *matrices*.
may [](https://developers.google.com/style/word-list#may)
: In general, reserve for official policy or legal considerations.
:
To convey *possibility* , use *can* or *might*
instead.
:
To convey *permission* , use *can* instead.
:
See also [can](https://developers.google.com/style/word-list#can), [could](https://developers.google.com/style/word-list#could),
[might](https://developers.google.com/style/word-list#might), [must](https://developers.google.com/style/word-list#must),
[should](https://developers.google.com/style/word-list#should), and [would](https://developers.google.com/style/word-list#would).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
MBps [](https://developers.google.com/style/word-list#megabytes-per-second)
:
Short for *megabytes per second*. By convention, we don't use
*MB/s*. For more information, see
[Units of measurement](https://developers.google.com/style/units-of-measure).
Mbps [](https://developers.google.com/style/word-list#mbps)
:
Short for *megabits per second*. By convention, we don't use
*Mb/s*. For more information, see
[Units of measurement](https://developers.google.com/style/units-of-measure).
media type [](https://developers.google.com/style/word-list#media-type)
:
In general, use the term [*media type*](https://www.iana.org/assignments/media-types/media-types.xhtml).
In contexts where you need to refer to a *content type*---For example, if you mention
the `Content-Type` HTTP header---it's okay to use *content type* instead, to avoid
confusion. Don't use *MIME type*.
meta\* [](https://developers.google.com/style/word-list#meta)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
metafeed [](https://developers.google.com/style/word-list#metafeed)
: Not *meta-feed*.
metageneration [](https://developers.google.com/style/word-list#metageneration)
: Not *meta-generation*.
method [](https://developers.google.com/style/word-list#method)
:
In programming contexts where *method* refers to a member of a class
(as in Java), avoid also using the word generically to mean "approach" or
"manner."
metropolitan area (metro) [](https://developers.google.com/style/word-list#metro)
:
In networking, a *metro* is a city where a colocation facility is
located.
microservices [](https://developers.google.com/style/word-list#microservices)
: Not *Microservices* or *micro-services*.
might [](https://developers.google.com/style/word-list#might)
:
Use to convey possibility or an uncertain outcome (for example, "You
might be prompted to enter your credentials").
:
See also [can](https://developers.google.com/style/word-list#can), [could](https://developers.google.com/style/word-list#could),
[may](https://developers.google.com/style/word-list#may), [must](https://developers.google.com/style/word-list#must),
[should](https://developers.google.com/style/word-list#should), and [would](https://developers.google.com/style/word-list#would).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
MIME type [](https://developers.google.com/style/word-list#mime-type)
:
*MIME* stands for "Multipurpose Internet Mail Extensions," and was originally used to
refer to email standards.
Don't use *MIME* when you mean [*media type*](https://www.iana.org/assignments/media-types/media-types.xhtml).
If you feel that might be ambiguous to an audience familiar with the term *MIME*,
then you can write *media (MIME) type* for clarity.
mobile [](https://developers.google.com/style/word-list#mobile)
:
Don't use *mobile* as a standalone noun. Instead, specify
*mobile phone*, or if you're talking about more than phones, then use
*mobile device*.
mobile data [](https://developers.google.com/style/word-list#mobile-data)
: Use instead of *cellular data*.
mobile device [](https://developers.google.com/style/word-list#mobile-device)
:
Use *mobile device* when you're referring to more than phones (for
example, tablets and phones). It's OK to use *phone* (without
*mobile*) when the context is clear.
mobile network [](https://developers.google.com/style/word-list#mobile-network)
: Use instead of *cellular network*.
mobile phone [](https://developers.google.com/style/word-list#mobile-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.
mom test [](https://developers.google.com/style/word-list#mom-test)
:
Don't use *mom test*, *grandmother test*, *grandma test*,
or *girlfriend test*. Instead, use terms like *beginner user test* or *novice user test*.
monkey, monkey test [](https://developers.google.com/style/word-list#monkey)
:
Don't use *monkey* to refer to people. When referring to tests, refer
to the specific function. For example: *automated, random tests*.
multi\* [](https://developers.google.com/style/word-list#multi)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
multi-cluster [](https://developers.google.com/style/word-list#multi-cluster)
:
Hyphenate. We generally prefer to close prefixed words, but this is an
exception because it's an established term.
multi-region, multi-regional [](https://developers.google.com/style/word-list#multi-region)
:
Hyphenate when referring to a Google Cloud location that consists of more
than one region.
:
You can use *multi-regional* as an adjective in the context of
multi-regions, but consider *multi-region* as
an attributive noun instead, such as in "The dataset is in the EU
multi-region location." Use *multiregional* in other contexts.
multi-service [](https://developers.google.com/style/word-list#multi-service)
:
Hyphenate. We generally prefer to close prefixed words, but this is
an exception because it's an established term.
multi-tenancy [](https://developers.google.com/style/word-list#multi-tenancy)
:
Hyphenate. We generally prefer to close prefixed words, but this is
an exception because it's an established term.
must [](https://developers.google.com/style/word-list#must)
:
Use to describe a required action or state (for example, "You must have
the Editor role"). You can also write *you need* in order to convey a
requirement.
:
See also [can](https://developers.google.com/style/word-list#can), [could](https://developers.google.com/style/word-list#could),
[may](https://developers.google.com/style/word-list#may), [might](https://developers.google.com/style/word-list#might),
[should](https://developers.google.com/style/word-list#should), and [would](https://developers.google.com/style/word-list#would).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
### N
N/A [](https://developers.google.com/style/word-list#na)
:
Not *NA*. Spell out as *not available* or *not applicable*
on first reference.
name server [](https://developers.google.com/style/word-list#name-server)
: Not *nameserver*.
namespace [](https://developers.google.com/style/word-list#namespace)
: Not *name space*.
native [](https://developers.google.com/style/word-list#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*.
navigation bar [](https://developers.google.com/style/word-list#navigation-bar)
:
Don't use to refer to a *navigation menu*. For more information, see
[Navigation menu](https://developers.google.com/style/ui-elements#term-navigation-menu).
neither [](https://developers.google.com/style/word-list#neither)
: Write *neither A nor B*, not *neither A or B*.
network IP address
[](https://developers.google.com/style/word-list#network-ip-address)
: Don't use. Instead, use *internal IP address*.
new, newer [](https://developers.google.com/style/word-list#new)
:
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*](https://developers.google.com/style/word-list#later). Make sure that you provide
a version number or release date by which to understand *later*.
In Android documentation, use
[*higher*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
ninja [](https://developers.google.com/style/word-list#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.
non\* [](https://developers.google.com/style/word-list#non)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
nonce [](https://developers.google.com/style/word-list#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*.
non-key [](https://developers.google.com/style/word-list#non-key)
: An exception to our usual preference for closed forms.
NoOps [](https://developers.google.com/style/word-list#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*. Don't use
*noops*.
:
For an instruction that does nothing, use
[*no-op*](https://wikipedia.org/wiki/NOP_(code)) or the
specific instruction name for your context.
NoSQL [](https://developers.google.com/style/word-list#nosql)
: Not *No-SQL* or *No SQL*.
notification drawer
[](https://developers.google.com/style/word-list#notification-drawer)
: In Android contexts, don't hyphenate. Lowercase except at the beginning of a sentence,
heading, or list item.
now [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
nuke [](https://developers.google.com/style/word-list#nuke)
:
Don't use. Instead use *remove* or *attack*. For example, a
*denial-of-service attack*.
### O
OAuth 2.0 [](https://developers.google.com/style/word-list#oauth-20)
: Not *OAuth 2*, *OAuth2*, or *Oauth*.
off-the-shelf, commercial off-the-shelf
(COTS)
[](https://developers.google.com/style/word-list#off-the-shelf)
:
Use more widely understood terms like *ready-made*, *prebuilt*,
*standard*, or *default*.
old, older [](https://developers.google.com/style/word-list#old)
:
Don't use to refer to a previous version of a product. Instead, use
[*earlier*](https://developers.google.com/style/word-list#earlier).
:
Make sure that you provide a version number by which to understand
*earlier*.
:
In Android documentation, use
[*lower*](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
omnibox [](https://developers.google.com/style/word-list#omnibox)
: Don't use. Instead, use *address bar*.
once [](https://developers.google.com/style/word-list#once)
:
If you mean *after*, then use *after* instead of *once*.
on-premises [](https://developers.google.com/style/word-list#on-premises)
:
Not *on prem*, *on premise*, or *on-premise*. Hyphenate
when used as any part of speech.
:
Use to refer to a customer's resources that they manage in their own
facilities. Don't use *peer*.
:
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.
OS [](https://developers.google.com/style/word-list#os)
: OK to use as a shortening of "operating system."
outpost [](https://developers.google.com/style/word-list#outpost)
: Don't use. Instead, use *channel*.
:
Recommended: social media channels
outside the box, out of the box,
out-of-the-box
[](https://developers.google.com/style/word-list#out)
: Avoid using in a figurative way. OK to use literally.
overview
screen
[](https://developers.google.com/style/word-list#overview-screen)
:
In Android documentation, don't use. Instead, use *recents screen*.
### P
PaaS [](https://developers.google.com/style/word-list#paas)
: Write out on first mention: *platform as a service (PaaS)*.
page [](https://developers.google.com/style/word-list#page)
: Use *page* to refer to the following:
- A whole web page, which can include text, images, links, banners, navigational panes, and other features.
- A sub-page of a [console](https://developers.google.com/style/word-list#console) in particular.
See also
[documentation or document or documents](https://developers.google.com/style/word-list#documentation).
:
Recommended: To refresh the page, press F5.
parameter [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#parent-child)
: Not *parent -- child* or *parent---child*.
path [](https://developers.google.com/style/word-list#path)
:
Avoid using *filepath*, *file path*, *pathname*, or *path name* if possible.
peer gateway [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#peering-zone)
: Not *peer zone*.
per [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/units-of-measure#rates).
: 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 [](https://developers.google.com/style/word-list#performant)
: Avoid where possible. Instead, use a more precise term.
:
Recommended: an accurate machine
learning model
:
Not recommended: a performant machine
learning model
persist [](https://developers.google.com/style/word-list#persist)
:
Don't use as a transitive verb. It's best to avoid using as a verb at all,
especially in [passive voice](https://developers.google.com/style/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 [](https://developers.google.com/style/word-list#persistent-disk)
: Not *PD*.
: Lowercase except at the start of a sentence.
personally identifiable information (PII) [](https://developers.google.com/style/word-list#pii)
:
Some government agencies use the less common term *personally identifying information*; use this alternate term only in contexts
where you're referring to a document that uses this term.
pets versus cattle, pets vs. cattle, pets
v. cattle
[](https://developers.google.com/style/word-list#pets-versus-cattle)
:
Don't use. Instead, use more precise terms like *persistent versus dynamic* or *manually configured versus automated*. For more
information, see
[Avoid
figurative language](https://developers.google.com/style/inclusive-documentation#figurative-language).
plain text [](https://developers.google.com/style/word-list#plain-text)
:
In most contexts, use *plain text*, but use *plaintext* in a
cryptography context.
please [](https://developers.google.com/style/word-list#please)
:
Don't use *please* in the normal course of explaining how to use a
product, even if you're explaining a difficult task.
: 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 you,
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
[voice and tone](https://developers.google.com/style/tone#politeness).
plugin (noun), plug-in (adjective), plug in (verb) [](https://developers.google.com/style/word-list#plugin)
:
Use the noun form *plugin* when referring to the software component. Use the adjective
form *plug-in* when referring to the action of installing a software component. Use the
verb form *plug in* when you're describing the process of installing a software
component.
PM [](https://developers.google.com/style/word-list#pm)
: See [AM, PM](https://developers.google.com/style/word-list#am-pm).
point to [](https://developers.google.com/style/word-list#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)](https://developers.google.com/style/word-list#hold-the-pointer-over). In most cases, it's better to use the verb
phrase *hold the pointer over* if you want the user to wait for the
UI to react.
POJO [](https://developers.google.com/style/word-list#pojo)
:
If you're not actually writing about a Plain Old Java Object for a Java
audience, use *simple object*. You can write *a simple object, similar to a POJO in Java* if that helps your audience.
PoP [](https://developers.google.com/style/word-list#pop)
: Acronym for *point of presence*.
:
Recommended: point of presence (PoP)
:
Not recommended: point of presence
(POP)
pop-up, popup [](https://developers.google.com/style/word-list#pop-up)
: Don't use.
:
To describe a window that appears and asks for, or presents, additional
information, use [*dialog*](https://developers.google.com/style/word-list#dialog).
:
To describe a menu that rises from an interface (such as a right-click
context menu), use *menu*.
populate [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#port)
: Use *listen on* (not *to*).
portal [](https://developers.google.com/style/word-list#portal)
:
Don't use to refer to the Google Cloud console. For more information, see
[console](https://developers.google.com/style/word-list#console).
possible [](https://developers.google.com/style/word-list#possible)
:
Don't use *possible* or *impossible* to mean *you can* or
*you can't*.
PostgreSQL [](https://developers.google.com/style/word-list#postgresql)
:
If the UI uses the name *Postgres*, it's OK to match the UI. Don't
use *PostgreSQL*.
postmortem [](https://developers.google.com/style/word-list#postmortem)
: Avoid in general usage. Instead, use *retrospective*.
:
In disaster recovery (DR) and DevOps contexts, use *blameless postmortem*.
practitioner [](https://developers.google.com/style/word-list#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\* [](https://developers.google.com/style/word-list#pre)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
prebuilt [](https://developers.google.com/style/word-list#prebuilt)
: Not *pre-built*.
precapture [](https://developers.google.com/style/word-list#precapture)
: Not *pre-capture*.
preemptible [](https://developers.google.com/style/word-list#preemptible)
: Not *pre-emptible* or *pre-emptive*.
pre-existing [](https://developers.google.com/style/word-list#pre-existing)
: Not *preexisting*.
preferred pronouns
[](https://developers.google.com/style/word-list#preferred-pronouns)
: Don't use. Instead, use *pronouns*.
prerecorded [](https://developers.google.com/style/word-list#prerecorded)
: Not *pre-recorded*.
pre-shared key [](https://developers.google.com/style/word-list#pre-shared-key)
: Not *preshared key*.
presently, at present [](https://developers.google.com/style/word-list#presently)
:
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](https://developers.google.com/style/word-list#as-of-this-writing) and
[currently](https://developers.google.com/style/word-list#currently).
:
Recommended: This setting is required.
:
Not recommended: At present, this
setting is required.
:
For more information, see
[Timeless documentation](https://developers.google.com/style/timeless-documentation).
press [](https://developers.google.com/style/word-list#press)
:
Use when referring to pressing a key or a key combination to cause an
action to occur. Also use for mechanical buttons.
: For on-screen and soft (capacitive) buttons, use *tap*.
:
Recommended: Press
Control+C (or Command+C on macOS).
presubmit [](https://developers.google.com/style/word-list#presubmit)
: Not *pre-submit*.
primitive [](https://developers.google.com/style/word-list#primitive)
:
Use with caution. Don't use *primitive* in a disparaging sense.
project [](https://developers.google.com/style/word-list#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.
proper, properly [](https://developers.google.com/style/word-list#proper)
:
Avoid *proper* and *properly*, which are vague and can imply subjective judgments of
correctness or superiority. Instead, focus on describing the technical details. For more
information, see [Use precise,
objective language](https://developers.google.com/style/inclusive-documentation#subjective-language).
:
Recommended: Verify that the port is open and accepting
connections.
:
Not recommended: Ensure the port is properly configured.
pros [](https://developers.google.com/style/word-list#pros)
:
Don't use. Instead, use a more precise term, such as *advantages*.
### Q
quick, quickly [](https://developers.google.com/style/word-list#quick)
:
What might be quick for you might not be quick for others. Try eliminating this word from the
sentence. For more information, see [Use precise, objective language](https://developers.google.com/style/inclusive-documentation#subjective-language).
quota [](https://developers.google.com/style/word-list#quota)
:
In API contexts, often refers to API usage limits. Where possible, it's
best to use a more specific term, such as *usage limit*; the word
*quota* means many different things to many different people.
:
In some contexts, such as Google Cloud documentation, the standard term is
*quota*, so use that term.
### R
RDP [](https://developers.google.com/style/word-list#rdp)
:
Don't use as a verb. Instead, use *connect using RDP*. If it's
clear from context that they're using RDP, it's OK to use *connect*.
re\* [](https://developers.google.com/style/word-list#re)
: See [guidance about hyphens with prefixes](https://developers.google.com/style/hyphens#prefixes).
read-only [](https://developers.google.com/style/word-list#read-only)
: Not *read only*. Always hyphenate *read-only*.
recents screen [](https://developers.google.com/style/word-list#recents-screen)
: In Android contexts, use instead of *overview screen*.
redline [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#regex)
: Don't use. Instead, use *regular expression*.
rehost [](https://developers.google.com/style/word-list#lift-and-shift)
:
Use to describe the migration of an app or workload with no changes or
minimal changes to that app or workload. Also known as *lift and shift*. For more
information, see [Rehost: lift and shift](https://cloud.google.com/architecture/migration-to-gcp-getting-started#rehost_lift_and_shift) in the Cloud Architecture Center.
:
On first mention, associate rehost with lift and shift. Okay to use *rehosting* as needed
after first mention.
:
Recommended: You can use this reference architecture to
efficiently rehost (lift and shift) on-premises applications to the cloud.
:
Recommended: The first step to modernization is to rehost
your application in the cloud (also known as lift and shift).
:
Don't use *the forklift approach*.
repo [](https://developers.google.com/style/word-list#repo)
: Don't use. Instead, use *repository*.
Representational State Transfer
[](https://developers.google.com/style/word-list#rest)
:
Don't use. To people unfamiliar with REST, this acronym expansion is
meaningless; it's better to refer to it as REST and not explain what it
stands for.
reservation, off the
[](https://developers.google.com/style/word-list#reservation)
: Don't use.
resource record set [](https://developers.google.com/style/word-list#resource-record-set)
: Not *resource recordset*.
retarded [](https://developers.google.com/style/word-list#retarded)
:
Don't use. If you are referring to a system or component being slowed,
use the word *slowed*.
retriable, triable [](https://developers.google.com/style/word-list#retriable)
:
Don't use *retriable* or *triable*, unless a code item uses that
spelling. Outside of code font, write around the term.
retryable, tryable [](https://developers.google.com/style/word-list#retryable)
:
Where possible, write around *retryable* and *tryable*. For
example, write out *you can try it again* or *can be tried again*.
review [](https://developers.google.com/style/word-list#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.
:
Avoid using phrasing like "If you've never heard of OAuth, then review the
OAuth documentation."
RFC [](https://developers.google.com/style/word-list#rfc)
:
When referencing an RFC specification, use a space between *RFC* and
the number (for example, *RFC 2318*).
roll out [](https://developers.google.com/style/word-list#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*.
RTFM [](https://developers.google.com/style/word-list#rtfm)
:
Don't use. Instead, use a more precise phrase like "For more information,
see ...."
runbook [](https://developers.google.com/style/word-list#runbook)
: Not *run book*.
runtime, run time [](https://developers.google.com/style/word-list#runtime)
:
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.
### S
SaaS [](https://developers.google.com/style/word-list#saas)
: Write out on first mention: *software as a service (SaaS)*.
sane [](https://developers.google.com/style/word-list#sane)
: Don't use. Instead use a word like *valid* or *sensible*.
sanity check [](https://developers.google.com/style/word-list#sanity-check)
:
Don't use. Instead, use a term like *quick check*, *confidence check*, *preliminary check* or *coherence check*.
SAP [](https://developers.google.com/style/word-list#sap)
:
Pronounced as the individual letters *S*, *A*, *P*, so
write *an SAP system*, not *a SAP system*. For more information, see
[Indefinite articles before abbreviations](https://developers.google.com/style/abbreviations#articles).
scale [](https://developers.google.com/style/word-list#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) [](https://developers.google.com/style/word-list#screenshot)
: Not *screen shot* or *screensnap*.
: Don't use as a verb; instead, use *take a screenshot*.
scroll [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/accessibility#document-rendering).
Search (as part of product name) [](https://developers.google.com/style/word-list#search)
:
Capitalize *Search* when referring to a product like Google Search.
Search Console [](https://developers.google.com/style/word-list#search-console)
: Capitalize each word in *Search Console*.
see [](https://developers.google.com/style/word-list#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
[Cross-references and linking](https://developers.google.com/style/cross-references).
select [](https://developers.google.com/style/word-list#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**.
sensitive [](https://developers.google.com/style/word-list#sensitive)
:
*Sensitive* data is data for which the release might be harmful. See
[confidential](https://developers.google.com/style/word-list#confidential).
service [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#service-level-indicator)
: Lowercase except at the beginning of a sentence,
heading, or list item.
: OK to abbreviate as *SLI* after first use.
service level objective [](https://developers.google.com/style/word-list#service-level-objective)
: Lowercase except at the beginning of a sentence,
heading, or list item.
: OK to abbreviate as *SLO* after first use.
setup (noun or adjective), set up (verb) [](https://developers.google.com/style/word-list#setup)
sexy [](https://developers.google.com/style/word-list#sexy)
:
Don't use. Instead, use precise, positive words, such as *fast*,
*powerful*, or *elegant*.
SHA-1 [](https://developers.google.com/style/word-list#sha-1)
:
Not *SHA1*, except in string literals/enums and in hyphenated phrases
such as *HSA-SHA1*.
shall [](https://developers.google.com/style/word-list#shall)
:
Avoid *shall* except under advice from a lawyer. For more
information, see [should](https://developers.google.com/style/word-list#should).
she, her, hers [](https://developers.google.com/style/word-list#she)
:
Don't use a gendered pronoun except for a specific individual of known
gender. Use *they* and *their* for the general singular pronoun.
sherpa [](https://developers.google.com/style/word-list#sherpa)
:
If possible, use a more precise term. For example, if you mean
*guide*, use that term.
shift left [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#should)
: Generally avoid.
:
Because *should* is ambiguous by definition, it can be problematic. For more information
and alternatives, see
[Word choice for recommendations and requirements](https://developers.google.com/style/prescriptive-documentation#word-choice).
:
See also [can](https://developers.google.com/style/word-list#can), [could](https://developers.google.com/style/word-list#could),
[may](https://developers.google.com/style/word-list#may), [might](https://developers.google.com/style/word-list#might),
[must](https://developers.google.com/style/word-list#must), and [would](https://developers.google.com/style/word-list#would).
sign-in (noun or adjective), sign in (verb) [](https://developers.google.com/style/word-list#sign-in)
: Not *log in* or *signin*.
sign into [](https://developers.google.com/style/word-list#sign-into)
: Don't use. Instead, use *sign in to*.
sign-on, sign on [](https://developers.google.com/style/word-list#sign-on)
:
Don't use either form on its own. Use the hyphenated version as part of
*single sign-on*.
sign-out (noun or adjective), sign out (verb) [](https://developers.google.com/style/word-list#sign-out)
: Not *log out* or *signout*.
simple, simply [](https://developers.google.com/style/word-list#simple)
:
What might be simple for you might not be simple for others. Try eliminating this word from
the sentence because usually the same meaning can be conveyed without it. For more
information, see [Use precise,
objective language](https://developers.google.com/style/inclusive-documentation#subjective-language).
since [](https://developers.google.com/style/word-list#since)
:
If you mean *because*, then use *because* instead of
*since*. *Since* is ambiguous; it can refer to the passage of
time. *Because* refers to causation or the reason for something.
single most [](https://developers.google.com/style/word-list#single-most)
: Not *singlemost*.
single pane of glass [](https://developers.google.com/style/word-list#single-pane-of-glass)
:
Avoid. This term is used to favorably compare a centralized control and
monitoring interface against the alternative of several disparate
interfaces. It can almost always be replaced by *single interface* or
*unified interface*.
single sign-on (noun or adjective) [](https://developers.google.com/style/word-list#single-sign-on)
slave [](https://developers.google.com/style/word-list#slave)
:
Don't use. Instead, use alternative terms appropriate to your domain, such
as *worker* or *replica*.
:
If you're replacing the terms *master* and *slave* together,
then consider such combinations as *primary*/*secondary*,
*primary*/*replica*, *original*/*replica*,
*controller*/*worker*, *initiator*/*responder*,
*mixer*/*leaf*, *aggregator*/*collector*,
*publisher*/*subscriber*, *leader*/*follower*, and
*active*/*standby*.
:
If the command or code that you're documenting uses the literal word
*slave*, then use this word only in direct reference to the code item
([formatted as code](https://developers.google.com/style/code-in-text)), make it clear what
you're referring to, and use the new term thereafter. For example, "Invoke
the secondary (`slave`) process directly when debugging issues
between the primary and secondary processes."
: See also [master](https://developers.google.com/style/word-list#master).
slice and dice [](https://developers.google.com/style/word-list#slice)
:
Don't use the phrase *slice and dice*. Instead, use specific terms
appropriate to the task that you're describing. Some possible options
include: *segment data for analysis* or *break information into smaller parts*.
smartphone, smart phone
[](https://developers.google.com/style/word-list#smartphone)
:
Don't use. Instead, use [*mobile phone*](https://developers.google.com/style/word-list#mobile) 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.
soon [](https://developers.google.com/style/word-list#soon)
:
Avoid 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](https://developers.google.com/style/word-list#eventually) and
[future](https://developers.google.com/style/word-list#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](https://developers.google.com/style/timeless-documentation).
spin up [](https://developers.google.com/style/word-list#spin-up)
:
As 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*.
SQL [](https://developers.google.com/style/word-list#sql)
: Refer to *a SQL* (pronounced "a sequel"), not *an SQL*. For more
information, see
[Indefinite articles before abbreviations](https://developers.google.com/style/abbreviations#articles).
ssh and SSH [](https://developers.google.com/style/word-list#ssh)
:
Don'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.
:
Recommended: Connect to the instance
by using SSH.
:
Not recommended: `ssh` into
your remote shell.
ssh'ing [](https://developers.google.com/style/word-list#sshing)
: Don't use. See also [ssh and SSH](https://developers.google.com/style/word-list#ssh).
:
Recommended: When you use
`ssh` to log in ...
startup (noun or adjective), start up (verb) [](https://developers.google.com/style/word-list#startup)
static external IP address [](https://developers.google.com/style/word-list#static-external-ip-address)
:
Don't use *static IP address* or *external IP address* to refer
to static external IP addresses.
status bar [](https://developers.google.com/style/word-list#status-bar)
: Not *statusbar* or *status-bar*.
: Lowercase except at the beginning of a sentence,
heading, or list item.
STONITH, STOMITH [](https://developers.google.com/style/word-list#stonith)
:
Avoid using
[graphic or
metaphorical language](https://developers.google.com/style/inclusive-documentation#graphic-language). Instead, explain the relevant feature, such as
*fence failed nodes*.
style sheet [](https://developers.google.com/style/word-list#style-sheet)
:
*Style sheet* and *stylesheet* are both acceptable spellings. However, be consistent
with your choice throughout a given document.
sub-command [](https://developers.google.com/style/word-list#sub-command)
: Not *subcommand*.
subnet [](https://developers.google.com/style/word-list#subnet)
:
OK to use as a shortening of *subnetwork*. Use the same term consistently throughout your
document. For more
information, see [Subnets vs. subnetworks](https://cloud.google.com/compute/docs/vpc/#subnets_vs_subnetworks).
subtree [](https://developers.google.com/style/word-list#subtree)
: Not *sub-tree*.
subzone [](https://developers.google.com/style/word-list#subzone)
: Not *sub-zone* or *sub zone*.
such as [](https://developers.google.com/style/word-list#such-as)
:
Use *such as* to introduce examples or draw comparisons. Note that *such as*,
*like*, and *include* introduce non-exhaustive lists, so it's redundant to combine
them with *etc.*, *so forth*, or *and more*. See also [etc.](https://developers.google.com/style/word-list#etc),
[like](https://developers.google.com/style/word-list#like). For more information, see [Format
examples](https://developers.google.com/style/format-examples).
surface [](https://developers.google.com/style/word-list#surface)
:
Avoid 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.
### T
tab [](https://developers.google.com/style/word-list#tab)
:
When referring to the sub-pages of a [console](https://developers.google.com/style/word-list#console), use
*page* instead of *tab*.
table name [](https://developers.google.com/style/word-list#table-name)
: Two words. Set specific table names in code font.
tablet [](https://developers.google.com/style/word-list#tablet)
:
*Tablet* is OK. If you don't know whether it's a tablet or a phone,
use *device*.
tag [](https://developers.google.com/style/word-list#tag)
: See [element](https://developers.google.com/style/word-list#element).
tap [](https://developers.google.com/style/word-list#tap)
:
In Android documentation, use for on-screen and soft (capacitive)
buttons.
:
Use instead of *click* when the environment is definitely a
touch device.
:
Use instead of *touch*. However, *touch \& hold* (not *touch and hold*) is OK to use.
: For mechanical buttons, use [*press*](https://developers.google.com/style/word-list#press).
tap \&
hold, tap and hold
[](https://developers.google.com/style/word-list#tap-and-hold)
:
In Android documentation, don't use. Instead, use *touch \& hold*.
(Not *touch and hold*.)
tarball [](https://developers.google.com/style/word-list#tarball)
: Don't use. Instead, use *tar file*.
target [](https://developers.google.com/style/word-list#target)
:
Avoid using as a verb when possible, especially in reference to people.
For some readers, *target* has aggressive connotations. Instead of
"targeting" audiences, we try to attract them or appeal to them or make
their lives easier.
:
It's OK to use *target* as an adjective, as in *target audience*, but consider rephrasing for clarity. Alternatives
include phrases such as *intended for*, *looking for*,
*focused on*, and *interacting with*.
terminate [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/code-syntax#linux-signals).
:
:
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 [](https://developers.google.com/style/word-list#textbox)
:
Don't use. Instead, use *box*. For more information, see
[Text box](https://developers.google.com/style/ui-elements#term-textbox).
:
In Google Cloud documentation, use
*field* instead of *box*. For example, "In the **Instance**
field, specify a value less than 64 characters long."
:
In Google Workspace documentation, use
*field* instead of *box*. For example, "In the **Instance**
field, specify a value less than 64 characters long."
their (singular) [](https://developers.google.com/style/word-list#their)
: See [*they*](https://developers.google.com/style/word-list#they).
then [](https://developers.google.com/style/word-list#then)
:
Although it is common in casual usage to omit the word *then* in *if...then*
statements, you should include helper words like *then* in technical documentation. For
more information, see
[Use clear, precise, and unambiguous language](https://developers.google.com/style/translation#clear-language).
they (singular) [](https://developers.google.com/style/word-list#they)
:
This is our preferred gender-neutral pronoun. Whether used as singular or plural, it always
takes the plural verb.
:
Recommended: A user enters their password, and then they
insert their security key.
:
See also [gender-neutral he](https://developers.google.com/style/word-list#gender).
third party (noun), third-party (adjective) [](https://developers.google.com/style/word-list#third-party)
:
Spell as *third party* when used as a noun and as *third-party* when used as an
adjective.
:
Avoid abbreviating to *3rd party* or *3rd-party*. For more information, see [Ordinal numbers](https://developers.google.com/style/numbers#ordinal-numbers).
this, that [](https://developers.google.com/style/word-list#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---otherwise, your reader
probably won't know what noun you're referring to, either.
timeframe [](https://developers.google.com/style/word-list#time-frame)
:
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 as one word.
timeout (noun), time out (verb) [](https://developers.google.com/style/word-list#timeout)
timestamp [](https://developers.google.com/style/word-list#time-stamp)
: Not *time stamp*.
time to live [](https://developers.google.com/style/word-list#ttl)
: Not *time-to-live*. Abbreviate as *TTL* after first use.
time zone (noun), time-zone (adjective) [](https://developers.google.com/style/word-list#time-zone)
:
Spell as *time zone* when used as a noun and as *time-zone* when used as an
adjective. See also [wake lock (noun), wake-lock (adjective)](https://developers.google.com/style/word-list#wake-lock).
tl;dr [](https://developers.google.com/style/word-list#tldr)
:
Don't use. Instead, use something like *To summarize*, or revise the
sentence.
toolkit [](https://developers.google.com/style/word-list#toolkit)
: Not *tool-kit* or *tool kit*.
touch
[](https://developers.google.com/style/word-list#touch)
:
In Android documentation, don't use. Instead, use *tap*. However,
*touch \& hold* is OK to use.
"touch \& hold" [](https://developers.google.com/style/word-list#touch-and-hold)
: Not *touch and hold*.
touchscreen [](https://developers.google.com/style/word-list#touchscreen)
: Not *touch screen*
traditional [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#transpile)
: Not *transcompile*.
tribal knowledge, tribal wisdom
[](https://developers.google.com/style/word-list#tribal-knowledge)
:
Don't use. Instead, use a less figurative term to indicate knowledge held
by a group of people.
trojan [](https://developers.google.com/style/word-list#trojan)
: Lowercase when referring to malware.
turn on [](https://developers.google.com/style/word-list#turn-on)
:
In procedures, use the appropriate label and action for the
[UI element](https://developers.google.com/style/ui-elements) that the user interacts with.
:
For turning on or activating an option or feature, use *turn on* or
[enable](https://developers.google.com/style/word-list#enable) consistently. Use the same term consistently throughout your
document.
:
Recommended: To turn on Magic Mode,
follow these steps.
:
Recommended: In **Settings** , click
the **Magic mode** toggle to the on position.
tutorial [](https://developers.google.com/style/word-list#tutorial)
: OK to use. See [documentation](https://developers.google.com/style/word-list#documentation).
type [](https://developers.google.com/style/word-list#type)
:
In general, use [enter](https://developers.google.com/style/word-list#enter) instead of *type* because
there is typically more than one way to enter text than typing (such as
pasting text or speaking).
typically [](https://developers.google.com/style/word-list#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.
### U
UI [](https://developers.google.com/style/word-list#ui)
:
Don't use generically to refer to a page or dashboard. Use a more specific
term like [*page*](https://developers.google.com/style/word-list#page) or
[*console*](https://developers.google.com/style/word-list#console). If a specific term is unavailable,
use *web interface*.
:
Recommended: In the Google Cloud
console
:
Recommended: On the **Cloud Tasks**
page
:
Recommended: In the Secure Source
Manager web interface
:
Not recommended: In the **Cloud
Tasks** UI
unarchive [](https://developers.google.com/style/word-list#unarchive)
: Don't use. Instead, use *extract*.
uncheck [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#uncompress)
: Don't use. Instead, use *extract*.
under [](https://developers.google.com/style/word-list#under)
:
Don't use for a range of version numbers. Instead,
use [*earlier*](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#unicode)
: Not *UNICODE*.
Unix-like [](https://developers.google.com/style/word-list#unix-like)
: Not *Unixlike* or *Unix like*.
Unix epoch time [](https://developers.google.com/style/word-list#unix-epoch-time)
:
Use instead of *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 [](https://developers.google.com/style/word-list#unselect)
:
Don't use. Instead, use *clear* for checkboxes, and *deselect*
for other UI elements.
:
unsighted [](https://developers.google.com/style/word-list#unsighted)
: Don't use. See [blind](https://developers.google.com/style/word-list#blind).
untar [](https://developers.google.com/style/word-list#untar)
: Don't use. Instead, use *extract*.
unzip [](https://developers.google.com/style/word-list#unzip)
: Don't use. Instead, use *extract*.
US [](https://developers.google.com/style/word-list#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](https://developers.google.com/style/abbreviations#periods).
user [](https://developers.google.com/style/word-list#user)
:
Use the word *user* only to refer to the user of the software that
your reader is developing. Otherwise, address the reader as *you*
and assume that they will complete the tasks that you're documenting. For
more information, see [Second person and first
person](https://developers.google.com/style/person).
user base [](https://developers.google.com/style/word-list#user-base)
: Not *userbase*.
using [](https://developers.google.com/style/word-list#using)
:
Where *using* might have more than one interpretation, use *by using* or
*that use* instead to help clarify the logic of the sentence.
:
Recommended: Remove the Compute Engine VMs by using the
test tag.
:
Recommended: Identify the service accounts that use the
Google Cloud console.
:
Not recommended: Filter the IAM roles using custom
permissions.
:
It's OK to use *using* (or *with*) when misinterpretation is unlikely.
:
Recommended: You can connect to Cloud SQL using IAM
database authentication.
UTF [](https://developers.google.com/style/word-list#utf)
:
Include the hyphen in the names of Unicode encodings, such as
*UTF-8*, *UTF-16*, and *UTF-32*.
:
utilize, utilization [](https://developers.google.com/style/word-list#utilize)
:
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
v (abbreviating *version*) [](https://developers.google.com/style/word-list#v)
: Use lowercase.
via [](https://developers.google.com/style/word-list#via)
: Don't use.
vice versa [](https://developers.google.com/style/word-list#vice-versa)
:
Don't use. Write out the relationship explicitly. To emphasize the
reciprocal or contrasting relationship, you can use a more precise term
like *conversely*.
:
Not recommended: You can copy local
files to the cloud and vice versa.
:
Recommended: You can upload local
files to the cloud or download cloud files to your local environment.
:
Recommended: You can upload local
files to the cloud. Conversely, you can download cloud files to your local
environment.
virtual machine (VM) instance [](https://developers.google.com/style/word-list#virtual-machine-instance)
:
Use when first introducing virtual machines on a given page. For
subsequent mentions, you can use *VM instance* or *VM*.
:
For Google Cloud: on first mention of a Compute Engine VM,
use *Compute Engine instance* and then use *compute instance*
throughout the rest of the document. If you need to indicate other types of
VMs, use *VM*, *VM instance*, or *bare metal instance*.
:
See also [GKE node](https://developers.google.com/style/word-list#gke-node).
visually challenged
[](https://developers.google.com/style/word-list#visually-challenged)
: See [blind](https://developers.google.com/style/word-list#blind).
VLAN attachment [](https://developers.google.com/style/word-list#vlan)
:
Don't use the following: *interconnect attachment (VLAN)*,
*Interconnect attachment*, *Cloud Interconnect attachment*, or
any variation thereof. See also
[interconnectAttachment](https://developers.google.com/style/word-list#interconnect-attachment).
voila [](https://developers.google.com/style/word-list#voila)
: Don't use.
voodoo [](https://developers.google.com/style/word-list#voodoo)
:
Don't use. Instead, use a term like *mysterious*, *complicated*,
or *nondeterministic*.
vs. [](https://developers.google.com/style/word-list#vs)
:
Don't use *vs.* as an abbreviation for *versus*; instead, use
the unabbreviated *versus*.
### W
wake lock (noun), wake-lock (adjective) [](https://developers.google.com/style/word-list#wake-lock)
:
Spell as *wake lock* when used as a noun and as *wake-lock* when used as an
adjective. See also [time zone (noun), time-zone (adjective)](https://developers.google.com/style/word-list#time-zone).
walkthrough [](https://developers.google.com/style/word-list#walkthrough)
: Not *walk-through*.
war room, warroom, war-room
[](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#warm)
:
When possible, avoid [jargon](https://developers.google.com/style/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.
we [](https://developers.google.com/style/word-list#we)
:
Don't use *we* (or other first-person plural pronouns such as
*our* or *us*) to address the reader who is performing the
tasks that you're documenting. Instead, use *you*.
:
It's OK to use *we* to refer to the organization that's represented
as the author of the document as long as the antecedent is clear. For more
information, see
[Second person and first person](https://developers.google.com/style/person).
web (lowercase) [](https://developers.google.com/style/word-list#web)
WebAssembly, Wasm [](https://developers.google.com/style/word-list#wasm)
: Use the capitalization established in the
[WebAssembly specification](https://webassembly.github.io/spec/core/intro/introduction.html#introduction).
web application firewall (lowercase) [](https://developers.google.com/style/word-list#web-application-firewall)
webmaster, web master
[](https://developers.google.com/style/word-list#webmaster)
:
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 server [](https://developers.google.com/style/word-list#web-server)
: Not *webserver*.
whether [](https://developers.google.com/style/word-list#whether)
:
- To decide whether it's more appropriate to use *if* or *whether*, see [Grammar Girl's
discussion of *if* and *whether*](http://www.quickanddirtytips.com/education/grammar/if-versus-whether).
- To decide whether you need to add *or not* when using *whether*, see [the New York
Times's blog post about whether (or not)](http://afterdeadline.blogs.nytimes.com/2010/03/01/whether-or-not/).
while [](https://developers.google.com/style/word-list#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 [](https://developers.google.com/style/word-list#white-box)
:
Avoid using *white-box*, *whitebox*, or *white box* to
describe monitoring and testing. Consider using a more precise term for
clarity.
- For monitoring, use *introspective monitoring*.
- For testing, use *clear-box testing*.
white glove, white-glove, whiteglove
[](https://developers.google.com/style/word-list#white-glove)
:
Avoid using. Instead use terms like *high-touch*, *premium*, or
*platinum-level*.
whitehat, white hat, white-hat
[](https://developers.google.com/style/word-list#whitehat)
:
Don't use. Instead, use precise terms for the kind of compliance, such as
*legal*, *ethical*, or *following the rules*.
white label, whitelabel, white-label
[](https://developers.google.com/style/word-list#white-label)
:
Don't use. Instead, use a more precise term for your context, such as
*unbranded*, *unlabeled*, or *blank label*.
whitelist, white list, white-list
[](https://developers.google.com/style/word-list#whitelist)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
whitelisted, white listed, white-listed
[](https://developers.google.com/style/word-list#whitelisted)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
whitelisting, white listing, white-listing
[](https://developers.google.com/style/word-list#whitelisting)
: Don't use. See [blacklist](https://developers.google.com/style/word-list#blacklist).
whitepaper [](https://developers.google.com/style/word-list#whitepaper)
: Not *white paper*.
: When possible, use a more precise term. The term *whitepaper* has a variety of
meanings in various contexts. If you must use the term *whitepaper*, also use descriptive
terms to provide context.
whitespace [](https://developers.google.com/style/word-list#whitespace)
: Not *white space*.
wildcard [](https://developers.google.com/style/word-list#wildcard)
: Not *wild card*.
will [](https://developers.google.com/style/word-list#will)
:
Avoid. Applies equally to its past tense, *would*. See also
[Present tense](https://developers.google.com/style/tense) and
[Documenting future features](https://developers.google.com/style/future).
wish [](https://developers.google.com/style/word-list#wish)
: Don't use. Instead, use a word like *want* or *need*.
with [](https://developers.google.com/style/word-list#with)
: Don't use *with* when expressing ownership:
:
Recommended: A handset that has 2 GB
of RAM.
:
Not recommended: A handset with 2 GB
of RAM.
: Don't use *with* when expressing use:
:
Recommended: Use the debugging tool
to debug.
:
Not recommended: Debug this tool with
the debugging tool.
workload [](https://developers.google.com/style/word-list#workload)
:
The term *workload* might refer to software, like an app or
a service; to app resources, like data and infrastructure; or to physical
components that work together.
:
Where possible, use a more precise term to describe what you mean. If you
use the term *workload*, define your meaning on first use as you
normally would with jargon and other ambiguous terms.
World Wide Web [](https://developers.google.com/style/word-list#world-wide-web)
: Don't use. Instead, use *web*.
would [](https://developers.google.com/style/word-list#would)
: Avoid using. Instead, use *can* where possible.
:
See also [can](https://developers.google.com/style/word-list#can), [could](https://developers.google.com/style/word-list#could),
[may](https://developers.google.com/style/word-list#may), [might](https://developers.google.com/style/word-list#might),
[must](https://developers.google.com/style/word-list#must), and [should](https://developers.google.com/style/word-list#should).
:
For information about clarifying who's performing an action, see
[Active voice](https://developers.google.com/style/voice).
:
For information about tenses, see [Present
tense](https://developers.google.com/style/tense).
### Y
ymmv [](https://developers.google.com/style/word-list#ymmv)
:
Don't use. Instead, use something like *Your results might vary*.
you [](https://developers.google.com/style/word-list#you)
:
Use *you* instead of [*user*](https://developers.google.com/style/word-list#user) to address the
reader of your document. For more information, see
[Second person and first person](https://developers.google.com/style/person).
### Z
zippy [](https://developers.google.com/style/word-list#zippy)
:
Don't use to refer to [expander arrows](https://developers.google.com/style/word-list#expander-arrow),
unless you're specifically referring to the [Zippy widget](https://google.github.io/closure-library/api/goog.ui.Zippy.html)
in Closure.