O’Reilly Style Guide and Word List

About O'Reilly Style

This style guide is for authors, copyeditors, and proofreaders working on books of all formats. As writers and editors, we know that language changes over time, so please check back regularly for updates to terms and conventions.

Authors, please also consult the authoring documentation for the format in which you’re writing (Asciidoc, HTMLbook, DocBook, or Word). For sponsored projects, please see our statement of editorial independence

Check our guide and word list first, then The Chicago Manual of Style, 17th edition, then Merriam-Webster’s Collegiate Dictionary. Use your book-specific word list (provided by production) to document style choices that differ or are not covered here (e.g., A.M. or a.m., data center or datacenter, etc.). For questions specific to your book or assignment, please consult with your editor or production editor.

To avoid unintentional bias, when writing about groups of people, check the group’s advocacy organization for guidance on appropriate language. The Conscious Style Guide is one good resource, aggregating links to relevant organizations. Always follow a person’s preference and note exceptions, if necessary (e.g., if quoting research that is decades old).

For questions specific to your book or assignment, please consult with your editor or production editor.

Considering Electronic Formats

Because we use a single set of source files to produce the print and electronic versions of our books, it’s important to keep all formats in mind while writing and editing:

O’Reilly Grammar, Punctuation, etc.

For any words or conventions not covered here, refer to The Chicago Manual of Style, 17th edition and Merriam-Webster.

back to top

Abbreviations/Acronyms

  • Generic pronouns should be they/their when needed, not he, she, or he/she.

  • Acronyms should generally be spelled out the first time they appear in a book, as in: "collaborative development environment (CDE)." See the Word List for common exceptions. After the acronym has been defined, you should generally use the acronym only (not the whole term, unless it makes more sense contextually to use the whole term). Usually, acronyms are defined only once per book. But if the author prefers, we can also define certain terms the first time they appear in each chapter.

  • Acronyms should be capitalized when expanded only if the term is a proper noun (and spelled that way by the company). For example, key performance indicator (KPI), but Amazon Web Services (AWS).

  • A.M. and P.M. or a.m. and p.m.—be consistent.

  • K = 1,024; k = 1,000. So a 56 kbps modem is equal to 56,000 bps, while 64K of memory is equal to 65,536.

  • In units of measure, do not use a hyphen. For example, it’s 32 MB hard drive, not 32-MB hard drive. (Though when the unit is spelled out, use a hyphen, e.g., 32-megabyte hard drive.)

  • University degrees (e.g., B.A., B.S., M.A., M.S., Ph.D., etc.) can appear with or without periods—just be consistent.

  • United States and United Kingdom should be spelled out on first mention. After that, just use the acronym with no periods (so, US or UK).

back to top

Bibliographical Entries and Citations

In general, when referring to another book within a book’s text, include the author name(s) for up to two authors. For three or more authors, state the first author name, followed by “et al.” (be sure to include the period).

On first reference to another book, include author and publisher name. For example, "You can find more information in The Elements of Typographic Style by Robert Bringhurst (H&M)," or "For more information, consult Robert Bringhurt’s The Elements of Typographic Style (H&M)." On subsequent references, just use the book title.

When referencing an O’Reilly book within the text, note only "O’Reilly" in parentheses, not "O’Reilly Media, Inc." References to other O’Reilly books should be linked to the book’s catalog page.

Make sure that the catalog page is anchored to the book’s title, rather than standing on its own like this: "See Programming F# 3.0." NOT THIS: "See Programming F# 3.0 (http://shop.oreilly.com/product/0636920024033.do)."

Citations

When citing other materials in bibliographies, reference lists, or footnotes, use the “Notes and Bibliography” system from the The Chicago Manual of Style, 17th edition. Chicago also has an Author-Date system that some authors prefer, which is perfectly acceptable. If there is no discernable consistency, suggest Chicago's Notes for footnotes and Bibliography for endnotes or back matter.

Let your production editor know which conventions you applied by adding a note to the Word List Doc.

