Clean up a bunch of typos.

daobrien · daobrien · commit 03de8a131ca8 · 2020-05-08T12:46:15.000+10:00
diff --git a/en-US/B.xml b/en-US/B.xml
@@ -146,7 +146,7 @@
 			<term>bimodal IT</term>
 			 <listitem>
 				<para>
-					Gartner phrase for the combination of traditional (mode 1 or type 1) and modern (mode 2 or type 2) IT infrastructure and resources.There are many ways to talk about this combination approach; be sure you use the right phrase for your audience. Using only the Gartner term can alienate other analysts or those not familar with Gartner's phrasing.
+					Gartner phrase for the combination of traditional (mode 1 or type 1) and modern (mode 2 or type 2) IT infrastructure and resources. There are many ways to talk about this combination approach; be sure you use the right phrase for your audience. Using only the Gartner term can alienate other analysts or those not familiar with Gartner's phrasing.
 				</para>
 				 <para>
 					The practice of having both modes together is often referred to as hybrid, agile, or modern IT.
diff --git a/en-US/Design.xml b/en-US/Design.xml
@@ -10,7 +10,7 @@
 		<title>Heading Styles</title>
     <para>
       This section covers various aspects of heading styles and design.
-      If your company or organisation has specific requirements in this regard, follow those requirements first.
+      If your company or organization has specific requirements in this regard, follow those requirements first.
     </para>
 		 <formalpara id="capitalization">
 				<title>Capitalization</title>
diff --git a/en-US/E.xml b/en-US/E.xml
@@ -133,7 +133,7 @@
 			<term>Exec-Shield</term>
 			 <listitem>
 				<para>
-					Exec-Shield is a security-enhancing modification to the Linux kernel that makes large parts of specially-marked programs including their stack not executable.
+					Exec-Shield is a security-enhancing modification to the Linux kernel that makes large parts of specially marked programs including their stack not executable.
 				</para>
 
 			</listitem>
diff --git a/en-US/Grammar.xml b/en-US/Grammar.xml
@@ -282,7 +282,7 @@
 			</listitem>
 			 <listitem>
 				<para>
-					Use semicolons to form a compound sentence. Think of a semi-colon as an extended breather; longer than a comma.
+					Use semicolons to form a compound sentence. Think of a semicolon as an extended breather; longer than a comma.
 				</para>
 
 			</listitem>
diff --git a/en-US/H.xml b/en-US/H.xml
@@ -13,7 +13,7 @@
 					<emphasis>v.</emphasis> Two words.
 				</para>
 				 <para>
-					<emphasis>adj.</emphasis> Hypenate.
+					<emphasis>adj.</emphasis> Hyphenate.
 				</para>
 				 <para>
 					Do not use the one-word form. No nominal form is currently recognized.
@@ -67,7 +67,7 @@
 			<term>help desk</term>
 			 <listitem>
 				<para>
-					Typically two words, but use the term accepted by your organisation.
+					Typically two words, but use the term accepted by your organization.
 				</para>
 
 			</listitem>
diff --git a/en-US/I.xml b/en-US/I.xml
@@ -60,7 +60,7 @@
 			<term>InfiniBand</term>
 			 <listitem>
 				<para>
-					InfiniBand is a switched fabric network topology used in high-performance computing. The term is both a service mark and a trademark of the InfiniBand Trade Association. Their rules for using the mark are standard ones: append the ™ symbol the first time it is used and respect the capitalization (including the inter-capped "B") from then on. In ASCIonly circumstances, the "(TM)" string is the acceptable alternative.
+					InfiniBand is a switched fabric network topology used in high-performance computing. The term is both a service mark and a trademark of the InfiniBand Trade Association. Their rules for using the mark are standard ones: append the ™ symbol the first time it is used and respect the capitalization (including the inter-capped "B") from then on. In ASCII-only circumstances, the "(TM)" string is the acceptable alternative.
 				</para>
 				 <para>
 					"Open InfiniBand" is deprecated and should not be used.
