[documentation-guide] Finish marking up the Word usage section of the Style Guide
Jared Smith
jsmith at fedoraproject.org
Sat Mar 22 16:54:29 UTC 2014
commit b79d26168b212120bbd778aa481612bd4d1d97ed
Author: Jared K. Smith <jaredsmith at jaredsmith.net>
Date: Sat Mar 22 12:53:36 2014 -0400
Finish marking up the Word usage section of the Style Guide
en-US/style.xml | 3129 +++++++++++++++++++++++++++++++++++++++++++------------
1 files changed, 2451 insertions(+), 678 deletions(-)
---
diff --git a/en-US/style.xml b/en-US/style.xml
index 81dae30..412665c 100644
--- a/en-US/style.xml
+++ b/en-US/style.xml
@@ -281,728 +281,2502 @@
</section>
<section id="sect-documentation_guide-style-word_usage">
<title>Word usage, capitalization, and spelling</title>
- <para/>
-<!--
-'''%'''
+ <variablelist>
+<varlistentry>
+ <term>%</term>
+ <listitem>
+ <para>
See percent.
-
-
-'''24x7'''
-See also ''time''.
-
-
-'''3-D''' (n. or adj.)
-
-
-'''a.m.'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>24x7</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>3-D (n. or adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-am">
+ <term>a.m.</term>
+ <listitem>
+ <para>
Lowercase with periods and a preceding space.
-
-
-'''above'''
-Do not use to refer to information mentioned previously. When documents are converted to another format or layout, the information may no longer be “above.”
-
-'''acronyms'''
-Spell out acronyms or initialization before using them in text, e.g., “Embedded DevKit (EDK).” Unless the acronym or initials stand for a proper noun, use sentence case for the spelled-out version, e.g., “central processing unit (CPU).”
-
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>above</term>
+ <listitem>
+ <para>
+Do not use to refer to information mentioned previously. When documents are converted to another format or layout, the information may no longer be <emphasis>above.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>acronyms</term>
+ <listitem>
+ <para>
+Spell out acronyms or initialization before using them in text, e.g., <emphasis>Embedded DevKit (EDK).</emphasis> Unless the acronym or initials stand for a proper noun, use sentence case for the spelled-out version, e.g., <emphasis>central processing unit (CPU).</emphasis>
+ </para>
+ <para>
To form the plural of an acronym, add a trailing, lowercase s with no apostrophe, e.g., ROMs, PINs.
-
-'''affect'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-affect">
+ <term>affect</term>
+ <listitem>
+ <para>
When you affect something, it produces an effect.
-
-'''alpha release'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>alpha release</term>
+ <listitem>
+ <para>
Do not capitalize this, as in "the alpha release of Product Foo."
-
-'''alternate'''
-Do not use this to mean “an alternative to something.” “Alternate” is a verb that means to change between two states or options. As an adjective, it means every second (alternating) thing in a series. If you mean “another way or option,” use “alternative.”
-
-'''and/or'''
-Avoid if possible. One or the other nearly always conveys the real meaning. If it doesn’t, try a structure like, “Have some bacon, eggs, or both.”
-
-'''applications'''
-When used as a proper name, use the capitalization of the product or project, such as GNUPro, Source-Navigator, and Red Hat Enterprise Linux. When used as a command, use lowercase as appropriate, such as “To start GCC, type gcc.”
-
-''Note: “vi” is always lowercase.''
-
-'''assure'''
-Assure suggests mental comfort. Example: “I assured my future father-in-law that I would eventually find a job.” Also see ensure and insure.
-
-'''auto-detect'''
-
-'''Autofs'''
-
-'''backport'''
-
-'''back end''' (n.); '''back-end''' (adj.)
-
-'''back up''' (v.); '''backup''' (n.); '''back-up''' (adj.)
-
-'''backtrace'''
-
-'''backward'''
-Avoid using “backwards” unless you are stating that something has “backwards compatibility.”
-
-'''backwards compatibility'''
-
-'''bandwidth'''
-
-'''basically'''
-Do not use. For example, removing the word “basically” in the following sentence strengthens it: “This is how it is basically done.”
-
-'''because'''
-Do not use “since” to mean “because.” Use “because” to refer to a reason. Use “since” to refer to the passage of time.
-
-'''below'''
-Do not use to refer to information mentioned “below.” When documents are converted to another format or layout, the information may no longer be “below.”
-
-'''BIOS'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>alternate</term>
+ <listitem>
+ <para>
+Do not use this to mean <emphasis>an alternative to something.</emphasis> <emphasis>Alternate</emphasis> is a verb that means to change between two states or options. As an adjective, it means every second (alternating) thing in a series. If you mean <emphasis>another way or option,</emphasis> use <emphasis>alternative.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>and/or</term>
+ <listitem>
+ <para>
+Avoid if possible. One or the other nearly always conveys the real meaning. If it doesn’t, try a structure like, <emphasis>Have some bacon, eggs, or both.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>applications</term>
+ <listitem>
+ <para>
+When used as a proper name, use the capitalization of the product or project, such as GNUPro, Source-Navigator, and Red Hat Enterprise Linux. When used as a command, use lowercase as appropriate, such as <emphasis>To start GCC, type gcc.</emphasis>
+ </para>
+ <para>
+Note: <emphasis>vi</emphasis> is always lowercase.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-assure">
+ <term>assure</term>
+ <listitem>
+ <para>
+Assure suggests mental comfort. Example: <emphasis>I assured my future father-in-law that I would eventually find a job.</emphasis> Also see <link linkend="anchor-ensure">ensure</link> and <link linkend="anchor-insure">insure</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>auto-detect</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Autofs</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>backport</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>back end (n.)</term>
+ <term>back-end (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>back up (v.)</term>
+ <term>backup (n.)</term>
+ <term>back-up (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>backtrace</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>backward</term>
+ <listitem>
+ <para>
+Avoid using <emphasis>backwards</emphasis> unless you are stating that something has <emphasis>backwards compatibility.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>backwards compatibility</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-bandwidth">
+ <term>bandwidth</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-basically">
+ <term>basically</term>
+ <listitem>
+ <para>
+Do not use. For example, removing the word <emphasis>basically</emphasis> in the following sentence strengthens it: <emphasis>This is how it is basically done.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-because">
+ <term>because</term>
+ <listitem>
+ <para>
+Do not use <emphasis>since</emphasis> to mean <emphasis>because.</emphasis> Use <emphasis>because</emphasis> to refer to a reason. Use <emphasis>since</emphasis> to refer to the passage of time.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>below</term>
+ <listitem>
+ <para>
+Do not use to refer to information mentioned <emphasis>below.</emphasis> When documents are converted to another format or layout, the information may no longer be <emphasis>below.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>BIOS</term>
+ <listitem>
+ <para>
Plural: BIOSes
-
-'''big data'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>big data</term>
+ <listitem>
+ <para>
Descriptive term, not a proper noun, so not capitalized.
-
-'''bit rate'''
-
-'''Boolean'''
-
-'''boot disk'''
-
-'''boot loader'''
-
-'''Bps, bps'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>bit rate</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Boolean</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>boot disk</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>boot loader</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Bps, bps</term>
+ <listitem>
+ <para>
Bits per second is abbreviated bps. Bytes per second is abbreviated Bps. Also see bandwidth.
-
-'''Britain'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Britain</term>
+ <listitem>
+ <para>
The language is English, and the place is the United Kingdom of Great Britain and Northern Ireland, aka the UK. Using Britain/British is usually wrong and to some implies a specific subjective statement about the state of Northern Ireland.
-
-'''bug fix'''
-
-'''built-in'''
-
-'''bulleted lists'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>bug fix</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>built-in</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>bulleted lists</term>
+ <listitem>
+ <para>
Lists should always consist of more than two items. Use bullets for a list in which the order of items is unimportant. Use a numbered list only when the order is important, as in a series of steps.
-
-'''can/may'''
-Use “can” to describe actions or conditions that are possible. Use “may” only to describe situations where permission is being given.
-
-'''cannot'''
-
-'''canceled'''
-
-'''capitalization'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>can/may</term>
+ <listitem>
+ <para>
+Use <emphasis>can</emphasis> to describe actions or conditions that are possible. Use <emphasis>may</emphasis> only to describe situations where permission is being given.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>cannot</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>canceled</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>capitalization</term>
+ <listitem>
+ <para>
If it’s not the official name of a real product or service, don’t capitalize it. Not even if it seems important. Capitalize only the first letter of the first word in headlines, titles, subtitles, and other call-out text.
-
-'''cd or CD'''
-When referring to the change directory command, use cd. When referring to a compact disk, use “CD.” The plural is “CDs.”
-
-'''checkbox'''
-
-'''chipset'''
-
-'''ciphertext'''
-
-'''client side''' (n.); '''client-side''' (adj.)
-
-'''cloud'''
-Use a lowercase “c” when referring to cloud or cloud computing in a general sense.
-
-'''combo-box'''
-
-'''commas'''
-Use serial commas. A serial comma is the comma before the “and” in a series of three or more items: “Item 1, item 2, and item 3.” Because in some cases it is necessary to use a serial comma to avoid confusion, it is best to always use it for consistency. An exception to this rule is in press releases, where it is traditional and preferred not to use serial commas.
-
-'''comma-delimited''' (adj.)
-
-'''command-driven''' (adj.)
-
-'''command language, line, processor'''
-
-'''contractions'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>cd or CD</term>
+ <listitem>
+ <para>
+When referring to the change directory command, use cd. When referring to a compact disk, use <emphasis>CD.</emphasis> The plural is <emphasis>CDs.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>checkbox</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>chipset</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>ciphertext</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>client side (n.);</term>
+ <term>client-side (adj.);</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>cloud</term>
+ <listitem>
+ <para>
+Use a lowercase <emphasis>c</emphasis> when referring to cloud or cloud computing in a general sense.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>combo-box</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>commas</term>
+ <listitem>
+ <para>
+Use serial commas. A serial comma is the comma before the <emphasis>and</emphasis> in a series of three or more items: <emphasis>Item 1, item 2, and item 3.</emphasis> Because in some cases it is necessary to use a serial comma to avoid confusion, it is best to always use it for consistency. An exception to this rule is in press releases, where it is traditional and preferred not to use serial commas.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>comma-delimited (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>command-driven (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>command language, line, processor</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>contractions</term>
+ <listitem>
+ <para>
Avoid when writing policy manuals or other more formal types of manuals. Contractions may also cause problems for documents that are translated, so avoid them in global content.
-
-'''control character'''
-
-'''control key'''
-Use Ctrl instead, such as “To save the program, press Ctrl+Z.”
-
-'''control program'''
-
-'''cross-site scripting'''
-
-'''cross-platform'''
-
-'''currency'''
-Use the following format: $1,500 USD, omitting “USD” if it is clear that it is in US currency.
-
-'''daisy chain'''
-
-'''dashes'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>control character</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>control key</term>
+ <listitem>
+ <para>
+Use Ctrl instead, such as <emphasis>To save the program, press Ctrl+Z.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>control program</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>cross-site scripting</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>cross-platform</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>currency</term>
+ <listitem>
+ <para>
+Use the following format: $1,500 USD, omitting <emphasis>USD</emphasis> if it is clear that it is in US currency.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>daisy chain</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>dashes</term>
+ <listitem>
+ <para>
When possible, use em-dashes (—) with no space on either side. When full em-dashes aren’t available, use double-dashes with no spaces on either side--like this.
-
-'''datacenter'''
-
-'''data mirroring'''
-
-'''data type'''
-
-'''datasheet'''
-
-'''debug'''
-
-'''denial of service (DoS)'''
-
-'''dialog box'''
-
-'''different'''
-Use “different from” rather than “different than.”
-
-'''disc, disk'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>datacenter</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>data mirroring</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>data type</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>datasheet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>debug</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>denial of service (DoS)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>dialog box</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>different</term>
+ <listitem>
+ <para>
+Use <emphasis>different from</emphasis> rather than <emphasis>different than</emphasis>.”
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>disc, disk</term>
+ <listitem>
+ <para>
Compact disc, but diskette or hard disk.
-
-'''double-click'''
-
-'''downtime'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>double-click</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>downtime</term>
+ <listitem>
+ <para>
The period during which a server, service, or other resource is unavailable.
-
-'''download'''
-
-'''dual-boot'''
-
-'''DVD writer'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>download</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>dual-boot</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>DVD writer</term>
+ <listitem>
+ <para>
Do not use DVD burner or CD burner (use CD writer in that case).
-
-'''e-book, e-business, e-commerce, e-learning'''
-
-'''earlier'''
-''See later.''
-
-'''Emacs'''
-
-'''email'''
-
-'''effect'''
-''See affect.''
-
-'''email'''
-
-'''ensure'''
-Ensure means “to make sure.” ''Also see assure and insure.''
-
-'''essentially''
-Do not use. ''Also see basically.''
-
-'''Ethernet'''
-
-'''exclamation points (!)'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>e-book, e-business, e-commerce, e-learning</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>earlier</term>
+ <listitem>
+ <para>
+See <link linkend="anchor-later">later</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Emacs</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>email</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>effect</term>
+ <listitem>
+ <para>
+See <link linkend="anchor-affect">affect</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>email</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-ensure">
+ <term>ensure</term>
+ <listitem>
+ <para>
+Ensure means <emphasis>to make sure.</emphasis> See also <link linkend="anchor-assure">assure</link> and <link linkend="anchor-insure">insure</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>essentially</term>
+ <listitem>
+ <para>
+Do not use. See also <link linkend="anchor-basically">basically</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Ethernet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>exclamation points (!)</term>
+ <listitem>
+ <para>
Do not use them at the end of sentences. An exclamation point can be used when referring to a command, such as the bang (!) command.
-
-'''Exif'''
-
-'''ext3'''
-
-'''extranet'''
-
-'''failover''' (n.); '''fail over''' (v.)
-
-'''fault tolerance'''
-
-'''Fedora™ Project'''
-
-'''fiber'''
-Despite the alternative spelling used in Fibre Channel, “fiber” is the correct form to use in all other cases.
-
-'''Fibre Channel'''
-
-'''file name'''
-
-'''file system'''
-
-'''FireWire'''
-
-'''firmware'''
-
-'''floating point'''
-
-'''forward'''
-Avoid using “forwards.”
-
-'''front end''' (n.); '''front-end''' (adj.)
-
-'''FTP'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Exif</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>ext3</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>extranet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>failover (n.);</term>
+ <term>fail over (v.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>fault tolerance</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Fedora™ Project</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>fiber</term>
+ <listitem>
+ <para>
+Despite the alternative spelling used in Fibre Channel, <emphasis>fiber</emphasis> is the correct form to use in all other cases.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Fibre Channel</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>file name</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>file system</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>FireWire</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>firmware</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>floating point</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>forward</term>
+ <listitem>
+ <para>
+Avoid using <emphasis>forwards.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>front end (n.)</term>
+ <term>front-end (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>FTP</term>
+ <listitem>
+ <para>
Stands for file transfer protocol. You may actually need to refer to SFTP, secure file transfer protocol. Use lowercase when referring to the command-line program.
-
-'''g++''' or '''G++'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>g++</term>
+ <term>G++</term>
+ <listitem>
+ <para>
When referring to the command, use g++. When referring to the program, use G++.
-
-'''gas''' or '''GAS'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gas</term>
+ <term>GAS</term>
+ <listitem>
+ <para>
When referring to the command, use gas. When referring to the program, use GAS.
-
-'''GB'''
-
-'''Gbps'''
-
-'''gcc or GCC'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GB</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Gbps</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gcc</term>
+ <term>GCC</term>
+ <listitem>
+ <para>
When referring to the command, use gcc. When referring to the program, use GCC.
-
-'''gcj or GCJ'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gcj</term>
+ <term>GCJ</term>
+ <listitem>
+ <para>
When referring to the command, use gcj. When referring to the program, use GCJ.
-
-'''gdb or GDB'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gdb</term>
+ <term>GDB</term>
+ <listitem>
+ <para>
When referring to the command, use gdb. When referring to the program, use GDB.
-
-'''gigabyte'''
-2 to the 30th power (1,073,741,824) bytes. One gigabyte is equal to 1,024 megabytes. Abbreviated “GB.”
-
-'''GIMP (GNU Image Manipulation Program)'''
-
-'''GNOME'''
-
-'''GNU'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gigabyte</term>
+ <listitem>
+ <para>
+2 to the 30th power (1,073,741,824) bytes. One gigabyte is equal to 1,024 megabytes. Abbreviated <emphasis>GB.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GIMP (GNU Image Manipulation Program)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GNOME</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GNU</term>
+ <listitem>
+ <para>
(GNU’s Not UNIX)
-
-'''GNUPro'''
-
-'''gray'''
-
-'''GTK+'''
-
-'''hard-coded''' (adj.); '''hard code''' (v.)
-
-'''hard copy'''
-Do not use. Instead, use “printed.”
-
-'''hard disk'''
-
-'''hard drive'''
-
-'''he/she'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GNUPro</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>gray</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>GTK+</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hard-coded (adj.)</term>
+ <term>hard code (v.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hard copy</term>
+ <listitem>
+ <para>
+Do not use. Instead, use <emphasis>printed.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hard disk</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hard drive</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>he/she</term>
+ <listitem>
+ <para>
Do not use. Reword to avoid.
-
-'''high-availability''' (adj.); '''high availability''' (n.)
-
-'''high-performance computing (HPC)'''
-
-'''homepage'''
-
-'''host group'''
-
-'''hostname'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>high-availability (adj.)</term>
+ <term>high availability (n.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>high-performance computing (HPC)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>homepage</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>host group</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hostname</term>
+ <listitem>
+ <para>
Capitalize when used at the beginning of a sentence, but try to reword the sentence to avoid this.
-
-'''hot add'''
-
-'''hot plug'''
-
-'''hot swap'''
-
-'''hotline'''
-
-'''HTML'''
-
-'''Hyper-Threading'''
-
-'''hypervisor'''
-
-'''Hz'''
-''Also see bandwidth.''
-
-'''I/O'''
-
-'''i.e.''' and '''e.g.'''
-i.e. means “in other words.” e.g. means “for example.” Add commas after each (e.g.,).
-
-'''illegal'''
-Illegal means “prohibited by law,” not “incorrect” or “not permitted.” You may be looking for the word “invalid.”
-
-'''in concert with'''
-Do not use. Instead, simply say “with.”
-
-'''Infrastructure-as-a-Service (IaaS)'''
-
-'''inline'''
-
-'''insecure'''
-Do not use “nonsecure,” “non-secure,” or “unsecured.”
-
-'''installation program'''
-Do not use “installer.”
-
-'''insure'''
-“Insure” relates to monetary insurance. Also see assure and ensure.
-
-'''Intel 64'''
-Do not use “Hammer,” “x86_64,” or “x86-64” as the name of this architecture. The correct term for AMD’s implementation of this architecture is “AMD64.”
-
-'''interesting'''
-Avoid using, as this is a substitute for showing the reader why something is of interest. For example, change “It is interesting to note” to “Note.”
-
-'''Internet'''
-
-'''intranet'''
-
-'''IP (Internet Protocol)'''
-
-'''IPsec (Internet Protocol security)'''
-
-'''is designed to'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hot add</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hot plug</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hot swap</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hotline</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>HTML</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Hyper-Threading</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>hypervisor</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Hz</term>
+ <listitem>
+ <para>
+Also see <link linkend="anchor-bandwidth">bandwidth</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>I/O</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>i.e.</term>
+ <term>e.g.</term>
+ <listitem>
+ <para>
+i.e. means <emphasis>in other words.</emphasis> e.g. means <emphasis>for example.</emphasis> Add commas after each (e.g.,).
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>illegal</term>
+ <listitem>
+ <para>
+Illegal means <emphasis>prohibited by law,</emphasis> not <emphasis>incorrect</emphasis> or <emphasis>not permitted.</emphasis> You may be looking for the word <emphasis>invalid.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>in concert with</term>
+ <listitem>
+ <para>
+Do not use. Instead, simply say <emphasis>with.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Infrastructure-as-a-Service (IaaS)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>inline</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>insecure</term>
+ <listitem>
+ <para>
+Do not use <emphasis>nonsecure,</emphasis> <emphasis>non-secure,</emphasis> or <emphasis>unsecured.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>installation program</term>
+ <listitem>
+ <para>
+Do not use <emphasis>installer.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-insure">
+ <term>insure</term>
+ <listitem>
+ <para>
+<emphasis>Insure</emphasis> relates to monetary insurance. Also see assure and ensure.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Intel 64</term>
+ <listitem>
+ <para>
+Do not use <emphasis>Hammer,</emphasis> <emphasis>x86_64,</emphasis> or <emphasis>x86-64</emphasis> as the name of this architecture. The correct term for AMD’s implementation of this architecture is <emphasis>AMD64.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>interesting</term>
+ <listitem>
+ <para>
+Avoid using, as this is a substitute for showing the reader why something is of interest. For example, change <emphasis>It is interesting to note</emphasis> to <emphasis>Note.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Internet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>intranet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>IP (Internet Protocol)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>IPsec (Internet Protocol security)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>is designed to</term>
+ <listitem>
+ <para>
Avoid this and similar phrases when describing a function.
-
+ </para>
+ <para>
Incorrect: SSH is designed to work with almost any kind of public key algorithm or encoding format.
-
+ </para>
+ <para>
Correct: SSH works with almost any kind of public key algorithm or encoding format.
-
-'''just'''
-Use sparingly and avoid when possible. For example, in a phrase like, “Just point your browser to,” omit the word “just.”
-
-'''KB'''
-
-'''kbps'''
-
-'''kernel space''' (n.); '''kernel-space '''(adj.)
-
-'''kilobit, kilobyte'''
-
-'''later/newer'''
-When referring to more recent versions of a product, package, or other software, use “later.” When referring to earlier versions, use “earlier.”
-
-'''left-click'''
-
-'''life cycle'''
-
-'''Linux®'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>just</term>
+ <listitem>
+ <para>
+Use sparingly and avoid when possible. For example, in a phrase like, <emphasis>Just point your browser to,</emphasis> omit the word <emphasis>just.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>KB</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>kbps</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>kernel space (n.)</term>
+ <term>kernel-space (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>kilobit, kilobyte</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry id="anchor-later">
+ <term>later/newer</term>
+ <listitem>
+ <para>
+When referring to more recent versions of a product, package, or other software, use <emphasis>later.</emphasis> When referring to earlier versions, use <emphasis>earlier.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>left-click</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>life cycle</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Linux®</term>
+ <listitem>
+ <para>
Linux is a registered trademark of Linus Torvalds. It gets a registered trademark symbol on first use.
-
-'''lists'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>lists</term>
+ <listitem>
+ <para>
Keep the structure of bulleted lists equivalent and consistent. If one bullet is a verb phrase, they should all be verb phrases. If one is a complete sentence, they should all be complete sentences, etc.
-
+ </para>
+ <para>
Capitalize the first word of each bullet, unless it is obvious that it is just a list of items, such as a list of items like:
-computer
-monitor
-keyboard
-
+ </para>
+ <itemizedlist>
+ <listitem><para>computer</para></listitem>
+ <listitem><para>monitor</para></listitem>
+ <listitem><para>keyboard</para></listitem>
+ </itemizedlist>
+ <para>
When the bulleted list items complete a sentence or are sentences themselves, use periods on each item. If they do not, or are simply a list of items (like the list above), no periods are necessary.
-
-'''log file'''
-
-'''log in''' (v.); '''log-in''' (adj.); '''login''' (n.)
-
-'''lookup''' (n.); '''look up''' (v.); '''look-up''' (adj.)
-
-'''LVM'''
-
-'''man page'''
-
-'''mashup'''
-
-'''may/can'''
-Use “can” to describe actions or conditions that are possible. Use “may” to describe situations where permission is being given.
-
-'''MB; Mb'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>log file</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>log in (v.)</term>
+ <term>log-in (adj.)</term>
+ <term>login (n.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>lookup (n.)</term>
+ <term>look up (v.);</term>
+ <term>look-up (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>LVM</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>man page</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>mashup</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>may/can</term>
+ <listitem>
+ <para>
+Use <emphasis>can</emphasis> to describe actions or conditions that are possible. Use <emphasis>may</emphasis> to describe situations where permission is being given.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>MB</term>
+ <term>Mb</term>
+ <listitem>
+ <para>
MB is short for megabyte (1,000,000 or 1,048,576 bytes, depending on the context). Mb is short for megabit.
-
-'''MBps'''
-
-'''metadata'''
-
-'''Microsoft'''
-Do not use “MS”, “MSFT” or “MicroSoft.”
-
-'''months'''
-Abbreviate months and states according to AP. Months are abbreviated only if they are used in conjunction with a day. Example: “The President visited in January 1999.” or “The President visited Jan. 12.” Abbreviated months: Jan., Feb., March, April, May, June, July, Aug., Sept., Nov., Dec.
-
-'''Mozilla Firefox'''
-Subsequent references can be “Firefox.”
-
-'''Mozilla Thunderbird'''
-Subsequent references can be “Thunderbird.”
-
-'''multi-'''
-Hyphenate words with the prefix “multi” unless the dictionary or this guide says otherwise.
-
-'''multiprocessing'''
-
-'''MySQL'''
-
-'''nameserver'''
-
-'''namespace'''
-
-'''.NET'''
-
-'''newer'''
-
-'''non-'''
-Hyphenate words with the prefix “non” unless the dictionary says otherwise.
-
-'''nonsecure'''
-Use “insecure” instead.
-
-'''NULL''' or '''null'''
-When a command or value is stated, use NULL. When stating that something is null, use “null.”
-
-'''numbers'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>MBps</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>metadata</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Microsoft</term>
+ <listitem>
+ <para>
+Do not use <emphasis>MS</emphasis>, <emphasis>MSFT</emphasis> or <emphasis>MicroSoft.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>months</term>
+ <listitem>
+ <para>
+Abbreviate months and states according to AP. Months are abbreviated only if they are used in conjunction with a day. Example: <emphasis>The President visited in January 1999.</emphasis> or <emphasis>The President visited Jan. 12.</emphasis> Abbreviated months: Jan., Feb., March, April, May, June, July, Aug., Sept., Nov., Dec.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Mozilla Firefox</term>
+ <listitem>
+ <para>
+Subsequent references can be <emphasis>Firefox.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Mozilla Thunderbird</term>
+ <listitem>
+ <para>
+Subsequent references can be <emphasis>Thunderbird.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>multi-</term>
+ <listitem>
+ <para>
+Hyphenate words with the prefix <emphasis>multi</emphasis> unless the dictionary or this guide says otherwise.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>multiprocessing</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>MySQL</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>nameserver</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>namespace</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>.NET</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>newer</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>non-</term>
+ <listitem>
+ <para>
+Hyphenate words with the prefix <emphasis>non</emphasis> unless the dictionary says otherwise.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>nonsecure</term>
+ <listitem>
+ <para>
+Use <emphasis>insecure</emphasis> instead.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>NULL</term>
+ <term>null</term>
+ <listitem>
+ <para>
+When a command or value is stated, use NULL. When stating that something is null, use <emphasis>null.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>numbers</term>
+ <listitem>
+ <para>
Write out numbers between one and nine.
-
-Exceptions:
-*Beginning a sentence
-*Preceding another number (four 6-pound bags)
-*Approximations (“thousands of”)
-*Very large values (4 billion)
-*Ranges (4—6 datacenters)
-
-Use numerals for numbers 10 and greater, negative numbers, fractions, percentages, decimals, measurements, references to book sections (Chapter 3, Table 5, Page 11), and numbers less than 10 if they appear with numbers of 10 or greater (“You answered 8 out of 14 questions correctly”). Also use numerals when referring to code (such as x = 6) and release versions (Fedora 18).
-
-'''numbered lists'''
+ </para>
+ <para>Exceptions:</para>
+ <itemizedlist>
+ <listitem><para>Beginning a sentence</para></listitem>
+ <listitem><para>Preceding another number (four 6-pound bags)</para></listitem>
+ <listitem><para>Approximations (<emphasis>thousands of</emphasis>)</para></listitem>
+ <listitem><para>Very large values (4 billion)</para></listitem>
+ <listitem><para>Ranges (4—6 datacenters)</para></listitem>
+ </itemizedlist>
+ <para>
+Use numerals for numbers 10 and greater, negative numbers, fractions, percentages, decimals, measurements, references to book sections (Chapter 3, Table 5, Page 11), and numbers less than 10 if they appear with numbers of 10 or greater (<emphasis>You answered 8 out of 14 questions correctly</emphasis>). Also use numerals when referring to code (such as x = 6) and release versions (Fedora 20).
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>numbered lists</term>
+ <listitem>
+ <para>
Lists should always consist of more than two items. Use bullets for a list in which the order of items is unimportant. Use a numbered list only when the order is important, as in a series of steps.
-
-'''Objective C'''
-
-'''object-oriented'''
-
-'''OEM (original equipment manufacturer)'''
-
-'''offline'''
-
-'''online'''
-
-'''on-site'''
-Hyphenated when used as an adjective, as in “on-site labs.”
-
-'''on demand''' (adv.); '''on-demand''' (adj.)
-
-'''opcodes'''
-
-'''open source'''
-
-'''operating system'''
-
-'''orientate'''
->Do not use. A user becomes “oriented” to an environment.
-
-'''over'''
-When referring to something quantifiable, use “more than” instead.
-
-'''override'''
-
-'''packet-switching'''
-
-'''pc''' or '''PC'''
-When referring to program counter, use pc. The first instance must have the acronym defined, such as “program counter (pc).” When referring to a general computer, use “PC.”
-
-'''percent (%)'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Objective C</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>object-oriented</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>OEM (original equipment manufacturer)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>offline</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>online</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>on-site</term>
+ <listitem>
+ <para>
+Hyphenated when used as an adjective, as in <emphasis>on-site labs.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>on demand (adv.)</term>
+ <term>on-demand (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>opcodes</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>open source</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>operating system</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>orientate</term>
+ <listitem>
+ <para>
+Do not use. A user becomes <emphasis>oriented</emphasis> to an environment.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>over</term>
+ <listitem>
+ <para>
+When referring to something quantifiable, use <emphasis>more than</emphasis> instead.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>override</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>packet-switching</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>pc</term>
+ <term>PC</term>
+ <listitem>
+ <para>
+When referring to program counter, use pc. The first instance must have the acronym defined, such as <emphasis>program counter (pc).</emphasis> When referring to a general computer, use <emphasis>PC.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>percent (%)</term>
+ <listitem>
+ <para>
Use the percent sign (%) whenever referring to numerical percentages.
+ </para>
+ <para>
Example: In a survey, 60% of users said they were satisfied with their technology solution.
+ </para>
+ <para>
Exception: Press releases and press blogs follow strict AP style, which spells out 'percent' in all uses.
-
-'''peer-to-peer architecture'''
-
-'''Perl'''
-
-'''plain text'''
-
-'''Platform-as-a-Service (PaaS)'''
-
-'''please'''
-Do not use. Instead of “Please refer to the Getting Started Guide,” write, “Refer to the Getting Started Guide.”
-
-'''plug-in''' (n); '''plug in''' (v)
-As a noun, “plug-in” is a hardware or software module that adds a specific feature or service to a larger system.
-
-'''p.m.'''
-''See a.m.''
-
-'''pop-up'''
-
-'''PostScript'''
-
-'''PowerPC'''
-Do not use “PPC” or variants.
-
-'''PPP'''
-
-'''proximity'''
-Don’t use “close proximity.” It’s redundant.
-
-'''pseudo-ops'''
-
-'''pulldown'''
-
-'''quotations'''
-“Place the punctuation inside the quotes,” said the editor. Except in rare instances, use only “said” or “says” for quotes. Other words liked “noted” or “quipped” get in the way of the quote itself and tend to editorialize.
-
-Place “said” first, followed by the name: “Friends, freedom, features, first,” said Beefy Miracle.
-
-'''regardless'''
-“Irregardless” is not a word.
-
-'''read-only'''
-
-'''read/write'''
-
-'''real-time''' (adj.); '''real time''' (n)
-
-'''reboot'''
-
-'''recursive'''
-
-'''Red Hat'''
-Write “Red Hat.” Not “Red Hat, Inc.” (The only exceptions to this rule are when the company itself is writing legal or financial statements.) “Red” and “Hat” should be on the same line together. Don’t let them be separated by a line break.
-
-Pronoun and verb agreement: A company is singular in the US. In other words, Red Hat is an “it,” not a “they.”
-
-'''right-click'''
-
-'''roadmap'''
-
-'''RPM'''
-
-'''runlevel'''
-
-'''runtime'''
-
-'''screenshot'''
-
-'''scrollbar'''
-
-'''SELinux'''
-
-'''server side''' (n.); '''server-side''' (adj.)
-
-'''set up''' (v.); '''setup''' (n.); '''set-up''' (adj.)
-
-'''sign up''' (verb), '''sign-up''' (noun, adjective)
-
-'''shut down''' (v.)
-
-'''simply'''
-Do not use. See basically.
-
-'''since'''
-'See because.''
-
-'''smart card'''
-
-'''soft copy'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>peer-to-peer architecture</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Perl</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>plain text</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Platform-as-a-Service (PaaS)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>please</term>
+ <listitem>
+ <para>
+Do not use. Instead of <emphasis>Please refer to the Getting Started Guide,</emphasis> write, <emphasis>Refer to the Getting Started Guide.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>plug-in (n)</term>
+ <term>plug in (v)</term>
+ <listitem>
+ <para>
+As a noun, <emphasis>plug-in</emphasis> is a hardware or software module that adds a specific feature or service to a larger system.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>p.m.</term>
+ <listitem>
+ <para>
+See <link linkend="anchor-am">a.m.</link>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>pop-up</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>PostScript</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>PowerPC</term>
+ <listitem>
+ <para>
+Do not use <emphasis>PPC</emphasis> or variants.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>PPP</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>proximity</term>
+ <listitem>
+ <para>
+Don’t use <emphasis>close proximity.</emphasis> It’s redundant.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>pseudo-ops</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>pulldown</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>quotations</term>
+ <listitem>
+ <para>
+<emphasis>Place the punctuation inside the quotes,</emphasis> said the editor. Except in rare instances, use only <emphasis>said</emphasis> or <emphasis>says</emphasis> for quotes. Other words liked <emphasis>noted</emphasis> or <emphasis>quipped</emphasis> get in the way of the quote itself and tend to editorialize.
+ </para>
+ <para>
+Place <emphasis>said</emphasis> first, followed by the name: <emphasis>Friends, freedom, features, first,</emphasis> said Beefy Miracle.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>regardless</term>
+ <listitem>
+ <para>
+<emphasis>Irregardless</emphasis> is not a word.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>read-only</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>read/write</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>real-time (adj.)</term>
+ <term>real time (n)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>reboot</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>recursive</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Red Hat</term>
+ <listitem>
+ <para>
+Write <emphasis>Red Hat.</emphasis> Not <emphasis>Red Hat, Inc.</emphasis> (The only exceptions to this rule are when the company itself is writing legal or financial statements.) <emphasis>Red</emphasis> and <emphasis>Hat</emphasis> should be on the same line together. Don’t let them be separated by a line break.
+ </para>
+ <para>
+Pronoun and verb agreement: A company is singular in the US. In other words, Red Hat is an <emphasis>it,</emphasis> not a <emphasis>they.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>right-click</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>roadmap</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>RPM</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>runlevel</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>runtime</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>screenshot</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>scrollbar</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>SELinux</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>server side (n.)</term>
+ <term>server-side (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>set up (v.)</term>
+ <term>setup (n.)</term>
+ <term>set-up (adj.)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>sign up (verb)</term>
+ <term>sign-up (noun, adjective)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>shut down (v.)</term>
+ <term> </term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>simply</term>
+ <listitem>
+ <para>
+Do not use. See <link linkend="anchor-basically">basically</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>since</term>
+ <listitem>
+ <para>
+See <link linkend="anchor-because">because</link>.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>smart card</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>soft copy</term>
+ <listitem>
+ <para>
Do not use.
-
-'''Software-as-a-Service (SaaS)'''
-
-'''sound card'''
-
-'''space'''
-Use when referring to white space, such as “Ensure there is a space between each command.” Use “spacebar” when referring to the keyboard key.
-
-'''spaces''' (using)
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Software-as-a-Service (SaaS)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>sound card</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>space</term>
+ <listitem>
+ <para>
+Use when referring to white space, such as <emphasis>Ensure there is a space between each command.</emphasis> Use <emphasis>spacebar</emphasis> when referring to the keyboard key.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>spaces (using)</term>
+ <term> </term>
+ <listitem>
+ <para>
Use only one space between sentences. Use no spaces around an em-dash.
-
-'''spec file'''
-
-'''standalone'''
-
-'''startup'''
-
-'''states'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>spec file</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>standalone</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>startup</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>states</term>
+ <listitem>
+ <para>
Use the two-letter postal abbreviations. See stateabbreviations.us for a list.
-
-'''stovepipe'''
-
-'''subdirectory'''
-
-'''submenu'''
-
-'''superuser'''
-
-'''swap space'''
-
-'''SysV'''
-
-'''taskbar'''
-
-'''Telnet'''
-
-'''that/which'''
-“That” introduces a restrictive clause — a clause that must be there for the sentence to make sense. A restrictive clause often defines the noun or phrase preceding it.
-
-“Which” introduces a non-restrictive, parenthetical clause — a clause that could be omitted without affecting the meaning of the sentence. Use”who” or “whom,” rather than “that” or “which,” when referring to a person.
-
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>stovepipe</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>subdirectory</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>submenu</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>superuser</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>swap space</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>SysV</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>taskbar</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Telnet</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>that/which</term>
+ <listitem>
+ <para>
+<emphasis>That</emphasis> introduces a restrictive clause — a clause that must be there for the sentence to make sense. A restrictive clause often defines the noun or phrase preceding it.
+ </para>
+ <para>
+<emphasis>Which</emphasis> introduces a non-restrictive, parenthetical clause — a clause that could be omitted without affecting the meaning of the sentence. Use”who” or <emphasis>whom,</emphasis> rather than <emphasis>that</emphasis> or <emphasis>which,</emphasis> when referring to a person.
+ </para>
+ <para>
For example: The car was travelling at a speed that would endanger lives. The car, which was travelling at a speed that would endanger lives, swerved onto the sidewalk.
-
-'''that vs. who'''
-Use "that" when referring to places and things, including groups (e.g., customers), teams, and companies. Use "who" when referring to individual persons.
-
-'''then/than'''
-“Then” refers to a time in the past or the next step in a sequence.
-“Than” is used for comparisons.
-
-'''third-party'''
-
-'''this'''
-The word “this” can be used as an adjective or a pronoun. If you use it as a pronoun, be clear what the antecedent is. If it is unclear, use the adjective form by following “this” with a noun.
-
-'''throughput'''
-
-'''time zone'''
-
-'''timeout'''
-
-'''token-ring'''
-
-'''toolbar'''
-
-'''troubleshoot'''
-
-'''under'''
-When referring to something quantifiable, use “fewer than.”
-
-'''UNIX'''
-UNIX is a registered trademark of The Open Group. Do not use “UNIX-like.” Use an expression like “Linux, UNIX, and similar operating systems” instead.
-
-'''upgrade'''
-
-'''URLs'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>that vs. who</term>
+ <listitem>
+ <para>
+Use <emphasis>that</emphasis> when referring to places and things, including groups (e.g., customers), teams, and companies. Use <emphasis>who</emphasis> when referring to individual persons.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>then/than</term>
+ <listitem>
+ <para>
+<emphasis>Then</emphasis> refers to a time in the past or the next step in a sequence.
+ </para>
+ <para>
+<emphasis>Than</emphasis> is used for comparisons.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>third-party</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>this</term>
+ <listitem>
+ <para>
+The word <emphasis>this</emphasis> can be used as an adjective or a pronoun. If you use it as a pronoun, be clear what the antecedent is. If it is unclear, use the adjective form by following <emphasis>this</emphasis> with a noun.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>throughput</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>time zone</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>timeout</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>token-ring</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>toolbar</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>troubleshoot</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>under</term>
+ <listitem>
+ <para>
+When referring to something quantifiable, use <emphasis>fewer than.</emphasis>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>UNIX</term>
+ <listitem>
+ <para>
+UNIX is a registered trademark of The Open Group. Do not use <emphasis>UNIX-like.</emphasis> Use an expression like <emphasis>Linux, UNIX, and similar operating systems</emphasis> instead.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>upgrade</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>URLs</term>
+ <listitem>
+ <para>
For URLs that begin with http://www., you may omit that portion and give the main URL, such as fedoraproject.org. If it begins with ftp or https, you should include the full URL.
-
-'''US''' (adjective), '''United States''' (noun)
-
-'''usable'''
-
-'''userid'''
-
-'''user interface'''
-
-'''username'''
-
-'''user space'''
-
-'''utilize'''
-Avoid this term. Write “use” instead.
-
-'''vi, Vim'''
-
-'''virtualization'''
-
-'''Web 2.0'''
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>US (adjective)</term>
+ <term>United States (noun)</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>usable</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>userid</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>user interface</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>username</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>user space</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>utilize</term>
+ <listitem>
+ <para>
+Avoid this term. Write <emphasis>use</emphasis> instead.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>vi, Vim</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>virtualization</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Web 2.0</term>
+ <listitem>
+ <para>
Avoid using this term.
-
-'''web, web browser, webmaster, web server, website'''
-
-'''white space'''
-
-'''whitepaper'''
-
-'''workflow'''
-
-'''worldwide'''
-
-'''writable'''
-
-'''x86'''
-
-'''Xen'''
-
-'''X Window System'''
-
-'''ZIP code'''
--->
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>web, web browser, webmaster, web server, website</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>white space</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>whitepaper</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>workflow</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>worldwide</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>writable</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>x86</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Xen</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>X Window System</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>ZIP code</term>
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+</varlistentry>
+ </variablelist>
</section>
<section id="sect-documentation_guide-style-quick_reference">
<title>Quick Reference</title>
@@ -1229,7 +3003,6 @@ Never use the trademark symbol (™) or the registration mark (®). If fo
In addition, all documentation should contain the disclaimer: "All other trademarks are the property of their respective owners." This marking is standard in all Fedora Documentation toolchains at the time of this writing.
-->
- </section>
</section>
<section id="sect-documentation_guide-style-resources">
<title>Resources</title>
More information about the docs-commits
mailing list