Source: https://developers.google.com/style/whats-new\n\n# What's new
Stay organized with collections
Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\n\n## Page Summary\n\n- The style guide is actively maintained and updated frequently with new terms, guidance, and best practices.\n- Significant emphasis is placed on clarity, consistency, accessibility, and inclusivity in technical documentation.\n- The "word list" is a core element, regularly updated with preferred and discouraged terms for writers to follow.\n- Updates address a broad range of topics: code formatting, UI elements, grammar, headings, links, images, and more.\n- The style guide aims to improve the overall quality and effectiveness of technical documentation for a global audience.\n\nThe style guide is actively maintained and updated frequently with new terms, guidance, and best practices.\n\nSignificant emphasis is placed on clarity, consistency, accessibility, and inclusivity in technical documentation.\n\nThe "word list" is a core element, regularly updated with preferred and discouraged terms for writers to follow.\n\nUpdates address a broad range of topics: code formatting, UI elements, grammar, headings, links, images, and more.\n\nThe style guide aims to improve the overall quality and effectiveness of technical documentation for a global audience.\n\nThis page provides a summary of significant changes to the style guide.\n\n\n## May 8, 2025\n\n\nNew guidance or change | Page\nRemoved outdated language that indicated that a list of options is treated differently
than other unordered lists. | Lists\nAdded a page about writing prescriptive documentation. | Prescriptive documentation,
Word list\nRemoved guidance that said to include empty parentheses after method names. | Code in text\nChanged footnotes guidance to recommend using numbers instead of symbols. | Footnotes\nSimplified contractions guidance, removing excess explanations and examples. | Contractions\nAdded examples to guidance about introducing sections of a document. | Headings and titles\nAdded an example service account ID. | Example domains and names\nSimplified and clarified guidance about articles, including using articles before
abbreviations and product names. | Abbreviations,
Articles (a, an, the),
Product names,
Word list\nIncluded a general explanation of why we don't document future features.
Document future features | Document future features\nRevised guidance to recommend using an abbreviation in a title or heading only if the
abbreviation is the more commonly known version of the word. | Headings and titles\nAdded a suggestion that when you use an imperative in running text, consider whether to
write a procedure instead. | Second person and first person\nGeneralized existing guidance on what to do when jargon is part of a command or code
sample. | Jargon\nConsolidated guidance about cross-references and linking into one page. | Cross-references and linking\nAdded some specific reasons why we avoid directional language when orienting the
reader to information on a page. | Write accessible documentation\nClarified that spacing around icons is a judgment call based on readability. | UI elements and interaction\nRemoved an example phone number. | Example domains and names\nRemoved the word list entry for property because its usage heavily depends on
the technical context. | Word list\n\nRemoved outdated language that indicated that a list of options is treated differently
than other unordered lists.\n\nAdded a page about writing prescriptive documentation.\n\nRemoved guidance that said to include empty parentheses after method names.\n\nChanged footnotes guidance to recommend using numbers instead of symbols.\n\nSimplified contractions guidance, removing excess explanations and examples.\n\nAdded examples to guidance about introducing sections of a document.\n\nAdded an example service account ID.\n\nSimplified and clarified guidance about articles, including using articles before
abbreviations and product names.\n\nIncluded a general explanation of why we don't document future features.\n\nRevised guidance to recommend using an abbreviation in a title or heading only if the
abbreviation is the more commonly known version of the word.\n\nAdded a suggestion that when you use an imperative in running text, consider whether to
write a procedure instead.\n\nGeneralized existing guidance on what to do when jargon is part of a command or code
sample.\n\nConsolidated guidance about cross-references and linking into one page.\n\nAdded some specific reasons why we avoid directional language when orienting the
reader to information on a page.\n\nClarified that spacing around icons is a judgment call based on readability.\n\nRemoved an example phone number.\n\nRemoved the word list entry for property because its usage heavily depends on
the technical context.\n\n\n## January 17, 2025\n\n\nNew guidance or change | Page\nConsolidated spelling guidance into the introduction to the word list.
Extended guidance about how to use the preferred dictionary to determine which spelling to
use for a word with multiple spellings. | Word list\nGeneralized guidance about when to use spaces or tabs for indentation in code samples. | Code samples\nChanged guidance for formatting telephone numbers to recommend using dashes instead of
parentheses to set the area code off from the rest of the number. | Format phone numbers\nExtended and clarified recommendation to avoid the abbreviations i.e., e.g.,
and etc. in most cases. | Abbreviations,
Comma-separated lists\n\nConsolidated spelling guidance into the introduction to the word list.
Extended guidance about how to use the preferred dictionary to determine which spelling to
use for a word with multiple spellings.\n\n\n## October 29, 2024\n\n\nNew guidance or change | Page\nConsolidated and expanded guidance about hyphens and closed compounds. | Hyphens\nAdded hotspot to the word list. | Word list\n\nConsolidated and expanded guidance about hyphens and closed compounds.\n\n\n## August 15, 2024\n\n\nNew guidance or change | Page\nAdded guidance for distinguishing between binary and decimal units, such as
gibibytes (GiB) and gigabytes (GB). Also corrected abbreviation of kilobyte
to kB. | Decimal and binary units\nExpanded guidance for referring to figures and other images in text. Clarified that
figure numbers are not required. | Figure captions\nAdded word list entries: curl, whitepaper, long-running operation | Word list\nUpdated word list entries: ingest, execute, content type,
media type, MIME | Word list\n\nAdded guidance for distinguishing between binary and decimal units, such as
gibibytes (GiB) and gigabytes (GB). Also corrected abbreviation of kilobyte
to kB.\n\nExpanded guidance for referring to figures and other images in text. Clarified that
figure numbers are not required.\n\n\n## May 16, 2024\n\n\nNew guidance or change | Page\nAdded the term generative AI. | Word list\nAdded the term rehost. Redirected the definition for lift and shift to rehost. | Word list\nClarified that the style guide shows examples of how placeholders render but doesn't
explain how to implement this visual styling. | Format placeholders\nAdded an example to the guidance showing how to use site-root-relative URLs to link to
another page on the same server. | Cross-references\nClarified guidance about how to format anchor text. | Make headings into link targets\n\nAdded the term generative AI.\n\nAdded the term rehost. Redirected the definition for lift and shift to rehost.\n\n\n## March 21, 2024\n\n\nNew guidance or change | Page\nExpanded guidance about avoidance of the term drop-down. | Word list\nAdded examples to guidance about writing documentation that focuses on the present
state of the software. | Timeless documentation\nAdded recommendation to use a more precise term than workload when
possible, or to define what the term means in the specific context.
Added related guidance about avoiding ambiguous or overloaded words like workload,
solution, and support, or defining them in each context. | Word list,
Jargon\nAligned guidance with XML and HTML specifications to recommend against the use of
angle brackets as part of an element name, but instead to only use angle brackets as part
of a tag. | Code in text\n\nExpanded guidance about avoidance of the term drop-down.\n\nAdded examples to guidance about writing documentation that focuses on the present
state of the software.\n\nAdded recommendation to use a more precise term than workload when
possible, or to define what the term means in the specific context.\n\nAdded related guidance about avoiding ambiguous or overloaded words like workload,
solution, and support, or defining them in each context.\n\nAligned guidance with XML and HTML specifications to recommend against the use of
angle brackets as part of an element name, but instead to only use angle brackets as part
of a tag.\n\n\n## January 22, 2024\n\n\nNew guidance or change | Page\nCleaned up word list by removing entries that only provided
hyphenation, spelling, or
abbreviation guidance that followed directly from our
general guidance. | Word list\nConsolidated and clarified guidance regarding alt text, figure captions, and figure
descriptions. | Diagrams, figures, and other images
Write accessible documentation\nAdded recommendation to avoid linking to other document sets from navigation controls
such as a table of contents. | Links to other sites\nClarified guidance about avoiding words such as above and below in
references to documentation and user interfaces for accessibility reasons, and provided
example of appropriate non-directional usage. | Word list\nRemoved prohibition against hyphenation of the phrase open source, so this term
now follows our general guidance for hyphenation, which allows for hyphenation of an
adjectival phrase to add clarity and remove ambiguity. | Word list\nChanged guidance for indicating the omission of code from an instructional code
snippet to recommend the use of an explanatory comment instead of a mere ellipsis. | Code samples\n\nCleaned up word list by removing entries that only provided
hyphenation, spelling, or
abbreviation guidance that followed directly from our
general guidance.\n\nConsolidated and clarified guidance regarding alt text, figure captions, and figure
descriptions.\n\nAdded recommendation to avoid linking to other document sets from navigation controls
such as a table of contents.\n\nClarified guidance about avoiding words such as above and below in
references to documentation and user interfaces for accessibility reasons, and provided
example of appropriate non-directional usage.\n\nRemoved prohibition against hyphenation of the phrase open source, so this term
now follows our general guidance for hyphenation, which allows for hyphenation of an
adjectival phrase to add clarity and remove ambiguity.\n\nChanged guidance for indicating the omission of code from an instructional code
snippet to recommend the use of an explanatory comment instead of a mere ellipsis.\n\n\n## November 8, 2023\n\n\nNew guidance or change | Page\nChanged guidance regarding run-in headings in description lists to recommend
that the punctuation (such as a colon) is not formatted as bold. Making the punctuation
bold caused the punctuation to seem to be part of the heading string, which caused confusion
in cases such as UI labels. | Lists\nRemoved the recommendation to use a special external icon (indicated by
class="external") for links. Readers and writers have expressed confusion
about the meaning and usage of this icon. We strengthened guidance about using other,
explicit means to inform the reader about the destination and behavior of a link. | Link text\n\nChanged guidance regarding run-in headings in description lists to recommend
that the punctuation (such as a colon) is not formatted as bold. Making the punctuation
bold caused the punctuation to seem to be part of the heading string, which caused confusion
in cases such as UI labels.\n\nRemoved the recommendation to use a special external icon (indicated by
class="external") for links. Readers and writers have expressed confusion
about the meaning and usage of this icon. We strengthened guidance about using other,
explicit means to inform the reader about the destination and behavior of a link.\n\n\n## October 24, 2023\n\n\nNew guidance or change | Page\nRemoved page about custom font styling, which only said to use styles
defined in the style sheet for the website. Redirected link to page about
HTML formatting and semantic tagging. | HTML and semantic tagging\nAdded word-list entry for then and expanded entry for if
to recommend the use of the optional helper word then in many cases in
which it might be omitted in casual usage. | Word list\nSimplified and unified guidance for jank and janky to
recommend that these terms only be used for specific graphics issues. | Word list\nStrengthened guidance against the use of and/or except in cases
where space is limited. | Slashes\n\nRemoved page about custom font styling, which only said to use styles
defined in the style sheet for the website. Redirected link to page about
HTML formatting and semantic tagging.\n\nAdded word-list entry for then and expanded entry for if
to recommend the use of the optional helper word then in many cases in
which it might be omitted in casual usage.\n\nSimplified and unified guidance for jank and janky to
recommend that these terms only be used for specific graphics issues.\n\nStrengthened guidance against the use of and/or except in cases
where space is limited.\n\n\n## September 29, 2023\n\n\nNew guidance or change | Page\nAdded several examples of when and how to use quotation marks. | Quotation marks\nAdded explanation of guidance against anthropomorphism. | Anthropomorphism\nAdded guidance about using a hyphen with the prefix non before hyphenated
compounds. | Hyphens\n\nAdded several examples of when and how to use quotation marks.\n\nAdded explanation of guidance against anthropomorphism.\n\nAdded guidance about using a hyphen with the prefix non before hyphenated
compounds.\n\n\n## August 24, 2023\n\n\nNew guidance or change | Page\nAdded link buttons to each entry in the word list to make deep-linking to
individual entries easier. | Word list\nExtended guidance about example names to recommend using an initial to
represent a person's surname. | Example person surnames\nClarified guidance about when to use present tense and when to use future tense. | Present tense\nExtended link text guidance to include an example for mailto links. | Link text\n\nAdded link buttons to each entry in the word list to make deep-linking to
individual entries easier.\n\nExtended guidance about example names to recommend using an initial to
represent a person's surname.\n\nClarified guidance about when to use present tense and when to use future tense.\n\nExtended link text guidance to include an example for mailto links.\n\n\n## July 26, 2023\n\n\nNew guidance or change | Page\nAdded link to
Google API guidelines for information about
code comments. | API reference code comments\nRevised guidance for the word toggle to recommend against use as a verb. | UI elements and interaction\nExtended and clarified guidance for names for directories and files. | Filenames and file types\nAdded explanation for why to use code format for code items. | Code in text\n\nAdded link to
Google API guidelines for information about
code comments.\n\nRevised guidance for the word toggle to recommend against use as a verb.\n\nExtended and clarified guidance for names for directories and files.\n\nAdded explanation for why to use code format for code items.\n\n\n## June 15, 2023\n\n\nNew guidance or change | Page\nConsolidated guidance about periods and end punctuation. Also removed standalone
pages about exclamation points and about spacing after periods. | Periods and other end punctuation\nRevised guidance about hyphens to suggest a lookup strategy, categorize uses,
and note exceptions. | Hyphens\nCreated firmer guidance about punctuation in lists for run-in headings and at
the end of list items. | Lists\nStrengthened capitalization guidance: when not to use capitalization, and
how to use capitalization with product names. | Capitalization,
Product names\nAdded guidance about using end punctuation when documenting a command-line
option or argument. | Document command-line syntax\nImproved description and examples for using first-person pronouns (we,
our). | Second person and first person\nUpdated word list entries: etc., OK, user, we, you | Word list\n\nConsolidated guidance about periods and end punctuation. Also removed standalone
pages about exclamation points and about spacing after periods.\n\nRevised guidance about hyphens to suggest a lookup strategy, categorize uses,
and note exceptions.\n\nCreated firmer guidance about punctuation in lists for run-in headings and at
the end of list items.\n\nStrengthened capitalization guidance: when not to use capitalization, and
how to use capitalization with product names.\n\nAdded guidance about using end punctuation when documenting a command-line
option or argument.\n\nImproved description and examples for using first-person pronouns (we,
our).\n\n\n## May 9, 2023\n\n\nNew guidance or change | Page\nSoftened guidance regarding the choice between the pronouns who and that. | Pronouns\nAdded web interface as an alternative to console and UI in
general references to a browser-based interface. | Word list\nClarified the purpose of the page about phone number formats. | Format phone numbers in text\n\nSoftened guidance regarding the choice between the pronouns who and that.\n\nAdded web interface as an alternative to console and UI in
general references to a browser-based interface.\n\n\n## March 31, 2023\n\n\nNew guidance or change | Page\nExpanded and clarified guidance about using trademarks only as modifiers. This
guidance emphasizes that you should never modify a trademark, such as by creating a
possessive or plural form. | Use trademarks only as modifiers\nStrengthened guidance against shortening product names to anything other than an
approved alternative name. | Google product names\nExpanded guidance about using ARIA labels in text that describes icons in graphical
user interfaces. This improves accessibility and increases consistency in terminology used
to refer to visual elements in text. | Buttons and icons,
Accessibility\nNew word list entry: toolkit | Word list\n\nExpanded and clarified guidance about using trademarks only as modifiers. This
guidance emphasizes that you should never modify a trademark, such as by creating a
possessive or plural form.\n\nStrengthened guidance against shortening product names to anything other than an
approved alternative name.\n\nExpanded guidance about using ARIA labels in text that describes icons in graphical
user interfaces. This improves accessibility and increases consistency in terminology used
to refer to visual elements in text.\n\n\n## February 13, 2023\n\n\nNew guidance or change | Page\nAdded a page about paragraph structure, which provides guidance about recommended
paragraph length and order of information. | Paragraph structure\nExpanded accessibility guidance to say that a document should convey its information
when you use it without images or animation. | Write accessible documentation\nClarified that letter keys should be represented with uppercase letters. | Press and type keyboard keys\nAdded existing to list of examples of potentially problematic words
in timeless documentation. | Timeless documentation\nRecommended using an empty alt attribute for icons that include a text
label. | Buttons and icons\nStrengthened and clarified guidance about avoiding culturally specific references and
about using simple and consistent language. | Voice and tone\nCreated section about items that are sometimes—but not always—formatted in code font,
such as email addresses. | Items that are sometimes in code font\nAdded information about example internationalized domain names. | Example domain names\nExpanded guidance about choosing example email addresses. | Example email addresses\nExpanded guidance about using second-person you to refer to the reader of a
document and, generally, using third-person user to refer to the intended user of
the software that the reader is developing. | Second person\n\nAdded a page about paragraph structure, which provides guidance about recommended
paragraph length and order of information.\n\nExpanded accessibility guidance to say that a document should convey its information
when you use it without images or animation.\n\nClarified that letter keys should be represented with uppercase letters.\n\nAdded existing to list of examples of potentially problematic words
in timeless documentation.\n\nRecommended using an empty alt attribute for icons that include a text
label.\n\nStrengthened and clarified guidance about avoiding culturally specific references and
about using simple and consistent language.\n\nCreated section about items that are sometimes—but not always—formatted in code font,
such as email addresses.\n\nAdded information about example internationalized domain names.\n\nExpanded guidance about choosing example email addresses.\n\nExpanded guidance about using second-person you to refer to the reader of a
document and, generally, using third-person user to refer to the intended user of
the software that the reader is developing.\n\n\n## December 12, 2022\n\n\nNew guidance or change | Page\nNew word list entry: anti-pattern | Word list\n\n\n## November 7, 2022\n\n\nNew guidance or change | Page\nTo emphasize a negative, use
<em>not</em>. | Contractions\n\nTo emphasize a negative, use
<em>not</em>.\n\n\n## October 31, 2022\n\n\nNew guidance or change | Page\nNew word list entry: standalone | Word list\n\n\n## October 10, 2022\n\n\nNew guidance or change | Page\nAdded guidance about how to document optional arguments for commands.
Special characters that indicate optional and mutually exclusive arguments in
commands—such as brackets, braces, and pipes—break commands if the
user doesn't edit them first. The new guidance offers several approaches for
avoiding these problems. | Code in text,
Code samples,
Document command-line syntax\nClarified that contractions are recommended in general, but not required in all
cases. | Contractions\n\nAdded guidance about how to document optional arguments for commands.\n\nSpecial characters that indicate optional and mutually exclusive arguments in
commands—such as brackets, braces, and pipes—break commands if the
user doesn't edit them first. The new guidance offers several approaches for
avoiding these problems.\n\nClarified that contractions are recommended in general, but not required in all
cases.\n\n\n## September 26, 2022\n\n\nNew guidance or change | Page\nIn figure captions, always use end punctuation, and use complete
sentences when possible. | Figures and other images\nAdded separators between word list terms, to improve
readability. | Word list\n\nIn figure captions, always use end punctuation, and use complete
sentences when possible.\n\nAdded separators between word list terms, to improve
readability.\n\n\n## September 19, 2022\n\n\nNew guidance or change | Page\nAdded guidance to multiple pages about ways to make documentation
more inclusive for readers who have a variety of cognitive patterns. | Write accessible documentation,
Cross-references, Numbers, Procedures\n\nAdded guidance to multiple pages about ways to make documentation
more inclusive for readers who have a variety of cognitive patterns.\n\n\n## September 12, 2022\n\n\nNew guidance or change | Page\nDon't present new information in tables through images or symbols
alone. | Tables\nClarified guidance about using footnotes in tables. | Tables\nAdded instructions for how to look up a UI element's
aria-label attribute. | UI elements and interaction\n\nDon't present new information in tables through images or symbols
alone.\n\nClarified guidance about using footnotes in tables.\n\nAdded instructions for how to look up a UI element's
aria-label attribute.\n\n\n## September 5, 2022\n\n\nNew guidance or change | Page\nStrengthened recommendation to avoid using semicolons where possible,
and removed basic information about semicolons.
Our accessibility guidance recommends
against using semicolons where possible, because screen readers may not clearly
indicate them. So we changed our semicolon guidance to be more in line with our
accessibility guidance. | Semicolons\nExpanded and clarified guidance about what to put in code
font. | Code in text\n\nStrengthened recommendation to avoid using semicolons where possible,
and removed basic information about semicolons.\n\nOur accessibility guidance recommends
against using semicolons where possible, because screen readers may not clearly
indicate them. So we changed our semicolon guidance to be more in line with our
accessibility guidance.\n\nExpanded and clarified guidance about what to put in code
font.\n\n\n## August 29, 2022\n\n\nNew guidance or change | Page\nChanged and clarified recommended phrasing for describing boolean
parameters in reference docs. | API reference code
comments\nExpanded and clarified explanation of why we use straight quotation
marks and apostrophes. | Quotation marks\nAdded suggested alternative terms for cloud-native. | Word list\nNew word list entries: prebuilt, scroll | Word list\n\nChanged and clarified recommended phrasing for describing boolean
parameters in reference docs.\n\nExpanded and clarified explanation of why we use straight quotation
marks and apostrophes.\n\nAdded suggested alternative terms for cloud-native.\n\n\n## August 22, 2022\n\n\nNew guidance or change | Page\nClarified that and then is generally better than just then. | Write for a global audience\nNew word list entries: canary, multi-service, precapture,
pre-existing, presubmit, rebranding, roll out | Word list\n\nClarified that and then is generally better than just then.\n\n\n## August 15, 2022\n\n\nNew guidance or change | Page\nExpanded table-formatting guidance, to improve accessibility. | Tables\nImproved guidance about figure captions, descriptions, and alt text. | Figures and other images\n\nExpanded table-formatting guidance, to improve accessibility.\n\nImproved guidance about figure captions, descriptions, and alt text.\n\n\n## August 8, 2022\n\n\nNew guidance or change | Page\nWrite a SQL rather than an SQL.
Both are in use, but a SQL is significantly more common. | Articles (a, an, the)\nAdded information about our distinction between don't use and
avoid. | Word list\nNew word list entries: nonce, SQL | Word list\n\nWrite a SQL rather than an SQL.\n\nBoth are in use, but a SQL is significantly more common.\n\nAdded information about our distinction between don't use and
avoid.\n\n\n## August 1, 2022\n\n\nNew guidance or change | Page\nExpanded guidance about mobile and related terms. | Word list\nIt's OK to use below in set phrases such as below (the)
average. | Word list\nExpanded our information about serial commas. | Commas\nTo refer to a file with the .tiff extension, use the
phrase TIFF file. | Filenames and file types\nNew word list entries: admin; blue-green; cold,
hot, and warm (in the context of a failover, spare, or standby);
inline; mobile phone; online | Word list\n\nExpanded guidance about mobile and related terms.\n\nIt's OK to use below in set phrases such as below (the)
average.\n\nExpanded our information about serial commas.\n\nTo refer to a file with the .tiff extension, use the
phrase TIFF file.\n\n\n## July 25, 2022\n\n\nNew guidance or change | Page\nUpdated guidance about the term Cloud console. | Word list\nClarified guidance about the term see. | Word list\n\nUpdated guidance about the term Cloud console.\n\nClarified guidance about the term see.\n\n\n## July 18, 2022\n\n\nNew guidance or change | Page\nRevised guidance about using the term element in HTML and XML
contexts. | Word list\nRevised and expanded guidance about how to form possessives. | Possessives\nNew word list entry: tag | Word list\n\nRevised guidance about using the term element in HTML and XML
contexts.\n\nRevised and expanded guidance about how to form possessives.\n\n\n## June 20, 2022\n\n\nNew guidance or change | Page\nNew word list entry: brown bag | Word list\n\n\n## June 13, 2022\n\n\nNew guidance or change | Page\nClarified guidance about placement of only. | Write for a global audience\nNew word list entry: using | Word list\n\nClarified guidance about placement of only.\n\n\n## June 6, 2022\n\n\nNew guidance or change | Page\nClarified guidance about Interconnect connection. | Word list\n\nClarified guidance about Interconnect connection.\n\n\n## May 16, 2022\n\n\nNew guidance or change | Page\nOffset footnote symbols using superscript. | Footnotes\nNew word list entries: could, would | Word list\n\nOffset footnote symbols using superscript.\n\n\n## May 9, 2022\n\n\nNew guidance or change | Page\nStrengthened guidance recommending avoiding humor in
documentation.
Most humor is difficult to translate, and much humor is culturally
specific. | Write for a global audience\nChanged the link to a resource about identity-first language.
The site that we had previously linked to has disappeared. | Write inclusive
documentation\n\nStrengthened guidance recommending avoiding humor in
documentation.\n\nMost humor is difficult to translate, and much humor is culturally
specific.\n\nChanged the link to a resource about identity-first language.\n\nThe site that we had previously linked to has disappeared.\n\n\n## April 25, 2022\n\n\nNew guidance or change | Page\nAdded a new page about jargon. | Jargon\nExpanded guidance about when to use the various notice types. | Notes, cautions, warnings, and other notices\nClarified and expanded guidance about when to remove locales from URLs. | Link to other sites\nNew word list entries: final solution, gsutil | Word list\n\nAdded a new page about jargon.\n\nExpanded guidance about when to use the various notice types.\n\nClarified and expanded guidance about when to remove locales from URLs.\n\n\n## April 18, 2022\n\n\nNew guidance or change | Page\nIntroduce an interactive element (such as a button that expands and collapses) in the
text preceding the element, to improve accessibility. | Write accessible documentation\n\nIntroduce an interactive element (such as a button that expands and collapses) in the
text preceding the element, to improve accessibility.\n\n\n## April 11, 2022\n\n\nNew guidance or change | Page\nChanged guidance about taking screenshots. | Figures and other images\nIn code samples, indicate omitted code using three dots and no spaces
(...) | Code samples\nNew word list entries: + (appended to numbers in text) | Word list\n\nChanged guidance about taking screenshots.\n\nIn code samples, indicate omitted code using three dots and no spaces
(...)\n\n\n## April 4, 2022\n\n\nNew guidance or change | Page\nRemoved guidance about using lettered lists for mutually exclusive options.
The semantic distinction that we were making isn't in wide use, and lettered lists aren't
supported in standard Markdown, so we no longer recommend using lettered lists. | Lists\nClarified recommendation about how to italicize in Markdown. | Text-formatting summary\nChanged guidance about dead-letter queue and hold the pointer
over. | Word list\nNew word list entry: break-glass | Word list\n\nRemoved guidance about using lettered lists for mutually exclusive options.\n\nThe semantic distinction that we were making isn't in wide use, and lettered lists aren't
supported in standard Markdown, so we no longer recommend using lettered lists.\n\nClarified recommendation about how to italicize in Markdown.\n\nChanged guidance about dead-letter queue and hold the pointer
over.\n\n\n## March 28, 2022\n\n\nNew guidance or change | Page\nClarified guidance about using an introductory phrase before the output of a
command. | Document command-line syntax\nNew word list entry: Unicode | Word list\n\nClarified guidance about using an introductory phrase before the output of a
command.\n\n\n## February 21, 2022\n\n\nNew guidance or change | Page\nUse gcloud CLI instead of
gcloud command-line tool. | Word list\nNew word list entry: shift left | Word list\n\nUse gcloud CLI instead of
gcloud command-line tool.\n\n\n## February 7, 2022\n\n\nNew guidance or change | Page\nIn general, don't use a single x or a series of x's as
placeholders; instead, use a more informative placeholder. | Formatting placeholders\nNew word list entry: GBps | Word list\n\nIn general, don't use a single x or a series of x's as
placeholders; instead, use a more informative placeholder.\n\n\n## January 31, 2022\n\n\nNew guidance or change | Page\nAvoid repeating the exact page title as a heading on the page.
Headings and titles | Headings and titles\nExpanded guidance about runtime and run time. | Word list\nAdded .adoc and .md to the list of examples of filename
extensions. | Filenames and file
types\n\nAvoid repeating the exact page title as a heading on the page.\n\nExpanded guidance about runtime and run time.\n\nAdded .adoc and .md to the list of examples of filename
extensions.\n\n\n## January 24, 2022\n\n\nNew guidance or change | Page\nClarified guidance about video formats.
The main reason to avoid using animated GIF is that it's
resource-inefficient. | Figures and other images\nClarified guidance about changing an existing custom anchor for a
heading. | Making headings into link
targets\n\nClarified guidance about video formats.\n\nThe main reason to avoid using animated GIF is that it's
resource-inefficient.\n\nClarified guidance about changing an existing custom anchor for a
heading.\n\n\n## January 18, 2022\n\n\nNew guidance or change | Page\nFor animations and videos, use a compressed format (such as MP4), not
animated GIF. | Figures and other images\nDon't use email as a verb. | Word list\nNew word list entry: healthcare | Word list\n\nFor animations and videos, use a compressed format (such as MP4), not
animated GIF.\n\nDon't use email as a verb.\n\n\n## December 31, 2021\n\n\nNew guidance or change | Page\nAdded headings to make guidance about using simple and unambiguous language easier to
find. | Writing for a global audience\nExpanded guidance about demonstrative pronouns. | Ambiguous pronoun references\nClarified guidance about when to use code format for URLs. | Code in text\nRefreshed guidance about optimizing for search (SEO). | Text for images,
Link text,
Filenames,
Headings\n\nAdded headings to make guidance about using simple and unambiguous language easier to
find.\n\nExpanded guidance about demonstrative pronouns.\n\nClarified guidance about when to use code format for URLs.\n\nRefreshed guidance about optimizing for search (SEO).\n\n\n## November 30, 2021\n\n\nNew guidance or change | Page\nAdded examples and clarified guidance recommending use of optional pronouns and other
helper words. | Optional pronouns,
Writing for a global audience\nAdded guidance for linking to a section of another page. | Links to sections on another page\nNew word list entries: portal, copy and paste, performant | Word list\n\nAdded examples and clarified guidance recommending use of optional pronouns and other
helper words.\n\nAdded guidance for linking to a section of another page.\n\n\n## November 1, 2021\n\n\nNew guidance or change | Page\nAdded guidance about expanding shortened words and symbols. | Abbreviations\nExpanded guidance about the order of information in complex procedures, including the
recommended order for goals, results, and justifications for steps. | Procedures\nAdded guidance about including a description of default behaviors in API reference
documents. | API reference code comments\nReinforced guidance about including words like file after items in code font, such
as filenames. | Filenames\nAdded guidance about using alternatives to directional terms such as above and
below when referring to location in a document. | Writing accessible documentation\nNew word list entries: practitioner, left-nav, right-nav, create new | Word list\n\nAdded guidance about expanding shortened words and symbols.\n\nExpanded guidance about the order of information in complex procedures, including the
recommended order for goals, results, and justifications for steps.\n\nAdded guidance about including a description of default behaviors in API reference
documents.\n\nAdded guidance about using alternatives to directional terms such as above and
below when referring to location in a document.\n\n\n## October 11, 2021\n\n\nNew guidance or change | Page\nSimplified placeholder examples and clarified when to repeat an explanation for a
placeholder. | Formatting placeholders\nAdded guidance on using brackets and dots ([...]) to indicate omitted
output in an example. | Output from commands\n\nSimplified placeholder examples and clarified when to repeat an explanation for a
placeholder.\n\nAdded guidance on using brackets and dots ([...]) to indicate omitted
output in an example.\n\n\n## October 4, 2021\n\n\nNew guidance or change | Page\nAdded page about philosophy and principles of the style guide. | Philosophy of this style guide\nClarified recommendation to include a noun after a code element and to avoid
inflecting code elements. | Code in text\nAdded guidance to not use numbers in headings to indicate a sequence of sections. | Headings and titles\nUpdated examples for verb forms in headings and titles, including special cases
such as Pricing and Billing. | Headings and titles\n\nAdded page about philosophy and principles of the style guide.\n\nClarified recommendation to include a noun after a code element and to avoid
inflecting code elements.\n\nAdded guidance to not use numbers in headings to indicate a sequence of sections.\n\nUpdated examples for verb forms in headings and titles, including special cases
such as Pricing and Billing.\n\n\n## September 13, 2021\n\n\nNew guidance or change | Page\nClarified guidance about specifying the context for a task. | Procedures\nAvoid using run the following command to introduce code.
Instead, focus on what the command does. | Procedures\nExpanded the guidance for CLI. | Word list\nNew word list entries: ransomware | Word list\n\nClarified guidance about specifying the context for a task.\n\nAvoid using run the following command to introduce code.
Instead, focus on what the command does.\n\nExpanded the guidance for CLI.\n\n\n## September 6, 2021\n\n\nNew guidance or change | Page\nAvoid words and phrases that anchor the documentation to a point in
time or assume knowledge of prior or future products and features. | Timeless documentation\nAdded navigation menu to the list of UI terms. | UI elements and interaction\nMarked slice and dice as don't use. | Word list\nNew word list entries: web application firewall,
while | Word list\n\nAvoid words and phrases that anchor the documentation to a point in
time or assume knowledge of prior or future products and features.\n\nAdded navigation menu to the list of UI terms.\n\nMarked slice and dice as don't use.\n\n\n## August 30, 2021\n\n\nNew guidance or change | Page\nIntroduce a list of placeholders with the phrase This output
includes the following values:
The old guidance for what introductory phrase to use wasn't a complete
sentence. | Formatting placeholders\n\nIntroduce a list of placeholders with the phrase This output
includes the following values:\n\nThe old guidance for what introductory phrase to use wasn't a complete
sentence.\n\n\n## August 16, 2021\n\n\nNew guidance or change | Page\nAdded guidance for heading and title phrasing.
Many writers ask what verb forms to use in headings and titles. The new
guidance helps writers make that decision more easily, and it improves
consistency for translators and readers. | Headings and titles\n\nAdded guidance for heading and title phrasing.\n\nMany writers ask what verb forms to use in headings and titles. The new
guidance helps writers make that decision more easily, and it improves
consistency for translators and readers.\n\n\n## August 2, 2021\n\n\nNew guidance or change | Page\nWhen you need an example project name, create a name that's
meaningful or descriptive. | Example domains and names\nNew word list entry: pop-up | Word list\n\nWhen you need an example project name, create a name that's
meaningful or descriptive.\n\n\n## July 26, 2021\n\n\nNew guidance or change | Page\nNew word list entry: intercluster | Word list\n\n\n## July 19, 2021\n\n\nNew guidance or change | Page\nAdded guidance about whether to include an abbreviation if it is used
only once in the document. | Abbreviations\nClarified and added guidance about the terms above, below,
earlier, higher, later, lower, and under | Word list\n\nAdded guidance about whether to include an abbreviation if it is used
only once in the document.\n\n\n## July 12, 2021\n\n\nNew guidance or change | Page\nDon't refer to casing styles by names like camel case or
snake case. | Capitalization\n\nDon't refer to casing styles by names like camel case or
snake case.\n\n\n## July 5, 2021\n\n\nNew guidance or change | Page\nIn the first sentence of each procedural step, include an imperative
verb. | Procedures\n\nIn the first sentence of each procedural step, include an imperative
verb.\n\n\n## June 28, 2021\n\n\nNew guidance or change | Page\nNew word list entries: can, might, must
A writer asked us to clarify our guidance for these terms. | Word list\n\nNew word list entries: can, might, must\n\nA writer asked us to clarify our guidance for these terms.\n\n\n## June 21, 2021\n\n\nNew guidance or change | Page\nUpdated guidance on fictitious person names, and added a list of
specific given names to use in examples.
Many writers have asked for a list of recommended names to
use. | Example domains and names\n\nUpdated guidance on fictitious person names, and added a list of
specific given names to use in examples.\n\nMany writers have asked for a list of recommended names to
use.\n\n\n## June 7, 2021\n\n\nNew guidance or change | Page\nDon't use UI element labels as if they were English verbs or
nouns. | UI elements and
interaction\n\nDon't use UI element labels as if they were English verbs or
nouns.\n\n\n## May 24, 2021\n\n\nNew guidance or change | Page\nClarified phrasing of guidance about avoiding using the same link
text for different target pages. | Link text\nAdded guidance about what to do when link text includes a command or
other code-font element. | Link text\nTry to keep the main subject and verb as close to the beginning of
a sentence as possible. | Writing for a global audience\nUpdated guidance about using a hyphen to indicate a range of
numbers.
For example, we now recommend using an ordinary hyphen rather than a
nonbreaking hyphen, for ease of authoring. | Hyphens\nRemoved the word list entry for AJAX.
The entry was outdated, and Wikipedia covers the term better. | Word list\nNew word list entries: webmaster, white label
Use more specific terms. | Word list\n\nClarified phrasing of guidance about avoiding using the same link
text for different target pages.\n\nAdded guidance about what to do when link text includes a command or
other code-font element.\n\nTry to keep the main subject and verb as close to the beginning of
a sentence as possible.\n\nUpdated guidance about using a hyphen to indicate a range of
numbers.\n\nFor example, we now recommend using an ordinary hyphen rather than a
nonbreaking hyphen, for ease of authoring.\n\nRemoved the word list entry for AJAX.\n\nThe entry was outdated, and Wikipedia covers the term better.\n\nNew word list entries: webmaster, white label\n\nUse more specific terms.\n\n\n## May 3, 2021\n\n\nNew guidance or change | Page\nDon't put a link in a heading.
A link in a heading is easy for a reader to miss. | Headings and
titles\nClarified and reorganized the material about which preposition to use
with each UI element. | UI elements and
interaction\n\nDon't put a link in a heading.\n\nA link in a heading is easy for a reader to miss.\n\nClarified and reorganized the material about which preposition to use
with each UI element.\n\n\n## April 26, 2021\n\n\nNew guidance or change | Page\nClarified guidance about when to create a custom anchor for a
heading. | Making headings into link
targets\n\n\n## April 19, 2021\n\n\nNew guidance or change | Page\nWrite one-step procedures with a bullet. | Procedures\nIn headings, use punctuation sparingly. | Headings and titles\nAdded a link to another resource about active and passive voice. | Active voice\nClarified guidance about the word native. | Word list\nNew entry: sherpa | Word list\n\n\n## April 12, 2021\n\n\nNew guidance or change | Page\nClarified that guidance that applies to text generally also applies to
headings. | Headings and titles\nStrengthened recommendation to use contractions. | Contractions\nNew entry: downscope | Word list\n\n\n## April 5, 2021\n\n\nNew guidance or change | Page\nExpanded guidance about using simple words and phrases. | Writing for a global audience\nNew entry: instance group | Word list\n\n\n## March 29, 2021\n\n\nNew guidance or change | Page\nTo form the plural of an abbreviation, treat the abbreviation like an
English word, and follow standard English pluralizing patterns. | Abbreviations\n\n\n## March 15, 2021\n\n\nNew guidance or change | Page\nNew entries: more than 60 terms to not use or to use with caution, for
inclusive-language reasons (too many to list here) | Word list\n\n\n## March 8, 2021\n\n\nNew guidance or change | Page\nExpanded and clarified guidance about placeholders. | Formatting placeholders\nNew entries: outside the box (and related terms), and more than
40 networking terms (too many to list here) | Word list\n\n\n## March 1, 2021\n\n\nNew guidance or change | Page\nClarified guidance about spelling out an abbreviation. | Abbreviations\nUse documentation set instead of docset. | Word list\n\n\n## February 15, 2021\n\n\nNew guidance or change | Page\nNew entry: lock-in | Word list\n\n\n## February 1, 2021\n\n\nNew guidance or change | Page\nRevised and clarified guidance about using should. | Word list\nIn some contexts, you can use active/standby as a
replacement for master/slave. | Word list\nUpdated guidance about using firewalls. | Word list\nNew entries: black-box, external IP address,
gray-box, IPsec, N/A, war room,
white-box | Word list\n\n\n## January 25, 2021\n\n\nNew guidance or change | Page\nUpdated guidance about link text to remove reliance on external
sources. | Link text\nDon't use abbreviations or product names as verbs. | Abbreviations, Product names\n\n\n## January 11, 2021\n\n\nNew guidance or change | Page\nClarified guidance about indentation in code samples. | Code samples\nAdded links to more coding-style guides. | Code in text\nClarified that you can use please under certain specific
circumstances. | Word list\nClarified guidance about terminate. | Word list\nNew entries: hang, MTU, utilize | Word list\n\n\n## January 4, 2021\n\n\nNew guidance or change | Page\nMerged landing page with "Other editorial resources" to help new readers
learn how to use this guide. | About this guide\nNew entry: deprecate | Word list\n\n\n## December 28, 2020\n\n\nNew guidance or change | Page\nAdded an explanation of what placeholders are. | Formatting placeholders\n\n\n## December 14, 2020\n\n\nNew guidance or change | Page\nDistinguished between the Google Cloud product called Identity and
Access Management (IAM) and the general practice of identity and access
management. | Word list\nClarified that the word terminate has a specific meaning in
telephony. | Word list\n\n\n## December 7, 2020\n\n\nNew guidance or change | Page\nWhen you describe navigating through menus using angle brackets, add an
aria-label
attribute to each angle bracket, for use by screen readers:
<span aria-label="and then">></span>. | UI elements and interaction\nNew entry: metageneration | Word list\n\n\n## November 30, 2020\n\n\nNew guidance or change | Page\nUpdated content-navigation titles for some style guide pages. | Content navigation\nClarified guidance for just. | Word list\nNew entry: time to live | Word list\n\n\n## November 23, 2020\n\n\nNew guidance or change | Page\nChanged guidance about fictitious email addresses. | Example domains and names\nNew entry: holiday, the holidays | Word list\n\n\n## November 16, 2020\n\n\nNew guidance or change | Page\nIn examples, use fictional street addresses. | Example domains and names\nClarified guidance for functionality. | Word list\n\n\n## November 9, 2020\n\n\nNew guidance or change | Page\nFormat folder and directory names in code font. | Code in text\n\n\n## November 2, 2020\n\n\nNew guidance or change | Page\nAvoid double negatives. | Writing accessible documentation\nExpanded guidance about how to write around unavoidable references to
non-inclusive words. | Writing inclusive
documentation\n\n\n## October 19, 2020\n\nWe're changing the format of the updates to this page, to focus on what each
change is rather than where it is.\n\n\nNew guidance or change | Page\nYou can use an asterisk to indicate emphasis in Markdown. Don't use a
double underscore to indicate bold in Markdown. | Text-formatting summary\n\n\n## October 12, 2020\n\n\nNew guidance or change | Page\nUse enable or turn on consistently. | Word list\nAll pages about linking are now grouped together under a new
Linking heading. | Content navigation\nDon't link to the same document multiple times in close succession. | Cross-references\nFor subsections, use the phrase in the following sections. | Headings and
titles\nDon't create your own abbreviations. | Abbreviations\nDon't reveal personally identifiable information. | Example domains and names\nFor exponents, use standard mathematical notation. | Numbers\nExpanded guidance about expressing times of day. | Dates and times\nNew entries: aka, America, -aware,
Black Friday, Cyber Monday, leverage, possible,
postmortem | Word list\n\n\n## October 5, 2020\n\n- In the word list, updated guidance about
the term disable.\n\n\n## September 28, 2020\n\n- On the Capitalization page, expanded
guidance about using consistent capitalization.\n- On the Procedures page, added guidance
about including keyboard shortcuts in procedures.\n\n\n## September 21, 2020\n\n- On the Figures and other images page, added
guidance about using image maps.\n- On the Text-formatting summary
page, added guidance about using a variable to indicate a range of version
numbers, and clarified guidance about using <em>.\n- Added entries to the word list:
distributed denial-of-service (DDoS), UTF.\n\n\n## September 14, 2020\n\n- On the Figures and other images page and the
Tables page, added guidance about introductory
sentences.\n- In the word list, clarified the
distinction between terms to never use and terms to avoid when possible. Also
added icons for both kinds of terms.\n\n\n## September 7, 2020\n\n- On the Writing for a global audience
page, clarified guidance about using simple verbs.\n- Added entries to the word list:
single pane of glass, will.\n\n\n## August 31, 2020\n\n- On the Figures and other images
page, clarified guidance about using SVG.\n\n\n## August 24, 2020\n\n- Added an entry to the word list:
see.\n\n\n## August 10, 2020\n\n- On the UI elements and interaction
page, added guidance about when to use in and when to use on.\n- On the Making headings into link
targets page, added guidance about changing anchors, and reorganized the
page.\n\n\n## August 3, 2020\n\n- On the Dates and times page, added
guidance about avoiding referring to seasons of the year.\n- In the word list, added more suggested
alternatives for master and slave.\n\n\n## July 27, 2020\n\n- Added entries to the word list:
grandfathered, graylist, greylist, multi-regional,
Unix epoch time. Expanded and clarified guidance for the
blacklist, master, and multi-region entries.\n\n\n## July 20, 2020\n\n- Reorganized and updated the Other editorial
resources page, and moved that page to near the top of the left nav.\n- On the Figures and other images page, added
links to Web Content Accessibility Guidelines (WCAG) resources.\n- On the Procedures page, added guidance
about introducing a procedure with an imperative.\n- Added entries to the word list:
bar, baz, canceled, foo, like, such
as.\n- As of this week, we've stopped including small-detail changes in this
page. For example, when we corrected a typo in the style guide in the past, we
used to mention that correction on this page, but we're no longer mentioning
minor changes that have no effect on guidance.\n\n\n## July 13, 2020\n\n- Renamed this summary-of-recent-changes page from "Release notes" to
"What's new," and moved it to near the top of the left nav.\n- In the Pronouns page, slightly updated the
guidance about using gender-neutral they.\n\n\n## June 29, 2020\n\n- On several pages, reorganized guidance about formatting code and
command lines. In particular:
Moved the guidance that was in a page about command-line terminology
to the Documenting command-line syntax page,
and deleted the separate command-line terminology page.
Moved the guidance about placeholders to a new Formatting placeholders page.
Added cross-references among various code-related pages.\n- Moved the guidance that was in a page about command-line terminology
to the Documenting command-line syntax page,
and deleted the separate command-line terminology page.\n- Moved the guidance about placeholders to a new Formatting placeholders page.\n- Added cross-references among various code-related pages.\n- In the word list, corrected a typo.\n\n- Moved the guidance that was in a page about command-line terminology
to the Documenting command-line syntax page,
and deleted the separate command-line terminology page.\n- Moved the guidance about placeholders to a new Formatting placeholders page.\n- Added cross-references among various code-related pages.\n\n\n## June 22, 2020\n\n- In the word list, changed guidance about
using earlier and later for a range of version numbers.\n\n\n## June 15, 2020\n\n- On the Capitalization page and other
pages, made guidance consistent about capitalizing references to document
titles.\n- On the Cross-references page and
other pages, added guidance about not forcing a link to open in a new tab.\n- On the Code in text page, added
guidance about when to put UI elements in code font.\n- Added an entry to the word list: best
effort.\n\n\n## June 8, 2020\n\n- On the Writing inclusive
documentation page, added guidance about avoiding figurative language that
relates to the slaughter of animals.\n\n\n## June 1, 2020\n\n- On the Figures and other images page,
updated guidance about alt text, figure descriptions, and figure captions.\n- Reorganized the HTML and semantic
tagging page, and added guidance about not using the br
element to change visual presentation. Also replaced a broken link to a
third-party site.\n- On the Numbers page, added guidance about
avoiding using Roman numerals.\n- Added entries to the word list:
currently, dash, NoOps.\n\n\n## May 25, 2020\n\n- On the Numbers page, corrected two examples
to match our guidance.\n- On the Abbreviations page, added
guidance about use of the term acronym.\n- Added entries to the word list:
happiness, scale, service level agreement, service level
indicator, service level objective. Also clarified guidance for
app.\n\n\n## May 18, 2020\n\n- On the Filenames and file types page,
added guidance about how to refer to a filename.\n- On the Headings and titles page, updated
the guidance about using code font in headings.\n- On the UI elements and interaction page
and elsewhere, replaced the term arrow notation with angle
bracket.\n- On the Procedures page, clarified the
guidance about stating the location of an action before stating the action.\n- Added entries to the word list:
config, extract, unarchive, uncompress,
untar. Also changed the guidance about ssh and related terms.
Also corrected a typo.\n\n\n## May 11, 2020\n\n- Major change: On the Code in text
page, changed guidance for placeholder styling. The new preferred style is
all-uppercase with underscore delimiters.\n- Also on the Code in text page,
corrected guidance about how to mark up placeholders with Markdown.\n- On the Figures and other images page,
corrected a typo.\n\n\n## May 4, 2020\n\n- On the Second person and first person page,
clarified guidance about when to use implicit you.\n- On the UI elements and interaction
page, added guidance about toggle.\n- Added entries to the word list:
dashboard, master. Unrelatedly, fixed a longstanding word list
typo.\n\n\n## April 27, 2020\n\n- On the Documenting command-line syntax
page, added guidance about showing the output of commands.\n- On the Example domains and names page,
added example IPv6 addresses.\n- On the Words as words page,
clarified guidance.\n- In the word list, clarified guidance for
the word following. Also clarified guidance for the various
console terms.\n- Added an entry to the word list:
native.\n\n\n## April 20, 2020\n\n- On the Units of measurement page,
added guidance about using per when referring to rates.\n- On the UI elements and interaction
page, clarified the distinction between text input and keyboard shortcuts, and
added guidance about when to use the code and
kbd elements. On the Code in
text page, added text input to the list of things to put in code font.\n- On the Accessible content page, added
a recommendation to use a screen reader to test your documentation. Also added
guidance about introducing tables.\n- On the Example domains and names page,
changed the recommended example company names to avoid camel case.\n- On the Code in text page and the Colons page, clarified and expanded guidance about how
to format a colon after text that's bold or in code font.\n- Added entries to the word list:
key, key ring, per, vice versa.\n\n\n## April 13, 2020\n\n- On the Lists page, expanded the guidance
about when not to use sentence-ending punctuation.\n- Added cross-references between the Abbreviations page and the Headings and titles page.\n- On the Numbers page, clarified the
guidance about hyphens and en dashes in ranges of numbers.\n- On the Units of measure page,
clarified guidance about what counts as a unit.\n- In the word list, clarified guidance
about using blacklist and whitelist.\n- Added entries to the word list:
ad tech, easily, fintech, NLU, quick,
quickly.\n\n\n## April 6, 2020\n\n- On the Abbreviations page, clarified
guidance about using abbreviations in headings and titles.\n- On the Text-formatting summary
page, added guidance on formatting mathematical variables.\n- On the Link text page, added guidance
about abbreviations in link text.\n- On the Dates and times page, added
guidance about how to express time zones.\n- In the word list, clarified guidance
about key-value pair.\n- Added an entry to the word list:
personally identifiable information (PII).\n\n\n## March 30, 2020\n\n- On the Hyphens page, clarified guidance
about ranges of numbers.\n- In the UI elements and interaction
page, changed guidance for formatting input for text boxes to recommend using
the HTML code element instead of the
kbd element.\n\n\n## March 23, 2020\n\n- On the Capitalization page, made the
following changes:
Removed outdated guidance about capitalization after a run-in heading.
For the current guidance, see "Description lists that use run-in headings" on
the Lists page.
Clarified guidance about avoiding all-uppercase and camel case.
Clarified guidance about avoiding lowercase at the start of a
sentence.
Clarified guidance about capitalization when referring to documents by
title in various contexts.\n- Removed outdated guidance about capitalization after a run-in heading.
For the current guidance, see "Description lists that use run-in headings" on
the Lists page.\n- Clarified guidance about avoiding all-uppercase and camel case.\n- Clarified guidance about avoiding lowercase at the start of a
sentence.\n- Clarified guidance about capitalization when referring to documents by
title in various contexts.\n- Expanded and reorganized the Code in
text page. In particular:
Expanded the guidance about documenting placeholders.
Expanded the list of items to put in code font.\n- Expanded the guidance about documenting placeholders.\n- Expanded the list of items to put in code font.\n- On the Commas page, added guidance about
using a comma with because.\n- On the Dashes page, added guidance about not
using en dashes.\n- Added entries to the word list:
datastore, tutorial. Also added guidance (in the entry for
documentation) about phrases like in this document.\n\n- Removed outdated guidance about capitalization after a run-in heading.
For the current guidance, see "Description lists that use run-in headings" on
the Lists page.\n- Clarified guidance about avoiding all-uppercase and camel case.\n- Clarified guidance about avoiding lowercase at the start of a
sentence.\n- Clarified guidance about capitalization when referring to documents by
title in various contexts.\n\n- Expanded the guidance about documenting placeholders.\n- Expanded the list of items to put in code font.\n\n\n## March 2, 2020\n\n- On the Capitalization page, added
guidance about using sentence case for labels and callouts.\n- On the Cross-references page,
added guidance about how to format the titles of web series.\n- Added an entry to the word list: web
server.\n\n\n## February 24, 2020\n\n- On the Resources page, added links to the
Kubernetes glossary and the Kubernetes style guide.\n- On the Lists page, added guidance about how
and when to use a bulleted list with run-in headings.\n- Updated the word list to refer to
Google Cloud instead of GCP, in accord with a recent name change.
In particular, changed entries for GCP, GCP Console, and GCP
project ID to Google Cloud, Google Cloud Console, and
Google Cloud project ID, respectively.\n- Added an entry to the word list: GKE
node. Also updated guidance for GKE.\n- In the left nav, moved the word list and the product-names page to near
the top.\n- On the Plurals in parentheses
page, added guidance about using the phrase one or more.\n\n\n## January 13, 2020\n\n- In the Writing for a global audience
page, fixed a broken link.\n- In the Code in text page, added
environment variable names to the list of items to put in code font.\n- Added entries to the word list:
A/B testing, BGP.\n\n\n## January 6, 2020\n\n- Added entries to the word list:
DevOps, ECMP, GFE, NoSQL, PostgreSQL. Also
updated guidance on virtual machine (VM) instance.\n\n\n## December 23, 2019\n\n- Expanded and clarified the Writing for a
global audience page.\n- Renamed the "Typographical conventions" page to "Text-formatting summary."\n- On the Tables page, clarified guidance
about punctuation in table column heads.\n- On the Filenames and file types page,
added .jar to the list of filename extensions.\n- On the UI elements page and the word
list, clarified guidance about when to use box and field to refer
to text boxes.\n\n\n## December 16, 2019\n\n- On the Abbreviations page, expanded
guidance about when to spell out abbreviations.\n- On the conventions page,
fixed two broken links.\n- Added entries to the word list:
as, big-endian, google.dev, little-endian.\n\n\n## December 9, 2019\n\n- On the Tables page, added guidance about
sorting tables, and clarified guidance about when to use tables.\n- Reverted last week's changes about using earlier and
later instead of lower and higher; those changes need
further refining.\n\n\n## December 2, 2019\n\n- On the Cross-references
page, added guidance about using the word about in cross-references,
rather than on.\n- Added entries to the word list: about
versus on, for instance, SLA. Also changed guidance about
using earlier and later for a range of version numbers.\n\n\n## November 25, 2019\n\n- On the UI elements and interaction
page, added guidance about focusing on the task rather than on UI elements as
such.\n- On various pages, added cross-references linking to other pages.\n\n\n## November 18, 2019\n\n- Added a new Typographic
conventions page.\n- Reorganized the Units of
measurement page. Also added guidance about Kelvin temperatures.\n- On the Cross-references page,
clarified guidance about cross-references that aren't links.\n- On the UI elements and interaction
page, added information about expander arrows.\n- Added a term to the word list:
slice and dice.\n\n\n## November 11, 2019\n\n- On the Figures and other images page,
clarified guidance about figure descriptions.\n- On the Units of measurement page,
added guidance about ranges of numbers.\n- On the Product names page, clarified
guidance about using full trademarked product names.\n- Added terms to the word list:
billing charges, port, repo, UI.\n\n\n## October 28, 2019\n\n- Added guidance about what to do if there's more than one way to complete a
task.\n- Added terms to the word list:
just, multi-tenancy.\n\n\n## October 21, 2019\n\n- Added a page about formatting
words as words.\n- Added a page about formatting key
terms.\n- Changed the guidance about how to capitalize a UI element name when the label is
all-uppercase in the UI.\n- Added guidance about explaining
placeholders.\n- Updated the list of items to put in
code font.\n- Clarified the guidance about using official capitalization for names of products.\n- Changed the title of the style guide landing
page.\n- Deleted the page about URLs in links, and moved the material that was on
that page to the cross-references
page. Also added some examples to that page.\n- Removed unnecessary explanations of the icons that indicate that a
guideline applies only in Android documentation or only in Google Cloud Platform
documentation.\n- Added examples to the footnotes
page.\n- Improved a link on the Accessible
content page.\n- Added terms to the word list:
BMaaS, US.\n\n\n## October 8, 2019\n\n- Reorganized the page about notices, and
added examples.\n- Cleaned up some minor formatting and phrasing issues in the word list.\n- Corrected a typo on the Accessible
content page.\n- Changed the title of the style guide to use sentence case.\n\n\n## September 30, 2019\n\n- Added a term to the word list:
PoP.\n\n\n## September 23, 2019\n\n- Added a page about footnotes.\n- Reorganized the Other editorial resources
page.\n\n\n## September 16, 2019\n\n- Added a page about using material from
other sources.\n- Added guidance about using
a and an with product names.\n- Removed contradictory guidance about quotation marks with link text.\n- Clarified guidance about periods
with abbreviations.\n- Clarified guidance about capitalization
following a colon.\n- Moved the list of UI-related verbs from the UI elements page to the word list.\n- Also added other terms to the word list:
cons, Gbps, Kbps, Mbps, pros. Also updated
the entry for service.\n\n\n## June 24, 2019\n\n- Added guidance about US currency to the Numbers page.\n\n\n## June 17, 2019\n\n- Added further guidance about accessibility to the Accessible content page and other related
pages.\n- Added guidance about graphically violent terms to the Writing inclusive documentation
page.\n- Added guidance about the term wheelchair-bound to the Writing inclusive documentation
page.\n- Added guidance about currency to the Units of measure page.\n- Added an example showing how to use
Markdown to mark up images.\n- Added terms to the word list:
disclosure triangle, hamburger menu, kebab menu,
outpost, STONITH. Also expanded guidance about should.\n\n\n## May 20, 2019\n\n- Added a new page about avoiding excessive claims.\n- Added material about file types to the Filenames and file types page.\n- Added terms to the word list: CSV,
traditional, YAML.\n\n\n## April 29, 2019\n\n- Replaced the guidelines on the Accessible content page with a new set of more
relevant guidelines.\n- Added a term to the word list:
execute.\n- Added material about Linux signals on the Command-line terminology page, and
updated related entries in the word list.\n\n\n## April 22, 2019\n\n- Added a term to the word list:
method. Also added to the guidance for Cloud.\n\n\n## April 15, 2019\n\n- Added more guidance about digit-group separators on the Numbers page.\n- Fixed a broken link on the Numbers
page, and another on the Writing for a global
audience page.\n- Updated guidance about example names on the Example domains and names page.\n- Added guidance about removing personally identifying information from
screenshots on the Figures and other images
page.\n- Added guidance about using code font for names of command-line utilities
on the Code in text page.\n- Added guidance about short and long versions of words like app and
demo on the Abbreviations page.\n\n\n## March 4, 2019\n\n- Clarified guidance about person-first and identity-first language on the
Writing inclusive documentation
page.\n- Added guidance about passive voice on the Active voice page.\n- Added more guidance about links on the Linking to other sites page.\n- Added terms to the word list:
guru, spin up. Also revised the guidance for Container
Engine.\n\n\n## February 25, 2019\n\n- Added extensive new material to the inclusive documentation page.\n- Updated the word list:
Clarified guidance for argument and flag.
Added terms: allows you to, desire, drop-down,
wish.
Removed the recommendations against using enable and
disable, and clarified guidance for those terms.\n- Clarified guidance for argument and flag.\n- Added terms: allows you to, desire, drop-down,
wish.\n- Removed the recommendations against using enable and
disable, and clarified guidance for those terms.\n\n- Clarified guidance for argument and flag.\n- Added terms: allows you to, desire, drop-down,
wish.\n- Removed the recommendations against using enable and
disable, and clarified guidance for those terms.\n\n\n## February 4, 2019\n\n- Added terms to the word list:
add-in, add-on.\n- Added guidelines about avoiding repetitive procedures.\n\n\n## January 28, 2019\n\n- Updated the word list:
Changed guidance for above and below.
Added terms: gcloud, ML.
Updated guidance for &.
Improved alphabetization.\n- Changed guidance for above and below.\n- Added terms: gcloud, ML.\n- Updated guidance for &.\n- Improved alphabetization.\n- Fixed a broken link in the Lists page.\n\n- Changed guidance for above and below.\n- Added terms: gcloud, ML.\n- Updated guidance for &.\n- Improved alphabetization.\n\n\n## January 14, 2019\n\n- Added terms to the word list:
comprise, console, fail over, GCP Console, Google
Cloud Platform Console, populate, surface.\n- Reorganized the UI elements page,
and added guidance and examples.\n- Added Markdown information to the URLs for
images page.\n- Clarified guidance about end punctuation for lists on the Periods page.\n- Clarified guidance about nonbreaking spaces in the Units of measurement page.\n\n\n## December 3, 2018\n\n- Added a term to the word list:
lifetime.\n- Elaborated on our guidance in the Closed compounds and prefixes section of
the word list.\n- Added a new page about command-line terminology for gcloud
and Linux.\n- Added a section on straight and
curly quotation marks to the Quotation marks page.\n- Added guidance about avoiding overuse of bolding to the Procedures page.\n- Added guidance about the phrases hold the pointer over and
point to to the UI elements and
interaction page.\n\n\n## October 29, 2018\n\n- Added terms to the word list:
blacklist, whitelist.\n- Reorganized the dates and times page,
and added guidance about times and about ISO 8601.\n\n\n## October 8, 2018\n\n- Added recommendations for example company names.\n- Added guidance about using monospace formatting to the UI elements and interaction page.\n- Added guidance about giving the location of an action in a procedure
to the Procedures page.\n\n\n## September 18, 2018\n\n- Added terms to the word list: GKE,
POJO.\n\n\n## September 4, 2018\n\n- Added guidance about cases where filenames aren't under your
control.\n- Added a term to the word list:
big data.\n\n\n## August 13, 2018\n\n- Added guidance about avoiding internet slang.\n- Added terms to the word list:
multi-cloud, RTFM, tl;dr, ymmv.\n\n\n## July 30, 2018\n\n- Added terms to the word list:
disaster recovery, file system, high availability,
high performance computing, OS, tarball, tar
file.\n- Updated guidance in the word list for on-premises.\n- Rephrased a paragraph of the landing page.\n\n\n## June 25, 2018\n\n- Added terms to the word list:
IP, SAP.\n\n\n## June 19, 2018\n\n- Added a term to the word list:
trojan.\n- Improved the organization, formatting, and phrasing of the filenames page.\n\n\n## June 12, 2018\n\n- Added terms to the word list:
appendix, index, matrix.\n\n\n## May 21, 2018\n\n- Changed the guidance about how to link to Android
reference documentation.\n- Added information about using the with
product names.\n- Added a note about indefinite and casual numbers to the Numbers page.\n- Fixed a broken link on the authorial tone
page.\n\n\n## May 14, 2018\n\n- Added terms to the word list:
multi-cluster, via. Clarified guidance on firewalls.\n\n\n## April 2, 2018\n\n- Added a page about writing inclusive documentation.\n- Added terms to the word list:
at scale, IAM, RFC.\n\n\n## March 26, 2018\n\n- Added information about alt text for
decorative images to the images page.\n- Added terms to the word list:
fill in, fill out, microservices.\n\n\n## February 26, 2018\n\n- Added a term to the word list:
ad hoc.\n\n\n## February 12, 2018\n\n- Added terms to the word list:
Cloud, Container Engine, ephemeral external IP address,
firewalls, GCP, GCP project ID, internal IP
address, NAT, network IP address, non-key,
on-premises, persistent disk, project, RDP,
static external IP address, subnet, table name,
textbox, turn on.\n- Added information about closed compounds and prefixes to the word list.\n\n\n## January 29, 2018\n\n- Added terms to the word list:
alpha, autohealing, autoscaling, autotagging,
bare metal, beta, CLI, Cloud SDK, colocate,
CPU, curated roles, data center campus, data
cleaning, data source, ETL, IaaS, impact,
ingest, k8s, key pair, PaaS, preemptible,
regex, SaaS, screenshot, sign-in, sign into,
sign-out, sub-command, v, virtual machine
instance.\n- Added a section on placeholder variables to the code in text page.\n\n\n## January 8, 2018\n\n- Added terms to the word list:
argument, backup, dataflow, flag, higher,
later, long press, multi-region, option,
slave, touch & hold, transpile, wildcard.\n- Added an item (DNS record types) to the list of items to put
in code font.\n\n\n## December 11, 2017\n\n- Added material on numerical
dimensions.\n- Added material about possessives of
company and product names.\n- Added terms to the word list:
docset, documentation, startup, sync.\n\n\n## November 13, 2017\n\n- Changed guidelines on end punctuation for
list items.\n- Added alphabetical headings to the word
list, so you can now jump to a specific letter using the in-page TOC.\n- Updated word list entries for
error-prone, real time, and Search.\n- Added terms to the word list:
dataset, legacy, nonfatal.\n\n\n## October 23, 2017\n\n- Added a new page about plurals in
parentheses.\n- Added a link to the C++ coding style guide, in the Code style guides section.\n\n\n## September 4, 2017\n\n- Added several more terms to the word list:
check, checkbox, clear, deselect, open
source, select, target, uncheck, Unix-like,
unselect.\n- Added material to the Trademarks page
about using trademarks as adjectives. Also added links to a couple of other
trademark-related pages from Google.\n- Removed Android-specific material from the Headings page, to bring Android doc guidelines more
into line with non-Android guidelines. Also, added notes about things not to
include in headings.\n- Removed Android label from material on the Tables page, to make that material also apply to
non-Android docs.\n- Added mention of degrees and percents to the Units of measurement page.\n\n\n## August 28, 2017\n\n- Added 160+ terms to the word list. (Too
many to list here.)\n- Added recommendations for image size and placement to the Images page.\n- Moved material about Javadoc links to the Code in text page.\n\n\n## August 21, 2017\n\n- Added new File names page.\n- Added new Units of measurement
page.\n- Changed "internet" to
lowercase.\n- Added material about line lengths and Javadoc-style links to the HTML formatting page.\n\n\n## July 31, 2017\n\n- Added new Headings and titles page, mostly
focused on Android documentation.\n- Added information about tables in Android docs to
the Tables page.\n\n\n## July 10, 2017\n\n- Added words to the word list: deep
linking, jank, wake lock.\n\n\n## June 8, 2017\n\n- Public release.\n