This Guide is for anyone who writes, edits, or otherwise contributes to a Holloway Guide. It is intended to ensure consistency, accuracy, and brand voice of all Holloway Guides and related content.
To assemble and publish reliable knowledge from experts for all to learn from and build on. You can read more here.
We write for an audience that is 100% intelligent and also 100% naive about the topic at hand.
Our editorial principles are:
Our aspiration in writing Guides is that they be both deep and engaging. Technical and accessible. We want to earn respect from both experts and beginners. The voice and tone we use are critical to striking this balance.
At Holloway, we’ve paced the halls of many a company large and small in our readers’ shoes—we know that modern work is fraught with endless choices and the tool of record for navigating those choices (searching Google) yields questionable results at best. The Holloway voice is that of a trusted friend sitting across from our reader over coffee. The trusted friend of our reader has years of experience, but is not an “expert” removed from our reader by multiple degrees and decades of experience. While the trusted friend harnesses the knowledge of experts, they are perhaps only two or three years ahead of the reader. They can remember what it is that motivates the reader and what scares them; they understand the anxieties with which the reader approaches a topic or problem; they get that a reader might be urgently trying to figure out some course of action, but they also know the reader would love to delve into all the nuances of a topic, given the time.
Our voice wants to converse, not just drop information into the vessel of a reader. That’s not what you do to friends! But our friends really, really want to move from a 2 or 3 on Tim Urban’s Scale for understanding complex ideas to a 7 or 8—someone who doesn’t just reiterate popular opinion but can answer expert questions and reconcile contradictory thoughts about the idea. Because that’s how they can have better conversations. And they know we can help them with that. With a conversational, trustworthy voice and a fervor for research, we prefer clarity over flowery descriptions, and accuracy over easy answers. We use humor where it can help make our readers feel comfortable with a difficult topic; humor can help people feel like a topic is approachable, like the writing is for them, and like they are part of the conversation.
Here it is broken down: 1. We prioritize rigor. Our writing is accurate, precise, logical, and clear. Readers come to us often after failing to find trustworthy, comprehensive coverage of something complex. Save the fluff for sandwiches. 2. We are direct and genuine. We always respect the reader’s intelligence. The ability to learn has little to do with how much exposure someone has had to a particular topic in the past. Without oversimplifying details or writing for short attention spans, we aim to intrigue visitors by giving them a clear sense of what we’re going to offer, so that they know if they stick around and keep reading, they’re going to learn something of value. 3. We embrace complexity and don’t avoid conflicts. It’s our job to present the real complexities inherent in our topics. It’s tempting to hide messy or confusing details from readers, but we must not underestimate people’s ability to manage information when it is supplied well. When there is controversy, we give an overview of perspectives, reference the key people or resources on different sides, and give rationale and context. We do offer advice when we strongly believe that readers might be supplied with advice that is bad for them elsewhere. 4. We are empathetic. We never tell readers they should already know something, or assume that they come from a particular place, are of a particular age, or have a particular background or level of experience. In fact, we never use the phrase “you should.” We speak to people’s anxieties. We are never thoughtless when using humor, which we do sparingly. Poorly or thoughtlessly executed, “jokes” can alienate, anger, and even do harm. When calling out bad behavior, we always punch up, not down.
Principles of voice will remain true across Guides, articles, social media, and blog posts, while the tone might change depending on the medium and/or audience—whether we’re writing or editing for a Guide, a blog post, an email to customers, or social media. The emotional and mental states of people engaging with these different platforms can vary; while the voice of friendly rigor is the same across all Holloway output, casual humor and slang make more sense on Twitter than they do in a Guide, and personal opinions make a lot more sense in a newsletter than they do in a blog post. We always use first-person plural in all our publications and across social media, with the exception of newsletters, which are written by individuals.
In general, we adhere to the Chicago Manual of Style. Here’s a few key high-level points to consider across all aspects of our content.
We create Guides, not books. Avoid any wording along these lines, including:
There are a few helpful reminders that should be checked thoroughly for consistency:
An important thing to know about the common comma that can save you loads of agonizing: It isn’t used to connect, it’s used to separate. If you’re trying to connect two separate thoughts, you mean to use a semicolon, an em dash, or a colon. This is a useful way to tell if you’re comma splicing, or using a comma to separate two pieces that can stand on their own (otherwise known as independent clauses). Use commas when:
Separating coordinate adjectives, aka, adjectives that cannot be separated by the word and,as in: “What a beautiful, thoughtful piece of writing.” “Yes, it is thoughtful and beautiful, how wise.”
Use them when:
Use them when:
There are three types of dashes, the hyphen, the en dash, and the em dash. Most people are familiar with hyphens, but they are often overused. En dashes are mostly structural, and em dashes often present significant challenges. Here’s how we use them:
Tip: If you use a Mac, the en dash can be typed as ⌥-
Em dash (—) The em dash is a favorite punctuation at Holloway, because it’s primarily emotional. In most cases, an em dash can be replaced by a comma clause or a set of parentheses and technically the sentence will be correct. But each of these options represents a different emotional register. While a comma clause indicates a piece of information that can be considered equal to the rest of the information in a sentence, and a parenthetical usually contains supplemental, surprising, clarifying, or detracting information, the em dash is used to separate—that’s right—the information in a sentence that you definitely want the reader to notice. They are used to mark a shift in tone or to mark off important information you don’t want anyone to miss. They’re also better to use than a comma in the case that your sentence already has a great deal of commas. We use the em dash a lot at Holloway because it tends to bring a conversational tone to complex constructions containing a lot of information. You’ll notice em dashes throughout this text—you can refer to these if you get confused!
Tip: If you use a Mac, the em dash can be typed as ⇧⌥-
Note: In British written English, the en dash does the work of the em dash, which is hardly used outside the U.S. We just like things bigger here.
Our main use of brackets is to provide or clarify information within a quote that doesn’t appear in the original quote. Say Cynthia is a really cool dancer, and is participating in a dance contest later this month. Angelica wants to tell you (on the record) something about Cynthia: “She will win.” When it turns out that the article you’re writing has more to do with Angelica and in fact you aren’t even mentioning Cynthia’s dance ability, but still want to include Angelica’s line about her, because it just says so much about who Angelica really is, you might do this: “She will win [the dance competition].” Got it?
Note: brackets are also used heavily in Markdown format, such as to format links, but the reader never sees them.
Use them in company names (AT&T) and names of law firms. Do not use them otherwise in text, headings, or section titles.
This refers to normal text, like this, that is neither italicized nor boldfaced. Also known as upright text.
Italics are used for many things, including:
Newspapers, magazines, and periodicals
danger️ If a phrase is italicized, only the punctuation that the phrase contains should be italicized. If a colon or semicolon or comma separates the italicized phrase from further roman text, do not leave it italicized!
We also use italics in the following ways:
When quoting within a quote, use single quote marks, like, “He said, ‘I love you,’ but I could hear the air quotes.” Colons and semicolons go outside quotation marks. If the punctuation applies to the quote, put it inside; if it doesn’t, put it outside. We also use quotation marks to offset the following:
Titles of blog posts: When naming the title of a blog post, put quotation marks around the title—even when the title is also an external link. Like this:
… as Founder Collective director Joseph Flaherty writes in “How to Write Better Cold Emails to VCs.”
Boldface is used only in definitions, because they serve a specific function in the product. We’ll explain more in the section on definitions.
Do not use underlining. It’s a typewriter habit and not supported in Markdown or the Holloway Reader. (The Holloway Reader does use underline styling to indicate web links.)
Specific paragraphs (or bulleted items) can be tagged with emoji that express a special meaning. These trigger formatting rules in our product that help call out the type of content visually. The set is extensible but includes:
These emoji appear at the beginning of a block (“chunk,” usually a paragraph, but sometimes at the top of a bulleted list) of text, never within it. Put a space between the emoji and the first word of the chunk.
Paid and login emoji, as well as media type emoji, do appear in-line, preceding linked text. They should be placed after the first parenthesis containing linked text, with no space between emoji and linked text.
Headings come at different levels: part, section (formerly know as chapter), sub-section, and so on. We refer to these as H1, H2, and H3. These correspond to HTML levels (that is, the actual codes used on websites) as well as Markdown levels (one, two, or more # signs).
These are headings which are at the head of a paragraph (not H2 or H3). We often use them to guide the eye where a main heading is excessive, or to label each paragraph in a bulleted list of items.
Boldface inline headings. Avoid inline headings that are plain roman.
Italics should be used when referencing book titles; the names of blogs; article titles; newspapers, magazines, and periodicals.
We do not italicize blog post titles.
We also use italics specific to Holloway in the following ways:
Use boldface when you really want to offset something important or surprising. It can actually be helpful to do this as you write, because it can alert us to product features and graphic design opportunities we might employ.
We follow AP style for quoting people in the context of a sentence or paragraph.
When you want to highlight a quote to stand out, often at the start of a section or paragraph, use the 🅀 emoji. Be sure to leave a space after the quote, followed by an em-dash and the person’s name:
Famous remarks are very seldom quoted correctly.Simeon Strunsky*
The internet is full of unattributed, un-cited quotes. Don’t add to the noise. We aim for every quote that we include to inspire but also inform. Cite your source, using a footnote whenever possible.
Lists are extremely important to the flow and readability of Guides. We use two types of lists, bullet and numbered.
Use numbered lists only when laying out steps that should be taken in order.
We sometimes use paragraphs and sometimes bullets. Validate there is a reasonable balance, using bullets judiciously. Key pieces of content that fit together in a narrative way are good as paragraphs.
Bullets and sub-bullets encouraged whenever there is a laundry list of items, or three or more items fit together in a natural way, or the list may expand in the future via contributions. But not over-done or many levels deep.
If the paragraph before the list ends in a colon and the list is an itemization:
If there is no preceding semicolon, the bullets should each represent a different, separable piece of relevant information that can stand apart from others in the list and still be understood. It may happen that a colon precedes a list of items that are separable and stand-alone.
If every item of a bulleted list has a small inline heading (with a colon), boldface all of them, e.g.:
Exception: No need to bold lists of subjects under examination, eg. “Hire 1:; Hire 2:”, even if each example is followed by a colon, and especially if the explanatory text contains bolded text like numbers.
There are two types of inline links, internal (within a post or Guide, or to another Holloway resource) and external (elsewhere on the web).
Some formatting is the same for both internal and external links:
Prefer the most descriptive and logical set of words as anchor text that give a clue to the linked page or linked internal section.
Given that, prefer shorter anchor text. Long, highlighted links (with mouseovers), especially more than five words or so, tend to be distracting and ugly.
Example of long article text link that could be changed to be shorter:
Best practices for anchor text are also guided by how SEO works.
Do not include parentheses or quotation marks in the linked text.
Do not include articles like “a” or “the” in the linked text.
Use actionable words or phrases in a sentence if the action or assertion is the primary point. Prefer the verb or verb phrase over the object alone:
Nouns can work too, optionally including the adjectives or other parts of the phrase, depending on length and clarity:
Still good: “According to a 2014 New York Times article…”
Avoid using completely generic, self-descriptive anchor text that tells the reader to “read this” or “click here.”
When working in Google Docs, to reference another section within the Guide, simply put a section symbol (§) before the text you want to link. When the document lands, we will manually add in the links using markdown internal linking conventions.
We read and reference a vast amount of information. Where we don’t intend to link to a source for a reader to visit and read, we can cite it instead. Citation has to main uses:
You can also format in the Google doc as a normal footnote, for when you want to cite something that is more than a link, such as:
The vast majority of the time, a footnote style citation will simply point to a link: https://www.holloway.com/g/venture-capital
Anything other than that will typically follow this MLA-based general format:
Quoting from an interview (conducted by Holloway)
Quoting from a source, anonymous
A magazine article or something behind a paywall (rare)
Quoting someone from the article:
Just citing the article:
Include an acronym (something that can be used as a word, like HUD or FIFA) or initialism (what can’t be pronounced as a word, like FCC or ASPCA) in parentheses following the first full usage of the phrase or title. After that, repeat the full version if enough space in the text has gone by that a person paying a reasonable amount of attention could have forgotten what the acronym stands for. Generally, repeat the full phrase or title if it hasn’t been used in 1,000 words. The exception is any acronyms or initialisms that appear as part of a defining occurrence, meaning they will get mouseovers throughout the Guide and so do not need to be spelled out outside of the defining occurrence.
Numbers one through ten should be written out. 11 and up should be numerals. Do not spell out a range, use numerals instead, as in “Create a list of 5–10 people.”
Note: You may see exceptions to this, such as “We’ve seen this happen ten to twenty times.” We don’t yet have a hard and fast rule for this, so if you see it, call it out and we’ll figure out the right usage.
Also, an en dash—not a hyphen—is used to show a range of numbers, as in “9–20.”
If you’re only using numbers below 10, write it out, as in “one through three” or “one to three.”
Money should always be numerical, as in $3M. (Do not spell out to 3 million.)
Never spell out percentages, use the % sign. Percentage ranges should always prefer an en dash, as in 5–10%, with the single % sign at the end. Plus signs and approximate symbols are fine, as in $300M+ or ~$300M.
Thanks to the UNC Writing Center for help with this section.
If you can summarize the data in a figure or table in one to two sentences, do so. If your data are more numerous, providing a figure or table for representation can be helpful and keep text from getting cluttered with numbers.
A table is a columned list of raw data, numbers of text, and is not designed to show the relationship between any variable. Tables should be:
Figures are maps, graphs, charts, drawings, or photos. These are what you use when you’re trying to share a conclusion about your data in the form of relationships between variables. Figures should be:
Tip: Keep track of ideas for tables and figures while writing, and share these ideas with your editor. They can work with the engineering team to help produce these.
Definitions are a unique aspect of Holloway Guides and writing, and have their own guidelines, format, and style. They add structure and rigor to the editorial process. They also power features of the Holloway Reader experience, including:
Our goal is to write definitions that are high quality, constantly expanding, and make all of these things possible from the same source content.
Definition The defining occurrence of a term (word or phrase) is the first definitive mention of that term within a Guide. Often, the defining occurrence is the first time a term is mentioned, but it may be mentioned in passing or incidentally before its defining occurrence.
The defining block is the one paragraph (or, rarely but possibly, a bulleted item) that has the defining occurrence. The defining block should include one to three (or so) sentences that define the term for the lay reader.
Following a defining block, a Guide can have elaborative text (or follow-on chunks) that gives additional context or information about the term that was defined or about its context or placement within that Guide. Elaborative text is specific to a single Guide.
The defining block may appear in multiple places:
Elaborative text may appear:
Every defined term can have one or more alternate terms. These might include an acronym or initialism of the term being defined, a shortened version, synonyms, or simply an alternate but relevant phrasing. These alternate terms usually directly follow the defined term in the defining occurrence chunk. They will be supported with mouseover definitions of the defined term if they appear in parentheses, in bold along with the parentheses. In general, use (and bold) “or” within the parentheses if showing an alternate phrase, synonym, or abbreviation; no “or” is needed if showing an acronym or initialism.
Sometimes a joint definition is a fine substitute if the words seem different enough: “A founder or entrepreneur is an individual who started a company and now runs that company.
It may be the case that the best phrasing of a definition separates the defined term and its alternate:
Often, only one term will be defined per chunk. But sometimes it makes the most sense to define two terms at once, in contrast or relation to each other. A 🄳 before a chunk that is defining two terms works the same way as with one term. The chunk as a whole, with both terms defined, will come up as a mouseover for either term throughout the text. We call these joint definitions.
If a reader invariably will need to understand both concepts at once (in both directions, meaning both definitions depend on each other), it’s best to have a joint definition. In this example, understanding the terms “shares” or “stock” is impossible without knowing about both.
The set of all terms, including joint definitions and alternate definitions, is a definition group. A defining block is a paragraph that defines every term in a definition group.
Mouseovers also allow you to visit the defining occurrence by clicking (or tapping) on the mouseover text itself. (What you just saw there is an example of a mouseover for the definition of the defining occurrence!) This is important because a reader is able to get the context of the defining occurrence if they need it. Users will be able to jump to the defining occurrence (and see its surrounding text) and then jump back to where they were (this may be a forward and back button in the browser, though the tooling may change down the road). Otherwise, a reader can simply remind themselves of the definition using the mouseover feature and move on with where they were in the text.
Mouseovers are helpful because sometimes structure dictates that a term be mentioned before being officially defined; other times, a term may not be mentioned again until a dozen pages after it was defined. A forward mouseover occurs over a term that precedes that term’s defining occurrence. A reverse mouseover refers to a defining occurrence from earlier in the text.
A mouseover refers to the definition of a term appearing as you hold your cursor over the term (desktop) or quick-tap the term (mobile) as it occurs throughout the text.
Mouseover matches will be for the longest matching phrase. For example, “ownership interest” would have a mouseover definition but “ownership” would not.
Some terms are formally defined but are so common (“company,” “property”), we configure them to have mouseovers disabled globally.
Sometimes mouseovers may not occur consistently if two different and related multi-word terms occur in context, such as in “public and private company” or “preferred and common stock.” In those instances, only “private company” and “common stock” would get mouseovers. In cases where a reader would expect both terms to have mouseovers, change them to be the complete terms, as in, “public company and private company” and “preferred stock and common stock.”
A defining block is the most important paragraph on the term being defined. It is arguably one of the hardest things to write well, as it should be thorough, precise, and brief.
The defining block begins with defining text, which are the sentences that precisely define what term is and include the term in boldface, possibly with alternate terms. For joint definitions, each of the terms must be defined. The defining text is one sentence in the most common cases, but could be more.
The paragraph continues with text that fills in context, details, and other essential information that goes beyond the defining text but is still essential enough to be mentioned right away.
It’s worth explicitly considering—and if appropriate, deliberately omitting—each of these elements in a definition:
Context: If there is context to make sense of what it is, include that. Sometimes this goes in the first sentence.
Essential resources: What resources, if any, are so important anyone learning this term know about them in the definition? Longer lists of resouurces go in elaborative text, but sometimes certain resources are definitive.
Other than the defining text being first, the order is not strict, but it often flows in the order listed. Sometimes some items just aren’t essential, so are skipped.
That’s a lot, but in addition, all this should be done with brevity. There is no hard and fast rule, but aim for one medium to long paragraph, so between three and eight sentences is ideal.
Remember, the defining block is formal—clarity, precision, and accuracy are top priority. Loose commentary, jokes, or levity don’t have a place in the defining block. Elaborative text in a Guide can be used for more informal commentary and illustrations.
It’s not always obvious what should be defined as a term. Questions to ask:
Is this an established term?
Will it fit with the purpose of definitions in the product? If most of these are yes it’s likely a good term to define:
Anything experts would generally agree is a concept (even if the details are a little murky), it’s best if we do define it.
The exact phrase isn’t found in books or Google results. In this case it’s likely a concept that might be emphasized as a section title or a boldfaced concept, but not a definition.
Things experts may not even agree is a thing.
What do you do if something doesn’t make the cut but still “feels” like a term? Options:
Because subjects of Guides are often related, it’s common that a term defined in one Guide will also appear in one or more other Guides.
When possible, globalize the defining block by making it reusable across all Guides, and readable stand-alone. To globalize a definition, the defining block should not utilize language that is specific to the content of any one Guide. It should not reference its place in any single Guide with phrases like, “Now that we’ve covered X, here’s Y.”
In some cases globalizing a definition is not possible or too much work, which is okay. For these, the definition text in one Guide may be different from in another Guide.
When a definition is globalized, remember that subsequent follow-on chunks can differ in each Guide.
Joint and singular definitions, however, should always be consistent. If we define “stocks and shares” together in the Guide to Equity Compensation, they must also be defined together in the Guide to Raising Venture Capital, as joint definitions. If in Raising Venture Capital we define “common stock” and “preferred stock” separately, the terms should not be defined jointly as “common and preferred stock” in Equity Compensation.
Definitions should be the best brief definition available within the context of the Guide, and should include:
Elaboration given context—either of a specific Guide or, if a global definition, of the general field in which the majority of Guides fall under. This is essential—what does the term mean specifically in the context of the topic under study?
The defined term must be boldfaced. When possible, the boldfaced term should occur near the front of the definition, as well as the defining text (or the clearest single sentence that precisely defines the fundamental aspects of the term). This makes mouseovers easier to digest, and emphasizes what term or terms are being defined.
Any alternates must be boldfaced, along with the parentheses that hold them. If “or” is part of the parenthetical, it too should be boldfaced.
In the case of joint definitions, both defined terms must be boldfaced.
Boldface full terms if the partial term would have misleading mouseovers.
Do not use emojis in definitions. If there is a quality about a particular definition that needs to be pointed out—a pitfall or confusion, say—make an emoji-tagged statement about that quality in the elaborative text.
Because definitions will appear in a glossary, they are generally more formal than the text that surrounds them. They should be able to stand alone.
Avoid first person plural in defining text, as in, “We call this X.”
Avoid the second person in defining text. Explanatory text that follows defining text can be more informal and employ the second person (particularly when a definition depends upon or leads to some kind of action).
If there is explanatory text in the same paragraph as the main definition, but it is situational or otherwise not important enough to always appear inside a definition, move it to a subsequent bullet or paragraph. Remember, emoji tagging can be used on bulleted explanatory text that follows the formal definition of a term.
If in a definition you are making use of other terms or concepts that themselves are formally defined elsewhere in the Guide, you can rely on mouseovers of those terms appearing in the definition you’re working on. A definition block should focus on defining one term or on two (or more) inextricable terms in a joint definition, relying on mouseovers for any further terms used to explain them.
A definition will never mouseover the same term already being defined, even if the text appears more than once.
An incidental definition is when a new term is introduced but for one reason or another, we’re not going to define it formally with a full definition. Use italics for incidental definitions, not boldface. That way, a reader should not have to wonder, “Is this really a definition?” Incidental definitions should not appear within the defining occurrence of another term.
Avoid uncertain and imprecise language within defining text. Words like “maybe,” “often,” and “typically” can confuse the reader about whether these are defining characteristics or just commentary. The definition itself should be certain, even if its implications are uncertain. These can always be elaborated on later or even after a clear initial explanation.
For example, avoid phrasing like this: “🄳 Mortgage Insurance (MI) is a type of insurance that may protect the lender in case you fail to make payments.”
We prefer this: “🄳Mortgage Insurance (MI) is a type of insurance that protects the lender in case the borrower fails to make payments. It typically…”
Be careful about directions of implications so the full sense of the word is clear.
For example, the defining statement “X is a situation where Y” is not the same as “In situation X, Y happens” or “Y occurs when X.” The first is a precise definition since it means “X implies Y and Y implies X,” while the latter two both mean only “X implies Y.”
We prefer not to use external links in the defining sentence, notably to other definitive sources (e.g. Wikipedia or Investopedia). Our definitions should be authoritative, complete, and stand on their own.
Unless you really need to, don’t write definitions that unnecessarily “talk about the words” as this gets repetitive and verbose:
“The word X means Y.” (No kidding. It’s a word!)
“X means Y.”
In cases where terms are themselves confusing, and language and usage need to be discussed, the definition should have a confusion-tagged follow-on chunk.
Be careful about directions of implications so the full sense of the word is clear.
In general we prefer singular nouns. But this isn’t a hard-and-fast rule. Do what makes the most sense and reflects current usage.
Product mouseovers will work either way on almost all singulars or plurals.
Definitions may include key, important facts or notes or examples if they’re relevant to most readers of the definition. But they shouldn’t include illustrative examples that are pedagogical or situational.
Yes: “The tax brackets in the United States as of 2018 are X%, Y%, Z% …” (These concretely specify the tax brackets. And they can be updated later as needed.)
No: “For example, if George makes $80000, he pays $X in tax.” (This is a pure illustration not appropriate for a defining occurrence. It can go as subsequent Guide text.)
The defining occurrence of a term (word or phrase) is the place in a Guide the defining block occurs.
In our traditional format, the 🄳 emoji is used to indicate the defining block and the defining occurrence, as in the paragraph above. (In the future, the defining block may only appear in another table.)
Often, the defining occurrence is the first time a term is used at all, but it may be mentioned in passing or incidentally before its defining occurrence. The defining occurrence should include one to three (or so) sentences that define the term for the lay reader.
When the 🄳 is added at the start of a chunk of text that contains a bolded term, the annotation will make the chunk (a paragraph or bulleted item) the defining block for that Guide: the block can then appear elsewhere (as a searchable definition, on a landing page, in a mouseover, etc.).
It is very helpful to have the 🄳 readily available to you! Bring up the emoji keyboard by pressing (control + command + space bar). Expand the keyboard by clicking the small box in the top right corner. Copy and paste the 🄳 into the emoji search bar, then drag it into the “frequently used” section of your emoji keyboard. Now you can find it easily.
The defining occurrence should only be in one place. If the reader is already expected to understand a term, avoid re-stating a definition again in similar form a second place. The mouseover will be sufficient.
A Guide should be understandable if read front to back, even without mouseovers.
That is, even though mouseovers will add a lot of convenience, we’re not abandoning the editorial responsibility of organizing the definitions.
Structurally this is still like a book in key ways. Thinking about sequencing helps us organize material, have editorial discussions on organization much like a book, and source authors much like a book too—but with the convenience that a lot of language (like “see the section on X”) can be omitted.
Forward mouseovers should be used for convenience but not to dispel confusion.
Defining occurrences should be wherever they best fit common usage by the reader. To consider where a definition goes, ask: If a reader doesn’t understand X, what other things should they be reading about?
Everything should be made as simple as possible but no simpler.Albert Einstein (maybe?)
It turns out, no-one is entirely sure who said that. And that’s something we’re keenly aware of at Holloway. We thoroughly research our Guides (and cite every source)—comparing, debating, and when possible, reconciling differing or confounding perspectives. Inaccurate or unverified quotes, ideas, data, or conclusions are anathema to us.
This section is almost entirely from MailChimp’s guide.
People are at the core of what we do at Holloway. Readers, experts, interview subjects, writers, editors, engineers—our Guides rely heavily on all these people and many more. Anything we write should be respectful, compassionate, inclusive, and accurate.
Don’t reference a person’s age unless it’s relevant to what you’re writing. If it is relevant, include the person’s specific age, offset by commas.
Don’t refer to people using age-related descriptors like “young,” “old,” or “elderly.”
When writing about a person with disabilities, don’t use the words “suffer,” “victim,” or “handicapped.” “Handicapped parking” is OK.
Don’t call groups of people “guys.” Don’t call women “girls.”
Avoid gendered terms in favor of neutral alternatives, like “server” instead of “waitress” and “businessperson” instead of “businessman.”
Gender neutral pronouns: When referencing a real person, be certain that you are using that person’s preferred gender pronoun. You can often find this information on a person’s Twitter, personal homepage, or Wikipedia page.
Use the following words as modifiers, but never as nouns:
Don’t use these words in reference to LGBT people or communities:
Don’t use “same-sex” marriage, unless the distinction is relevant to what you’re writing. (Avoid “gay marriage.”) Otherwise, it’s just “marriage.”
When writing about a person, use their communicated pronouns. When in doubt, just ask or use their name.
Use “deaf” as an adjective to describe a person with significant hearing loss. You can also use “partially deaf” or “hard of hearing.”
Don’t use hyphens when referring to someone with dual heritage or nationality. For example, use “Asian American” instead of “Asian-American.”
Don’t refer to a person’s medical condition unless it’s relevant to what you’re writing.
If a reference to a person’s medical condition is warranted, use the same rules as writing about people with physical disabilities and emphasize the person first. Don’t call a person with a medical condition a “victim.”
Don’t refer to a person’s mental or cognitive condition unless it’s relevant to what you’re writing. Never assume that someone has a medical, mental, or cognitive condition.
Don’t describe a person as “mentally ill.” If a reference to a person’s mental or cognitive condition is warranted, use the same rules as writing about people with physical disabilities or medical conditions and emphasize the person first.
Use the adjective “blind” to describe a person who is unable to see. Use “low vision” to describe a person with limited vision.
Yeah, well, that’s just, like, your opinion, man.The Dude, The Big Lebowski
Not everyone agrees on the internet, but here’s how we handle these words at Holloway.
email (never hyphenate, never capitalize unless it begins a sentence)
Common mistakes, covered.
Use which when you’re providing information about a noun, use that when you’re pointing it out. E.g. “These rules, which I’m writing for you, are extremely helpful”; “That editor is remarkably arrogant.” This sounds simple, but ignoring this (oft-ignored) rule can lead to grave confusion.
It’s okay if this is hard, but it doesn’t have to be. Who refers to the main subject of a sentence, and whom refers to the thing being acted upon by the main verb; that thing is also known as the object. The easiest way to get this right is to use the substitution rule. If who can be substituted with he/she, it’s correct. Whom can be substituted only by him/her. Use the same rule when deciding between whoever and whomever. “Come and get it, whoever wants it.” “She wants it!” “Can I ever use whosoever?” Only if you’re singin’ Gospel.
Affect is a verb that means to influence, while effect is a noun, something that was influenced. (Affect can be a noun, and effect can be a verb, but don’t worry about all that. Just remember that you almost always mean affect.)
Many people don’t know this, but there is a difference. Further refers to metaphorical or figurative distance; farther is literal. Toward and towards (and backward(s) and afterward(s) and forward(s)) Easy! Since Holloway is out of California, and California is in America, just don’t use the s. The British edition can use it.
E.g. means “exempli gratia,” or, “for example.” I.e. means “id est,” or, “that is.” These Guides shouldn’t be so stuffy that you find yourself using these. Try “for example,” “like,” and “that is” or “as in.” Et al. means “and others,” and is usually used in reference to the multiple authors of an academic article, as in, “Frankenstein, et al.” This may come up in your list of citations.
Yes. “But” and “and” are acceptable! The revolution has been won by rebel forces.
While these guides are professional and designed to be authoritative, they shouldn’t be stuffy. It’s okay to use contractions occasionally, particularly when breaking into a more informal tone in, say, a parenthetical or another type of aside.
This editor is a proponent of separating this common conjunction in the cases that it helps with emphasis. Think of the options here as a line of defense: Can not is serious (“You can not take heroin, Timmy!”), cannot is normal (“We regret to inform you that we cannot attend your wedding”), and can’t is casual (“Dogs are the best; they just can’t help it!”) Can not is also correct when the not is part of another phrase or construction, as in, “Dogs can not only wag their tails, they can dig holes, too!”
This one just about sticks in my craw, I tell you what! Into and in to are not interchangeable, and often professional writers don’t know the difference. You are going into the mystic. But you go into let your soul and spirit fly. In to is a shortened version of in order to. Now you know!
A site is a place, either physical or electronic. Cite is short for citation:
“This would make a mighty fine site for a sawmill,” said Brent. “Sure would,” said Macadamia. “Let me look up how to build one on the internet. What’s that How-To site called?” “Look up Holloway Guides. Just make sure you cite them in your book about this grand adventure!”
Data are plural, as in “These data suggest that people fight about grammar more on the internet than in person.” Data point and datum (though it is rarely used) both take a singular construction.
When referring to a specific season, as in, “The average investor check size in Spring 2019 was $400B,” capitalize the season. When referring to the mere idea of a season, as in, “I love fall, isn’t it romantic,” don’t.
Getting tech company names right can feel like an endless game of Whac-a-Mole (or is it WhackAMole?). Here’s where to look when you’re not sure, and please let us know any that we should add to this list!