updates based on review comments

Author: kalexand-rh

architecture/architecture.adoc

@@ -30,8 +30,6 @@ include::modules/operators-overview.adoc[leveloffset=+2]
 
 include::modules/abstraction-layers.adoc[leveloffset=+2]
 
-include::modules/security-overview.adoc[leveloffset=+2]
-
 include::modules/machine-api-overview.adoc[leveloffset=+1]
 
 [[observability-architecture]]

modules/cloud_installations.adoc

@@ -27,7 +27,7 @@ components
 * Cluster registration, which associates the cluster identity to your Red Hat
 account to facilitate the gathering of usage metrics
 
-In {product-title} version 4.0, the installer is a Go binary that performs a
+In {product-title} v4, the installer is a Go binary that performs a
 series of file transformations on a set of assets. With the fully-managed option,
 you delegate the infrastructure bootstrapping and provisioning to the installer
 instead of doing it yourself. Because you do not use the installer to upgrade or

modules/machine-api-overview.adoc

@@ -5,10 +5,10 @@
 [id='machine-api-overview-{context}']
 = Machine API overview
 
-On {product-title} version 4.0 clusters, the Machine API performs all node
+For {product-title} v4 clusters, the Machine API performs all node
 management actions after the cluster installation finishes. Because of this
-system, {product-title} version 4.0 offers an elastic, dynamic provisioning
-method.
+system, {product-title} v4 offers an elastic, dynamic provisioning
+method on top of public or private cloud infrastructure.
 
 The Machine API is a combination of primary resources that are based on the upstream
 link:https://github.com/kubernetes-sigs/cluster-api[Cluster API] project and

modules/node-management.adoc

@@ -7,7 +7,7 @@
 
 {product-title} version 4.0 integrates management of
 the container operating system and cluster management. Because the cluster manages
-both its updates and updates to Red Hat CoreOS, {product-title} provides an opinionated
+its updates, including updates to Red Hat CoreOS on cluster nodes, {product-title} provides an opinionated
 lifecycle management experience that simplifies the orchestration of upgrades.
 
 {product-title} employs three DaemonSets and controllers to simplify node management:
@@ -19,7 +19,7 @@ applies the specified machine configuration and controls kubelet configuration.
 
 These tools orchestrate operating system updates and configuration changes to
 the hosts by using standard Kuberentes-style constructs. A `machine-config-daemon`
-DaemonSet runs on each compute node in the cluster and watches for changes in
+DaemonSet runs on each machine in the cluster and watches for changes in
 the machine configuration for it to apply. The machine configuration is a subset
 of the Ignition configuration. The `machine-config-daemon` reads the machine configuration to see
 if it needs to do an OSTree update, if it should apply a series of systemd

modules/operators-overview.adoc

@@ -11,7 +11,7 @@ operations and run services on the cluster for your applications to use.
 [id='platform-operators-{context}']
 == Platform Operators in {product-title}
 
-In {product-title} version 4.0, all cluster functions are divided into a series
+In {product-title} v4, all cluster functions are divided into a series
 of platform Operators. Platform operators manage a particular area of
 cluster functionality, such as cluster-wide application logging, management of
 the Kubernetes control plane, or the machine provisioning system.

modules/security-overview.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * architecture/architecture.adoc
+// * orphaned
 
 [id='security-overview-{context}']
 = Security in {product-title}