Skip to content

Commit 3241eff

Browse files
committed
Update Blog “getting-started-with-hpe-greenlake-api-for-data-services”
1 parent 81fd3ca commit 3241eff

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

content/blog/getting-started-with-hpe-greenlake-api-for-data-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Paste the valid access token into the **Bearer Token** using Ctrl-v (short cut i
6767

6868
![](/img/send-the-api-after-token-entered.png)
6969

70-
Click the **Send** button to execute that API and you will see the response page indicating a good status (**Status: 0x200**). Finish up by clicking on the **Body: Expand All** button to display the completed response body in JSON.
70+
Click the **Send** button to execute that API and you will see the response page indicating a good status (`Status: 0x200`). Finish up by clicking on the **Body: Expand All** button to display the completed response body in JSON.
7171

7272
![](/img/response-from-the-tryit-test.png)
7373

@@ -120,7 +120,7 @@ Following the above recommendation, the following request body shows where I ent
120120

121121
The completed execution of this API is shown below.
122122

123-
![Response from issues with the correct select](/img/execution-result-from-active-issues.png)
123+
![Response from issues with the correct select](/img/api-response-with-select-for-active-issues.png)
124124

125125
*The above figure shows the output from GET issues given the parameter: `select=body,createdAt,customerId,generation,id,lastOccuredAt,resourceURI,type,updatedAt`.*
126126

333 KB
Loading

0 commit comments

Comments
 (0)