Update README

Adjusted Scenario description

Author: SQLBek

demos-sdk2/VMFS-VMDK Snapshot/README.md

@@ -4,22 +4,22 @@
 <!-- /wp:separator -->
 
 # Scenario:
-Production SQL Server & database(s) reside on a VMFS datastore.  Non-production SQL Server resides on 
-a different VMFS datastore.  User database(s) data and log files reside on two different VMDK disks 
-in each datastore.
-<BR><BR>
-Each datastore also resides on a different FlashArray, to demonstrate use of async snapshot replication.
-<BR><BR>
 This example is for a repeatable refresh scenario, such as a nightly refresh of a production database on
 another non-production SQL Server.
 <BR><BR>
+Production SQL Server & database(s) reside on a VMFS datastore.  Non-production SQL Server resides on 
+a different VMFS datastore.  User database(s) data and log files reside on two different VMDK disks 
+in each datastore.  This workflow is intended to only be impact select Windows Disks/VMDKs that contain user 
+databases.  Each datastore also resides on a different FlashArray, to demonstrate use of async snapshot 
+replication.
+<BR><BR>
 This example's workflow takes an on-demand snapshot of the Production datastore and async replicates it to
 the second FlashArray.  Then the snapshot is cloned as a new temporary volume/datastore.  The VMDKs with the
 production database files, residing on the temporary cloned datastore are attached to the target SQL Server,
 replacing the prior VMDKs that stored the database files previously.  Finally Storage vMotion is used to
 migrate the VMDKs to the non-production datastore, then the temporary cloned datastore is discarded.
 <BR><BR>
-This workflow is intended to only be impact select Windows Disks/VMDKs that contain user databases.  
+
 
 # Disclaimer:
 This example script is provided AS-IS and is meant to be a building block to be adapted to fit an individual organization's  infrastructure.
@@ -37,3 +37,4 @@ _The contents of the repository are intended as examples only and should be modi
 
 
 
+