Merge pull request #53517 from ShaunaDiaz/OSDOCS-4657

OSDOCS-4657 update manifest module in config

Author: mjpytlak

modules/microshift-auto-apply-manifests.adoc

@@ -5,8 +5,7 @@
 :_content-type: CONCEPT
 [id="microshift-auto-apply-manifests_{context}"]
 = Automatically applying manifests with `kustomize`
-
- Providing multiple directories allows a flexible method of managing {product-title} workloads. When you run the `kustomize` configuration management tool, {product-title} searches the `/etc/microshift/manifests` and `/usr/lib/microshift/` manifest directories for a `kustomization.yaml` file. If it finds one, {product-title} automatically runs the `kubectl apply -k` command to apply the manifests to the cluster.
+Providing multiple directories allows a flexible method of managing {product-title} workloads. When you run the `kustomize` configuration management tool, {product-title} searches the `/etc/microshift/manifests` and `/usr/lib/microshift/` manifest directories for a `kustomization.yaml` file. If it finds one, {product-title} automatically runs the `kubectl apply -k` command to apply the manifests to the cluster.
 
 [IMPORTANT]
 ====
@@ -32,25 +31,25 @@ This example demonstrates automatic deployment of a BusyBox container using `kus
 .Procedure
 . Create the BusyBox manifest files by running the following commands:
 +
-* Define the directory location.
+.. Define the directory location:
 +
 [source,terminal]
 ----
 $ MANIFEST_DIR=/etc/microshift/manifests
 ----
 +
-* Make the directory by running the following command:
+.. Make the directory:
 +
 [source,terminal]
 ----
 $ sudo mkdir -p ${MANIFEST_DIR}
 ----
 +
-* Place the `yaml` file in the directory.
+.. Place the YAML file in the directory:
 +
 [source,terminal]
 ----
-$ sudo tee ${MANIFEST_DIR}/busybox.yaml &>/dev/null <<EOF
+$ sudo cat << EOF > ${MANIFEST_DIR}/busybox.yaml
 
 apiVersion: v1
 kind: Namespace
@@ -76,43 +75,43 @@ spec:
         command:
           - sleep
           - "3600"
+EOF
 ----
-// what are the "---" after name: busybox?
 .Procedure
 . Create the `kustomize` manifest files by running the following commands:
 +
-* Run the command to read and write the standard inputs.
-[source,terminal]
+.. Place the YAML file in the directory:
 +
+[source,terminal]
 ----
-$ sudo tee
+$ sudo cat << EOF > ${MANIFEST_DIR}/kustomization.yaml
 ----
-* Apply the `yaml` configuration.
+.. Apply the YAML configuration:
 +
 [source,terminal]
 ----
-$ {MANIFEST_DIR}/kustomization.yaml &>/dev/null
+$ {MANIFEST_DIR}/kustomization.yaml
 
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 namespace: busybox
+---
 resources:
   - busybox.yaml
 images:
   - name: BUSYBOX_IMAGE
     newName: registry.k8s.io/busybox
+EOF
 ----
 
-. Restart {product-title} to apply the manifests and verify that the BusyBox pod is running by running the following commands:
-+
-* Restart {product-title}.
+. Restart {product-title} to apply the manifests by running the following command:
 +
 [source,terminal]
 ----
 $ sudo systemctl restart microshift
 ----
 +
-* Apply the manifests and start the BusyBox pod.
+. Apply the manifests and start the BusyBox pod by running the following command:
 +
 [source,terminal]
 ----

modules/microshift-config-yaml.adoc

@@ -12,7 +12,7 @@ Configure your {product-title} using a YAML file. The values specified in your c
 [id="microshift-yaml-default_{context}"]
 == Default settings
 If you do not create a `config.yaml` file, the default values are used.
-// Q: what creates this default yaml?
+// Q: what creates the default yaml?
 // Q: can default file be modified? (instead of making a new one)
 
 .Default YAML file example