Fixes per editoring

Author: anaharris-ms

articles/azure-maps/creator-long-running-operation-v2.md

@@ -1,9 +1,9 @@
 ---
-title: Azure Maps Long-Running Operation API V2
+title: Azure Maps long-running operation API V2
 description: Learn about long-running asynchronous V2 background processing in Azure Maps
 author: anastasia-ms 
 ms.author: v-stharr 
-ms.date: 05/12/2020
+ms.date: 05/18/2021
 ms.topic: conceptual 
 ms.service: azure-maps 
 services: azure-maps 
@@ -15,7 +15,7 @@ ms.custom: mvc
 
 Some APIs in Azure Maps use an [Asynchronous Request-Reply pattern](/azure/architecture/patterns/async-request-reply). This pattern allows Azure Maps to provide highly available and responsive services. This article explains Azure Map's specific implementation of long-running asynchronous background processing.
 
-## Submitting a request
+## Submit a request
 
 A client application starts a long-running operation through a synchronous call to an HTTP API. Typically, this call is in the form of an HTTP POST request. When an asynchronous workload is successfully created, the API will return an HTTP `202` status code, indicating that the request has been accepted. This response contains a `Location` header pointing to an endpoint that the client can poll to check the status of the long-running operation.
 
@@ -29,7 +29,7 @@ Operation-Location: https://atlas.microsoft.com/service/operations/{operationId}
 
 If the call doesn't pass validation, the API will instead return an HTTP `400` response for a Bad Request. The response body will provide the client more information on why the request was invalid.
 
-### Monitoring the operation status
+### Monitor the operation status
 
 The location endpoint provided in the accepted response headers can be polled to check the status of the long-running operation. The response body from operation status request will always contain the `status` and the `created` properties. The `status` property shows the current state of the long-running operation. Possible states include `"NotStarted"`, `"Running"`, `"Succeeded"`, and `"Failed"`. The `created` property shows the time the initial request was made to start the long-running operation. When the state is either `"NotStarted"` or `"Running"`, a `Retry-After` header will also be provided with the response. The `Retry-After` header, measured in seconds, can be used to determine when the next polling call to the operation status API should be made.
 
@@ -45,7 +45,7 @@ Retry-After: 30
 }
 ```
 
-## Handling operation completion
+## Handle operation completion
 
 Upon completing the long-running operation, the status of the response will either be `"Succeeded"` or `"Failed"`. All responses will return an HTTP 200 OK code. When a new resource has been created from a long-running operation, the response will also contain a `Resource-Location` header that points to metadata about the resource. Upon a failure, the response will have an `error` property in the body. The error data adheres to the OData error specification.