Merge branch 'rest-api' of github.com:leapfrogtechnology/coding-standards-convention into develop

Author: anishmanandhar

docs/rest-api/get.md

@@ -77,7 +77,7 @@ Use **GET requests** to retrieve resource representation/information only – an
 
 ### Response Header
 
-Specify `Content-type` header, and its should be `application/json` while returing json response, `application/xml` while returning xml response and so on.
+Specify `Content-type` header, and it should be `application/json` while returing json response, `application/xml` while returning xml response and so on.
 
 ### Response code and Results
 

docs/rest-api/patch.md

@@ -6,9 +6,9 @@ sidebar_label: Patch
 
 PATCH is used for **modify** capabilities. The PATCH request only needs to contain the changes to the resource, not the complete resource.
 
-This resembles PUT, but the body contains a set of instructions describing how a resource currently residing on the server should be modified to produce a new version.PATCH is neither safe nor idempotent. However, a PATCH request can be issued in such a way as to be idempotent, which also helps prevent bad outcomes from collisions between two PATCH requests on the same resource in a similar time frame. Collisions from multiple PATCH requests may be more dangerous than PUT collisions because some patch formats need to operate from a known base-point or else they will corrupt the resource. Clients using this kind of patch application should use a conditional request such that the request will fail if the resource has been updated since the client last accessed the resource. 
+This resembles PUT, but the body contains a set of instructions describing how a resource currently residing on the server should be modified to produce a new version.PATCH is neither safe nor idempotent. However, a PATCH request can be issued in such a way as to be idempotent, which also helps prevent bad outcomes from collisions between two PATCH requests on the same resource in a similar time frame. Collisions from multiple PATCH requests may be more dangerous than PUT collisions because some patch formats need to operate from a known base-point or else they will corrupt the resource. Clients using this kind of patch application should use a conditional request such that the request will fail if the resource has been updated since the client last accessed the resource.
 
-*PATCH request can usuallly be used to update the status of resource like from `pending` to `accepted`, `active`  to `expired`*
+*PATCH request can usually be used to update the status of resource like from `pending` to `accepted`, `active`  to `expired`*
 
 > * **/employees/{employee-id}**
 > * **/departments/{department-id}**