final steps

Author: jjaygbay

articles/azure-large-instances/faq.md

@@ -52,8 +52,7 @@ Customers are responsible for any additional third-party agents that they would
 
 It’s also recommended to rerun Azure Large Instances GenIO test post third-party agents are installed to check for any performance variations.
 
-For more information, see “Shared Responsibility Model"
-## How will I get notified if there's any issue with our Azure Large Instances resource? How Microsoft communicates unplanned issues?
+## How will I get notified if there's any issue with our Azure Large Instances resource? How does Microsoft communicate unplanned issues?
 
 Microsoft sends service health notification only through the Azure portal.
 We always recommend customers to configure alerts for service health notifications.  

articles/azure-large-instances/toc.yml

@@ -10,7 +10,7 @@
   items:
   - name: Onboarding requirements
     href: onboarding-requirements.md
-  - name: Quality checks ofAzure Large Instances
+  - name: Quality checks of Azure Large Instances
     href: quality-checks.md
   - name: Find your subscription ID
     href: find-your-subscription-id.md

articles/azure-large-instances/workloads/epic/create-a-volume-group.md

@@ -44,9 +44,9 @@ Expected output: lists all the logical volumes created.
 ```
 
 > [!Note]
- - `-L 45T` specifies the  logical volume size.  
- - `-i 32` specifies the number of stripes, this is equal to the number of physical LUNs to scatter the logical volume.  
- - `-I 8M` specifies the stripe size.
+ > - `-L 45T` specifies the  logical volume size.  
+ > - `-i 32` specifies the number of stripes, this is equal to the number of physical LUNs to scatter the logical volume.  
+ > - `-I 8M` specifies the stripe size.
 
 5. Make the file system