addressing review feedback

Author: WilliamAntonRohm

docs/relational-databases/indexes/columnstore-indexes-data-loading-guidance.md

@@ -92,9 +92,9 @@ SELECT col1 /* include actual list of columns in place of col1*/
 FROM [<Staging Table>]
 ```  
 
- There are following optimizations available when loading into clustered columnstore index from staging table:
--   **Log Optimization:** Reduced logging when the data is loaded into compressed rowgroup.   
--   **Locking Optimization:** When loading into compressed rowgroup, the X lock on rowgroup is acquired. However, with delta rowgroup, an X lock is acquired at rowgroup but [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] still locks the locks PAGE/EXTENT because X rowgroup lock is not part of locking hierarchy.  
+ There are following optimizations available when loading into a clustered columnstore index from staging table:
+-   **Log Optimization:** Reduced logging when the data is loaded into a compressed rowgroup.   
+-   **Locking Optimization:** When loading into a compressed rowgroup, the X lock on rowgroup is acquired. However, with delta rowgroup, an X lock is acquired at rowgroup but [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] still locks the locks PAGE/EXTENT because X rowgroup lock is not part of locking hierarchy.  
 
  If you have one or more nonclustered indexes, there is no locking or logging optimization for the index itself, but the optimizations on the clustered columnstore index as described above are still there.