added Pivot group, validation fixes

Author: vac0224

articles/communication-services/tutorials/includes/twilio-to-acs-chat-android-tutorial.md

@@ -13,10 +13,10 @@ ms.custom: mode-other
 
 ## Prerequisites
 
-1. Create an Azure account with an active subscription. For details, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+1. Create an Azure account with an active subscription. For more information, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 2. Install [Visual Studio](https://visualstudio.microsoft.com/downloads/).
-3. Create an Azure Communication Services resource. For details, see [Create an Azure Communication Services resource](../../quickstarts/create-communication-resource.md). Record your resource **endpoint and connection string**.
-4. A [User Access Token](../../quickstarts/identity/access-tokens.md). Be sure to set the scope to **chat**, and **note the token string and user_id string**. You can also use the Azure CLI and run the command below with your connection string to create a user and an access token.
+3. Create an Azure Communication Services resource. For more information, see [Create an Azure Communication Services resource](../../quickstarts/create-communication-resource.md). Record your resource **endpoint and connection string**.
+4. A [User Access Token](../../quickstarts/identity/access-tokens.md). Be sure to set the scope to **chat**, and **note the token string and user_id string**. You can also use the Azure CLI and run the following command with your connection string to create a user and an access token.
 
   ```azurecli-interactive
   az communication identity token issue --scope chat --connection-string "yourConnectionString"
@@ -54,7 +54,7 @@ The following classes handle some of the major features of the Azure Communicati
 
 | Name                                  | Description                                                  |
 | ------------------------------------- | ------------------------------------------------------------ |
-| `ChatClient` | This class is needed for the Chat functionality. You instantiate it with your subscription information, and use it to create, get and delete threads. |
+| `ChatClient` | This class is needed for the Chat functionality. You instantiate it with your subscription information, and use it to create, get, and delete threads. |
 | `ChatThreadClient` | This class is needed for the Chat Thread functionality. You obtain an instance via the ChatClient, and use it to send/receive/update/delete messages, add/remove/get participants, send typing notifications and read receipts. |
 
 ## Create a chat client
@@ -95,7 +95,7 @@ var conversation = ConversationResource.Create(
 
 In Azure Communication Services, you create a thread, which is equivalent to a conversation in Twilio.
 
-Use the `createChatThread` method on the chatClient to create a chat thread
+To create a chat thread, use the `createChatThread` method on the chatClient:
 - Use `topic` to give a topic to this chat; you can update the `topic` after the chat thread is created using the `UpdateTopic` function.
 - Use `participants` property to pass a  list of `ChatParticipant` objects to be added to the chat thread. Initialize the `ChatParticipant` object with a `CommunicationIdentifier` object. `CommunicationIdentifier` could be of type `CommunicationUserIdentifier`, `MicrosoftTeamsUserIdentifier`, or `PhoneNumberIdentifier`. For example, to get a `CommunicationIdentifier` object, you need to pass an Access ID created following the instructions to [Create a user](../../quickstarts/identity/access-tokens.md#create-an-identity).
 
@@ -214,13 +214,13 @@ var message = MessageResource.Create(
 
 #### Azure Communication Services
 
-Unlike Twilio, Azure Communication Services does not have a separate function to send text messages or media.
+Unlike Twilio, Azure Communication Services doesn't have a separate function to send text messages or media.
 
 Use `SendMessage` to send a message to a thread.
-- Use `content` to provide the content for the message, it's required.
+- Use `content`, required, to provide the content for the message.
 - Use `type` for the content type of the message such as `Text` or `Html`. If not specified, `Text` is the default.
 - Use `senderDisplayName` to specify the display name of the sender. If not specified, empty string is the default.
-- Use `metadata` optionally to include any additional data you want to send along with the message. This field provides a mechanism for developers to extend chat message function and add custom information for your use case. For example, when sharing a file link in the message, you might want to add `hasAttachment:true` in the metadata so that recipient's application can parse that and display accordingly.
+- Use `metadata` optionally to include other data you want to send along with the message. This field provides a mechanism for developers to extend chat message function and add custom information for your use case. For example, when sharing a file link in the message, you might want to add `hasAttachment:true` in the metadata so that recipient's application can parse that and display accordingly.
 
 ```csharp
 SendChatMessageOptions sendChatMessageOptions = new SendChatMessageOptions()
@@ -268,7 +268,7 @@ The following code snippet shows how to receive a media file.
 
 #### Azure Communication Services
 
-Unlike Twilio, Azure Communication Services does not have a separate function to receive text messages or media.
+Unlike Twilio, Azure Communication Services doesn't have a separate function to receive text messages or media.
 
 Azure Communication Services Chat enables you to subscribe to events directly within the application.
 
@@ -282,11 +282,11 @@ await foreach (ChatMessage message in allMessages)
 }
 ```
 
-`GetMessages` takes an optional `DateTimeOffset` parameter. If that offset is specified, you receive messages that were received, updated, or deleted after it. Note that messages received before the offset time but edited or removed after it are also be returned.
+`GetMessages` takes an optional `DateTimeOffset` parameter. If that offset is specified, you receive messages that were received, updated, or deleted after it. Messages received before the offset time but edited or removed after it are also returned.
 
 `GetMessages` returns the latest version of the message, including any edits or deletes that happened to the message using `UpdateMessage` and `DeleteMessage`. For deleted messages, `chatMessage.DeletedOn` returns a datetime value indicating when that message was deleted. For edited messages, `chatMessage.EditedOn` returns a datetime indicating when the message was edited. You can access the original time of message creation using `chatMessage.CreatedOn`, and use it for ordering the messages.
 
-`GetMessages` returns different types of messages which can be identified by `chatMessage.Type`. These types are:
+`GetMessages` returns different types of messages, which you can identify by `chatMessage.Type`. These types are:
 
 - `Text`: Regular chat message sent by a thread member.
 
@@ -390,7 +390,7 @@ await foreach (ChatParticipant participant in allParticipants)
 ```
 
 #### Azure Communication Services 
