Skip to content

Commit d730c4e

Browse files
authored
Merge pull request #128336 from jeremytcorp/patch-1
Fix typos in async operations documentation
2 parents ead4a71 + 3fcd097 commit d730c4e

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/azure-resource-manager/management/async-operations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ After getting the 201 or 202 response code, you're ready to monitor the status o
2929

3030
## URL to monitor status
3131

32-
There are two different ways to monitor the status the asynchronous operation. You determine the correct approach by examining the header values that are returned from your original request. First, look for:
32+
There are two different ways to monitor the status of the asynchronous operation. You determine the correct approach by examining the header values that are returned from your original request. First, look for:
3333

3434
* `Azure-AsyncOperation` - URL for checking the ongoing status of the operation. If your operation returns this value, use it to track the status of the operation.
3535
* `Retry-After` - The number of seconds to wait before checking the status of the asynchronous operation.
@@ -213,7 +213,7 @@ GET
213213
https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.Storage/operations/{operation-id}?monitor=true&api-version=2019-06-01
214214
```
215215

216-
If the request is still running, you receive a status code 202. If the request is completed, your receive a status code 200. The body of the response contains the properties of the storage account that was created.
216+
If the request is still running, you receive a status code 202. If the request is completed, you receive a status code 200. The body of the response contains the properties of the storage account that was created.
217217

218218
## Next steps
219219

0 commit comments

Comments
 (0)