diff --git a/en-US/P.xml b/en-US/P.xml
@@ -92,7 +92,7 @@
 			<term>pluggable</term>
 			 <listitem>
 				<para>
-					<emphasis>adj.</emphasis> Something that is capable of being plugged in, especially in terms of (for example) software modules. "hot-pluggable" is also widely used with respect to hardware to indicate that it can be connected and recognized without powering down the system.
+					<emphasis>adj.</emphasis> Something that is capable of being plugged in, especially in terms of (for example) software modules. "Hot-pluggable" is also widely used with respect to hardware to indicate that it can be connected and recognized without powering down the system.
 				</para>
 
 			</listitem>
diff --git a/en-US/Punctuation.xml b/en-US/Punctuation.xml
@@ -432,7 +432,7 @@
 			Do not put quotation marks around cliches or slang terms (in fact, avoid using cliches and slang as it makes the translation of content more difficult).
 		</para>
 		 <para>
-			A word or words being introduced to readers should not be placed in quotation marks. In DocBook, use the &lt;firstterm&gt; element for first reference. If you are writing outside of the SGML tagging enviroment, use quotation marks for first references. Subsequent references do not need quotation marks or the &lt;firstterm&gt; element.
+			A word or words being introduced to readers should not be placed in quotation marks. In DocBook, use the &lt;firstterm&gt; element for first reference. If you are writing outside of the SGML tagging environment, use quotation marks for first references. Subsequent references do not need quotation marks or the &lt;firstterm&gt; element.
 		</para>
 
 	</section>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
@@ -18,7 +18,7 @@
 				 <revdescription>
 					<simplelist>
 						<member>Fix issue "use 'singular to plural' pronouns -- typo? #6 .</member>
-						 <member>Repair some xml in the grammar section.</member>
+						 <member>Repair some XML in the grammar section.</member>
 						 <member>Minor repairs to language.</member>
 
 					</simplelist>
@@ -86,8 +86,8 @@
 				</author>
 				 <revdescription>
 					<simplelist>
-						<member>General clean-up of "U" section. BZ 1037923: Added entry for "uninterruptible".</member>
-						 <member>General clean-up of "T" section. BZ 1038090: Added entry for "tier-1".</member>
+						<member>General cleanup of "U" section. BZ 1037923: Added entry for "uninterruptible".</member>
+						 <member>General cleanup of "T" section. BZ 1038090: Added entry for "tier-1".</member>
 						 <member>General tidy-up. Fix some typos. Updates cross-references. Started on BZ 820071.</member>
 
 					</simplelist>
@@ -164,7 +164,7 @@
 						 <member>BZ 915987 Add entry for "bare metal".</member>
 						 <member>Add exception for Brand and Marketing heading styles.</member>
 						 <member>BZ 1017549 Added entry for how to use URLs and footnotes.</member>
-						 <member>BZ 1019258 Fixed Gunning Fog typo Chpt 1 under "Readability".</member>
+						 <member>BZ 1019258 Fixed Gunning Fog typo Ch 1 under "Readability".</member>
 						 <member>BZ 989838 Updated entry for x86 usage.</member>
 						 <member>BZ 1010163 Added entry for "Q and A".</member>
 						 <member>BZ 821606 Updated entry for qeth based on new information.</member>
@@ -331,7 +331,7 @@
 						 <member>BZ 821615 Correct use of JVM</member>
 						 <member>BZ 836869 Update SSH entry to allow for lowercase version</member>
 						 <member>BZ 829173 Add correct usage of "time to live" to Usage Dictionary</member>
-						 <member>BZ 821616 capitalization when referring to btrfs</member>
+						 <member>BZ 821616 capitalization when referring to Btrfs</member>
 						 <member>BZ 821612 Usage Dictionary addition: "zip"</member>
 						 <member>BZ 824209 word usage: segfault</member>
 						 <member>BZ 821599 Documenting exceptions</member>