-Use `SendReadReceipt` to notify other participants that the message is read by the user.
+Use `SendReadReceipt` to notify other participants that the user read the message.
 
 ```csharp
 await chatThreadClient.SendReadReceiptAsync(messageId: messageId);

articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md

@@ -54,7 +54,7 @@ The following classes handle some of the major features of the Azure Communicati
 
 | Name                                  | Description                                                  |
 | ------------------------------------- | ------------------------------------------------------------ |
-| `ChatClient` | This class is needed for the Chat functionality. You instantiate it with your subscription information, and use it to create, get and delete threads. |
+| `ChatClient` | This class is needed for the Chat functionality. You instantiate it with your subscription information, and use it to create, get, and delete threads. |
 | `ChatThreadClient` | This class is needed for the Chat Thread functionality. You obtain an instance via the ChatClient, and use it to send/receive/update/delete messages, add/remove/get participants, send typing notifications and read receipts. |
 
 ## Create a chat client
@@ -95,7 +95,7 @@ var conversation = ConversationResource.Create(
 
 In Azure Communication Services, you create a thread, which is equivalent to a conversation in Twilio.
 
-Use the `createChatThread` method on the chatClient to create a chat thread
+To create a chat thread, use the `createChatThread` method on the `chatClient`:
 - Use `topic` to give a topic to this chat; you can update the `topic` after the chat thread is created using the `UpdateTopic` function.
 - Use `participants` property to pass a  list of `ChatParticipant` objects to be added to the chat thread. Initialize the `ChatParticipant` object with a `CommunicationIdentifier` object. `CommunicationIdentifier` could be of type `CommunicationUserIdentifier`, `MicrosoftTeamsUserIdentifier`, or `PhoneNumberIdentifier`. For example, to get a `CommunicationIdentifier` object, you need to pass an Access ID created following the instructions to [Create a user](../../quickstarts/identity/access-tokens.md#create-an-identity).
 
@@ -214,13 +214,13 @@ var message = MessageResource.Create(
 
 #### Azure Communication Services
 
-Unlike Twilio, Azure Communication Services does not have a separate function to send text messages or media.
+Unlike Twilio, Azure Communication Services doesn't have a separate function to send text messages or media.
 
 Use `SendMessage` to send a message to a thread.
 - Use `content` to provide the content for the message, it's required.
 - Use `type` for the content type of the message such as `Text` or `Html`. If not specified, `Text` is the default.
 - Use `senderDisplayName` to specify the display name of the sender. If not specified, empty string is the default.
-- Use `metadata` optionally to include any additional data you want to send along with the message. This field provides a mechanism for developers to extend chat message function and add custom information for your use case. For example, when sharing a file link in the message, you might want to add `hasAttachment:true` in the metadata so that recipient's application can parse that and display accordingly.
+- Use `metadata` optionally to include any other data you want to send along with the message. This field provides a mechanism for developers to extend chat message function and add custom information for your use case. For example, when sharing a file link in the message, you might want to add `hasAttachment:true` in the metadata so that recipient's application can parse that and display accordingly.
 
 ```csharp
 SendChatMessageOptions sendChatMessageOptions = new SendChatMessageOptions()
