1# Topic Page Style Guide
3From the GitHub Style Guide:
5> Words are an important part of how software works. Just as we have a style guide for our code, we have a style guide for our tone and our voice. Even though there may be dozens of people creating a product, it should still sound like we speak in one consistent voice.
7>**The way we write is just as important as the way we build. Consider these things when writing copy.**
11* **Make it approachable.** Use familiar language and don't assume the reader has prior topic knowledge.
12* **Keep it concise.** Use the simplest possible language and link to outside content for deeper dives.
13* **Think about the community.** Add content that will benefit many vs. an individual.
15## Grammar and usage
18Use "and" rather than an ampersand unless you’re referencing a brand name, for example: Procter & Gamble.
21Always use the [Oxford comma](https://en.wikipedia.org/wiki/Serial_comma).
24Include and spell out the month. Include the day number without the "th" or "nd" at the end, for example: October 12.
26### Exclamation points
27Avoid exclamation points in topic pages and collections.
30Always use correct capitalization when referring to “GitHub” or “Git.” Never use “GitHub” or “Git” as a verb.
33Write out “one” and every number less than 10.
36Avoid using "users" in favor of developers, people, or a more specific description of the group of people.
38### Words that can be tricky
39- **Agile (e.g. agile development):** Don’t capitalize “agile” unless it’s starting a sentence.
40- **Email:** Use “email”, not "e-mail."
41- **Internet:** Don’t capitalize “internet” unless it’s starting a sentence.
42- **Open source:**
43 - Adjective: “Open source” is always lowercase, except when at the start of the sentence. You can use it as an adjective without a hyphen, as in “open source project” or “open source software.”
44 - Noun: You can also use the term on its own to refer to open source in general, as in “give back to open source."
45 - Verb: It’s acceptable to use open source as a verb when referring to a project that has been “open sourced” or that you intend to “open source.”
46- **Pull request:** Never abbreviate "pull request." "Pull request" is always lowercase unless it's starting a sentence.
47- **Repository:** Never abbreviate "repository." "Repository" is always lowercase unless it's starting a sentence.