@@ -393,7 +393,7 @@
 						 <member>Updates to and integration of Chapters X, Y, and Z.</member>
 						 <member>Updated section on "Avoiding Slang."</member>
 						 <member>Removed some redundant entries.</member>
-						 <member>Various clean-ups based on IBM Style Guide.</member>
+						 <member>Various cleanups based on IBM Style Guide.</member>
 						 <member>New entries from Word Nerds discussions.</member>
 
 					</simplelist>
@@ -488,7 +488,7 @@
 				</author>
 				 <revdescription>
 					<simplelist>
-						<member>Docbook conversion from original guide on the Intranet.</member>
+						<member>DocBook conversion from original guide on the Intranet.</member>
 
 					</simplelist>
 
diff --git a/en-US/S.xml b/en-US/S.xml
@@ -368,7 +368,7 @@
       <term>SLA</term>
       <listitem>
         <para>
-          <emphasis>n.</emphasis> SLA stands for service-level agreement.
+          <emphasis>n.</emphasis> SLA stands for Service Level agreement.
           The phrase itself is not normally capitalized but official SLA defect ratings, such as Low, Moderate, and Critical, carry initial caps.
           This distinguishes the SLA-defined ratings from the severity of general issues and identifies them as requiring a predetermined response time and level of support according to agreements.
         </para>
@@ -469,7 +469,7 @@ a programming and technical sense this also means "Run the <command>source</comm
 			<term>specific</term>
 			 <listitem>
 				<para>
-					When used as a modifier, put a hyphen before "specific," such as "MIPspecific," "Linux-specific," and "chip-specific."
+					When used as a modifier, put a hyphen before "specific," such as "MIP-specific," "Linux-specific," and "chip-specific."
 				</para>
 
 			</listitem>
@@ -498,7 +498,7 @@ a programming and technical sense this also means "Run the <command>source</comm
 					When referring to Microsoft's proprietary product, SQL Server, pronounce it as a word: "sequel." In this case, it takes "a" as an indefinite article.
 				</para>
 				 <para>
-					NB: Oracle also pronounces its SQbased products (such as PL/SQL) as "sequel."
+					NB: Oracle also pronounces its SQL-based products (such as PL/SQL) as "sequel."
 				</para>
 				 <para>
 					More generally, avoid using "SQL" as a generic marker if at all possible. When discussing MySQL, write "MySQL." When discussing Microsoft SQL Server, write "Microsoft SQL Server." When discussing PostgreSQL (which is pronounced pŏstgrĕs kyü ĕl), write "PostgreSQL."
diff --git a/en-US/U.xml b/en-US/U.xml
@@ -62,7 +62,7 @@
 					UNIX is a registered trademark of The Open Group.
 				</para>
 				 <para>
-					Do not use "UNIlike." Use an expression such as "Linux, UNIX, and similar operating systems" instead.
+					Do not use "UNIX-like." Use an expression such as "Linux, UNIX, and similar operating systems" instead.
 				</para>
 
 			</listitem>
diff --git a/en-US/V.xml b/en-US/V.xml
@@ -45,7 +45,7 @@
           Only use "vim" (all lowercase) when referring to the command to start the application.
 				</para>
 				 <para>
-					Vim is an acronym, derived from Vi IMproved. (In the original 1991 release for the Amiga platform, the acronym was derived from Vi IMitation. It became Vi IMproved when ported to various UNIbased operating systems in 1992.) Despite being an acronym, and despite the first word of the "About" text that appears when you start the editor, the standard, proper noun-derived, mixed-case spelling has been in use since its release on the Amiga.
+					Vim is an acronym, derived from Vi IMproved. (In the original 1991 release for the Amiga platform, the acronym was derived from Vi IMitation. It became Vi IMproved when ported to various UNIX-based operating systems in 1992.) Despite being an acronym, and despite the first word of the "About" text that appears when you start the editor, the standard, proper noun-derived, mixed-case spelling has been in use since its release on the Amiga.
 				</para>
 
 			</listitem>
