Apply suggestions from code review

Acrolinx and related fixes

Author: AnnaMHuff

articles/communication-services/concepts/chat/concepts.md

@@ -36,7 +36,7 @@ Chat conversations happen within **chat threads**. Chat threads have the followi
 - Users are added as a participant to any chat threads that they create.
 
 ### User access
-Azure Communication Services support three levels of user access control, using the chat tokens. See [Identity and Tokens](../identity-model.md) for details. Participants don't have write-access to messages sent by other participants, which means only the message sender can update or delete their sent messages. If another participant tries to do that, they get an error. 
+Azure Communication Services supports three levels of user access control, using the chat tokens. See [Identity and Tokens](../identity-model.md) for details. Participants don't have write-access to messages sent by other participants, which means only the message sender can update or delete their sent messages. If another participant tries to do that, they get an error. 
 
 ### Chat Data 
 Azure Communication Services stores chat messages indefinitely until they are deleted by the customer. Chat thread participants can use `ListMessages` to view  message history for a particular thread. Users that are removed from a chat thread are able to view previous message history but can't send or receive new messages. Accidentally deleted messages aren't recoverable by the system. To learn more about data being stored in Azure Communication Services chat service, refer to the [data residency and privacy page](../privacy.md).  

articles/communication-services/concepts/identity-model.md

@@ -22,11 +22,11 @@ Azure Communication Services is an identity-agnostic service, which offers multi
 
 Azure Communication Services identity model works with two key concepts.
 
-## User Identity / Mapping:
+## User identity / mapping
 Uniquely identifies a user through a user-identifier, which is generated by Azure Communication Services when a user is created. External identifiers such as phone numbers, users, devices, applications, and GUIDs can't be used for identity in Azure Communication Services. You can create Azure Communication Service user identities for free. Charges are only incurred when the user consumes communications modalities such as a chat or a call. Your users identity can be mapped to Azure Communication Services user Identity in 1:1, 1:N, N:1, N:N configurations. A user can participate in multiple communication sessions, using multiple devices, simultaneously. Mapping between Azure Communication Services user identity and customer's private user identity is kept and maintained by the customer. For example, customers can add a `CommunicationServicesId` column in their user table to store the associated Azure Communication Services identity.
 
-## Access Tokens: 
-After a user identity is created, a user is granted with the capability to participate in communications using chat or calls, using access tokens. For example, only a user with chat token can participate in chat and user with VoIP token can participate in a VoIP call. A user can have multiple tokens simultaneously. Azure Communication Services support multiple types of tokens to account for users who require full access vs limited access. Access token have following properties.
+## Access tokens 
+After a user identity is created, a user is granted with the capability to participate in communications using chat or calls, using access tokens. For example, only a user with chat token can participate in chat and user with VoIP token can participate in a VoIP call. A user can have multiple tokens simultaneously. Azure Communication Services supports multiple types of tokens to account for users who require full access vs limited access. Access tokens have the following properties.
 
 |Property|Description|
 |---|----|
@@ -36,7 +36,7 @@ After a user identity is created, a user is granted with the capability to parti
 
 An access token is a JSON Web Token (JWT) and has integrity protection. That is, its claims can't be changed after it's issued. So a manual change of properties such as identity, expiration, or scopes will invalidate the access token. If primitives are used with invalidated tokens, then access will be denied to the primitives. Azure Communication Services supports the following scopes for access tokens.
 
-## Chat Token Scopes
+## Chat token scopes
 Three types of chat token scopes are supported. Permissions for each token are described below.
 - chat
 - chat.join
@@ -60,7 +60,7 @@ Three types of chat token scopes are supported. Permissions for each token are d
 |Send typing indicator | Y | Y | Y |
 |Get participant for thread ID | Y | Y | Y |
 
-## VoIP Token Scopes
+## VoIP token scopes
 Two types of VoIP token scopes are supported. Permissions for each token are described below.
 - voip
 - voip.join
@@ -71,10 +71,10 @@ Two types of VoIP token scopes are supported. Permissions for each token are des
 |Start a VoIP call in Virtual Rooms, when the user is already invited to the Room| Y | Y |
 |Join an InProgress VoIP call | Y | Y |
 |Join an InProgress VoIP call in Virtual Rooms, when the user is already invited to the Room| Y | Y |
-|All other in call operations such as mute/unmute, screen share etc. | Y | Y |
-|All other in call operations such as mute/unmute, screen share etc. in Virtual Rooms| Y | Determined by user role |
+|All other in-call operations such as mute/unmute, screen share etc. | Y | Y |
+|All other in-call operations such as mute/unmute, screen share etc. in Virtual Rooms| Y | Determined by user role |
 
-## Revoke or Update access token
+## Revoke or update access token
 - Azure Communication Services Identity library can be used to revoke an access token before its expiration time. Token revocation isn't immediate. It can take up to 15 minutes to propagate.
 - The removal of an identity, resource, or subscription revokes all access tokens.
 - If you want to remove a user's ability to access specific functionality, revoke all access tokens. Then issue a new access token that has a more limited set of scopes.

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -22,7 +22,7 @@ Once you've started development, check out the [known issues page](../known-issu
 Key features of the Calling SDK:
 
 - **Addressing** - Azure Communication Services provides generic [identities](../identity-model.md) that are used to address communication endpoints. Clients use these identities to authenticate to the service and communicate with each other. These identities are used in Calling APIs that provide clients visibility into who is connected to a call (the roster).
-- **User Accesss Security**
+- **User Access Security**
   - **Roster** control, **Schedule** control, and user **roles/permissions** are enforced through [Virtual Rooms](../rooms/room-concept.md).
   - Ability for a user to **Initiate a new call** or to **Join an existing call** can be managed through [User Identities and Tokens](../identity-model.md) 
 - **Encryption** - The Calling SDK encrypts traffic and prevents tampering on the wire.