OSDOCS-17109:CQA-2-MSH-INST-3-bootc

microshift_install_bootc/microshift-about-rhel-image-mode.adoc

@@ -6,6 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You can embed {microshift-short} into an operating system image using image mode for {op-system-base-full}.
 
 include::modules/microshift-install-bootc-conc.adoc[leveloffset=+1]

microshift_install_bootc/microshift-install-bootc-image.adoc

@@ -6,6 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 {microshift-short} is built and published as image mode containers. When installing a {op-system-base-full} bootable container image with {microshift-short}, use either a prebuilt bootable container image or build your own custom bootable container image.
 
 include::modules/microshift-install-bootc-workflow.adoc[leveloffset=+1]

microshift_install_bootc/microshift-install-bootc-physically-bound.adoc

@@ -6,6 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 If you need your bootc image to include everything required to run workloads, use physically-bound container images. Edge-computing scenarios involving embedded systems on specialized devices, high security, or high hardware control scenarios are likely candidates.
 
 include::modules/microshift-install-bootc-physically-bound-con.adoc[leveloffset=+1]

microshift_install_bootc/microshift-install-running-bootc-image-vm.adoc

@@ -6,6 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 Use the bootable container image as an installation source to set up a {op-system-base-full} virtual machine.
 
 include::modules/microshift-install-bootc-prepare-kickstart.adoc[leveloffset=+1]

modules/microshift-embed-cont-images-bootc-image.adoc

@@ -6,6 +6,7 @@
 [id="microshift-embed-cont-images-bootc-image_{context}"]
 = Embedding container images into a bootc image
 
+[role="_abstract"]
 First, you must add instructions to an existing Containerfile to copy the images you want and list them in a file to keep track of the copied image names. Then, you must copy images locally from the `/usr/lib/containers/storage` directory to the local container storage.
 
 [IMPORTANT]
@@ -29,7 +30,8 @@ You cannot store images in the default or additional container storage directory
 ----
 $ podman build --secret id=pullsecret,src=/_<path/to/pull/secret>_.json <1>
 ----
-<1> Specify the path to your pull secret in _<path/to/pull/secret>_.
++
+Specify the path to your pull secret in _<path/to/pull/secret>_.
 
 . Add the instructions to physically embed the image at build time by adding the following to your Containerfile:
 +

modules/microshift-install-bootc-conc.adoc

@@ -6,6 +6,7 @@
 [id="microshift-bootc-conc_{context}"]
 = About image mode for {op-system-base-full}
 
+[role="_abstract"]
 By using image mode for {op-system-base}, you can use the same tools and techniques for the operating system that you use with application containers. Image mode for {op-system-base} is a deployment method that uses a container-native approach to build, deploy, and manage the operating system as a `rhel-bootc` image.
 
 * This container image uses standard OCI or Docker containers as a transport and delivery format for base operating system updates.

modules/microshift-install-bootc-creating-vm.adoc

@@ -6,6 +6,7 @@
 [id="microshift-install-bootc-creating-vm_{context}"]
 = Creating a virtual machine
 
+[role="_abstract"]
 You can create a virtual machine by using the {op-system-base-full} boot ISO image.
 
 .Prerequisites

modules/microshift-install-bootc-physically-bound-con.adoc

@@ -6,6 +6,7 @@
 [id="microshift-install-bootc-physically-bound_{context}"]
 = About physically bound bootc image building
 
+[role="_abstract"]
 When a bootc image is fully self-contained, everything you need to run workloads is embedded with the bootc image, including {microshift-short} and application container images. The underlying mechanism is to pre-pull physically-bound images during image build and then make them available at runtime.
 
 Because embedded images might change with each system update, you cannot pull the images directly to the default container storage. Additional image stores do not work in this case because of current implementation limits. These limits do not allow bootc image updates for those container images.

modules/microshift-install-bootc-prepare-kickstart.adoc

@@ -6,6 +6,7 @@
 [id="microshift-install-bootc-prepare-kickstart_{context}"]
 = Creating the Kickstart file
 
+[role="_abstract"]
 You must create the Kickstart file to use during installation.
 
 .Prerequisites
@@ -33,9 +34,10 @@ $ PULL_SECRET=~/.pull-secret.json
 +
 [source,terminal,subs="attributes+,quotes"]
 ----
-$ IMAGE_REF="quay.io/_<myorg>/<mypath>_/microshift-{product-version}-bootc" <1>
+$ IMAGE_REF="quay.io/_<myorg>/<mypath>_/microshift-{product-version}-bootc"
 ----
-<1> Replace _<myorg/<mypath>_ with your remote registry organization name and path.
++
+Replace _<myorg/<mypath>_ with your remote registry organization name and path.
 
 . Create the `kickstart.ks` file to use during installation by running the following script:
 +

modules/microshift-preparing-for-image-building-bootc.adoc

@@ -6,6 +6,7 @@
 [id="microshift-preparing-for-image-building_{context}"]
 = Preparing for bootc image building
 
+[role="_abstract"]
 Use the image builder tool to compose customized {microshift-short} bootc images optimized for edge deployments. You can run a {microshift-short} node with your applications on a {op-system-image} virtual machine for development and testing first, then use your whole solution in edge production environments.
 
 Use the following {op-system-base} documentation to understand the full details of using {op-system-image}: