Skip to content

Commit 3b04afe

Browse files
committed
Update Blog “converting-hpe-greenlake-api-specifications-in-oas-3-1-using-openapi-tools”
1 parent dd06969 commit 3b04afe

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/blog/converting-hpe-greenlake-api-specifications-in-oas-3-1-using-openapi-tools.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ Let me give you an example of converting the HPE GreenLake API for Data Services
142142

143143
1. I downloaded the HPE GreenLake API for Data Services OpenAPI Standard 3.1 spec file from the HPE GreenLake Developer website using the UI:
144144

145-
![Download OpenAPI 3.1 JSON spec file from HP GL Data Services](/img/download-the-openapi-3.1-spec-data-services-from-developer-website.png)
145+
![Download OpenAPI 3.1 JSON spec file from HP GreenLake Data Services](/img/download-the-openapi-3.1-spec-data-services-from-developer-website.png)
146146

147147
2. Afterward, I changed the name of the downloaded file from `swagger.json` to `GL-dataservices-31.json` so that I could recognize this OpenAPI Standard 3.1 spec file from HPE GreenLake APIs for Data Services.
148148
3. After I renamed the JSON file, I followed by using the `openapi-down-convert` tool to convert the OpenAPI Standard 3.1 to OpenAPI Standard 3.0 using the following command shown below. I named the converted file as `GL-dataservices-30.json`.

0 commit comments

Comments
 (0)