fixed wrapping and file naming convention

Author: albecker1

includes/managed-disks-bursting-2.md

@@ -17,7 +17,9 @@ The following scenarios can benefit greatly from bursting:
 
 ## Bursting flow
 The bursting credit system applies in the same manner at both the virtual machine level and disk level. Your resource, either a VM or disk, will start with fully stocked credits. These credits will allow you to burst for 30 minutes at the maximum burst rate. Bursting credits accumulate when your resource is running under their provisioned disk storage limits. For all IOPS and MB/s that your resource is using below the provisioned limit you begin to accumulate credits. If your resource has accrued credits to use for bursting and your workload needs the extra performance, your resource can use those credits to go above your provisioned limit to give it the disk IO performance it needs to meet the demand.
-![Bursting bucket Diagram](media/managed-disks-bursting/Bucket-Diagram.jpg)
+
+![Bursting bucket Diagram](media/managed-disks-bursting/bucket-diagram.jpg)
+
 One thing to note about burst accumulation is that it is different for each resource since it is based on the unused IOPS and MB/s below their provisioned amounts. This means that higher baseline performance products can accrue their bursting amounts faster than lower baseline performing products. For example, a P1 disk idling with no activity will accrue 120 IOPS per second whereas a P20 disk accrues 2,300 IOPS per second while idling with no activity.
 
 ## Bursting states
@@ -41,12 +43,17 @@ The following examples show how bursting works with various virtual machine and
     - Max burst MB/s: 170
 
  When the VM boots up it will retrieve data from the OS disk. Since the OS disk is part of a VM that is getting started, the OS disk will be full of bursting credits. These credits will allow the OS disk burst its startup at 170 MB/s second as seen below:
+
 ![Non-bursting vm bursting disk startup](media/managed-disks-bursting/nonbursting-vm-busting-disk/nonbusting-vm-bursting-disk-startup.jpg)
 
 After the boot up is complete, an application is then run on the VM and has a non-critical workload. This workload requires 15 MB/S that gets spread evenly across all the disks:
-![Non-bursting vm bursting disk idle](media/managed-disks-bursting/nonbursting-vm-busting-disk/nonbusting-vm-bursting-disk-idiling.jpg)
+
+![Non-bursting vm bursting disk idle](media/managed-disks-bursting/nonbursting-vm-busting-disk/nonbusting-vm-bursting-disk-idling.jpg)
+
 Then the application needs to process a batched job that requires 192 MB/s. 2 MB/s are used by the OS Disk and the rest are evenly split between the data disks:
+
 ![Non-bursting vm bursting disk bursting](media/managed-disks-bursting/nonbursting-vm-busting-disk/nonbusting-vm-bursting-disk-bursting.jpg)
+
 ### Burstable virtual machine with non-burstable disks
 **VM and disk combination:** 
 - Standard_L8s_v2 
@@ -59,7 +66,9 @@ Then the application needs to process a batched job that requires 192 MB/s. 2 MB
 
  After the initial boot up, an application is run on the VM and has a non-critical workload. This workload requires 30 MB/s that gets spread evenly across all the disks:
 ![Bursting vm non-bursting disk idle](media/managed-disks-bursting/bursting-vm-nonbursting-disk/burst-vm-nonbursting-disk-normal.jpg)
+
 Then the application needs to process a batched job that requires 600 MB/s. The Standard_L8s_v2 bursts to meet this demand and then requests to the disks get evenly spread out to P50 disks:
+
 ![Bursting vm non-bursting disk bursting](media/managed-disks-bursting/bursting-vm-nonbursting-disk/burst-vm-nonbursting-disk-bursting.jpg)
 ### Burstable virtual machine with burstable Disks
 **VM and disk combination:** 
@@ -74,8 +83,13 @@ Then the application needs to process a batched job that requires 600 MB/s. The
     - Max burst MB/s: 170 
 
 When the VM boots up, it will burst to request its burst limit of 1,280 MB/s from the OS disk and the OS disk will respond with its burst performance of 170 MB/s:
+
 ![Bursting vm bursting disk startup](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-startup.jpg)
+
 Then after the boot up is complete, an application is then run on the VM. The application has a non-critical workload that requires 15 MB/s that gets spread evenly across all the disks:
-![Bursting vm bursting disk idle](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-idiling.jpg)
+
+![Bursting vm bursting disk idle](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-idling.jpg)
+
 Then the application needs to process a batched job that requires 360 MB/s. The Standard_L8s_v2 bursts to meet this demand and then requests. Only 20 MB/s are needed by the OS disk. The remaining 340 MB/s are handled by the bursting P4 data disks:  
+
 ![Bursting vm bursting disk bursting](media/managed-disks-bursting/bursting-vm-bursting-disk/burst-vm-burst-disk-bursting.jpg)