add notes/improve section formatting

Signed-off-by: Andrew Jandacek <[email protected]>

docs/user-guide/install-zowe-pswi-deployment.md

@@ -5,11 +5,18 @@
 
 After the portable software instance or software instance is registered in z/OSMF, you can use z/OSMF Deployments to install the product software and create the product data sets (global, CSI, target libraries, and distribution libraries) for the new software instance. The deployment jobs create a copy of the source product data sets to create the product target runtime environment. Creating a copy of the SMP/E target data sets keeps the SMP/E environment clean and separates the product runtime environment for maintenance activities. You can also perform z/OSMF workflows to customize the SMP/E data sets, mount UNIX System Services (USS) files if necessary, and configure the new software instance on the target system.
 
-To install Zowe PSWI using z/OSMF and make the product software available for use on a system by users and other programs, you need to define a new deployment. This step defines the SMP/E environment name and the prefix of the CSI data set in z/OSMF. Specify data set allocation parameters for all SMP/E data sets, target libraries, and distribution libraries.
+## Prerequisite - Define a new deployment
 
-To define a new deployment, complete the deployment checklist (specify the USS path, DSN, VOLSERs), and submit the deployment jobs through the z/OSMF user interface. When the deployment is complete, you have a source and target copy of the software.
+To install Zowe PSWI using z/OSMF and make the product software available for use on a system by users and other programs, you first need to define a new deployment. This step defines the SMP/E environment name and the prefix of the CSI data set in z/OSMF. Specify data set allocation parameters for all SMP/E data sets, target libraries, and distribution libraries.
 
-For more information about these tasks, see [Deploying software](https://www.ibm.com/docs/en/zos/2.4.0?topic=task-deploying-software) in the IBM documentation.
+To define a new deployment, complete the deployment checklist as specified in [Deploying software](https://www.ibm.com/docs/en/zos/2.4.0?topic=task-deploying-software) in the IBM documentation.
+Specify the following configuration elements:
+
+* UNIX System Services path (USS path) 
+* Data Set Name (DNS)
+* Volume Serial Numbers (VOLSERs)
+
+Then submit the deployment jobs through the z/OSMF user interface. When the deployment is complete, you have a source and target copy of the software.
 
 Subsequent product maintenance activities update the SMP/E environment without affecting your active product runtime environments. You can decide when to redeploy the maintenance-updated SMP/E target data sets to each of the product runtime environments.
 
@@ -62,8 +69,10 @@ Before installing, ensure the [z/OSMF requirements](install-zowe-pswi-address-re
 
    10. Specify the name and description of the new target software instance.
 
-        - All workflows that are mentioned in the previous steps are part of the PSWI.  
-        **Note:** You do not have to execute all workflows during PSWI provisioning in z/OSMF immediately.
+:::note Notes
+* All workflows that are mentioned in the previous steps are part of the PSWI.  
+* You do not have to execute all workflows during PSWI provisioning in z/OSMF immediately.
+:::
 
 The deployment process is complete. The new software instance is defined to z/OSMF. You are now ready to Import Product Information into z/OSMF before you install product maintenance.
 
@@ -72,7 +81,7 @@ The deployment process is complete. The new software instance is defined to z/OS
 ### Cleanup
 
 If there is a need to update the deployment settings such as the HLQ after a previour run, consider that the deployment process does not perform a full cleanup of the datasets.
-Before attempting it again, make sure the following datasets are deleted to avoid write conflicts:
+Before attempting deployment again, make sure the following datasets are deleted to avoid write conflicts:
 
 ```plaintext
 {TARGET_HLQ}.PRODUCT.ZOWE.V2.CSI
@@ -94,7 +103,16 @@ Before attempting it again, make sure the following datasets are deleted to avoi
 {TARGET_HLQ}.PRODUCT.ZOWE.V2.ZFS.#
 ```
 
-If deployment options must be modified and the JCL recreated, before doing so, check the original JCL for the temporary ZFS dataset name like `<user>.SWDEPL.<random_id>.ZFS` and delete it manually. The deployment job will be unable to clean it once it is recreated because the random id will change.
+If deployment options must be modified and the JCL recreated, first check the original JCL for the temporary ZFS dataset name.
+
+**Example:**
+`<user>.SWDEPL.<random_id>.ZFS`
+
+ Delete this name manually. 
+
+ :::note 
+ Note that the deployment job is unable to clean this data set name once this is recreated because the random id will change.
+ :::
 
 ### Resources