Updated references to content view environments.

Because multiCV is now default, references to
content view environments should be plural when
relating to the host assigning content view
environments.

Author: jberendz

guides/common/modules/con_conditions-for-content-availability.adoc

@@ -4,7 +4,7 @@
 = Conditions for content availability
 
 [role="_abstract"]
-A host can access a repository only when that repository is in a content view environment of the host, passes filters, is enabled, and matches any architecture or operating system version restrictions.
+A host can access a repository only when that repository is in a content view environments of the host, passes filters, is enabled, and matches any architecture or operating system version restrictions.
 When any requirement fails, packages stay unavailable to the host even though {Project} still publishes the repository.
 
 A host can access a package or repository only if all of the following conditions are true:

guides/common/modules/con_content-view-environment-ordering-and-priority.adoc

@@ -6,12 +6,12 @@
 [role="_abstract"]
 The order of content view environments on a host or activation key determines which repository version the host uses when the same repository exists in multiple content view environments.
 
-During host registration, an activation key assigns content view environments in the order in which they are stored.
+During host registration, an activation key assigns content view environments in the order they are stored.
 
-A host pulls content from the first assigned content view environment that contains the repository.
+A host pulls content from the first assigned content view environments that contain the repository.
 If `Library` is first in the list, it overrides other content view environments because it contains all repositories.
 
-Content view environment order is critical when repository conflicts occur.
+The order of the content view environment is critical when repository conflicts occur.
 A repository conflict occurs when multiple content view environments contain a repository with the same label.
 For example:
 A host assigned to the content view environments `Library/cv1, dev/cv1` uses the following configuration:

guides/common/modules/con_content-view-environments-overview.adoc

@@ -7,7 +7,7 @@
 By default, you can assign multiple content view environments to hosts and activation keys.
 This is controlled by the *Allow multiple content views* setting.
 
-Hosts registered with multiple activation keys handle content view environment assignments based on the order of activation keys and content view environments.
+Hosts registered with multiple activation keys handle content view environment assignments based on the order of activation keys and order of content view environments.
 
 When you disable *Allow multiple content views*, multi-environment hosts remain assigned to multiple content view environments and retain access to all their content.
 Existing multi-environment activation keys remain associated with multiple content view environments, and both multi-environment hosts and activation keys remain visible in the {ProjectWebUI} and accessible through the Hammer CLI.

guides/common/modules/proc_changing-the-content-view-environment-of-a-host.adoc

@@ -1,10 +1,10 @@
 :_mod-docs-content-type: PROCEDURE
 
 [id="changing-the-content-view-environment-of-a-host"]
-= Changing the content view environment of a host
+= Changing the content view environments of a host
 
 [role="_abstract"]
-You can change the content view environment of a host when you need to alter which content the host can consume from {Project}.
+You can change the content view environments of a host when you need to alter which content the host can consume from {Project}.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Hosts* > *All Hosts*.

guides/common/modules/ref_best-practices-for-errata.adoc

@@ -8,7 +8,7 @@ Apply these recommendations when managing errata so you patch security issues in
 
 * Use errata to add patches for security issues to a frozen set of content without unnecessarily updating other unaffected packages.
 * Automate errata management by using a Hammer script or an {ansible-docs-url}[Ansible Playbook].
-* View errata on the host details page and compare the errata of the current content view environment to the Library lifecycle environment, which contains the latest synchronized packages.
+* View the errata on the host details page. Compare the errata of the current content view environments to the Library lifecycle environment, which contains the latest synchronized packages.
 +
 You can only apply errata included in the content view version of the lifecycle of your host.
 You can view applicable errata as a recommendation to create an incremental content view to provide errata to hosts.

guides/common/modules/ref_prerequisites-for-installing-errata-on-hosts.adoc

@@ -4,7 +4,7 @@
 = Prerequisites for installing errata on hosts
 
 [role="_abstract"]
-Installing errata on hosts requires synchronized repositories, installable errata in the content view environment, registered hosts, and remote execution configuration.
+Installing errata on hosts requires synchronized repositories, installable errata in the content view environments, registered hosts, and remote execution configuration.
 
 ifdef::katello[]
 * Repositories on {ProjectServer} are synchronized with the latest errata available from upstream.
@@ -15,11 +15,11 @@ endif::[]
 ifdef::satellite[]
 * Repositories on {ProjectServer} are synchronized with the latest errata available from Red{nbsp}Hat.
 endif::[]
-* The host is registered to a content view environment.
+* The host is registered to content view environments.
 * The host is configured for remote execution.
 * Errata are *installable*.
 +
-Applicable errata have updates for packages on hosts, but you can only install errata included in the content view environment of the host.
+Applicable errata have updates for packages on hosts, but you can only install errata included in the content view environments of the host.
 If errata are applicable but not installable, the content view must be incrementally updated and promoted to the lifecycle environment of the host.
 
 .Additional resources