@@ -268,7 +268,7 @@ The following code snippet shows how to receive a media file.
 
 #### Azure Communication Services
 
-Unlike Twilio, Azure Communication Services does not have a separate function to receive text messages or media.
+Unlike Twilio, Azure Communication Services doesn't have a separate function to receive text messages or media.
 
 Azure Communication Services Chat enables you to subscribe to events directly within the application.
 
@@ -282,15 +282,15 @@ await foreach (ChatMessage message in allMessages)
 }
 ```
 
-`GetMessages` takes an optional `DateTimeOffset` parameter. If that offset is specified, you receive messages that were received, updated, or deleted after it. Note that messages received before the offset time but edited or removed after it are also be returned.
+`GetMessages` takes an optional `DateTimeOffset` parameter. If that offset is specified, you receive messages that were received, updated, or deleted after it. Messages received before the offset time but edited or removed after it are also returned.
 
 `GetMessages` returns the latest version of the message, including any edits or deletes that happened to the message using `UpdateMessage` and `DeleteMessage`. For deleted messages, `chatMessage.DeletedOn` returns a datetime value indicating when that message was deleted. For edited messages, `chatMessage.EditedOn` returns a datetime indicating when the message was edited. You can access the original time of message creation using `chatMessage.CreatedOn`, and use it for ordering the messages.
 
-`GetMessages` returns different types of messages which can be identified by `chatMessage.Type`. These types are:
+`GetMessages` returns different types of messages, which can be identified by `chatMessage.Type`. These types are:
 
 - `Text`: Regular chat message sent by a thread member.
 
-- `Html`:  A formatted text message. Note that Communication Services users currently can't send `RichText` messages. This message type is supported by messages sent from Teams users to Communication Services users in Teams Interop scenarios.
+- `Html`:  A formatted text message. Communication Services users currently can't send `RichText` messages. This message type is supported by messages sent from Teams users to Communication Services users in Teams Interop scenarios.
 
 - `TopicUpdated`: System message that indicates the topic has been updated. (readonly)
 
@@ -390,7 +390,7 @@ await foreach (ChatParticipant participant in allParticipants)
 ```
 
 #### Azure Communication Services 
