fixing copy issues

Author: klgill

docs_user/modules/proc_completing-prerequisites-for-migrating-ceph-monitoring-stack.adoc

@@ -21,7 +21,6 @@ ifeval::["{build}" != "upstream"]
 For more information about assigning labels to nodes, review the Red Hat Knowledgebase article https://access.redhat.com/articles/1548993[Red Hat Ceph Storage: Supported configurations].
 endif::[]
 +
-[source,yaml]
 ----
 [tripleo-admin@controller-0 ~]$ sudo cephadm shell -- ceph orch host ls
 
@@ -46,7 +45,6 @@ In case the desired option is to rely on the https://github.com/ceph/ceph/blob/r
 shipped by cephadm, remove the following config options from the {CephCluster} cluster.
 endif::[]
 +
-[source,yaml]
 ----
 $ ceph config dump
 ...
@@ -69,10 +67,9 @@ endif::[]
 
 . Remove the undercloud container images:
 +
-[source,yaml]
 ----
-$ cephadm shell -- ceph config rm mgr mgr/cephadm/container_image_base
-for i in prometheus grafana alertmanager node_exporter; do
-    cephadm shell -- ceph config rm mgr mgr/cephadm/container_image_$i
+$ cephadm shell -- ceph config rm mgr mgr/cephadm/container_image_base \
+for i in prometheus grafana alertmanager node_exporter; do \
+    cephadm shell -- ceph config rm mgr mgr/cephadm/container_image_$i \
 done
 ----

docs_user/modules/proc_completing-prerequisites-for-migrating-ceph-rgw.adoc

@@ -10,7 +10,6 @@ Complete the following prerequisites before you begin the Ceph Object Gateway (R
 
 . Check the current status of the {Ceph} nodes:
 +
-[source,yaml]
 ----
 (undercloud) [stack@undercloud-0 ~]$ metalsmith list
 
@@ -48,7 +47,6 @@ Full List of Resources:
 
 . Identify the ranges of the storage networks. The following is an example and the values might differ in your environment:
 +
-[source,yaml]
 ----
 [heat-admin@controller-0 ~]$ ip -o -4 a
 
@@ -95,7 +93,6 @@ listen ceph_rgw
 
 .. Confirm that the network is used as an HAProxy front end. The following example shows that `controller-0` exposes the services by using the external network, which is absent from the {Ceph} nodes. You must propagate the external network through {OpenStackPreviousInstaller}:
 +
-[source,yaml]
 ----
 [controller-0]$ ip -o -4 a
 
@@ -111,7 +108,6 @@ If the target nodes are not managed by director, you cannot use this procedure t
 
 .. In the NIC template that you use to define the `ceph-storage` network interfaces, add the new config section in the {Ceph} network configuration template file, for example, `/home/stack/composable_roles/network/nic-configs/ceph-storage.j2`:
 +
-[source,yaml]
 ----
 ---
 network_config:
@@ -157,7 +153,6 @@ network_config:
 [NOTE]
 Ensure that 'network_config_update' is enabled for network propagation to the target nodes when `os-net-config` is triggered.
 +
-[source,yaml]
 ----
 - name: CephStorage
   count: 3
@@ -184,11 +179,8 @@ Ensure that 'network_config_update' is enabled for network propagation to the ta
 
 .. Configure the new network on the bare metal nodes:
 +
-[source,yaml]
 ----
-(undercloud) [stack@undercloud-0]$
-
-openstack overcloud node provision
+(undercloud) [stack@undercloud-0]$ openstack overcloud node provision \
    -o overcloud-baremetal-deployed-0.yaml \
    --stack overcloud \
    --network-config -y \
@@ -197,7 +189,6 @@ openstack overcloud node provision
 
 .. Verify that the new network is configured on the {CephCluster} nodes:
 +
-[source,yaml]
 ----
 [root@cephstorage-0 ~]# ip -o -4 a