OSDU-API-Quick-start-guide.md

@@ -89,7 +89,7 @@ You have several options to obtain `refresh_token`. But in all cases you need to
 - Copy-paste CLIENT_ID and CLIENT_SECRET into the environmental variables in Postman. Make sure you are updating both `INITIAL VALUE` and `CURRENT VALUE`
 ![Image 5. Updating CLIEND_ID and CLIENT_SECRET in the Postman environment variables](uploads/f984c539a3ade847147ad3872a171e7c/image009.png)
 
-#### Obtaining `refresh_token` via Postman UI
+#### Option1 (Simple): Obtaining `refresh_token` via Postman UI
 
 Refer to [Postman authentication guide](https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M16/GCP-M16/Postman_Authentication_Guide.md).
 
@@ -143,7 +143,7 @@ Press `Use Token` button. Your just created token become active and switch `Auto
 
 ![current token](./uploads/qsg-img/postman-current_token.png)
 
-Save the environment.
+Save the environment and collection.
 
 Now you just need to ensure that `Authorization` for all requests and folders in collection are set to `Inherit auth from parent` and Postman will refresh token for you when needed
 
@@ -151,7 +151,7 @@ Now you just need to ensure that `Authorization` for all requests and folders in
 
 You could still use `Refresh Token` requests from Postman collection to get new access tokens manually.
 
-#### Obtaining `refresh_token` via Google OAuth 2.0 Playground
+#### Option 2 (Legacy):  Obtaining `refresh_token` via Google OAuth 2.0 Playground
 
 - Open [OAuth 2.0 Playground](https://developers.google.com/oauthplayground)