-Use `SendReadReceipt` to notify other participants that the message is read by the user.
+Use `SendReadReceipt` to notify other participants that the user read the message.
 
 ```csharp
 await chatThreadClient.SendReadReceiptAsync(messageId: messageId);

articles/communication-services/tutorials/includes/twilio-to-acs-chat-java-tutorial.md

@@ -412,7 +412,7 @@ Once a chat thread is created, you can then add and remove users from it. By add
 
 Use the `addParticipants` method to add participants to the thread.
 
-- `communicationIdentifier`, required, is the `CommunicationIdentifier` you created using `CommunicationIdentityClient` in the [User Access Token](../../quickstart/identity/access-tokens.md) quickstart.
+- `communicationIdentifier`, required, is the `CommunicationIdentifier` you created using `CommunicationIdentityClient` in the [User Access Token](../../quickstarts/identity/access-tokens.md) quickstart.
 - `displayName`, optional, is the display name for the thread participant.
 - `shareHistoryTime`, optional, is the time from which the chat history is shared with the participant. To share history since the inception of the chat thread, set this property to any date equal to, or less than the thread creation time. To share no history previous to when the participant was added, set it to the current date. To share partial history, set it to the required date.
 

articles/communication-services/tutorials/includes/twilio-to-acs-chat-js-tutorial.md

@@ -301,7 +301,7 @@ console.log(`Message sent!, message id:${messageId}`);
 
 ### Receive chat messages from a chat thread
 
-Unlike Twilio, Azure Communication Services doesn't have separate functions to receive text messages or media. Azure Communication Services uses Azure Event Grid to handle events. For more information, see [Event Handling](/azure/event-grid/event-schema-communication-services.md).
+Unlike Twilio, Azure Communication Services doesn't have separate functions to receive text messages or media. Azure Communication Services uses Azure Event Grid to handle events. For more information, see [Event Handling](/azure/event-grid/event-schema-communication-services).
 
 #### Twilio
 

articles/communication-services/tutorials/migrating-to-azure-communication-services-chat.md

@@ -11,7 +11,7 @@ ms.topic: how-to
 ms.service: azure-communication-services
 ms.subservice: chat
 ms.custom: template-how-to
-zone_pivot_groups: acs-js-swift-android-
+zone_pivot_groups: acs-migrate-twilio
 ---
 
 # Migrate from Twilio Conversations Chat to Azure Communication Services
@@ -37,6 +37,7 @@ Migrating might involve not just replacing API calls but also rethinking how you
 ## Key features available in Azure Communication Services Chat SDK
 
 | **Feature** | **JavaScript SDK** | **iOS SDK** | **Android SDK** | **.NET SDK** | **Java SDK** | **Python SDK** |
+| --- | --- | --- | --- | --- | --- | --- |
 | **Install** | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
 | **Import** | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
 | **Auth** | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
@@ -89,8 +90,8 @@ Migrating might involve not just replacing API calls but also rethinking how you
 |                   | Send Unicode emojis as part of message content                                                   | ✔️   | ✔️   | ✔️  | ✔️    | ✔️  |  ✔️    | ✔️   |	
 |                   | Add metadata to chat messages                                                                    | ❌   | ✔️   | ✔️  | ✔️    | ✔️  |  ✔️    | ✔️   |	
 |                   | Add display name to typing indicator notification                                                | ❌   | ✔️   | ✔️  | ✔️    | ✔️  |  ✔️    | ✔️   |	
-|Real-time notifications (enabled by proprietary signaling package**)|  Chat clients can subscribe to get real-time updates for incoming messages and other operations occurring in a chat thread. To see a list of supported updates for real-time notifications, see [Chat concepts](concepts.md#real-time-notifications)                                     | ❌   | ✔️   | ❌    | ❌  | ❌  | ✔️  | ✔️  |	
-|Mobile push notifications with Notification Hub |  The Chat SDK provides APIs allowing clients to be notified for incoming messages and other operations occurring in a chat thread by connecting an Azure Notification Hub to your Communication Services resource. In situations where your mobile app is not running in the foreground, patterns are available to [fire pop-up notifications](../notifications.md) ("toasts") to inform end-users, see [Chat concepts](concepts.md#push-notifications).                                     | ❌   | ❌   | ❌    | ❌  | ❌  | ✔️  | ✔️  |	
+|Real-time notifications (enabled by proprietary signaling package**)|  Chat clients can subscribe to get real-time updates for incoming messages and other operations occurring in a chat thread. To see a list of supported updates for real-time notifications, see [Chat concepts](../concepts.md#real-time-notifications)                                     | ❌   | ✔️   | ❌    | ❌  | ❌  | ✔️  | ✔️  |	
+|Mobile push notifications with Notification Hub |  The Chat SDK provides APIs allowing clients to be notified for incoming messages and other operations occurring in a chat thread by connecting an Azure Notification Hub to your Communication Services resource. In situations where your mobile app is not running in the foreground, patterns are available to [fire pop-up notifications](../concepts/notifications.md) ("toasts") to inform end-users, see [Chat concepts](../concepts.md#push-notifications).                                    | ❌   | ❌   | ❌    | ❌  | ❌  | ✔️  | ✔️  |	
 | Reporting </br>(This info is available under Monitoring tab for your Communication Services resource on Azure portal)      | Understand API traffic from your chat app by monitoring the published metrics in Azure Metrics Explorer and set alerts to detect abnormalities     | ✔️   | ✔️   | ✔️  | ✔️    | ✔️  |  ✔️    | ✔️   |	
 |                   | Monitor and debug your Communication Services solution by enabling diagnostic logging for your resource    | ✔️   | ✔️   | ✔️  | ✔️    | ✔️  |  ✔️    | ✔️   |	
 

articles/zone-pivot-groups.yml

@@ -3452,3 +3452,18 @@ groups:
     title: React
   - id: vue
     title: Vue
+#Owner: ektrishi
+- id: acs-migrate-twilio
+  title: Programming languages
+  prompt: Choose a programming language
+  pivots:
+  - id: programming-language-javascript
+    title: JavaScript
+  - id: programming-language-android
+    title: Android
+  - id: programming-language-swift
+    title: Swift
+  - id: programming-language-csharp
+    title: C#
+  - id: programming-language-java
+    title: Java