Current Issue

The Kairos Style Guide

Design Requirements

All webtexts go through a design-edit to ensure they are ready for publication. The design edit consists of checking for readability, accessibility, usability, and sustainability. Design-editing, just like copy-editing, is a practice in negotiation with the author's design-voice. Authors of HTML-based webtexts (e.g., everything except wiki webtexts) are required to follow these design and coding requirements.

Rhetorical Considerations

  • All media and design elements should be non-gratuitous and facilitate or enact the rhetorical and aesthetic argument of the webtext.
  • All links should contribute to the possible meanings and readings of the texts. Linking for the sake of linking is discouraged (e.g., external links in-text to outside sources is usually discouraged in favor of links in the works cited; internal linking to the works cited is discouraged unless a text specfically requires it, and then back-navigation must also be provided).
  • Authors should attempt to make clear where links are going so that readers may make informed navigational decisions. This can often be done by linking from descriptive phrases rather than individual words.
  • Links to external nodes should point, to the best of the author's knowledge, to stable sites and resources. Since back issues of Kairos will be available in our archives, we must strive to make all links as current and accurate as possible. Authors might consider contacting the authors of pages they link to in hopes of determining such stability.
  • Care should be given in linking to commercial sites in order to avoid promoting any particular companies or their products. If links must be made to commercial sites for the purposes of the webtext, they should be made to informational documents rather than sales pages when possible.
  • Offsite/external links should open in a new browser window.
  • Links to other Kairos webtexts should open in the same window.
  • Do not link terminal punctuation.