Footnotes

  • Footnotes in running text are numbered and start over at 1 in each chapter. Footnote markers in running text should always appear after punctuation.

    This: The following query selects the symbol column and all columns from stocks whose names start with the prefix price.1

    Not this: The following query selects the symbol column and all columns from stocks whose names start with the prefix price1.

  • Footnotes should contain more than just a URL, whether a full citation for the text the URL points to or context for where the link leads.

    This:

    1. The Wikipedia entry on JavaScript (https://en.wikipedia.org/wiki/JavaScript) provides more information.
    2. Grove, John. 2015. “Calhoun and Conservative Reform.” American Political Thought 4, no. 2 (March): 203–27. https://doi.org/10.1086/680389.

    Not this:

    1. https://en.wikipedia.org/wiki/JavaScript
    2. https://doi.org/10.1086/680389
  • Table footnotes are lettered (a, b, c, etc.) and appear directly after the table. They should be kept to a minimum.

More details about styling footnotes in AsciiDoc are in Writing in AsciiDoc.

back to top

Cross References

Here are a few examples of cross references:

  • Chapter: See Chapter 27.

  • Section: See the section “Treatment”. (The text “on page x” will be added post-conversion, so the final xref will eventually read “Treatment” on page 37.)

  • Section in another chapter: See “Acceptable Gifts” on page 58 in Chapter 27.

More details on cross-references in Asciidoc are available in our Writing in AsciiDoc guide.

These cross-reference styles are also available in DocBook under various <xref>: formats. Please refer to the DocBook Authoring Guidelines.

For information about styling URLs and hyperlinks, see Considering Electronic Formats.

back to top

Headings

Capitalization in headings:

  • In most of our design templates, A- and B-level headings are initial-capped (or title case): cap the first letter of each word, with the exception of articles, conjunctions, and program names or technical words that are always lowercase.

  • Prepositions of four letters or fewer are not initial-capped, unless they function as part of a verb (e.g., “Set Up Your Operating System”).

  • Hyphenated words in subordinating conjunctions (e.g., as, if, that, because, etc.) are always initial-capped (even if they are four letters or less). Hyphenated words in titles or captions should both be capped if the second word is a main word, but only the first should be capped if the second word isn’t too important (it’s a bit of a judgment call). For example: Big-Endian, Built-in. See The Chicago Manual of Style.

  • C-level headings have initial cap on the first word only (also called sentence-case), with the exception of proper nouns and the first word that follows a colon (unless that word refers to code and should be lowercase).

  • D-level headings (rare) are run-in with the following paragraph and have an initial cap on the first word only, with the exception of proper nouns and the first word that follows a colon (unless that word refers to code and should be lowercase), with a period at the end of the heading.

  • Sidebar titles are initial-capped, or title case (like A- and B-level headings, mentioned previously).

  • Admonition (note/tip/warning) titles are initial-capped, or title case (like A- and B-level headings, mentioned previously). Admonition titles are optional.

Headings should not contain inline code font or style formatting such as bold, italic, or code font.

Headings should always immediately precede body text. Do not follow a heading with an admonition or another heading without some form of introductory or descriptive text.

back to top

Dates and Numbers

What to spell out and when:

  • Spell out numbers under 10 and certain round multiples of those numbers unless the same object appears in a sentence with an object 10 or over (five apples; five apples and one hundred oranges; 5 apples and 110 oranges). The whole numbers one through nine followed by hundred, thousand, million, billion, and so forth are usually spelled out (except in the sciences or with monetary amounts).

  • In most numbers of one thousand or more, commas should be used between groups of three digits, counting from the right (32,904 NOT 32904). Exceptions: page numbers, addresses, port numbers, etc.

  • Use numerals for versions (version 5 or v5).

  • Use a numeral if it’s an actual value (e.g., 5% 7″ $6.00).

  • Always use the symbol % with numerals rather than the spelled out word (percent), and make sure it is closed up to number: .05%. Unless the percentage begins a sentence or title/caption, the number should be a numeral with the % symbol.

  • Ordinal numbers: Spell out first through ninth, use numerals for 10th and above. No superscript.

Formatting:

  • Use spaces around inline operators (1 + 1 = 2. NOT 1+1=2).

  • 32-bit integer.

  • 1980s or ’80s.

  • Phone numbers can appear in the format xxx-xxx-xxxx.

  • Use an en dash (–) with negative numbers or for minus signs, rather than a hyphen.

  • Use multiplication symbol “×” for dimensions, not "by" (e.g., "8.5 × 11").

back to top

Figures, Tables, and Examples

Every figure, table, and example should be preceded by a specific in-text reference (for example: see Figure 99-1; Example 1-99 shows; Table 1-1 lists, etc.). Figures, tables, and examples should not be introduced with colons or phrases like “in the following figure,” or “as shown in this table.” Lack of specific in-text references may cause incorrect placement of figures.

If you are writing or copyediting in Word, figure, table, and example numbers should be numbered as follows: 1-2 (note hyphen [-], not en dash [–] between numbers). The first number is the chapter number. This will be soft-coded in production if not during the writing process.

If you are writing or copyediting in Asciidoc, please refer to Writing in AsciiDoc for examples of Asciidoc cross references.

If you are writing or copyediting in DocBook, please reference each figure, table, and example with an <xref>.

Any word groupings within a figure should have an initial cap on the first word only, with the exception of proper nouns. Generally, we don’t use periods at the end of these word groupings.

  • Figure 1-1. Figure captions are initial-capped on first word only, with the exception of proper nouns. Code styling is allowed within the figure name or caption. There is no period after figure captions, but if all captions are long and sentence style, periods can be used as long as they are used consistently throughout.

  • Table 1-1. Column heads and table titles are initial-capped on the first word only, with the exception of proper nouns. Code styling is allowed within the table name or caption. There is no period after table titles.

  • Example 1-1. Example titles are initial-capped on the first word only, with the exception of proper nouns. Code styling is allowed within the example name or caption. There is no period after example titles.

When working in Word, make sure all table cells are tagged with a cell paragraph tag, even if they’re blank. Any bold “headings” that appear below the very first row of a table should be tagged CellSubheading rather than CellHeading.

Also in Word, all figures must be within a FigureHolder paragraph followed directly by a FigureTitle paragraph.

back to top

Code

Line Length

Maximum line length for code varies slightly between book formats. Consult the table below to find the maximum line length for your book’s series within Atlas v2. If writing in Word, please keep code within the margins that appear in the Word template and indicate proper linebreaks and indents for all code. Indent using spaces, not tabs.

Series Body (top-level code) Examples Lists Readeraids Sidebars

Animal

81

85

73

57

77

Animal 6x9

64

68

56

40

60

Report 6x9

64

68

56

40

60

Trade 6x9

76

72

65

80

69

Cookbook

81

85

73

57

77

Make 1-column

89

89

81

66

39

Make 2-column

45

46

35

28

40

Make Getting Started

63

67

60

51

60

Nutshell

71

75

67

60

75

Pocket Ref

51

55

50

42

51

Theory in Practice

81

85

77

51

83

Syntax Highlighting

We use a tool called Pygments to colorize code. In most books, code will appear in black and white in the print book and in color in all electronic formats, including the web pdf. If you’re an author, please consult the list of available lexers and apply them to your code as you write. To apply syntax highlighting in Asciidoc, consult Writing in AsciiDoc. To apply syntax highlighting in DocBook, consult the DocBook Authoring Guidelines. To apply syntax highlighting in Word, consult the O’Reilly Media Word Template Quickstart Guide.

Formatting Code in Word

When copyediting in Word, please do a global search and replace for tabs in code (search for \^t to find them) before submitting files for conversion; tabs will not convert. A general rule of thumb is one tab can be replaced with four spaces (which is the same number that the clean-up macro in the ORA.dot template uses). However, this number can vary, so the most important thing is that copyeditors replace tabs with the numbers of spaces needed to match the indentation and make sure levels of indentation are preserved.

back to top

Lists

Typically, we use three types of lists: numbered lists, for ordered steps or chronological items; variable lists, for terms and explanations/definitions; and bulleted lists, for series of items. List items are sentence-capped. List items should be treated as separate items and should not be strung together with punctuation or conjunctions.

NOT O'Reilly style:

  • Here is an item, and
  • here is another item; and
  • here is the final item.

O'Reilly style:

  • Here is an item
  • Here is another item
  • Here is the final item

Following are examples of each type of list.

Numbered list

The following list of step-by-step instructions is an example of a numbered list:

  1. Save Example 2-1 as the file hello.cs.

  2. Open a command window.

  3. From the command line, enter csc /debug hello.cs.

  4. To run the program, enter Hello.

Variable list

The following list of defined terms is an example of a variable list:

Setup project

This creates a setup file that automatically installs your files and resources.

Web setup project

This helps deploy a web-based project.

Bulleted list

The following series of items is an example of a bulleted list:

  • Labels

  • Buttons

  • A text box

“Bulleted” lists nested inside of bulleted lists should have em dashes as bullets.

Frequently, bulleted lists should be converted to variable lists. Any bulleted list whose entries consist of a short term and its definition should be converted. For example, the following bulleted list entries:

  • Spellchecking: process of correcting spelling

  • Pagebreaking—process of breaking pages

should be variable list entries:

Spellchecking

Process of correcting spelling

Pagebreaking

Process of breaking pages

back to top

Punctuation

For anything not covered in this list, please consult the Chicago Manual of Style, 17th Edition.

  • Serial comma (this, that, and the other).

  • Commas and periods go inside quotation marks.

  • Curly quotes and apostrophes (“ ” not " ") in regular text.

  • Straight quotes (" " not “ ”) in constant-width text and all code. Some Unix commands use backticks (`), which must be preserved.

  • No period after list items unless one item forms a complete sentence (then use periods for all items within that list, even fragments).

  • Em-dashes are always closed (no space around them).

  • Ellipses are always closed (no space around them).

  • For menu items that end with an ellipsis (e.g., "New Folder…"), do not include ellipsis in running text.

  • Lowercase the first letter after a colon: this is how we do it. (Exception: headings.)

  • Parentheses are always roman, even when the contents are italic. For parentheses within parentheses, use square brackets (here’s the first parenthetical [and here’s the second]).

back to top

Miscellaneous

  • Do not use a hyphen between an adverb and the word it modifies. So, “incredibly wide table” rather than “incredibly-wide table.”

  • Unless part of a proper noun, close up words with the prefixes “micro,” “meta,” “multi,” “pseudo,” “re,” “non,” “sub,” and "co" (e.g., “multiusers,” “pseudoattribute,” “nonprogammer,” “subprocess,” "coauthor"). Exceptions are noted in the word list (e.g., "re-create," "re-identification").

  • Compound words are closed up when used as nouns (“coverup”), hyphenated when used as adjectives (“the cover-up measures”), and two words when used as verbs (“cover up the flaw with…”).

  • Avoid using the possessive case for singular nouns ending in “s,” if possible. So, it’s “the Windows Start menu,” not “Windows’s Start menu.”

  • Avoid wholesale changes to the author’s voice—for example, changing the first-person plural (the royal “we”) to the first-person singular or the second person. However, do try to maintain a consistency within sentences or paragraphs, where appropriate.

  • We advise using a conversational, user-friendly tone that assumes the reader is intelligent but doesn’t have this particular knowledge yet—like an experienced colleague onboarding a new hire. First person pronouns, contractions, and active verbs are all encouraged.

  • Companies are always singular. So, for example, “Apple emphasizes the value of aesthetics in its product line. Consequently, it dominates the digital-music market” is correct. “Apple emphasize the value of aesthetics in their product line. They dominate the digital-music market” is not. (Also applies to generic terms “organization,” “team,” “group,” etc.)

  • When referring to software elements or labels, always capitalize words that are capitalized on screen. Put quotes around any multiword element names that are lowercase on screen and would thus be hard to distinguish from the rest of the text (e.g., Click “Don’t select object until rendered” only if necessary.)

  • Use “between” for two items, “among” for three or more. Use “each other” for two, “one another” for three or more.

  • Use the American spellings of words when they differ.

  • Common foreign terms (such as “en masse”) are roman.

  • Introduce unnumbered code blocks with colons.

  • Do not stack admonitions, sidebars, or headings.

  • Avoid obscenities and slurs, and obscure if included (grawlix, a two em dash, etc.)

back to top

Typography and Font Conventions

The following shows the basic font conventions used in O’Reilly books. Follow these links for detailed instructions for applying these styles in Asciidoc, DocBook, and Word.

If you want to use a font convention that is slightly different for one of the following items, check with your editor first—some things can change; some can’t. For example, URLs will not be anything but italic, but you might come up with a different font convention for function names or menu items. If you do use something that differs from the following list, please write it down on your printout of this stylesheet, which should be submitted with your manuscript.

If you have a “new” element, please consult with your editor about which font to use, then write it on your printout and submit it with your manuscript.

Type of element Final result

Filenames, file extensions (such as .jpeg), directory paths, libraries, and commands in Unix, Oracle, SQL, and Linux books

Body font italic

URLs, URIs, email addresses, domain names

Body font italic

Emphasized words (shouting!).

Please use italics rather than bold for emphasis.

Body font italic

First instance of a technical term

Body font italic

Code blocks

Constant width

Registry keys

Constant width

Language and script elements: class names, types, namespaces, attributes, methods, variables, keywords, functions, modules, commands, properties, parameters, values, objects, events, XML and HTML tags, and similar elements. Some examples include: System.Web.UI, a while loop, the Socket class, and the Obsolete attribute. Exception: commands in Unix, Oracle, SQL, and Linux book, which are regular italics.

Constant width

Replaceable items (placeholder items in syntax); “username” in the following example is a placeholder: login: username

Constant width italic

Commands or text to be typed by the user

Constant width bold

Line annotations

Body font italic (but smaller)

Placeholders in paths, directories, URLs, or other text that would be italic anyway

http://www.<yourname>.com

Keyboard accelerators (Ctrl, Shift, etc.), menu titles, menu options, menu buttons

Body text

These font conventions may vary slightly for each project; please consult your editor, the production editor, or the freelance coordinator if you have any questions. Please note: Word authors should refer to the Word Template Quickstart Guide; DocBook authors should refer to our DocBook Authoring Guidelines (username: guest; leave the password blank).

It’s very important to follow tagging conventions for terms. The method for applying conventions will vary depending on the format: Word/OpenOffice, DocBook XML, or InDesign. Please consult with your editor or toolsreq@oreilly.com for instructions specific to each environment.

For Word copyediting, please do the following before submitting files for conversion: replace any tabs in code with the appropriate number of spaces (see earlier section, Code); convert any remaining Word comments to tagged Comment paragraphs highlighted in blue; search for any manual linebreaks (^l) and delete or replace with paragraph breaks as appropriate; and accept all changes and make sure filenames adhere to house style.

back to top

O'Reilly Cover Style

Use Chicago Maual of Style, 17th Edition for anything not mentioned here.

Bulleted lists on the back cover should begin with a capitalized word and end with no punctuation. Even if the list item is a complete sentence, it will not take a period.

back to top

O’Reilly Word List

Alphabetical Word List: Default spellings

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z |

A

  • acknowledgments
  • ActionScript
  • ActiveX control
  • Addison-Wesley
  • ad hoc
  • ADO.NET
  • Agile (cap when referring to Agile software development or when used on its own as a noun)
  • AI (no need to expand acronym to artificial intelligence)
  • Ajax
  • a.k.a. or aka (be consistent)
  • a.m. or A.M.
  • Alt key
  • Alt-N
  • anonymous FTP
  • antipattern
  • API (no need to expand acronym to application programming interface)
  • appendixes
  • applet (or Java applet)
  • AppleScript
  • AppleScript Studio (ASS)
  • ARPAnet
  • ASCII
  • ASP.NET
  • at sign
  • autogenerate
  • awk

back to top

B

  • backend
  • background processes
  • backpressure
  • backquote
  • backslash
  • Backspace key
  • backtick
  • backup (n); back up (v)
  • backward
  • backward compatible
  • bandwidth
  • BeOS
  • Berkeley Software Distribution (BSD)
  • Berkeley Unix (older books may have UNIX)
  • BHOs
  • big data
  • Big Design Up Front (BDUF)
  • bioinformatics
  • Bitcoin (capitalize the concept/network/currency in general; lowercase specific units of currency)
  • bitmap
  • bit mask
  • Bitnet
  • bit plane
  • bitwise operators
  • BlackBerry
  • –black-box/white-box testing s/b avoided (alternatives: behavioral/structural testing, closed/open testing, opaque/clear testing)
  • –black hat/white hat s/b avoided (alternatives: unethical/ethical, malicious/preventative)
  • –blacklist/whitelist s/b avoided (alternatives: blocklist/allowlist, deny/permit, forbidden/permissible)
  • Boolean (unless referring to a datatype in code, in which case s/b lowercase)
  • Bourne-again shell (bash)
  • Bourne shell
  • braces or curly braces
  • brackets or square brackets
  • browsable
  • _build->measure->learn_ cycle
  • built-in (a, n)
  • button bar

back to top

C

  • CacheStorage
  • call-to-cation
  • Caps Lock key
  • caret or circumflex
  • CAT-5
  • CD-ROM
  • C language (n)
  • C-language (a)
  • checkbox
  • checkmark
  • check-in (n)
  • classpath
  • CLI (no need to expand acronym to command-line interface)
  • click-through (a)
  • client/server
  • client side (n)
  • client-side (a)
  • cloud native (n or a)
  • co-class
  • coauthor
  • code set
  • colorcell
  • colormap
  • Command key (Macintosh)
  • command line (n)
  • command-line (a)
  • Common Object Request
  • Broker Architecture (CORBA)
  • compact disc
  • compile time (n)
  • compile-time (a)
  • CompuServe
  • Control key (Mac)
  • copyleft
  • copyright
  • coworker
  • CPU (no need to expand to central processing unit)
  • –crazy s/b avoided (alternatives: foolish, bizarre, etc.)
  • criterion (s), criteria (p)
  • cross-reference
  • C shell
  • <CR><LF>
  • Ctrl key (Windows)
  • Ctrl-Alt-Delete
  • Ctrl-N
  • curly braces or braces
  • cybersecurity

back to top

D

  • database
  • data block
  • datacenter or data center (be consistent)
  • Data Encryption Standard (DES)
  • datafile
  • datatype or data type (be consistent)
  • data is
  • dataset or data set (be consistent)
  • DB-9
  • Debian GNU/Linux
  • decision making (n)
  • decision-making (a)
  • deep learning (n and a, no hyphen)
  • de-identification (hyphenate)
  • DevOps
  • dial-up (a)
  • dial up (v)
  • disk
  • disk-imaging software
  • Delete key
  • design time (n)
  • design-time (a)
  • DNS
  • DocBook
  • Document Object Model (DOM)
  • Domain Name System
  • dot
  • dot-com
  • double-click
  • double-precision (a)
  • double quotes
  • down arrow
  • downlevel (a)
  • download
  • drag-and-drop (n)
  • drag and drop (v)
  • drop-down (a)
  • –dummy s/b avoided (alternatives include: placeholder)

back to top

E

  • ebook* ebusiness* ecommerce
  • eBay
  • Emacs
  • email
  • empty-element tag
  • end-of-file (EOF)
  • end-tag
  • end user (n); end-user (a)
  • Engines of Groth
  • Enter key
  • equals sign
  • ereader
  • Escape key (or Esc key)
  • et al.
  • Ethernet
  • exclamation mark
  • Exim

back to top

F

  • failback
  • failover
  • fax
  • file manager
  • filename
  • filepath
  • file server
  • filesystem
  • file type
  • FireWire
  • foreground
  • FORTRAN
  • Fortran 90
  • forward (adv)
  • frame type
  • FreeBSD
  • Free Documentation License (FDL)
  • Free Software Foundation (FSF)
  • frontend
  • _ftp_ (Unix command)
  • FTP (protocol)
  • FTP site
  • full stack (Full Stack in headings), no hyphen, even if adjective

back to top

G

  • gateway
  • Gb (gigabit)
  • GB (gigabyte)
  • GBps (gigabytes per second)
  • GHz
  • gid
  • GIMP
  • GNOME
  • GNU Emacs
  • GNU Public License (GPL)
  • GNUstep
  • Google PageRank
  • grayscale
  • greater-than sign or >
  • greenlight (v)
  • GUI, GUIs

back to top

H

  • handcode
  • handoff (n)
  • hardcoded
  • hardcore
  • hardcode (v)
  • hardcopy
  • hard link
  • hardware-in-the-loop
  • hash sign or sharp sign
  • high-level (a)
  • home page
  • hostname
  • hotspot
  • HTML
  • HTTP
  • hypertext

back to top

I

  • IDs
  • IDE
  • IndexedDB
  • infrastructure as a service (IaaS)
  • inline
  • inode
  • interclient
  • internet, the internet
  • internetwork
  • intranet
  • Intrinsics
  • I/O
  • IP (Internet Protocol)
  • IPsec
  • ISO
  • ISP

back to top

J

  • Jabber
  • Jabber client
  • Jabber server
  • Jabber applet
  • JAR archive
  • JAR file
  • JavaScript
  • JPEG

back to top

K

  • K Desktop Environment (KDE)
  • Kb (kilobit)
  • KB (kilobyte) (denotes file size or disk space)
  • Kbps (kilobits per second)
  • Kerberos
  • keepalive (n or a)
  • keyclick
  • keycode
  • keymaps
  • keypad
  • keystroke
  • keysym
  • keywords
  • key performance indicators (KPIs)
  • kHz (kilohertz)
  • –kill s/b avoided (alternatives: end, exit, cancel)
  • Korn shell

back to top

L

  • lambda (lc unless referring to a product name)
  • Lean (capitalize noun or adjective when referring to Lean business methodology)
  • local area network or LAN
  • left angle bracket or <
  • lefthand (a)
  • leftmost
  • less-than sign or <
  • leveled (not levelled)
  • life cycle
  • line-feed (a)
  • line feed (n)
  • Linux
  • LinuxPPC
  • listbox
  • logfile
  • login, logout, or logon (n or a)
  • log in, log out, or log on (v)
  • lower- and uppercase
  • lowercase
  • lower-level (a)
  • lower-right (a)
  • Linux Professional Institute (LPI)

back to top

M

  • Macintosh
  • macOS (replaces Mac OS X)
  • machine learning (n and a, no hyphen)
  • mail-handling (adjective)
  • – man hours s/b avoided (alternatives: work hours, employee hours)
  • manpage
  • markup
  • –master/slave (n, a) s/b avoided (alternatives: parent/child, leader/follower, primary/secondary)
  • Mb (megabit)
  • MB (megabyte)
  • MBps (megabytes per second)
  • McGraw-Hill
  • menu bar
  • metacharacter
  • Meta key
  • Meta-N
  • MHz (megahertz)
  • mice or mouses (be consistent)
  • microservices
  • Microsoft Windows
  • Microsoft Windows Me
  • Microsoft Windows NT
  • Microsoft Windows XP
  • Microsoft Windows 2000
  • –middleman s/b avoided (alternatives: go-between, link, etc.)
  • MIDlet
  • MKS Toolkit
  • model-in-the-loop
  • MS-DOS
  • multiline (Unless before a proper noun, always close up the following prefixes: “non,” “sub,” “multi,” and “pseudo.”)
  • Multi-Touch (when referring to Apple's trademark)
  • My Services
  • MySpace

back to top

N

  • nameserver
  • name service
  • namespace
  • the Net
  • .NET
  • NetBIOS
  • NetBSD
  • NetInfo
  • newline
  • newsgroups
  • NeXTSTEP
  • NGINX (company), nginx (server)
  • NOOP
  • nonlocal
  • NoSQL
  • Novell NetWare
  • the New York Times

back to top

O

  • Objective-C
  • object linking and embedding (OLE)
  • object-oriented programming (OOP)
  • object request broker (ORB)
  • OK
  • offline
  • offload
  • onboard
  • ongoing
  • online
  • open source (n or a, rewrite to avoid using in a verb form)
  • open source software (OSS)
  • OpenBSD
  • OpenMotif
  • OpenStep
  • OpenWindows
  • Option key (Macintosh)
  • Oracle7
  • Oracle8
  • Oracle 8.0
  • Oracle 8i (italic “i”)
  • Oracle 9i (italic “i”)
  • Oracle Parallel Query Option
  • O’Reilly Media, Inc.
  • OS/2
  • OSA
  • OSF/Motif
  • OS X

back to top

P

  • packet switch networks
  • Paint Shop Pro
  • pagefile
  • page rank (but Google PageRank™)
  • parentheses (p)
  • parenthesis (s)
  • Pascal
  • password
  • pathname
  • pattern-matching (a)
  • peer-to-peer (or P2P)
  • % (not percent)
  • performant (Oracle)
  • period
  • Perl
  • Perl DBI
  • plain text (n)
  • plain-text (a)
  • platform as a service (PaaS)
  • Plug and Play (PnP)
  • plug in (v)
  • plug-in (a, n)
  • p.m. or P.M.
  • Point-to-Point Protocol (PPP)
  • pop up (v)
  • pop-up (n, a)
  • POP-3
  • Portable Document Format (PDF)
  • Portable Network Graphics (PNG)
  • Portable Operating
    • System Interface (POSIX)
  • POSIX-compliant
  • Post Office Protocol (POP)
  • postprocess
  • PostScript
  • Prentice Hall
  • process ID
  • progress bar
  • pseudoattribute
  • pseudo-tty
  • public key (n)
  • public-key (a)
  • pull-down (a)

back to top

Q

  • qmail
  • Qt
  • QuarkXPress
  • Quartz
  • Quartz Extreme
  • QuickTime
  • quotation marks (spell out first time; it can be “quotes” thereafter)

back to top

R

  • random-access (a)
  • RCS
  • read-only (a)
  • read/write
  • real time (n)
  • real-time (a)
  • re-create
  • Red Hat Linux
  • Red Hat Package Manager (RPM)
  • redirection
  • reference page or manpage
  • re-identification (hyphenate)
  • remote-access server
  • rename
  • Rendezvous (Mac OS X Zeroconf networking)
  • Return (key)
  • RFC 822
  • rich text (n)
  • rich-text (a)
  • right angle bracket or greater-than sign (>)
  • right-click
  • righthand (a)
  • rmail
  • rollback (n); roll back (v)
  • rollout (n); roll out (v)
  • rootkit
  • Rubout key
  • rulebase
  • ruleset
  • runtime (n, a)

back to top

S

  • Samba
  • saveset
  • screen dump
  • screenful
  • screensaver
  • screenshot
  • scroll bar
  • securelevel (in Linux)
  • Secure Shell (SSH)
  • Secure Sockets Layer (SSL)
  • sed scripts
  • semicolon
  • server-dependent
  • server side (n)
  • server-side (a)
  • service worker
  • servlet
  • set up (v)
  • setup (n)
  • SGML
  • sharp sign or hash sign
  • shell (lowercase even in shell name: Bourne shell)
  • shell scripts
  • Shift key
  • shortcut
  • Simple API for XML (SAX)
  • single-precision (a)
  • single quote
  • site map
  • –slave/master (n, a) s/b avoided (alternatives: child/parent, follower/leader, secondary/primary)
  • slideshow
  • Smalltalk
  • SMP (a, n)
  • SOAP
  • Social Security number (SSN)
  • software as a service (SaaS)
  • software-in-the-loop
  • source code
  • space bar
  • spam (not SPAM)
  • spellcheck
  • spellchecker
  • split screen
  • square brackets or brackets
  • standalone
  • standard input (stdin)
  • standard output (stdout)
  • start tag
  • startup file
  • stateful
  • stateless
  • status bar
  • stylesheet
  • subprocess (Unless before a proper noun, always close up the following prefixes: “non,” “sub,” “multi,” and “pseudo.”)
  • SUSE Linux
  • swapfile
  • swapspace
  • sync
  • system administrator
  • system-wide

back to top

T

  • 10-baseT
  • T1
  • t-shirt
  • Tab key
  • TAR file
  • TCP/IP
  • Telnet (the protocol)
  • telnet (v)
  • terabyte
  • TEX
  • texinfo
  • text box
  • text-input mode
  • thread pooling (n)
  • time-sharing processes
  • timestamp
  • time zone
  • title bar
  • Token Ring
  • toolbar
  • toolchain
  • toolkit
  • tool tip
  • top-level (a)
  • toward
  • trade-off
  • – tribe s/b avoided (alternatives: company, institution, network, community)
  • troubleshoot
  • tweet, retweet, live-tweet v, n (avoid “tweet out”)
  • Twitter user (preferred to "tweeter")
  • Twitterstorm, tweetstorm

back to top

U

  • UI (no need to expand to user interface)
  • UK (for United Kingdom)
  • Ultrix
  • Universal Serial Bus (USB)
  • Unix (UNIX in many books, esp. older ones)
  • up arrow
  • upper- and lowercase
  • uppercase
  • upper-left corner
  • UPSs
  • up-to-date
  • URLs
  • US (for United States)
  • Usenet
  • user ID (n)
  • user-ID (a)
  • username
  • UX (no need to expand to user experience)

back to top

V

  • v2 or version 2
  • VAX/VMS
  • VB.NET
  • versus (avoid vs.)
  • vice versa
  • VoiceXML
  • Visual Basic .NET
  • Visual Basic 6 or VB 6
  • Visual C++ .NET
  • Visual Studio .NET
  • VS.NET
  • Volume One

back to top

W

  • the Wall Street Journal
  • the web (n)
  • web (a)
  • web client
  • webmaster
  • web page
  • web server
  • web services (unless preceded by a proper noun, as in Microsoft Web Services)
  • website
  • –white hat/black hat s/b avoided (alternatives: ethical/unethical, preventative/malicious)
  • white pages
  • –whitelist/blacklist s/b avoided (alternatives: allowlist/blocklist, permit/deny, permissible/forbidden)
  • whitepaper (I printed my whitepaper on white paper.)
  • whitespace
  • wide area network or WAN
  • WiFi
  • wiki
  • wildcard
  • Windows 95
  • Windows 98
  • Windows 2000
  • Windows NT
  • Windows Vista
  • Windows XP
  • Wizard (proper noun)
  • wizard (a, n)
  • workaround
  • workbench
  • workgroup
  • workstation
  • World Wide Web (WWW)
  • wraparound
  • writable
  • write-only (a)
  • WYSIWYG

back to top

X

  • (x,y) (no space)
  • x-axis
  • Xbox
  • X client
  • x coordinate
  • X protocol
  • X server
  • X Toolkit
  • XView
  • X Window series
  • X Window System
  • x86
  • xFree86
  • XHTML
  • XLink
  • XML
  • XML Query Language (XQuery)
  • XML-RPC
  • XPath
  • XPointer
  • XSL
  • XSLT

back to top

Y

  • Yahoo!
  • y-axis
  • y coordinate

back to top

Z

  • Zeroconf (short for “Zero Configuration”)
  • zeros
  • zip code
  • zip (v)
  • ZIP file

back to top