Merge all updates from dev to master for 6.1 release (#523)

* Working on #450.

* Run Vale over Design.xml.

This is the end of part 1/4 of "Run Vale over the style guide." Too big a job to
try to handle in one issue and PR.

* Ongoing updates for #456

* Closes #456

Part 2 of running Vale over the style guide.
I also addressed a few other issues along the way, such as one sentence per
line and removing old comments.

Language.xml in particular contains lots of examples of what not to do, so it
produces lots of noise in Vale.

* s/may/might/ per Julian's review.

* Working on #457 Run Vale of the style guide part 3.

* Closes #457 Run Vale over the style guide, part 3.

* Remove spurious space.

* Closes #458 Run Vale over style guide part 4.

* Closes #365 Remove DocBook references.

* Closes #78 Update entry for "virtualized".

Basically copy/paste from corp guide.

* Closes #355. Improve a bit of formatting.

* feat: Add advice on naming the default branch in an inclusive way. (#493)

* feat: Add advice on naming the default branch in an inclusive way.

* Update en-US/Language.xml

Co-authored-by: julian-cable <79939933+julian-cable@users.noreply.github.com>

* Update en-US/Language.xml

Co-authored-by: julian-cable <79939933+julian-cable@users.noreply.github.com>

* Update en-US/Language.xml

Co-authored-by: julian-cable <79939933+julian-cable@users.noreply.github.com>

---------

Co-authored-by: julian-cable <79939933+julian-cable@users.noreply.github.com>

* Updated section about writing titles (#492)

* Updated section about writing titles

* Reverted title ID

* Further edits

* Updated guidance on continuation prompts (#494)

* Various fixes for 6.1 release (#495)

* Various fixes for 6.1 release

* XML fix

* Updated IBM Style access info (#496)

* Updated term entries (#497)

* Added guidance on omitting part of an output (#500)

* Added guidance on omitting part of an output

* Updated wording

* Typo fix

* Updated sample names and other small fixes (#502)

* Various fixes (#512)

* Implementing various feedback suggestions from Rachel (#513)

* Implementing various feedback suggestions from Rachel

* Addressed review comments

* Addressed further review comment

* Added more punctuation guidance (#515)

* Added more punctuation guidance

* Implemented review feedback

* Updated audience description (#518)

* Updated audience description

* Further updated audience wording

* Adding information about posessives (#519)

* feat: added section about posessives

* feat: here's the actual section

* fix: made some revisions

* Content and formatting updates

* Update en-US/Punctuation.xml

Co-authored-by: Rachel Lee <131199744+rclee33@users.noreply.github.com>

* fix: made some revisions

* fix: made another revision

* Removed company name and restructured section

* added link in section 3.6

* Final XML fix

---------

Co-authored-by: Julian Cable <jcable@redhat.com>
Co-authored-by: Rachel Lee <131199744+rclee33@users.noreply.github.com>

* Updated view and edit files section

* Added release notes for 6.1 and updated version information (#522)

* updating homepage (#525)

---------

Co-authored-by: daobrien <noreply@solaris.milky.way>
Co-authored-by: David O'Brien <daobrien@users.noreply.github.com>
Co-authored-by: mweetman-redhat <mweetman@redhat.com>
Co-authored-by: Christine Belzie <105683440+CBID2@users.noreply.github.com>
Co-authored-by: Rachel Lee <131199744+rclee33@users.noreply.github.com>
Co-authored-by: Harpal Singh <52556240+harpasin@users.noreply.github.com>

Author: 7 people

css/style.css

@@ -9,7 +9,7 @@
 }
 
 body {
-    font-family: 'overpass',sans;
+    font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
     background-color: #fff;
     margin: 0;
     padding: 0;
@@ -44,15 +44,16 @@ header img {
 }
 
 #main > div {
-    padding-top: 5%;
+    padding-top: 2%;
 }
 
 #main > img {
     padding-top: 5%;
 }
 
 #main p {
-    width: 50%;
+    text-align: left;
+    width: 70%;
     font-size: 1.33em;
     margin: auto;
 }

en-US/A.xml

@@ -5,9 +5,7 @@
 ]>
 <chapter id="a">
 	<title>A</title>
-<!-- Some of the entries were not listed in alphabetical order.	 -->
 	 <variablelist>
-<!-- Entries previously used a mixture of "v." and "vb." to denote a verb. Changed all occurrences to "v." -->
 		<varlistentry id="amp-and-">
 			<term>"&amp;" and "+"</term>
 			 <listitem>
@@ -29,7 +27,6 @@
 			</listitem>
 
 		</varlistentry>
-<!-- Removed "acronyms" entry (as it is not a literal term) and added this content instead to section 3.6. -->
 
 		 <varlistentry id="agile-development">
 			<term role="true">agile</term>
@@ -55,10 +52,10 @@
 		</varlistentry>
 		 <varlistentry id="all-in-one">
 			<term role="true">all-in-one</term>
-      <term role="false">allinone</term>
 			 <listitem>
 				<para>
-					<emphasis>n., adj.</emphasis> Hyphenate in both places. Do not use "allinone" or other variations.
+					<emphasis>n., adj.</emphasis> Write as shown as both a noun and an adjective.
+					Do not use other variations.
 				</para>
 
 			</listitem>
@@ -78,7 +75,7 @@
 			</listitem>
 
 		</varlistentry>
-		 
+
 		 <varlistentry id="alternative">
 			<term role="true">alternative</term>
 			 <listitem>
@@ -98,7 +95,7 @@
 			 <listitem>
 				<para>
 					For times of day, use uppercase without periods, and use a preceding nonbreaking space after the numeral, for example "11&nbsp;AM".
-				</para> 
+				</para>
         <para>
           See also <xref linkend="pm"/>.
         </para>
@@ -123,7 +120,6 @@
 					<para>
 						The AMD64 logo is trademarked; the term "AMD64" is not. For more information about AMD trademarks, see the <citetitle>AMD Trademark Information</citetitle> page at <ulink url="https://www.amd.com/en/corporate/trademarks" />.
 					</para>
-		<!-- Updated URL for AMD trademarks. -->			
 					 <para>
 						For more information about Intel&reg; trademarks, see <ulink url="http://www.intel.com/content/www/us/en/legal/trademarks.html" /> and <ulink url="http://www.intel.com/content/www/us/en/trademarks/trademarks.html" />.
 					</para>
@@ -147,7 +143,6 @@
 
 		</varlistentry>
 
-<!-- Added "appendixes" entry. -->
 		 <varlistentry id="appendixes">
 			<term>appendixes</term>
 			 <listitem>
@@ -157,27 +152,25 @@
 
 			</listitem>
 
-		</varlistentry>		
+		</varlistentry>
 
-<!-- Commenting out this entry as it is not a literal term entry. Consider moving elsewhere, such as to Section 3.7 and expand scope of that section? 		
-		 <varlistentry id="application">
-			<term>application</term>
+		 <varlistentry id="application-velocity">
+			<term>application velocity</term>
 			 <listitem>
 				<para>
-					When used as a proper name, use the capitalization of the product, such as GNUPro, Source-Navigator, and Red&nbsp;Hat Enterprise&nbsp;Linux.
-          When used as a command, use lowercase as appropriate, such as "To start GCC, type gcc".
+					Used on its own, this phrase does not indicate what aspect of the application lifecycle is faster, because velocity means "speed in a given direction.”
+				</para>
+				<para>
+					Always provide context on first mention for what exactly is moving faster (for example, application development velocity, development velocity, development and deployment velocity).
+					Then, unless the meaning changes, you can use “application velocity” for subsequent uses.
+				</para>
+				<para>
+					For example, the OpenShift team has used this term to mean "creating a streamlined developer experience" whose context is key to setting audience expectations for their content.
 				</para>
-				 <note>
-					<para>
-						"vi" is always lowercase.
-					</para>
-
-				</note>
 
 			</listitem>
 
 		</varlistentry>
--->
 
 		 <varlistentry id="applixware">
 			<term role="true">Applixware</term>
@@ -263,7 +256,7 @@
 					</listitem>
 					 <listitem>
 						<para>
-							MaaS (Messaging-as-a-Service)
+							MaaS (Messaging-as-a-Service, Metal-as-a-Service)
 						</para>
 
 					</listitem>
@@ -295,14 +288,14 @@
 						<para>
 							When in all capitals, such as a title or headline, the "aa" in the acronym remains lowercase (such as INTRODUCTION TO PaaS SOLUTIONS).
 						</para>
-<!-- When would all capitals be used? -->						
+<!-- When would all capitals be used? -->
 
 					</listitem>
 					 <listitem>
 						<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/Audience.xml

@@ -6,11 +6,18 @@
 <section id="audience">
 	<title>Audience</title>
 	 <para>
-		This guide is the official style guide for technical documentation for Red&nbsp;Hat training and certification content, including how to write for global audiences and translation, common mistakes to avoid, rules for everyday punctuation, and grammar.
+		This guide is the official style guide for Red&nbsp;Hat training and certification content, and for all other technical documentation except as stated.
+		Red&nbsp;Hat product documentation by Customer Content Services (CCS) follows the Red&nbsp;Hat supplementary style guide at <ulink url="https://redhat-documentation.github.io/supplementary-style-guide/" /> instead of this Red&nbsp;Hat Technical Writing Style Guide.
 	</para>
 	 <para>
-        Other Red&nbsp;Hat technical documentation, including product documentation by Customer Content Services (CCS), follows the Red&nbsp;Hat supplementary style guide for product documentation at <ulink url="https://redhat-documentation.github.io/supplementary-style-guide/" /> instead of this Red&nbsp;Hat Technical Writing Style Guide.
+		The Red&nbsp;Hat Technical Writing Style Guide includes everyday punctuation and grammar, common mistakes to avoid, strategies for translation and global audiences, and a word usage dictionary.        
 	</para>
+	 <para>
+		This guide is a public guide. It is reviewed and maintained by Red&nbsp;Hat. Contributions from the wider community are always welcomed.        
+	</para>
+	<para>
+        Other resources for technical writing are listed in <xref linkend="resources"/>.
+    </para>	
 
 </section>
 

en-US/Author_Group.xml

@@ -5,7 +5,7 @@
 ]>
 <authorgroup>
 	<author>
-		<firstname>Red Hat Documentation Team</firstname>
+		<firstname>Red&nbsp;Hat Documentation Team</firstname>
 		 <surname></surname>
 		 <affiliation>
 			<orgname></orgname>

en-US/B.xml

@@ -75,7 +75,6 @@
 				<para>
 					Do not use. Instead, use "compatible with earlier versions" to refer to something that is compatible with older equipment or previous versions of software. See also <xref linkend="forwards-compatible" />.
 				</para>
-<!-- Replaced with "compatible with earlier versions", to align with advice for "forwards-compatible". -->				
 
 			</listitem>
 
@@ -362,8 +361,8 @@
 			<term>broadcast</term>
 			 <listitem>
 				<para>
-					To send the same message simultaneously to multiple recipients. Broadcasting is a useful feature in email systems. 
-<!-- Deleted reference to fax. 					
+					To send the same message simultaneously to multiple recipients. Broadcasting is a useful feature in email systems.
+<!-- Deleted reference to fax.
 					It is also supported by some fax systems. -->
 				</para>
 				 <para>
@@ -383,7 +382,7 @@
 					See <ulink url="http://en.wikipedia.org/wiki/Btrfs" /> for more information on this file system.
 				</para>
 				 <para>
-					See <ulink url="http://en.wikipedia.org/wiki/List_of_file_systems" /> for a list of file system names and how to present them.
+					See <ulink url="http://en.wikipedia.org/wiki/List_of_file_systems" /> for a list of file-system names and how to present them.
 				</para>
 
 			</listitem>

en-US/Book_Design.xml

@@ -99,7 +99,9 @@
 			Drawing these basics together might produce the following example abstract:
 		</para>
 		 <para>
-			"The Red&nbsp;Hat Satellite&nbsp;5.6 API Guide is a full reference for Satellite's XMRPC API. The guide explains each API method and demonstrates examples of data models for input and output. This book provides a basis for administrators and developers to write custom scripts and to integrate Red Hat Satellite with third-party applications."
+			"The Red&nbsp;Hat Satellite&nbsp;5.6 API Guide is a full reference for Satellite's XMRPC API.
+			The guide explains each API method and demonstrates examples of data models for input and output.
+			This book provides a basis for administrators and developers to write custom scripts and to integrate Red&nbsp;Hat Satellite with third-party applications."
 		</para>
 		 <para>
 			Update or modify each component according to the type of book that you are writing.
@@ -122,7 +124,7 @@
 	</section>
 	 <section id="unused-heading-titles">
 		<title>Unused Heading Titles</title>
-		 <para>		
+		 <para>
 			This section lists various heading titles that might be used in Red&nbsp;Hat technical documentation, but that should be avoided except in specific circumstances.
 		</para>
 		 <formalpara id="overview">

en-US/Book_Info.xml

@@ -8,11 +8,11 @@
 	<!-- Change title to "The Red Hat Style Guide" -->
 	 <productname>Red&nbsp;Hat Technical Writing Style&nbsp;Guide</productname>
 	 <productnumber></productnumber>
-	 <edition>6.0</edition>
+	 <edition>6.1</edition>
 	 <pubsnumber>1</pubsnumber>
 	 <abstract>
 		<para>
-			The Red&nbsp;Hat Style Guide and Word Usage Dictionary is a joint effort by various groups within Red&nbsp;Hat. It is intended as a supplement to the titles listed in <xref linkend="resources" />
+			The Red&nbsp;Hat Technical Writing Style Guide and Word Usage Dictionary is a joint effort by various groups within Red&nbsp;Hat. It is intended as a supplement to the titles listed in <xref linkend="resources" />
 		</para>
 
 	</abstract>

en-US/Cross_references.xml

@@ -40,15 +40,15 @@
 
 	</section>
 	 <section id="repeatability-test">
-		<title>The Repeatability Test</title>
+		<title>Repetition</title>
 		 <para>
-			Must the information be repeated?
+			Repetition is a useful tool for reinforcing new knowledge and skills, emphasizing important ideas, and providing readers with important information at their point of need.
 		</para>
 		 <para>
-			This is a hard question, and one that many authors abhor. Often the answer is yes. If the information is vital, and must appear in multiple places, then it must be repeated. It's not a crime. In some circumstances, such is in online help, the reader wants the answer immediately. Do not force even one extra click on them. In a safety situation, it might be the only chance for the reader to find critical information quickly. Any vital information, which is not more than a couple of paragraphs (or half a page, or five rows of a table), can be repeated rather than be cross-referenced to.
+			Repeating necessary information also saves the reader time and effort. In some circumstances, such as when using online help, the reader is trying to answer an immediate question or to solve a problem. In a safety situation, it is important for the reader to find critical information quickly.
 		</para>
 		 <para>
-			Cross-referencing is a good servant but a poor master. Content still rules!
+			If the information is vital, and must appear in multiple places, then it must be repeated. Any vital information, which is not more than a couple of paragraphs (or half a page, or five rows of a table), can be repeated rather than be cross-referenced to.
 		</para>
 
 	</section>

en-US/D.xml

@@ -142,7 +142,6 @@
 			</listitem>
 
 		</varlistentry>
-<!-- Added "desire". -->
 		<varlistentry id="desire">
 			<term>desire</term>
 			 <listitem>
@@ -210,7 +209,12 @@
       <term>digital transformation</term>
       <listitem>
         <para>
-          Avoid this phrase. It is vague and could mean use of digital technology to do something faster, to do something differently, or to do a completely new thing. The word "transform" implies a process with a beginning and an end. Some people use the phrase "digital leadership" to describe the ongoing adoption of digital technologies to advance their organization. If you must discuss the concepts of digital transformation or digital leadership, briefly define what you mean on the first occurrence. Describe, rather than label.
+          Avoid this phrase.
+          It is vague and could mean use of digital technology to do something faster, to do something differently, or to do something new.
+          The word "transform" implies a process with a beginning and an end.
+          Some people use the phrase "digital leadership" to describe the ongoing adoption of digital technologies to advance their organization.
+          If you must discuss the concepts of digital transformation or digital leadership, briefly define what you mean on the first occurrence.
+          Describe, rather than label.
         </para></listitem>
       </varlistentry>
 		 <varlistentry id="disk-druid">