Update validate-document-creator.md

Acrolinx fixes to bring the overall Acrolinx score to at least 80

Author: AnnaMHuff

articles/azure-fluid-relay/how-tos/validate-document-creator.md

@@ -9,11 +9,11 @@ fluid.url: https://fluidframework.com/docs/apis/azure-client/itokenprovider/
 
 # How to: Validate a user who created a container
 
-When you create a container in Azure Fluid Relay, the JWT provided by the ITokenProvider for the creation request can only be used once. After creating a container, the client must generate a new JWT that contains the document ID (which is really the container ID) provided by the service at creation time. If an application has an authorization service that manages container access control, it will need to know who created a container with a given ID in order to authorize the generation of a new JWT for access to that container.
+When you create a container in Azure Fluid Relay, the JWT provided by the ITokenProvider for the creation request can only be used once. After creating a container, the client must generate a new JWT that contains the document ID (which is really the container ID) provided by the service at creation time. If an application has an authorization service that manages container access control, it needs to know who created a container with a given ID in order to authorize the generation of a new JWT for access to that container.
 
 ## Inform an authorization service when a container is created
 
-An application can tie into the container creation lifecycle by implementing a public documentPostCreateCallback() method in its `TokenProvider`. (The name of this function can be confusing. It is really a callback for post *container* creation.) This callback will be triggered directly after creating the container, before a client requests the new JWT it needs to gain read/write permissions to the container that was created.
+An application can tie into the container creation lifecycle by implementing a public documentPostCreateCallback() method in its `TokenProvider`. (The name of this function can be confusing. It's really a callback for post *container* creation.) This callback will be triggered directly after creating the container, before a client requests the new JWT it needs to gain read/write permissions to the container that was created.
 
 The `documentPostCreateCallback()` receives two parameters: 1) the ID of the container that was created (also called the "document ID") and 2) a JWT signed by the service with no permission scopes. The authorization service can verify the given JWT and use the information in the JWT to grant the correct user permissions for the newly created container.
 
@@ -104,7 +104,7 @@ export default httpTrigger;
 
 ### Implement the `documentPostCreateCallback`
 
-This example implementation below extends the AzureFunctionTokenProvider and uses the [axios](https://www.npmjs.com/package/axios) library to make a HTTP request to the Azure Function used for generating tokens.
+This example implementation below extends the AzureFunctionTokenProvider and uses the [axios](https://www.npmjs.com/package/axios) library to make an HTTP request to the Azure Function used for generating tokens.
 
 ```typescript
 import { AzureFunctionTokenProvider, AzureMember } from "@fluidframework/azure-client";