Source: https://developers.google.com/style/product-names ↗\n\n# Product names

  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- Capitalize Google product names in title case, except when matching UI labels or if the official name starts with a lowercase letter.\n- Feature names are generally lowercase, unless officially capitalized or matching a UI label; follow existing documentation for precedents.\n- Use the full trademarked product name, avoiding abbreviations unless matching a UI label and ensuring clarity in its reference.\n- Use "the" before tool and API names, but not before product names unless qualifying something else; use "service" to refer to multiple products to avoid ambiguity.\n- Avoid using product or feature names as verbs, maintaining clear and grammatically correct language.\n\nCapitalize Google product names in title case, except when matching UI labels or if the official name starts with a lowercase letter.\n\nFeature names are generally lowercase, unless officially capitalized or matching a UI label; follow existing documentation for precedents.\n\nUse the full trademarked product name, avoiding abbreviations unless matching a UI label and ensuring clarity in its reference.\n\nUse "the" before tool and API names, but not before product names unless qualifying something else; use "service" to refer to multiple products to avoid ambiguity.\n\nAvoid using product or feature names as verbs, maintaining clear and grammatically correct language.\n\nThis page describes how to use product names.\n\n\n## Capitalize product names\n\nIn general, Google product names are in title case, sometimes called
init-capped, which means that every word is capitalized except for
prepositions like of or on and articles like a or
the. When you refer to a Google product, use title case except
when you're matching a UI label. For information about how to refer to UI
labels, see
UI elements and interaction.\n\nWhen you write about any product, follow the official capitalization for the
names of brands, companies, software, products, services, features, and
terms defined by companies and open source communities.\n\n- For example, if you're using Kubernetes-related terms, then follow
      the capitalization that's shown in the Kubernetes Concepts
      documentation.

Recommended in a Kubernetes context: A Job creates one or more Pods.

Recommended: The Cloud Scheduler job publishes a message to a Pub/Sub topic at one-minute intervals.\n- If an official name begins with a lowercase letter, then put it in lowercase even at the start of a sentence. But it’s better to revise the sentence to avoid putting a lowercase word at the start, if possible.

Recommended: You can use macOS to run the app.

Not recommended: macOS can run the app.\n\nFor example, if you’re using Kubernetes-related terms, then follow the capitalization that’s shown in the Kubernetes Concepts documentation.\n\nRecommended in a Kubernetes context: A Job creates one or more Pods.\n\nRecommended: The Cloud Scheduler job publishes a message to a Pub/Sub topic at one-minute intervals.\n\nIf an official name begins with a lowercase letter, then put it in lowercase even at the start of a sentence. But it’s better to revise the sentence to avoid putting a lowercase word at the start, if possible.\n\nRecommended: You can use macOS to run the app.\n\nNot recommended: macOS can run the app.\n\n\n### Feature names\n\nA feature is a distinctive attribute or capability of a product. Features are usually described in terms of what they can do as part of a product. In general, feature names are lowercase, although there are exceptions.\n\nWhen you write about a feature, don’t capitalize it unless the name is officially capitalized. If you’re unsure, follow the precedent that’s set by other documents that describe the feature. As with products, match the capitalization of a UI label if you’re referring to one.\n\nFor more general information about capitalization, see Capitalization.\n\n\n## Shorten Google product names\n\nWhen referring to a Google product, sometimes you might want to abbreviate the product name. For example, when you’re referring to Google Spreadsheets, it can be awkward to refer to it as Google Spreadsheets every time; sometimes you might want to call it Spreadsheets.\n\nUse the full trademarked product name. Don’t abbreviate product names, except in cases where you’re matching a UI label. In such cases, make it clear that you’re referring to the Google product and not some other thing with a similar name.\n\nAlso consider whether you need to refer to a product name throughout a document, or if you can use a more general term. For example, if you’ve established that you’re talking about Anthos Service Mesh, you can probably frame your discussion around the concept of a service mesh throughout much of the document.\n\n\n## Possessives of product names\n\nFor information about forming possessives with product names, see Product, feature, and company names.\n\n\n## Articles before product names\n\nDon’t use the before a product name unless you’re using the name to modify something else. Do use the before tool and API names.\n\nRecommended: Using Cloud Datastore with Cloud Dataproc\n\nRecommended: The Cloud Datastore options page\n\nRecommended: The Google Cloud console\n\nRecommended: The Transcoder API\n\nRecommended: The gcloud CLI\n\nNot recommended: Using the Cloud Datastore with Cloud Dataproc\n\nIf you use a product name as a modifier with an indefinite article (a or an), pay close attention to which article precedes the product name.\n\nRecommended: An Anthos Service Mesh environment\n\nRecommended: A Service Mesh environment\n\nFor more information about using articles, see Articles.\n\n\n## Use “service” to refer to multiple products\n\nIt’s OK to refer to Google products as services, such as the Google Kubernetes Engine service or the Compute Engine service. However, if the term services leads to ambiguity, use the product names.\n\n\n## Don’t use product names as verbs\n\nDon’t use product names or feature names as verbs.\n