Source: https://developers.google.com/style/spelling ↗\n\n# Word list

  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- This style guide promotes clear, concise, and inclusive language in technical documentation.\n- It provides specific word choices and formatting guidelines for Google Cloud and other technical content.\n- The guide discourages jargon, ambiguous language, and potentially offensive terms, prioritizing user understanding.\n- It offers preferred alternatives for various technical and general terms to ensure accuracy and consistency.\n- The guidelines aim to enhance clarity, accessibility, and inclusivity for a global audience.\n\nThis style guide promotes clear, concise, and inclusive language in technical documentation.\n\nIt provides specific word choices and formatting guidelines for Google Cloud and other technical content.\n\nThe guide discourages jargon, ambiguous language, and potentially offensive terms, prioritizing user understanding.\n\nIt offers preferred alternatives for various technical and general terms to ensure accuracy and consistency.\n\nThe guidelines aim to enhance clarity, accessibility, and inclusivity for a global audience.\n\nThis word list covers style and usage guidelines that are specific to developer documentation.\n\nIf the term that you're looking for isn't on this list, check our other

editorial resources, including our preferred dictionary, Merriam-Webster. 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, the first form listed for the past tense is canceled, indicating that it’s more common than cancelled.\n\nIf you’re looking for a technical definition, then it’s often a good idea to check the authoritative documentation on the topic.\n\nTerminology 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:\n\n- Jargon\n- Inclusive language\n- Write for a global audience\n- Hyphens\n- Capitalization\n\nAs always, it’s fine to deviate from our guidance if that serves your readers better. For more information, see Break the rules.\n\n\n## Word list\n\nAll word list entries have a link 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.\n\nSome word list entries include guidance to avoid or don’t use a term. Apply this guidance as follows:\n\n- 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 page.\n- 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.\n- Android. Applies only to Android documentation.\n- Google Cloud. Applies only to Google Cloud documentation.\n- Google Workspace. Applies only to Google Workspace documentation.\n\n\n### Numbers and Symbols\n\n\n### A\n\nIn 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.\n\nA 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.\n\n\n### B\n\n- For monitoring, use synthetic monitoring.\n- For testing, use opaque-box testing.\n\n- For the noun blacklist, consider using a replacement such as
      denylist, excludelist, or blocklist.\n- For the noun whitelist, consider using a replacement such as
      allowlist, trustlist, or safelist.\n- For the noun graylist (greylist), consider using a
      replacement such as provisional list.\n\n- To describe a general emergency or procedure that grants emergency
      access, use emergency access.\n- To describe a fallback procedure, use manual fallback or
      preplanned procedure.\n\n\n### C\n\nUse can in the following ways:\n\n- To convey permission or ability (for example, "You can access the
      server").\n- To refer to an optional action (for example, "You can also view
      logs with the Log Viewer").\n- To describe a possible outcome (for example, "The process can
      take 30 minutes").\n\n\n### D\n\nTo 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.\n\nAlways spell out documentation except in cases where space is limited, such as in tabs and URLs. See also page.\n\nAlways spell out documentation except in cases where space is limited, such as in tabs and URLs.\n\nSee also page.\n\n\n### E\n\n- Use the same term in introductory text as described in the procedure.\n- Use the same term throughout the document unless there’s a difference in the UI elements for different procedures.\n\n\n### F\n\n\n### G\n\n\n### H\n\nOnly use this verb phrase in the following cases:\n\n- 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.\n- When the duration of time is important.\n\nThe phrase point to is more common.\n\n\n### I\n\n- CDN Interconnect connection\n- Cloud Interconnect connection\n- Dedicated Interconnect connection\n- Partner Interconnect connection\n\nOK to use connection on subsequent mentions.\n\n\n### J\n\n\n### K\n\n\n### L\n\n\n### M\n\n\nDon’t use master in conjunction with slave in any context. | Cloud SQL primary/replica | Cloud SQL master/slave\nAvoid 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)\n\n- GKE control plane\n- Jenkins controller\n- root key (in security)\n- primary key (in databases)\n\n- GKE master plane\n- Jenkins master\n- master key (in security)\n- master key (in databases)\n\n\n### N\n\nIn Android documentation, use higher instead of later.\n\n\n### O\n\n\n### P\n\nUse page to refer to the following:\n\n- A whole web page, which can include text, images, links, banners, navigational panes, and other features.\n- A sub-page of a console in particular.\n\nSee also documentation or document or documents.\n\n\n### Q\n\n\n### R\n\n\n### S\n\n\n### T\n\n\n### U\n\n\n### V\n\n\n### W\n\n- To decide whether it’s more appropriate to use if or whether, see Grammar Girl’s discussion of if and whether.\n- To decide whether you need to add or not when using whether, see the New York Times’s blog post about whether (or not).\n\n- For monitoring, use introspective monitoring. For testing, use clear-box testing.\n- For testing, use clear-box testing.\n\n\n### Y\n\n\n### Z\n