OSDOCS-8012: fix attribute for microshift

Author: ShaunaDiaz

_attributes/attributes-microshift.adoc

@@ -13,12 +13,11 @@
 :rhel-major: rhel-9
 :op-system-base-full: Red Hat Enterprise Linux (RHEL)
 :op-system: RHEL
+:op-system-base: RHEL
 :op-system-ostree-first: Red Hat Enterprise Linux for Edge (RHEL for Edge)
 :op-system-ostree: RHEL for Edge
 :op-system-version: 9.2
 :op-system-version-major: 9
-:op-system-bundle-first: Red Hat Device Edge (RHDE)
 :op-system-bundle: Red Hat Device Edge
-:op-system-bundle-short: RHDE
 :rpm-repo-version: rhocp-4.14
 :VirtProductName: OpenShift Virtualization

_topic_maps/_topic_map_ms.yml

@@ -33,14 +33,14 @@ Name: Release notes
 Dir: microshift_release_notes
 Distros: microshift
 Topics:
-- Name: MicroShift 4.14 release notes
+- Name: Red Hat build of MicroShift 4.14 release notes
   File: microshift-4-14-release-notes
 ---
 Name: Getting started
 Dir: microshift_getting_started
 Distros: microshift
 Topics:
-- Name: Understanding MicroShift
+- Name: Understanding Red Hat build of MicroShift
   File: microshift-understanding
 - Name: Architecture
   File: microshift-architecture
@@ -66,7 +66,7 @@ Topics:
   File: microshift-about-updates
 - Name: Update options
   File: microshift-update-options
-- Name: Updates with RPM-OSTree systems
+- Name: Updates with rom-ostree systems
   File: microshift-update-rpms-ostree
 - Name: Manual updates with RPMs
   File: microshift-update-rpms-manually
@@ -75,9 +75,9 @@ Name: Support
 Dir: microshift_support
 Distros: microshift
 Topics:
-- Name: MicroShift etcd
+- Name: The etcd service
   File: microshift-etcd
-- Name: MicroShift sos report
+- Name: The sos tool
   File: microshift-sos-report
 ---
 Name: API reference
@@ -401,15 +401,15 @@ Name: Storage
 Dir: microshift_storage
 Distros: microshift
 Topics:
-- Name: About MicroShift storage
+- Name: About storage
   File: index
-- Name: Understanding ephemeral storage for MicroShift
+- Name: Understanding ephemeral storage
   File: understanding-ephemeral-storage-microshift
-- Name: Generic ephemeral volumes for MicroShift
+- Name: Generic ephemeral volumes
   File: generic-ephemeral-volumes-microshift
-- Name: Understanding persistent storage for MicroShift
+- Name: Understanding persistent storage
   File: understanding-persistent-storage-microshift
-- Name: Expanding persistent volumes for MicroShift
+- Name: Expanding persistent volumes
   File: expanding-persistent-volumes-microshift
 - Name: Dynamic storage using the LVMS plugin
   File: microshift-storage-plugin-overview

microshift_configuring/microshift-cluster-access-kubeconfig.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Learn about how `kubeconfig` files are used with {product-title} deployments. CLI tools use `kubeconfig` files to communicate with the API server of a cluster. These files provide cluster details, IP addresses, and other information needed for authentication.
+Learn about how `kubeconfig` files are used with {microshift-short} deployments. CLI tools use `kubeconfig` files to communicate with the API server of a cluster. These files provide cluster details, IP addresses, and other information needed for authentication.
 
 include::modules/microshift-kubeconfig-overview.adoc[leveloffset=+1]
 

microshift_configuring/microshift-greenboot-checking-status.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-To deploy applications or make other changes through the {product-title} API with tools other than `kustomize` manifests, you must wait until the Greenboot health checks have finished. This ensures that your changes are not lost if Greenboot rolls your `rpm-ostree` system back to an earlier state.
+To deploy applications or make other changes through the {microshift-short} API with tools other than `kustomize` manifests, you must wait until the Greenboot health checks have finished. This ensures that your changes are not lost if Greenboot rolls your `rpm-ostree` system back to an earlier state.
 
 The `greenboot-healthcheck` service runs one time and then exits. After Greenboot has exited and the system is in a healthy state, you can proceed with configuration changes and deployments.
 

microshift_configuring/microshift-using-config-tools.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-A YAML file customizes {product-title} instances with your preferences, settings, and parameters.
+A YAML file customizes {microshift-short} instances with your preferences, settings, and parameters.
 
 include::snippets/microshift-greenboot-status-snip.adoc[leveloffset=+2]
 

microshift_getting_started/microshift-architecture.adoc

@@ -11,7 +11,7 @@ Learn the specifics of {product-title} architecture including design intent, how
 
 [id="microshift-architectural-design_{context}"]
 == Architectural design
