Source: https://developers.google.com/style/pluralization\n\n# Pluralization



      Stay organized with collections



      Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\nIn general, follow the standard rules for pluralization in US English and use the regular
  plural form of a word in most cases. Avoid using 's to form a plural to avoid confusing
  a plural with a possessive or contraction.\n\nFor more information, see Contractions and Possessives.\n\n\n## Singular and plural\n\nFor sentences with long or complex subjects, make sure to use either a plural or singular
  appropriately.\n\nRecommended: Confirm that the number of
    entries listed in the directory is accurate.\n\nRecommended: The workloads with the
    app: backend label represent the traffic source.\n\nNot recommended: The efficiency of
    algorithms that process data sets depend on memory allocation.\n\nFor sentences with more than one subject being connected by and or or, make sure
  to use either a plural and singular appropriately.\n\nRecommended: The request payload and
    header information are logged for debugging.\n\nRecommended: Either the API keys or
    service account wasn't authenticated.\n\nNot recommended: User authentication and
    authorization is processed and handled by the security module.\n\nFor consistent style, use a plural after one or more, not a singular.\n\nBecause one or more can express the possibility of one or more outcomes, it's sometimes
  helpful to reword the sentence for clarity.\n\nRecommended: If one or more tests fail, a
    system warning is triggered.\n\nRecommended: If any one test fails, a
    system warning is triggered.\n\nSee also Plurals in parentheses.\n\nUse a singular after more than one, not a plural.\n\nRecommended: You can create more than one
    instance at a time.\n\n\n## Plural abbreviations\n\nIn general, treat acronyms, initialisms, and other abbreviations as regular words when making
  them plural. Avoid using 's to form the plural to help distinguish the plural form from the
  possessive. For more information, see Possessives.\n\nRecommended: APIs, SKEs, and IDEs\n\nNot recommended: API's, SKE's, and
    IDE's\n\nIf the acronym, initialism, or abbreviation ends in s, sh, ch, or
  x, then add es—for example, OSes, DISHes, DCCHes, and
  BMXes.\n\nWhen spelling out a term, make sure that both the spelled-out term and abbreviation match,
  with both either being a plural or singular.\n\nRecommended: virtual machines (VMs)\n\nNot recommended: virtual machines (VM)\n\nWhen using numbers with units of measure, use the singular when spelling out the unit if the
  number is one. Otherwise, use the plural form for all other numbers, including zero,
  decimal numbers, and numbers greater than one.\n\nRecommended: 0 degrees\n\nRecommended: 0.5 degrees\n\nRecommended: 1 degree\n\nRecommended: 15 degrees\n\nDon't make an abbreviation plural when used as a unit with a number.\n\nRecommended: 64 GB\n\nNot recommended: 64 GBs\n\nMake sure to include a space, preferably a nonbreaking space, between the number and
  abbreviation. For more information, see Spaces in units of
  measurement.\n\nFor more information, see Abbreviations.\n\n\n## Plural product and feature names\n\nIn general, don't form a plural or possessive for the trademark of a product, feature, or
  company name. For more information, see Use trademarks only as modifiers and
  Product, feature, and company
  names.\n\nIn general, use singular class names. Don't manually make a singular class name plural. Doing
  so might cause issues in translation. Instead, add a plural noun after the class name.\n\nRecommended: Intent objects
    and Activity instances\n\nNot recommended: Intents and
    Activitys\n\nNot recommended: Intents and
    Activities\n\nFor more information, see API reference code
  comments.\n\n\n## Plurals in parentheses\n\nDon't put optional plurals in parentheses. Instead, use either a plural or singular
  construction and keep things consistent throughout your documentation. Choose what is most
  appropriate for your documentation and your audience. If it's important in a specific context to
  indicate both, use one or more.\n\n\nRecommended | Not recommended\nTo find your API key, visit the Credentials page. | To find your API key(s), visit the Credentials page.\nThe value of the parent depends on the values of its children. | The value of the parent depends on the value(s) of its child(ren).\nYou can use a physical linecard, which can contain one or more ports. | You can use a physical linecard, which can contain port(s).\n\n\n## Plural pronouns\n\nFor information about plural pronouns like we, you, and they, see Pronouns and Second person and first
  person.\n