Accessibility

  • Use alt-tags with every image and embedded media element to provide a clear and concise description of the image and improve accessibility; alt tags should describe the image, title tags should explain the rhetorical use of the image. Where feasible, use the <figure> and <figcaption> tags for images, illustrations, charts, graphs, maps, and so on.
  • All submissions that include audio or video multimedia files must also include transcripts.
  • Sceenshots that primarily contain text should not be placed as images in a webtext (transcribe the text and style it with CSS).
  • Contact the journal if you think you may need to use using proprietary presentation software. For any media or presentation types, please provide alternate versions of your text as external XML and/or multimodal transcripts to increase readabilty and accessibility of your webtext. If we do accept work that uses an authoring system, you may be asked to submit the editable version (.fla, .doc, .aup, etc.) for editing by the staff once a piece has been accepted for publication.
  • Use WAVE (http://wave.webaim.org/) to review your webtext for accessibility issues, including code requirements and design considerations such as making sure text elements are presented with sufficient background-foreground contrast.
  • Upon acceptance, any text files or transcripts (usually Word or PDF files) that are linked to the webtext must be supplied for archiving on our server.

Usability

  • All non-wiki submissions require an HTML page (e.g. for a video or audio text, there must be an HTML page container for the media elements).
  • The home page for all non-wiki webtexts should be "index.html"
  • All HTML-based filenames and folders must be lowercase and include no spaces or non-Web characters.
  • All webpages in non-wiki webtexts should have titles that follow Kairos's page-title conventions (e.g. Authorlastname, Short Webtext Title - PageTitle). See current issue for examples.
  • Double-check to make sure all internal and external links work.
  • All images should reside in an /images/ folder (or /media/ folder, as appropriate).
  • HTML-based webtexts should demonstrate cross-browser compatibility (i.e., Internet Explorer 6+, Firefox 1.0+, Safari 1.0+, Opera 8+) and degrade gracefully when elements such as JavaScript are not enabled by a user's browser or when images/CSS fail to load.

Sustainability

  • We need to be able to archive everything we publish, so we cannot accept webtexts hosted on third-party sites (like WIX and Weebly).
  • We no longer accept webtexts in WordPress, or those composed in Adobe MUSE.
  • We strongly encourage authors to use standard, non-proprietary formats (HTML 5, CSS, etc.) rather than Flash or other embedded proprietary media or template engines.
  • Upon acceptance, we will need copies of all embedded media files, and all 3rd-party sites that host files must be shared with the journal in order to facilitate editing and archiving.

Code Requirements

Upon submission, all webtexts will be reviewed for adherence to the basic standards of valid markup. The simplest approach is to code properly from the outset, rather than attempting to correct errors at the end of the editorial process. This primarily requires a few simple steps to ensure that your code will validate. (Tip: You can use http://validator.w3.org/ for HTML and http://jigsaw.w3.org/css-validator/ for CSS to review your code at any time during the development process.)

The following is a short list of requirements that published webtexts will be expected to meet prior to final publication:

  • External style sheets are required to facilitate the editing process. Please do not use inline styles.
  • All element and attribute names must be lowercase (e.g. use alt, not ALT; p not P, etc.)
  • Attribute values must always be quoted (e.g. width="75" not width=75)
  • All non-empty elements that have an opening tag must have a matching closing tag. For example:
    a break must be coded as <br />, list items must end in </li>, and img tags require a closing /
  • Please use character entities for ampersands (&amp;), em-dashes (&mdash;), and en-dashes (&ndash;); however, do not use character entities for other characters.
  • We strongly prefer HTML 5 as the coding standard for Kairos webtexts.
  • The following lines should appear at the top of each HTML page (you can copy and past the code below if it is not already in the file):

    <!DOCTYPE html >
    <html lang="en">
    <head>
    <meta charset="utf-8">

Modified APA Citation Style

Kairos follows a modified version of APA, 7th edition. This in-house style is modified to include authors' and editors' full names in all reference lists and full names when the author(s) or editor(s) are mentioned in in-text citations for the first time in each webpage of a webtext. Like APA, 7th edition, the in-house style only includes the Retrieved on dates for website citations when the webpage is one that is likely to be updated (like Wikipedia, terms of service pages, about pages, and similar pages).

General Format for In-Text Citations in APA Style for Kairos

In-text citations selected from José Luis Cano Jr.'s "A Scyborg Composition Course"; Margaret Price and Erin Kathleen Bahl's "The Rhetoric of Description: Embodiment, Power, and Playfulness in Representations of the Visual"; and Sean Zdenek's "Designing Captions: Disruptive Experiments with Typography, Color, Icons, and Effects."

  • In "'Students' Right to Their Own Language': A Retrospective," Geneva Smitherman (1995) concluded that this resolution "served its historical time and paved the way for this next evolutionary stage," which she considered the "issue of multiple linguistic voices" (p. 26).
  • Bruce Horner and John Trimbur (2002) noticed the components that foster a "sense of inevitability that makes it difficult to imagine writing instruction in any language other than English" (p. 595).
  • Writing on the Rio Grande Valley, Alyssa Cavazos (2019) explored students' perceptions of linguistic matters in comp courses.

Many Kairos webtexts are submitted by authors more familiar with MLA style. With that in mind, what follows are some of the most common changes authors will have to make to be sure a webtext follows APA style for in-text citations:

  • A citation should include the name(s) of the author(s) and publication year. It should also include the page number when directly quoting or citing a very specific idea.
    We argued in Navigating This Webtext that "access is an interpretive relation between bodies" (Titchkosky, 2011, p. 3)
  • When the author name is used in a signal statement, the publication year follows the author name, and the page information appears at the end of the citation.
    In A Third University Is Possible, la paperson (2017) wrote: "The university is in assemblage. It is imbricated with other assemblages" (p. 62).
  • APA uses past tense for author signal statements. Example: "la paperson (2017) argued…"
  • Use an ampersand between the names of multiple authors or editors in parenthetical citations and reference lists (Selfe & Selfe, 1994).
  • Use block quotation format (the <blockquote> element) when including quotations of 40 or more words. Start the block quotation on a new line with a blockquote indentation and omit quotation marks:
    Disability is one thread in an "antenarrative" of technical and professional communication (TPC) research, according to Natasha Jones et al. (2016):
    Although TPC scholars have long been exploring issues of inclusion, the collective contribution of this work has gone largely unnoticed, (over)shadowed by the dominant narrative that technical communication is most concerned with objective, apolitical, acultural practices, theories, and pedagogies. The official narrative of our field indicates that TPC is about practical problem solving: a pragmatic identity that values effectiveness. But this is not the whole story. The narrative should be reframed to make visible competing (i.e., a collection of nondominant) narratives about the work our field can and should do. (pp. 211–212)

General Format for References Page in APA Style for Kairos

References page citations selected from issue 26.2 (Spring 2022) webtexts: Amanda Athon's "Great Power, Great Responsibility: Accessible Pedagogy for Teaching Comics"; Margaret Price and Erin Kathleen Bahl's "The Rhetoric of Description: Embodiment, Power, and Playfulness in Representations of the Visual"; Julianne Newmark and Tiffany Bourelle's "Fostering Community Through Metacognitive Reflection in Online Technical Communication Courses"; José Luis Cano Jr.'s "A Scyborg Composition Course"; and Jonathan Marine's Review of Rhetoric, Technology, and the Virtues.

Journal Articles

Open Access Journal Article with a DOI:

Cachia, Amanda. (2013). "Disabling" the museum: Curator as infrastructural activist. Canadian Journal of Disability Studies, 2(4). https://doi.org/10.15353/cjds.v2i4.110

<p>Cachia, Amanda. (2013). "Disabling" the museum: Curator as infrastructural activist. <cite>Canadian Journal of Disability Studies</cite>, <i>2</i>(4). <a href="https://doi.org/10.15353/cjds.v2i4.110" target="_blank">https://doi.org/10.15353/cjds.v2i4.110</a></p>

Open Access Journal Article with a URL but not a DOI:
(Note that links to Kairos webtexts don't open in a new tab like other external links do.)

Butler, Janine. (2016). Where access meets multimodality: The case of ASL music videos. Kairos: A Journal of Rhetoric, Technology, and Pedagogy, 21(1). http://kairos.technorhetoric.net/21.1/topoi/butler/index.html

<p>Butler, Janine. (2016). Where access meets multimodality: The case of ASL music videos. <cite>Kairos: A Journal of Rhetoric, Technology, and Pedagogy</cite>, <i>21</i>(1). <a href="/21.1/topoi/butler/index.html">http://kairos.technorhetoric.net/21.1/topoi/butler/index.html</a></p>

Thompson, Riki, & Lee, Meredith J. (2012). Talking with students through screencasting: Experimentations with video feedback to improve student learning. The Journal of Interactive Technology and Pedagogy, 1(1). https://jitp.commons.gc.cuny.edu/talking-with-students-through-screencasting-experimentations-with-video-feedback-to-improve-student-learning/

<p>Thompson, Riki, &amp; Lee, Meredith J. (2012). Talking with students through screencasting: Experimentations with video feedback to improve student learning. <cite>The Journal of Interactive Technology and Pedagogy</cite>, <i>1</i>(1). <a href="https://jitp.commons.gc.cuny.edu/talking-with-students-through-screencasting-experimentations-with-video-feedback-to-improve-student-learning/" target="_blank">https://jitp.commons.gc.cuny.edu/talking-with-students-through-screencasting-experimentations-with-video-feedback-to-improve-student-learning/</a></p>

Paywalled Journal Article with a DOI (the DOI URL remains unlinked):

Selfe, Cynthia L., & Selfe, Richard J., Jr. (1994). The politics of the interface: Power and its exercise in electronic contact zones. College Composition and Communication, 45(4), 480–504. https://doi.org/10.2307/358761

<p>Selfe, Cynthia L., &amp; Selfe, Richard J., Jr. (1994). The politics of the interface: Power and its exercise in electronic contact zones. <cite> College Composition and Communication</cite>, <i>45</i>(4), 480&ndash;504. https://doi.org/10.2307/358761</p>

Paywalled Journal Article with no DOI (don't use the index or database URL) or Print-only Article:

Kerschbaum, Stephanie. (2012). Avoiding the difference fixation: Identity categories, markers of difference, and the teaching of writing. College Composition and Communication, 63(4), 616–644.

<p>Kerschbaum, Stephanie. (2012). Avoiding the difference fixation: Identity categories, markers of difference, and the teaching of writing. <cite>College Composition and Communication</cite>, <i>63</i>(4), 616&ndash;644.</p>

Special Issues of a Journal
(Follow the same guidance above for articles regarding print versus online and open versus paywalled.)

Zdenek, Sean (Ed.). (2018b). Reimagining disability and accessibility in technical and professional communication [Special issue]. Communication Design Quarterly, 6(4).

<p>Zdenek, Sean (Ed.). (2018b). Reimagining disability and accessibility in technical and professional communication [Special issue]. <cite>Communication Design Quarterly</cite>, <i>6</i>(4).</p>

Books

Print Book:

Ahmed, Sara. (2019). What's the use? On the uses of use. Duke University Press.

<p>Ahmed, Sara. (2019). <cite>What's the use? On the uses of use</cite>. Duke University Press.</p>

Open Access Book with a DOI:

Dolmage, Jay Timothy. (2017). Academic ableism: Disability and higher education. University of Michigan Press. https://doi.org/10.3998/mpub.9708722

<p>Dolmage, Jay Timothy. (2017). <cite>Academic ableism: Disability and higher education</cite>. University of Michigan Press. <a href="https://doi.org/10.3998/mpub.9708722" target="_blank">https://doi.org/10.3998/mpub.9708722</a></p>

Open Access Book with a URL:

VanKooten, Crystal. (2020). Transfer across media: Using digital video in the teaching of writing. Computers and Composition Digital Press; Utah State University Press. https://ccdigitalpress.org/book/transfer-across-media/index.html

<p>VanKooten, Crystal. (2020). <cite>Transfer across media: Using digital video in the teaching of writing</cite>. Computers and Composition Digital Press; Utah State University Press. <a href="https://ccdigitalpress.org/book/transfer-across-media/index.html" target="_blank">https://ccdigitalpress.org/book/transfer-across-media/index.html</a></p>

Paywalled Digital Book with a DOI:

Holmes, Steve. (2017). The rhetoric of videogames as embodied practice: Procedural habits. Routledge. https://doi.org/10.4324/9780203731260

<p>Holmes, Steve. (2017). <cite>The rhetoric of videogames as embodied practice: Procedural habits</cite>. Routledge. https://doi.org/10.4324/9780203731260</p>

Edition Other Than the First:

Johnson-Sheehan, Richard. (2012). Technical communication today (4th ed.). Pearson.

<p>Johnson-Sheehan, Richard. (2012). <cite>Technical communication today</cite> (4th ed.). Pearson.</p>

Edited Collections
(Follow the same guidance above for books regarding print versus online and open versus paywalled.)

Elbow, Peter (Ed.). (1994). Landmark essays on voice and writing. Routledge.

<p>Elbow, Peter (Ed.). (1994). <cite>Landmark essays on voice and writing</cite>. Routledge.</p>

Chapters in Edited Collection
(Follow the same guidance above for books regarding print versus online and open versus paywalled.)

Arola, Kristin. (2017). Indigenous interfaces. In Douglas M. Walls & Stephanie Vie (Eds.), Social writing/social media: Publics, presentations, and pedagogies (pp. 209–224). https://doi.org/10.37514/PER-B.2017.0063.2.11

<p>Arola, Kristin. (2017). Indigenous interfaces. In Douglas M. Walls &amp; Stephanie Vie (Eds.), <cite>Social writing/social media: Publics, presentations, and pedagogies</cite> (pp. 209&ndash;224). <a href="https://doi.org/10.37514/PER-B.2017.0063.2.11" target="_blank">https://doi.org/10.37514/PER-B.2017.0063.2.11</a></p>

Articles in Online Periodicals

Metz, Cade. (2015, October 27). Facebook's AI can caption photos for the blind on its own. Wired. http://www.wired.com/2015/10/facebook-artificial-intelligence-describes-photo-captions-for-blind-people/

<p>Metz, Cade. (2015, October 27). Facebook's AI can caption photos for the blind on its own. <cite>Wired</cite>. <a href="http://www.wired.com/2015/10/facebook-artificial-intelligence-describes-photo-captions-for-blind-people/" target="_blank">http://www.wired.com/2015/10/facebook-artificial-intelligence-describes-photo-captions-for-blind-people/</a></p>

Podcast Episodes

Reid, Thomas (Host). (2018, May 2). On Black Panther audio description: On race, selection, and time [Audio podcast episode]. In Reid my mind. http://reidmymind.com/reid-my-mind-radio-on-black-panther-audio-description-race-selection-time/

<p>Reid, Thomas (Host). (2018, May 2). On Black Panther audio description: On race, selection, and time [Audio podcast episode]. In <cite>Reid my mind</cite>. <a href="http://reidmymind.com/reid-my-mind-radio-on-black-panther-audio-description-race-selection-time/" target="_blank">http://reidmymind.com/reid-my-mind-radio-on-black-panther-audio-description-race-selection-time/</a></p>

Webpages That Are Likely to Change or Be Updated
(Use "Retrieved from" and the date you accessed it.)

Twitter Help Center. (n.d.). How to make images accessible for people. Retrieved December 1, 2021, from https://help.twitter.com/en/using-twitter/picture-descriptions

<p>Twitter Help Center. (n.d.). <cite>How to make images accessible for people</cite>. Retrieved December 1, 2021, from <a href="https://help.twitter.com/en/using-twitter/picture-descriptions" target="_blank">https://help.twitter.com/en/using-twitter/picture-descriptions</a></p>

YouTube Videos

Marvel Entertainment. (2015, July 14). Marvel's Ms. Marvel volume 1: No normal in GraphicAudio trailer [Video file]. YouTube. https://youtu.be/_Gs357uNpOA

<p>Marvel Entertainment. (2015, July 14). Marvel's Ms. Marvel volume 1: No normal in GraphicAudio trailer [Video file]. <cite>YouTube</cite>. <a href="https://youtu.be/_Gs357uNpOA" target="_blank">https://youtu.be/_Gs357uNpOA</a></p>

Images

Todd, Gary Lee. (2016, July 22). Ancient Greece stone statues [Photograph]. Flickr. https://flic.kr/p/KoZfPb

<p>Todd, Gary Lee. (2016, July 22). <cite>Ancient Greece stone statues</cite> [Photograph]. Flickr. <a href="https://flic.kr/p/KoZfPb" target="_blank">https://flic.kr/p/KoZfPb</a></p>

Blog Posts

Kynard, Carmen. (2012, August 20). "Beyond Miranda's meanings": My first two lessons. Education, Liberation, and Black Radical Traditions for the 21st Century. http://carmenkynard.org/beyond-mirandas-meanings/

<p>Kynard, Carmen. (2012, August 20). "Beyond Miranda's meanings": My first two lessons. <cite>Education, Liberation, and Black Radical Traditions for the 21st Century</cite>. <a href="http://carmenkynard.org/beyond-mirandas-meanings/" target="_blank">http://carmenkynard.org/beyond-mirandas-meanings/</a></p>

ChatGPT and Generative AI

If you use ChatGPT or any other generative AI tools to produce content, we ask that you cite it in APA format.

General Suggestions for Modified APA, 7th edition

Many Kairos webtexts are submitted by authors more familiar with MLA style. With that in mind, what follows are some of the most common differences authors will have to make to be sure a webtext follows APA style for a final references page:

  • The final listing of sources in APA is called a "References" page, not "Works Cited" or "Bibliography."
  • The date is usually in second position (right behind author(s) or titles) and included within parentheses followed by a period.
  • Capitalize only the first letter of article/book titles and the first letter after a colon if there’s one in the title (with the exception of proper nouns and acronyms):
    Baca, Isabel. (2019). English, Español, or los dos. In Isabel Baca, Yndalecio Isaac Hinojosa, & Susan Wolff Murphy (Eds.), Bordered writers: Latinx identities and literacy practices at Hispanic-serving institutions (pp. 189–192). State University of New York Press.
  • Use "&" instead of "and" when listing multiple author or editor names:
    Selfe, Cynthia L., & Selfe, Richard J., Jr. (1994). The politics of the interface: Power and its exercise in electronic contact zones. College Composition and Communication, 45(4), pp. 480–504. https://doi.org/10.2307/358761
  • Multiple publications by the same author should be listed in chronological order, with names spelled out in all instances. If publications occur in the same year by a single author (or co-authors), add letters to the year of publication and list the entries in alphabetical order by title. Include the letters—e.g., (Zdenek, 2018a) or (Zdenek, 2018b)—when making in-text references.
    Zdenek, Sean. (2018a). Designing captions: Disruptive experiments with typography, color, icons, and effects. Kairos: A Journal of Rhetoric, Technology, and Pedagogy, 23(1). http://kairos.technorhetoric.net/23.1/topoi/zdenek/
    Zdenek, Sean (Ed.). (2018b). Reimagining disability and accessibility in technical and professional communication [Special issue]. Communication Design Quarterly, 6(4).
  • Italicize journal titles and issue numbers, using <cite> for the journal title and <i> for the volume number
    <cite>College Composition and Communication</cite>, <i>45</i>(4)
  • University press names are spelled out:
    Ahmed, Sara. (2019). What's the use? On the uses of use. Duke University Press.
  • APA, 7th edition, no longer requires cities to be listed for publications. Don't include them. They're anocronistic.
  • For electronic references, there is no final punctuation and the URL should be linked to open in a new browser tab unless it’s linked to another Kairos webtext, in which case it should not open in a new tab. Use the attribute and value target="_blank" for <a> to open a link in a new window. Leave it out for Kairos webtexts:
    <p>Butler, Janine. (2016). Where access meets multimodality: The case of ASL music videos. <cite>Kairos: A Journal of Rhetoric, Technology, and Pedagogy</cite>, <i>21</i>(1). <a href="http://kairos.technorhetoric.net/21.1/topoi/butler/index.html">http://kairos.technorhetoric.net/21.1/topoi/butler/index.html</a></p>
    <p>Thompson, Riki, &amp; Lee, Meredith J. (2012). Talking with students through screencasting: Experimentations with video feedback to improve student learning. <cite>The Journal of Interactive Technology and Pedagogy</cite>, <i>1</i>(1). <a href="https://jitp.commons.gc.cuny.edu/talking-with-students-through-screencasting-experimentations-with-video-feedback-to-improve-student-learning/" target="_blank">https://jitp.commons.gc.cuny.edu/talking-with-students-through-screencasting-experimentations-with-video-feedback-to-improve-student-learning/</a></p>
  • For electronic resources, APA, 7th edition, only requires a Retrieved on date if the webpage is not stable or is likely to be updated. Don't include Retrieved on dates for stable webpages. Include them on websites that are likely to be updated:
    Butler, Janine. (2016). Where access meets multimodality: The case of ASL music videos. Kairos: A Journal of Rhetoric, Technology, and Pedagogy, 21(1). http://kairos.technorhetoric.net/21.1/topoi/butler/index.html
    Twitter Help Center. (n.d.). How to make images accessible for people. Retrieved December 1, 2021, from https://help.twitter.com/en/using-twitter/picture-descriptions
  • APA uses an en dash to mark page ranges. This is marked in html with &ndash;: 480&ndash;504
  • Use <cite> for italicized titles, <em> for words that should be emphasized, and <i> for italicized words that aren't emphasized (like volume numbers or non-English words):
    Baca, Isabel. (2019). English, <i>Español</i>, or <i>los dos</i>. In Isabel Baca, Yndalecio Isaac Hinojosa, &amp; Susan Wolff Murphy (Eds.), <cite>Bordered writers: Latinx identities and literacy practices at Hispanic-serving institutions</cite> (pp. 189&ndash;192). State University of New York Press.

Common Grammar, Style, and Usage Errors

  • When referring to the Kairos text itself, refer to it as a webtext (not an article or an essay) unless there's a PDF or other accompaniment being referred to.
  • Abbreviations: spell out entire name on the first use and include abbreviation in parenthesis after (e.g., short–term memory (STM)). The abbreviation can be used thereafter, but must be redefined on every node. Note that APA allows for some terms that have their own Webster's Dictionary entries to be listed alone, such as IQ.
  • Ampersands: use character entities (&amp;). These should only be used in References lists or in names that are trademarked with & (e.g., Computers and Composition is trademarked as is, not with an ampersand).
  • Capitalization: in text, do not capitalize field names (e.g., Rhetoric should be rhetoric) unless it is a proper noun (e.g., English should be English). Similarly, do not capitalize job titles (e.g., Associate Professor) or units (e.g., Writing Center) unless it precedes the person's name or is used as a proper noun (e.g., the writing center is the hub of all activity; The Sweetland Center for Writing is the pre-eminent...). In the References list, book titles, article titles, and chapter titles should only have the first word, proper nouns and acronyms, and words directly following a colon capitalized. All other words in book titles, article titles, and chapter titles should be lowercase.
  • Commas around years: set off year in exact dates (e.g., April 25, 2011, was the correct date) but not month only (e.g., April 2011).
  • –em dashes: use character entities (&mdash;), and there should be no spaces around them.
  • –en dashes: use character entities (&ndash;), and there should be no spaces around them. The –en dash is frequently used when there are sets of pages, and character entities should be used in text and in the References list.
  • Hyphenation: do not use hyphens with "non–" words, unless meaning would be confused without the hyphen.
  • In–text citations: in APA style, writers only need to repeat the author and year citation within a single paragraph when a second citation has been inserted in between two citations for the previous author and year.
  • Parentheses: (When a complete sentence is enclosed in parentheses, place punctuation in the sentence inside the parentheses, like this.) If only part of a sentence is enclosed in parentheses (like this), place punctuation outside the parenthesis (like this).
  • Serial comma: use a comma between elements in a series of three or more items (e.g., height, width, and depth).
  • Sets of page numbers: when including a set of page numbers, all numerals should be included (e.g., pp. 119–157 instead of pp. 119–57).