minor changes

Author: AbhishekMallick01

articles/backup/restore-postgresql-database-use-rest-api.md

@@ -56,7 +56,7 @@ GET https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
 
 #### Responses for list of recovery points
 
-Once you submit the *GET* request, this returns response as 200 (OK), and the list of all discrete recovery points with all the relevant details.
+Once you submit the `GET` request, this returns response as 200 (OK), and the list of all discrete recovery points with all the relevant details.
 
 |Name  |Type  |Description  |
 |---------|---------|---------|
@@ -226,7 +226,7 @@ For an archive-based recovery point, you need to:
 
 #### Restore as files
 
-Fetch the URI of the container, within the storage account to which permissions were assigned as detailed [above](#set-up-permissions). For example, a container named **testcontainerrestore** under a storage account **testossstorageaccount** with a different subscription.
+Fetch the URI of the container, within the storage account to which permissions were assigned as detailed [above](#set-up-permissions). For example, a container named `testcontainerrestore` under a storage account `testossstorageaccount` with a different subscription.
 
 ```http
 "https://testossstorageaccount.blob.core.windows.net/testcontainerrestore"
@@ -342,7 +342,7 @@ We have constructed a section of the same in the [above section](#create-a-reque
 
 ##### Response to validate restore requests
 
-The _validate restore request_ is an [asynchronous operation](../azure-resource-manager/management/async-operations.md). So, this operation creates another operation that you need to track separately.
+The `validate restore request` is an [asynchronous operation](../azure-resource-manager/management/async-operations.md). So, this operation creates another operation that you need to track separately.
 
 It returns two responses: 202 (Accepted) when another operation is created. Then 200 (OK) when that operation completes.