Source: https://developers.google.com/style/slashes\n\n# Slashes



      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- Avoid using slashes to denote alternatives, instead use "or" or "and" to ensure clarity.\n- Do not use slashes in date formats, abbreviations (such as c/o or w/), or fractions; opt for clearer alternatives like dedicated date formats, spelled-out words, and decimals/percentages respectively.\n- Use forward slashes appropriately in computer file paths and URLs (backslashes for Windows paths), and break long URLs after a forward slash.\n- Generally, replace slashes with "and" or "or" for better readability and to avoid ambiguity, except for code, file paths, and URLs where they have specific functions.\n\nAvoid using slashes to denote alternatives, instead use "or" or "and" to ensure clarity.\n\nDo not use slashes in date formats, abbreviations (such as c/o or w/), or fractions; opt for clearer alternatives like dedicated date formats, spelled-out words, and decimals/percentages respectively.\n\nUse forward slashes appropriately in computer file paths and URLs (backslashes for Windows paths), and break long URLs after a forward slash.\n\nGenerally, replace slashes with "and" or "or" for better readability and to avoid ambiguity, except for code, file paths, and URLs where they have specific functions.\n\nAvoid using slashes, except in code.\n\n\n## Slashes with dates\n\nDon't use date formats that rely on slashes.\n\nFor information about how to write dates, see
  Dates and times.\n\n\n## Slashes with alternatives\n\nDon't use slashes to separate alternatives.\n\nRecommended: For example, a disaster
relief map is not subject to the usage limits even if it has been developed and
is hosted by a commercial entity.\n\nRecommended: For example, a disaster
relief map is not subject to the usage limits even if it has been developed or
is hosted by a commercial entity.\n\nNot recommended: For example, a disaster
relief map is not subject to the usage limits even if it has been
developed/hosted by a commercial entity.\n\nRecommended: Call this method five or six
times.\n\nNot recommended: Call this method 5/6
times.\n\n\n### And/or\n\nOften, and implies or, so you don't need to write both words.
If you need to specify both in your content, avoid writing and/or except
when space is limited, such as in tables.\n\nRecommended: You can view
and edit your own data.\n\nNot recommended: You can
view and/or edit your own data.\n\nRecommended: You can
export raw events, processed events, or both.\n\nNot recommended: You can
export raw and/or processed events.\n\n\n## Slashes with file paths and URLs\n\nUse forward slashes, as appropriate, in computer file paths and URLs.\n\nRecommended:
  https://developers.google.com/cardboard/\n\nWhere very long URLs extend beyond a line, add a line break immediately after
  a slash. Don't ever insert an extraneous hyphen into a URL to break it between two lines.\n\nRecommended:
  https://developers.google.com/
  cardboard/\n\n\n## Slashes with fractions\n\nDon't use slashes with fractions because they can be ambiguous.\n\nIn the following example, 3/4 could be interpreted either as three-quarters
or as stating that 4 is an alternative to 3.\n\nRecommended: ¾\n\nRecommended: 0.75\n\nRecommended: 75%\n\nNot recommended: 3/4\n\n\n## Slashes with abbreviations\n\nDon't use abbreviations that rely on slashes. Instead, spell the words out.\n\nRecommended: care of, with\n\nNot recommended: c/o, w/\n