Merge pull request #171506 from v-hearya/Broken-link-fixes-vargupt-Sep06

Image Urls updated

Author: PRMerger10

articles/virtual-machines/capacity-reservation-overview.md

@@ -133,7 +133,7 @@ Capacity Reservation doesn’t create limits on the number of VM deployments. Az
 
 When a reservation is created, Azure sets aside the requested number of capacity instances in the specified location: 
 
-![Capacity Reservation image 1.](\media\capacity-reservation-overview\capacity-reservation-1.jpg) 
+![Capacity Reservation image 1.](./media/capacity-reservation-overview/capacity-reservation-1.jpg) 
 
 Track the state of the overall reservation through the following properties:  
 - `capacity` = Total quantity of instances reserved by the customer 
@@ -144,31 +144,31 @@ The above example will start with `capacity` as 2 and length of `virutalMachines
 
 When a VM is then allocated against the Capacity Reservation, it will logically consume one of the reserved capacity instances: 
 
-![Capacity Reservation image 2.](\media\capacity-reservation-overview\capacity-reservation-2.jpg) 
+![Capacity Reservation image 2.](./media/capacity-reservation-overview/capacity-reservation-2.jpg) 
 
 The status of the Capacity Reservation will now show `capacity` as 2 and length of `virutalMachinesAllocated` and `virtualMachinesAssociated` as 1.  
 
 Allocations against the Capacity Reservation will succeed as along as the VMs have matching properties and there is at least one empty capacity instance.  
 
 Using our example, when a third VM is allocated against the Capacity Reservation, the reservation enters the [overallocated](capacity-reservation-overallocate.md) state. This third VM will require unused quota and extra capacity fulfillment from Azure. Once the third VM is allocated, the Capacity Reservation now looks like this: 
 
-![Capacity Reservation image 3.](\media\capacity-reservation-overview\capacity-reservation-3.jpg) 
+![Capacity Reservation image 3.](./media/capacity-reservation-overview/capacity-reservation-3.jpg) 
 
 The `capacity` is 2 and the length of `virutalMachinesAllocated` and `virtualMachinesAssociated` is 3. 
 
 Now suppose the application scales down to the minimum of two VMs. Since VM 0 needs an update, it's chosen for deallocation. The reservation automatically shifts to this state: 
 
-![Capacity Reservation image 4.](\media\capacity-reservation-overview\capacity-reservation-4.jpg) 
+![Capacity Reservation image 4.](./media/capacity-reservation-overview/capacity-reservation-4.jpg) 
 
 The `capacity` and the length of `virtualMachinesAllocated` are both 2. However, the length for `virtualMachinesAssociated` is still 3 as VM 0, though deallocated, is still associated with the capacity reservation.  
 
 The Capacity Reservation will exist until explicitly deleted. To delete a Capacity Reservation, the first step is to dissociate all the VMs in the `virtualMachinesAssociated` property. Once disassociation is complete, the Capacity Reservation should look like this: 
 
-![Capacity Reservation image 5.](\media\capacity-reservation-overview\capacity-reservation-5.jpg) 
+![Capacity Reservation image 5.](./media/capacity-reservation-overview/capacity-reservation-5.jpg) 
 
 The status of the Capacity Reservation will now show `capacity` as 2 and length of `virtualMachinesAssociated` and `virtualMachinesAllocated` as 0. From this state, the Capacity Reservation can be deleted. Once deleted, you'll not pay for the reservation anymore.  
 
-![Capacity Reservation image 6.](\media\capacity-reservation-overview\capacity-reservation-6.jpg)
+![Capacity Reservation image 6.](./media/capacity-reservation-overview/capacity-reservation-6.jpg)
 
 
 ## Usage and billing 
@@ -179,13 +179,13 @@ When a Capacity Reservation is empty, VM usage will be reported for the correspo
 
 For example, let's say a Capacity Reservation with quantity reserved 2 has been created. The subscription has access to one matching Reserved VM Instance of the same size. The result is two usage streams for the Capacity Reservation, one of which is covered by the Reserved Instance: 
 
-![Capacity Reservation image 7.](\media\capacity-reservation-overview\capacity-reservation-7.jpg)
+![Capacity Reservation image 7.](./media/capacity-reservation-overview/capacity-reservation-7.jpg)
 
 In the image above, a Reserved VM Instance discount is applied to one of the unused instances and the cost for that instance will be zeroed out. For the other instance, PAYG rate will be charged for the VM size reserved.  
 
 When a VM is allocated against the Capacity Reservation, the other VM components such as disks, network, extensions, and any other requested components must also be allocated. In this state, the VM usage will reflect one allocated VM and one unused capacity instance. The Reserved VM Instance will zero out the cost of either the VM or the unused capacity instance. The other charges for disks, networking, and other components associated with the allocated VM will also appear on the bill. 
 
-![Capacity Reservation image 8.](\media\capacity-reservation-overview\capacity-reservation-8.jpg)
+![Capacity Reservation image 8.](./media/capacity-reservation-overview/capacity-reservation-8.jpg)
 
 In the image above, the VM Reserved Instance discount is applied to VM 0, which will only be charged for other components such as disk and networking. The other unused instance is being charged at PAYG rate for the VM size reserved.
 
@@ -218,4 +218,4 @@ In the image above, the VM Reserved Instance discount is applied to VM 0, which
 Create a Capacity Reservation and start reserving Compute capacity in an Azure region or an Availability Zone. 
 
 > [!div class="nextstepaction"]
-> [Create a Capacity Reservation](capacity-reservation-create.md)
+> [Create a Capacity Reservation](capacity-reservation-create.md)