-{product-title} 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.
+{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:
 
@@ -58,12 +58,12 @@ Figure 2 shows that {oke} has the same cluster capabilities as {product-title},
 * 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 {product-title}, 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.
 
 [id="microshift-openshift-apis_{context}"]
-== {product-title} OpenShift APIs
+== {microshift-short} OpenShift APIs
 
-In addition to standard Kubernetes APIs, {product-title} includes a small subset of the APIs supported by {OCP}.
+In addition to standard Kubernetes APIs, {microshift-short} includes a small subset of the APIs supported by {OCP}.
 
 [cols="1,1",options="header"]
 |===
@@ -74,4 +74,8 @@ In addition to standard Kubernetes APIs, {product-title} includes a small subset
 | security.openshift.io/v1
 |===
 
-include::modules/microshift-k8s-apis.adoc[leveloffset=+1]
+include::modules/microshift-k8s-apis.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../microshift_rest_api/index.adoc#api-index[API index]

microshift_getting_started/microshift-understanding.adoc

@@ -6,6 +6,6 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Get an overview of what you can do with {product-title}, a Kubernetes distribution derived from {OCP} that is designed for optimizing small form factor devices and edge computing.
+Get an overview of what you can do with {microshift-short}, a Kubernetes distribution derived from {OCP} that is designed for optimizing small form factor devices and edge computing.
 
 include::modules/microshift-about.adoc[leveloffset=+1]

microshift_install/microshift-embed-in-rpm-ostree.adoc

@@ -1,12 +1,12 @@
 :_content-type: ASSEMBLY
 [id="microshift-embed-in-rpm-ostree"]
-= Embedding {product-title} in a {op-system-ostree} image
+= Embedding {microshift-short} in a {op-system-ostree} image
 include::_attributes/attributes-microshift.adoc[]
 :context: microshift-embed-in-rpm-ostree
 
 toc::[]
 
-You can embed {product-title} into a {op-system-ostree-first} {op-system-version} image. Use this guide to build a {op-system} image containing {product-title}.
+You can embed {microshift-short} into a {op-system-ostree-first} {op-system-version} image. Use this guide to build a {op-system} image containing {microshift-short}.
 
 //include::snippets/microshift-tech-preview-snip.adoc[leveloffset=+1]
 
@@ -28,7 +28,6 @@ include::modules/microshift-ca-adding-bundle.adoc[leveloffset=+1]
 include::modules/microshift-ca-adding-bundle-ostree.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
-[id="additional-resources_microshift-add-cert-bundle"]
 .Additional resources
 
 * xref:../microshift_install/microshift-embed-in-rpm-ostree.adoc#microshift-creating-ostree-iso_microshift-embed-in-rpm-ostree[Creating the {op-system-ostree} image]

microshift_install/microshift-greenboot.adoc

@@ -6,14 +6,14 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Greenboot is the generic health check framework for the `systemd` service on RPM-OSTree-based systems. The `microshift-greenboot` RPM and `greenboot-default-health-checks` are RPM packages installed with {product-title}. Greenboot is used to assess system health and automate a rollback to the last healthy state in the event of software trouble, for example:
+Greenboot is the generic health check framework for the `systemd` service on RPM-OSTree-based systems. The `microshift-greenboot` RPM and `greenboot-default-health-checks` are RPM packages installed with {microshift-short}. Greenboot is used to assess system health and automate a rollback to the last healthy state in the event of software trouble, for example:
 
 * This health check framework is especially useful when you need to check for software problems and perform system rollbacks on edge devices where direct serviceability is either limited or non-existent.
 * When health check scripts are installed and configured, health checks run every time the system starts.
 * Using Greenboot can reduce your risk of being locked out of edge devices during updates and prevent a significant interruption of service if an update fails.
 * When a failure is detected, the system boots into the last known working configuration using the `rpm-ostree` rollback capability.
 
-A {product-title} application health check script is included in the `microshift-greenboot` RPM. The `greenboot-default-health-checks` RPM also includes health check scripts verifying that DNS and `ostree` services are accessible. In addition, you can create your own health check scripts for the workloads you are running. You can write one that verifies that an application has started, for example.
+A {microshift-short} application health check script is included in the `microshift-greenboot` RPM. The `greenboot-default-health-checks` RPM also includes health check scripts verifying that DNS and `ostree` services are accessible. In addition, you can create your own health check scripts for the workloads you are running. You can write one that verifies that an application has started, for example.
 
 [NOTE]
 ====

microshift_install/microshift-installing-troubleshooting.adoc

@@ -6,13 +6,13 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-To troubleshoot a failed {product-title} installation, you can run an sos report. Use the `sos report` command to generate a detailed report that shows all of the enabled plugins and data from the different components and applications in a system.
+To troubleshoot a failed {microshift-short} installation, you can run an sos report. Use the `sos report` command to generate a detailed report that shows all of the enabled plugins and data from the different components and applications in a system.
 
 include::modules/microshift-gathering-sos-report.adoc[leveloffset=+1]
 
 [id="additional-resources_microshift-installing-troubleshooting_{context}"]
 [role="_additional-resources"]
 == Additional resources
-* xref:../microshift_support/microshift-sos-report.adoc#microshift-sos-report[About MicroShift sos reports]
+* xref:../microshift_support/microshift-sos-report.adoc#microshift-sos-report[About {microshift-short} sos reports]
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/getting_the_most_from_your_support_experience/generating-an-sos-report-for-technical-support_getting-the-most-from-your-support-experience[Generating an sos report for technical support]