Skip to main content
Humanities LibreTexts

8.6: Strategies for marking up technical materials

  • Page ID
    51575
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \) \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)\(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\) \(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\)\(\newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    When you edit technical materials, your specific actions will depend on the type of editing and the materials' format.

    Copyediting vs. Proofreading

    Technical editors help develop technical communication artifacts as well as review them just before they are published. Before you begin editing, make sure you know which approach you should take.

    Editing during the developmental phase is called copyediting. This type of editing may involve "shaping" the document through deep edits and multiple comments to the materials' author. Documents that are being copyedited in hard copy are often (but not always) double-spaced.

    Editing during the pre-production phase is called proofreading. Ideally, proofreading should only require a superficial level of edit because it requires an editor to look for differences between the approved "dead copy" that has been edited multiple times and the first printed proof version—the "galley"—that will be reproduced and published. Documents that are being proofread in hard copy (on paper) are almost always single-spaced.

    Procedural markup vs. Structural markup

    Technical editors use different types of markup on text that depend on the editing goals and the edited materials' format. These approaches are complementary, not opposite.

    Procedural markup involves going through a document and marking specific changes. A common example is correcting misspelled words or deleting blank spaces. You may also use procedural markup to provide instructions for changing a document's layout and design.

    Structural markup involves "tagging" sections of a document to indicate they belong to specific categories. It is akin to using the Styles function of MS Word.

    You can also combine the two approaches by using procedural markup to indicate textual changes and structural markup to indicate formatting changes.

    Screenshot 2020-06-26 at 11.45.46.png
    Screenshot 2020-06-26 at 11.46.32.png

    Figure \(\PageIndex{1}\)


    This page titled 8.6: Strategies for marking up technical materials is shared under a CC BY license and was authored, remixed, and/or curated by Tiffani Reardon, Tammy Powell, Jonathan Arnett, Monique Logan, & Cassie Race.

    • Was this article helpful?