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

@@ -20,7 +20,7 @@ This set of APIs provides the capability for manipulating resources made availab
 
 There will be more resources added into this set of APIs in the future releases that will cover *cloud service providers, and cloud assets*. For more information on how to use this HPE GreenLake for Backup and Recovery service, please visit the [website ](https://www.hpe.com/us/en/hpe-greenlake-backup-recovery.html)and the getting started [guide](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sd00003454en_us).
 
-The specification of this API is publicized as an OpenAPI specification in JSON format, and the specification is available for download from this [section](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/guide/) of the documentation (shown below). The specification follows the OpenAPI standard 3.1, and it contains all required information so that this JSON file can be consumed by any OpenAPI tools to provide client library, server mock, or documentation as described in this [OpenAPI ](https://tools.openapis.org/)Initiative.
+The specification of this API is publicized as an OpenAPI specification in JSON format, and the specification is available for download from this [section](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/guide/) of the documentation (shown below). The specification follows the OpenAPI Specification v3.1, and it contains all required information so that this JSON file can be consumed by any OpenAPI tools to provide client library, server mock, or documentation as described in this [OpenAPI ](https://tools.openapis.org/)Initiative.
 
 > **NOTE:** 
 > There are two different sets of OpenAPI specs that are downloadable from the documentation page of the Backup and Recovery in the March 2024 release. The two sets represent the two versions of Backup and Recovery APIs that were made available for separate resources, namely **hypervisor-managers** and **the rest of other resources** as shown in this picture below. To get into the page for downloading each of the OpenAPI specification file, scroll through the left windows and select the appropriate API version page.
@@ -432,7 +432,7 @@ These are the steps required to apply the protection policy against a virt
 
 ![API to find virtual-machines and it's properties](/img/api-find-virtual-machines.png)
 
-2. I created a JSON structure of a request body for applying the protection policy against a virtual machine without a protection group to make a simple example for this blog post. Note that this JSON body structure created the association of the asset, which is a virtual machine, against the protection policy. The two other parameters entered here were the consistency `(CRASH vs APPLICATION)` and technology for protection `(VMWARE_CBT vs VOLUME)`. The three values obtained from previous response of the previous API `POST /backup-recovery/v1beta1/protection-policies` associated with SNAPSHOT, BACKUP and CLOUD would be used as part of this request body. Each of these protections will be identified with schedule id marked 1,2 and 3 as shown below. There are other options available as part of this JSON structure of this request body, and they are documented in the Payload tab of this interactive guide for this [API](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/openapi/backup-recovery-public-v1beta1/operation/DataManagementJobCreate/).
+2. I created a JSON structure of a request body for applying the protection policy against a virtual machine without a protection group to make a simple example for this blog post. **Note** that this JSON body structure created the association of the asset, which is a virtual machine, against the protection policy. The two other parameters entered here were the consistency `(CRASH vs APPLICATION)` and technology for protection `(VMWARE_CBT vs VOLUME)`. The three values obtained from previous response of the previous API `POST /backup-recovery/v1beta1/protection-policies` associated with SNAPSHOT, BACKUP and CLOUD would be used as part of this request body. Each of these protections will be identified with schedule id marked 1,2 and 3 as shown below. There are other options available as part of this JSON structure of this request body, and they are documented in the Payload tab of this interactive guide for this [API](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/openapi/backup-recovery-public-v1beta1/operation/DataManagementJobCreate/).
 
 > **Note:** As of March 2024, value of `type` from `virtualization/virtual-machine` was translated to `hybrid-cloud/virtual-machine.`
 >
@@ -596,7 +596,7 @@ Each of the recovery points, regardless of the location of store (array snapshot
 
 ## Summary
 
-This blog post introduces the new set of REST API from the family of the APIs for data services on HPE Greenlake, namely **HPE GreenLake API for Backup and Recovery**. This set of APIs is documented at the HPE GreenLake for developer [website](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/) using interactive documentation based on OpenAPI version 3.1. 
+This blog post introduces the new set of REST API from the family of the APIs for data services on HPE Greenlake, namely **HPE GreenLake API for Backup and Recovery**. This set of APIs is documented at the HPE GreenLake for developer [website](https://developer.greenlake.hpe.com/docs/greenlake/services/backup-recovery/public/) using interactive documentation based on OpenAPI Specification version 3.1. 
 
 Early in this blog post, I laid down the relationship of the resources in this set of HPE GreenLake APIs with the objects in the HPE GreenLake Backup and Recovery user interface. In this blog post, I also introduced the examples from several use cases associated with utilizing HPE GreenLake for Backup and Recovery to provide virtual machine protection from day one.