Updated term entries (#497)

Author: julian-cable

en-US/A.xml

@@ -256,7 +256,7 @@
 					</listitem>
 					 <listitem>
 						<para>
-							MaaS (Messaging-as-a-Service)
+							MaaS (Messaging-as-a-Service, Metal-as-a-Service)
 						</para>
 
 					</listitem>
@@ -295,7 +295,7 @@
 						<para>
 							Hyphenate when written out: Thing-as-a-Service.
               For two-word prefixes, do not include a hyphen between the first and second words, for example: Mobile Backend-as-a-Service.
-              It can be used as an adjective to describe multiple: for example, when referring to IaaS, PaaS, and SaaS, use as-a-Service offerings, as-a-Service products, or similar wording.
+              It can be used as an adjective to describe multiple: for example, when referring to IaaS, MaaS, PaaS, and SaaS, use as-a-Service offerings, as-a-Service products, or similar wording.
 						</para>
 
 					</listitem>

en-US/Design.xml

@@ -590,7 +590,7 @@ $ vi myFile.txt
           </listitem>
           <listitem>
             <para>
-              As much as possible, leave the system-wide default as <varname>become: false</varname> or <varname>become: no</varname> and if a single task needs privileges, set <varname>become: true</varname> or <varname>become: yes</varname> on that task.
+              As much as possible, leave the systemwide default as <varname>become: false</varname> or <varname>become: no</varname> and if a single task needs privileges, set <varname>become: true</varname> or <varname>become: yes</varname> on that task.
             </para>
           </listitem>
           <listitem>

en-US/Grammar.xml

@@ -865,7 +865,7 @@ Split contractions and abbreviations into separate paragraphs. -->
 		 <formalpara id="hyphenate-complex-adjectives">
 			<title>Hyphenate Complex Adjectives</title>
 			 <para>
-				Hyphenate complex adjectives (compound modifiers). This is when two adjectives work together to modify an object. The hyphen is used when the first adjective modifies the second adjective. For example, cloud-based solutions, right-side paralysis, system-wide menu.
+				Hyphenate complex adjectives (compound modifiers). This is when two adjectives work together to modify an object. The hyphen is used when the first adjective modifies the second adjective. For example, cloud-based solutions, right-side paralysis, systemwide menu.
 			</para>
 
 		</formalpara>

en-US/K.xml

@@ -103,7 +103,7 @@
 			<term>key ring</term>
 			 <listitem>
 				<para>
-					<emphasis>n.</emphasis> Use the two-word form as a noun. For example, "add your new key to the key ring".
+					<emphasis>n.</emphasis> Use the two-word form as a noun. For example, "Verify that the Ceph client key ring is present in the <filename>/etc/ceph</filename> directory on the client node", or "add your new key to the key ring".
 				</para>
 				 <para>
 					<emphasis>adj.</emphasis> Use the hyphenated form as an adjective. For example, "copy the key-ring file to the server".

en-US/O.xml

@@ -279,6 +279,17 @@
 			</listitem>
 
 		</varlistentry>
+		 <varlistentry id="OTP">
+			<term>OTP</term>
+			 <listitem>
+				<para>
+					<emphasis>n.</emphasis> OTP stands for "one-time password".
+          			Always use lowercase for the phrase itself. Do not use any other variations.
+				</para>
+
+			</listitem>
+
+		</varlistentry>		
 		 <varlistentry id="output-device">
 			<term>output device</term>
 			 <listitem>

en-US/S.xml

@@ -419,7 +419,7 @@
 			<term>smart card</term>
 			 <listitem>
 				<para>
-					<emphasis>n.</emphasis> Do not use smartcard or smart-card.
+					<emphasis>adj., n.</emphasis> Always use the two-word form. Do not use "smart-card" or other variations. Do not capitalize unless it is part of a product name or other proper noun.
 				</para>
 
 			</listitem>
@@ -547,6 +547,16 @@ a programming and technical sense, it also means "Run the <command>source</comma
 			</listitem>
 
 		</varlistentry>
+		 <varlistentry id="squad">
+			<term>squad (n.)</term>
+			 <listitem>
+				<para>
+					Do not use to refer to a group that is formed to accomplish a task. Use "team" or "group" instead.
+				</para>
+
+			</listitem>
+
+		</varlistentry>			
 		 <varlistentry id="sr-iov">
 			<term>SR-IOV</term>
 			 <listitem>

en-US/T.xml

@@ -210,6 +210,16 @@
 			</listitem>
 
 		</varlistentry>
+		 <varlistentry id="tribe">
+			<term>tribe (n.)</term>
+			 <listitem>
+				<para>
+					Do not use to refer to a group that is formed to accomplish a task. Use "team" or "group" instead.
+				</para>
+
+			</listitem>
+
+		</varlistentry>		
 		 <varlistentry id="troubleshoot_v.">
 			<term>troubleshoot (v.)</term>
 			 <listitem>