Update Blog “getting-started-with-hpe-greenlake-api-for-backup-and-recovery”

Author: rondharma

content/blog/getting-started-with-hpe-greenlake-api-for-backup-and-recovery.md

@@ -123,7 +123,7 @@ Here is the list of the steps required to perform this use case using HPE Gre
 
 ![Discover deployed StoreOnce to create cloud protection store](/img/api-discover-storeonce.png)
 
-2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using the HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/operation/ListLocations/) for Data Services API set. Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I the copied value `"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
+2. Next, I discovered the cloud storage at the correct location from the list of the available storage location and copy the `storageLocationId` as shown in below JSON response body. The discovery was done by using the HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/operation/ListLocations/) for Data Services API set. Note from the below figure that I used filter `“backup-and-recovery”` in capabilities to capture selected storage locations with the correct capability. The below figure shows information about the location (region) where the data will be stored; conversely, it’s located at `“Richmond”`, cloud service provide was `“AZURE”`, and cloud services provider identification is `“eastus2”`. I the copied value `"azure:eastus2"` from the key `id` of this API's response body as the `storageLocationID` value. The API used for this: `GET /data-services/v1beta1/storage-locations?filter=”backup-and-recovery” in capabilities`.
 
 ![API to figure out the Azure storage location](/img/figure-out-storage-location.png)
 
@@ -424,7 +424,7 @@ Next in the list of use cases for this blog post, I followed the progression for
 
 These are the steps required to apply the protection policy against a virtual machine:
 
-1. I obtained the values from `virtual machine id, name, and type` keys that were going to be used as the key-pair values required for the key `assetInfo` as shown in below figures. To obtain those, I used the HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/virtualization/public/openapi/virtualization-public-v1beta1/operation/VirtualMachinesList/) for Virtualization to discover the detail information of a virtual machine `“0-Linux-Demo-VM02”`. The API used for this: 
+1. I obtained the values from `virtual machine id, name, and type` keys that were going to be used as the key-pair values required for the key `assetInfo` as shown in below figures. To obtain those, I used one of the HPE GreenLake [API](https://developer.greenlake.hpe.com/docs/greenlake/services/virtualization/public/openapi/virtualization-public-v1beta1/operation/VirtualMachinesList/) from Virtualization API set to discover the detail information of a virtual machine `“0-Linux-Demo-VM02”`. The API used for this: 
 
    ```shellsession
    GET /virtualization/v1beta1/virtual-machines?sort=name desc& select=appType,id,name,type,guestInfo,protectionJobInfo& filter=name eq '0-Linux-Demo-VM02'