OSDOCS-16189-419: adds corrections 4.17+

_topic_maps/_topic_map_ms.yml

@@ -119,7 +119,7 @@ Topics:
   File: microshift-disable-lvms-csi-provider-csi-snapshot
 - Name: Checking the status of Greenboot health checks
   File: microshift-greenboot-checking-status
-- Name: Cluster access with kubeconfig
+- Name: Cluster access with kubeconfig files
   File: microshift-cluster-access-kubeconfig
 - Name: Configuring MicroShift authentication and security
   Dir: microshift_auth_security

microshift_configuring/microshift-cluster-access-kubeconfig.adoc

@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="microshift-kubeconfig"]
-= Cluster access with kubeconfig
+= Cluster access with kubeconfig files
 include::_attributes/attributes-microshift.adoc[]
 :context: microshift-kubeconfig
 

microshift_networking/microshift-cni.adoc

@@ -66,6 +66,7 @@ Bridge mappings allow provider network traffic to reach the physical network. Tr
 include::modules/microshift-nw-topology.adoc[leveloffset=+1]
 
 [id="_additional-resources_microshift-cni_{context}"]
+[role="_additional-resources"]
 == Additional resources
 
 * xref:../microshift_configuring/microshift-using-config-yaml.adoc#microshift-config-yaml_microshift-configuring[Using a YAML configuration file]

microshift_welcome/index.adoc

@@ -28,7 +28,7 @@ For related information, use the following links:
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_device_edge/4/html/overview/device-edge-overview[Red Hat Device Edge overview]
 * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/composing_installing_and_managing_rhel_for_edge_images/index[RHEL for Edge documentation]
-* link:https://docs.openshift.com/container-platform/latest/welcome/index.html[{OCP} documentation]
+* link:https://docs.openshift.com/container-platform/[{OCP} documentation]
 
 include::modules/microshift-about.adoc[leveloffset=+1]
 

modules/microshift-arch-design.adoc

@@ -5,9 +5,10 @@
 :_mod-docs-content-type: CONCEPT
 [id="microshift-architectural-design_{context}"]
 == Architectural design
+
 {microshift-short} is a single-node container orchestration runtime designed to extend the benefits of using containers for running applications to low-resource edge environments. Because {microshift-short} is primarily a platform for deploying applications, only the APIs and features essential to operating in edge and small form factor computing environments are included.
 
-For example, {microshift-short} contains only the following Kubernetes cluster capabilities:
+For example, {microshift-short} has only the following Kubernetes cluster capabilities:
 
 * Networking
 * Ingress
@@ -51,4 +52,4 @@ The figure "{product-title} differences from {oke}" shows that {oke} has the sam
 * Cloud Integration
 * Virtual Machines (VMs) through {VirtProductName}
 
-In {oke} and other {OCP} deployments, all of the components from the operating system through the cluster capabilities work as one comprehensive unit, with full cluster services for a multi-node Kubernetes workload. With {microshift-short}, functions such as over-the-air-updates, monitoring, and logging, are performed by the operating system.
+In {oke} and other {OCP} deployments, all of the components from the operating system through the cluster capabilities work as one comprehensive unit, with full cluster services for a multi-node Kubernetes workload. With {microshift-short}, functions such as over-the-air-updates, monitoring, and logging, are performed by the operating system.

modules/microshift-check-journal-logs-updates.adoc

@@ -22,7 +22,7 @@ The default configuration of the `systemd` journal service stores data in a vola
 $ sudo journalctl -u microshift
 ----
 
-* Check the Greenboot journal logs by running the following command:
+* Check the greenboot journal logs by running the following command:
 +
 [source,terminal]
 ----
@@ -48,8 +48,7 @@ IDX  BOOT ID                          	FIRST ENTRY                 LAST ENTRY
 
 ** Check the journal logs for the specific boot you want by running the following command:
 +
-[source,terminal]
-[subs="+quotes"]
+[source,terminal,subs="+quotes"]
 ----
 $ sudo journalctl --boot __<idx_or_boot_id>__ <1>
 ----
@@ -57,8 +56,7 @@ $ sudo journalctl --boot __<idx_or_boot_id>__ <1>
 
 ** Check the journal logs for the boot of a specific service by running the following command:
 +
-[source,terminal]
-[subs="+quotes"]
+[source,terminal,subs="+quotes"]
 ----
 $ sudo journalctl --boot __<idx_or_boot_id>__ -u __<service_name>__ <1> <2>
 ----