Update lvms-scaling-storage-of-clusters-using-rhacm.adoc

- Incorrect command in scaling up the storage of clusters by using RHACM documentation.
- Here is the documentation link:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/storage/configuring-persistent-storage#lvms-scaling-storage-of-clusters-using-rhacm_logical-volume-manager-storage 
- Command mentioned in step 2 of the procedure and example cr mentioned in the step 3 is incorrect.

Here is updated look:

2.  Edit the LVMCluster CR that you created using RHACM by running the following command
~~~
$ oc edit -f <file_name> -n <namespace> 1 
~~~

3. In the LVMCluster CR, add the path to the new device in the deviceSelector field.
Example LVMCluster CR
~~~
apiVersion: policy.open-cluster-management.io/v1
kind: ConfigurationPolicy
metadata:
  name: lvms
spec:
  object-templates:
     - complianceType: musthave
       objectDefinition:
         apiVersion: lvm.topolvm.io/v1alpha1
         kind: LVMCluster
         metadata:
           name: my-lvmcluster
           namespace: openshift-storage
         spec:
           storage:
             deviceClasses:
# ...
               deviceSelector: (1)
                 paths: (2)
                 - /dev/disk/by-path/pci-0000:87:00.0-nvme-1
                 optionalPaths: (3)
                 - /dev/disk/by-path/pci-0000:89:00.0-nvme-1
~~~

Author: prithvipatil97

modules/lvms-scaling-storage-of-clusters-using-rhacm.adoc

@@ -21,7 +21,7 @@ You can scale up the storage capacity of worker nodes on the clusters by using {
 +
 [source,terminal]
 ----
-$ oc edit -f <file_name> -ns <namespace> <1>
+$ oc edit -f <file_name> -n <namespace> <1>
 ----
 <1> Replace `<file_name>` with the name of the `LVMCluster` CR.
 
@@ -31,27 +31,27 @@ $ oc edit -f <file_name> -ns <namespace> <1>
 [source,yaml]
 ----
 apiVersion: policy.open-cluster-management.io/v1
-      kind: ConfigurationPolicy
-      metadata:
-        name: lvms
-      spec:
-        object-templates:
-           - complianceType: musthave
-             objectDefinition:
-               apiVersion: lvm.topolvm.io/v1alpha1
-               kind: LVMCluster
-               metadata:
-                 name: my-lvmcluster
-                 namespace: openshift-storage
-               spec:
-                 storage:
-                   deviceClasses:
+kind: ConfigurationPolicy
+metadata:
+  name: lvms
+spec:
+  object-templates:
+     - complianceType: musthave
+       objectDefinition:
+         apiVersion: lvm.topolvm.io/v1alpha1
+         kind: LVMCluster
+         metadata:
+           name: my-lvmcluster
+           namespace: openshift-storage
+         spec:
+           storage:
+             deviceClasses:
 # ...
-                     deviceSelector: <1>
-                       paths: <2>
-                       - /dev/disk/by-path/pci-0000:87:00.0-nvme-1
-                       optionalPaths: <3>
-                       - /dev/disk/by-path/pci-0000:89:00.0-nvme-1
+               deviceSelector: <1>
+                 paths: <2>
+                 - /dev/disk/by-path/pci-0000:87:00.0-nvme-1
+                 optionalPaths: <3>
+                 - /dev/disk/by-path/pci-0000:89:00.0-nvme-1
 # ...
 ----
 <1> Contains the configuration to specify the paths to the devices that you want to add to the LVM volume group.
@@ -66,4 +66,4 @@ You can specify the device paths in the `paths` field, the `optionalPaths` field
 After a device is added to the LVM volume group, it cannot be removed.
 ====
 
-. Save the `LVMCluster` CR.
+. Save the `LVMCluster` CR.