Avoid using slashes, except in code.
Slashes with dates
Don't use date formats that rely on slashes.
For information about how to write dates, see Dates and times.
Slashes with alternatives
Don't use slashes to separate alternatives.
Recommended: 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.
Recommended: 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.
Not 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.
Recommended: Call this method five or six times.
Not recommended: Call this method 5/6 times.
Often, 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.
Recommended: You can view and edit your own data.
Not recommended: You can view and/or edit your own data.
Recommended: You can export raw events, processed events, or both.
Not recommended: You can export raw and/or processed events.
Slashes with file paths and URLs
Use forward slashes, as appropriate, in computer file paths and URLs.
Where 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.
Slashes with fractions
Don't use slashes with fractions because they can be ambiguous.
In the following example, 3/4 could be interpreted either as three-quarters or as stating that 4 is an alternative to 3.
Not recommended: 3/4
Slashes with abbreviations
Don't use abbreviations that rely on slashes. Instead, spell the words out.
Recommended: care of, with
Not recommended: c/o, w/