Merge pull request #262072 from ShawnJackson/communication-services-how-tos

[AQ] edit pass: Communication Services how-to articles (batch 1)

Author: ktoliver

articles/communication-services/how-tos/ui-library-sdk/data-model.md

@@ -1,7 +1,7 @@
 ---
-title: Custom Data Model Injection over the UI Library
+title: Inject a custom data model in the UI Library
 titleSuffix: An Azure Communication Services how-to guide
-description: Use Azure Communication Services UI library for Mobile native to set up Custom Data Model Injection
+description: Set up custom data model injection in the Azure Communication Services UI Library.
 author: garchiro7
 ms.author: jorgegarc
 ms.service: azure-communication-services
@@ -10,34 +10,36 @@ ms.date: 05/24/2022
 ms.custom: template-how-to
 zone_pivot_groups: acs-plat-web-ios-android
 
-#Customer intent: As a developer, I want to set up the Custom Data Model Injection in my application
+#Customer intent: As a developer, I want to set up custom data model injection in the UI Library for my application.
 ---
 
-# Custom Data Model Injection
+# Inject a custom data model in the UI library for an application
 
-Azure Communication Services uses an identity agnostic model where developers can [bring their own identities](../../concepts/identity-model.md). Contoso can get their data model and link it to Azure Communication Services identities. A developer's data model for a user most likely includes information such as their display name, profile picture or avatar, and other details. Information is used by developers to power their applications and platforms.
+Azure Communication Services uses an identity-agnostic model in which developers can [bring their own identities](../../concepts/identity-model.md). Developers can get their data model and link it to Azure Communication Services identities. The data model for a user most likely includes information such as display name, profile picture or avatar, and other details. Developers use this information to build their applications and platforms.
 
-The UI Library makes it simple for developers to inject that user data model into the UI Components. When rendered, they show users provided information rather than generic information that Azure Communication Services has.
+The UI Library makes it simple for you to inject a user data model into the UI components. When you render the UI components, they show users the provided information rather than generic information from Azure Communication Services.
 
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
-- A `User Access Token` to enable the call client. For more information on [how to get a `User Access Token`](../../quickstarts/identity/access-tokens.md)
-- Optional: Complete the quickstart for [getting started with the UI Library composites](../../quickstarts/ui-library/get-started-composites.md)
+- A user access token to enable the call client. [Get a user access token](../../quickstarts/identity/access-tokens.md).
+- Optional: Completion of the [quickstart for getting started with the UI Library composites](../../quickstarts/ui-library/get-started-composites.md).
+
+## Set up injection
 
 ::: zone pivot="platform-web"
-[!INCLUDE [Data model over the Web UI library](./includes/data-model/web.md)]
+[!INCLUDE [Data model over the Web UI Library](./includes/data-model/web.md)]
 ::: zone-end
 
 ::: zone pivot="platform-android"
-[!INCLUDE [Data model over the Android UI library](./includes/data-model/android.md)]
+[!INCLUDE [Data model over the Android UI Library](./includes/data-model/android.md)]
 ::: zone-end
 
 ::: zone pivot="platform-ios"
-[!INCLUDE [Data model over the iOS UI library](./includes/data-model/ios.md)]
+[!INCLUDE [Data model over the iOS UI Library](./includes/data-model/ios.md)]
 ::: zone-end
 
 ## Next steps
 
-- [Learn more about UI Library](../../concepts/ui-library/ui-library-overview.md)
+- [Learn more about the UI Library](../../concepts/ui-library/ui-library-overview.md)

articles/communication-services/how-tos/ui-library-sdk/includes/data-model/android.md

@@ -1,5 +1,5 @@
 ---
-description: In this tutorial, you learn how to use the Calling composite on Android to customize the Participant Avatars and Display Names
+description: Learn how to use the Calling composite on Android to customize participant avatars and display names.
 author: garchiro7
 
 ms.author: jorgegarc
@@ -8,33 +8,38 @@ ms.topic: include
 ms.service: azure-communication-services
 ---
 
-Azure Communication UI [open source library](https://github.com/Azure/communication-ui-library-android) for Android and the sample application code can be found [here](https://github.com/Azure-Samples/communication-services-android-quickstarts/tree/main/ui-calling)
+For more information, see the [open-source Android UI Library](https://github.com/Azure/communication-ui-library-android) and the [sample application code](https://github.com/Azure-Samples/communication-services-android-quickstarts/tree/main/ui-calling).
 
-### Local Participant View Customization
+### Local participant view customization
 
-The UI Library gives developers the ability to provide a more customized experience regarding Participant information. At launch, developers can optionally inject local participant data. This local data isn't shared with the server and can be used to customize the display name and avatar of the local user.
+The UI Library gives developers the ability to provide a customized experience regarding participant information. At launch, you can optionally inject local participant data. This local data isn't shared with the server, and you can use it to customize the display name and avatar of the local user.
 
-#### Local Options
+#### Local options
 
-`CallCompositeLocalOptions` is the data model that can have `CallCompositeParticipantViewData` and `CallCompositeSetupScreenViewData`. It represents the local participant.  By default, for remote participants, the UI library displays the `displayName` injected in `RemoteOptions` that is sent to Azure Communication Service backend server. If `CallCompositeParticipantViewData` is injected, the participant `displayName` and `avatar` are displayed in all avatar components locally. 
+`CallCompositeLocalOptions` is the data model that can have `CallCompositeParticipantViewData` and `CallCompositeSetupScreenViewData`. It represents the local participant.
 
-Similarly, for `CallCompositeSetupScreenViewData`, the `title` and `subtitle` in `CallCompositeSetupScreenViewData` overwrites the navigation bar's title and subtitle in premeeting screen respectively. By default, the UI library displays 'Setup' as the title and nothing as the subtitle.
+By default, for remote participants, the UI Library displays `displayName` information injected in `RemoteOptions`. This information is sent to the Azure Communication Services back-end server. If `CallCompositeParticipantViewData` is injected, the participant `displayName` and `avatar` information is displayed in all avatar components locally.
 
-#### Local Participant View Data
+Similarly, for `CallCompositeSetupScreenViewData`, `title` and `subtitle` in `CallCompositeSetupScreenViewData` overwrite the navigation bar's title and subtitle on the premeeting screen, respectively. By default, the UI Library displays **Setup** as the title and nothing as the subtitle.
 
-`CallCompositeParticipantViewData` is a class that set the `displayName`, `avatarBitmap` and `scaleType` for avatar control. This class is passed to the `CallCompositeLocalOptions` in order to customize the local participants view information.
+#### Local participant view data
 
-This class is held in the `CallCompositeLocalOptions` object that represents options used locally on the device making the call.
+`CallCompositeParticipantViewData` is a class that sets `displayName`, `avatarBitmap`, and `scaleType` for avatar control. This class is passed to `CallCompositeLocalOptions` in order to customize the local participants' view information. This class is held in the `CallCompositeLocalOptions` object that represents options used locally on the device that makes the call.
 
-`displayName` differs from the `displayName` passed in via the `CallCompositeRemoteOptions`. `CallCompositeParticipantViewData` `displayName` is only used locally as an override, where `CallCompositeRemoteOptions` `displayName` is passed to the server and shared with other participants. When `CallCompositeParticipantViewData` `displayName` isn't provided, `CallCompositeRemoteOptions` `displayName` is used.
+This instance of `displayName` differs from the `displayName` information passed in via `CallCompositeRemoteOptions`:
 
-#### Setup Screen View Data
+- The `CallCompositeParticipantViewData` instance of `displayName` is only used locally as an override.
+- The `CallCompositeRemoteOptions` instance of `displayName` is passed to the server and shared with other participants.
 
-`CallCompositeSetupScreenViewData` is an object that sets the `title` and `subtitle` for the navigationBar on call setup screen. If `subtitle` isn't defined, then subtitle is hidden. Here `title` is a required to set the `subtitle` but `subtitle` is optional when `title` is set. This class is locally stored and its information aren't sent up to the server.
+If you don't provide the `CallCompositeParticipantViewData` instance of `displayName`, the application uses the `CallCompositeRemoteOptions` instance of `displayName`.
+
+#### Setup screen view data
+
+`CallCompositeSetupScreenViewData` is an object that sets `title` and `subtitle` for the navigation bar on the call setup screen. If `subtitle` isn't defined, the subtitle is hidden. Here, `title` is required to set `subtitle`, but `subtitle` is optional when `title` is set. This class is locally stored, and its information isn't sent to the server.
 
 #### Usage
 
-To use the `CallCompositeLocalOptions`, pass the instance of `CallCompositeParticipantViewData` and/or `CallCompositeSetupScreenViewData` and inject `CallCompositeLocalOptions` to `callComposite.launch`.
+To use `CallCompositeLocalOptions`, pass the instance of `CallCompositeParticipantViewData` and/or `CallCompositeSetupScreenViewData`, and inject `CallCompositeLocalOptions` to `callComposite.launch`.
 
 #### [Kotlin](#tab/kotlin)
 
@@ -73,26 +78,27 @@ final CallCompositeLocalOptions localOptions = new CallCompositeLocalOptions()
 
 callComposite.launch(callLauncherActivity, remoteOptions, localOptions);
 ```
+
 -----
 
-|Setup View| Calling Experience View|
+|Setup view| Calling experience view|
 | ---- | ---- |
-| :::image type="content" source="media/android-model-injection.png" alt-text="Screenshot of an Android data custom model injection."::: | :::image type="content" source="media/android-model-injection-name.png"  alt-text="Screenshot of an Android data custom model injection with name."::: |
+| :::image type="content" source="media/android-model-injection.png" alt-text="Screenshot of Android data custom model injection."::: | :::image type="content" source="media/android-model-injection-name.png"  alt-text="Screenshot of Android data custom model injection with name."::: |
 
-### Remote Participant View Customization
+### Remote participant view customization
 
-In some instances, you may wish to provide local overrides for remote participants to allow custom avatars and titles.
+In some instances, you might want to provide local overrides for remote participants to allow custom avatars and titles.
 
-The process is similar to the local participant process, however the data is set when participants join the call. As a developer you would need to add a listener to when remote participants join the call, and then call a method to set the `CallCompositeParticipantViewData` for that remote user.
+The process is similar to the local participant process, but the data is set when participants join the call. As a developer, you would need to add a listener when remote participants join the call, and then call a method to set `CallCompositeParticipantViewData` for those remote users.
 
 #### Usage
 
-To set the participant view data for remote participant, set `setOnRemoteParticipantJoinedHandler`. On remote participant join, use callComposite `setRemoteParticipantViewData` to inject view data for remote participant. The participant identifier [CommunicationIdentifier](https://azure.github.io/azure-sdk-for-android/azure-communication-common/index.html) is to uniquely identify a remote participant.
+To set the view data for remote participants, set `setOnRemoteParticipantJoinedHandler`. On remote participant join, use `setRemoteParticipantViewData` for `callComposite` to inject view data for remote participants. The participant identifier [CommunicationIdentifier](https://azure.github.io/azure-sdk-for-android/azure-communication-common/index.html) uniquely identifies a remote participant.
 
-Calls to `setRemoteParticipantViewData` return a result of `CallCompositeSetParticipantViewDataResult`, which has the following values.
+Calls to `setRemoteParticipantViewData` return a result of `CallCompositeSetParticipantViewDataResult`, which has the following values:
 
-- CallCompositeSetParticipantViewDataResult.SUCCESS
-- CallCompositeSetParticipantViewDataResult.PARTICIPANT_NOT_IN_CALL
+- `CallCompositeSetParticipantViewDataResult.SUCCESS`
+- `CallCompositeSetParticipantViewDataResult.PARTICIPANT_NOT_IN_CALL`
 
 #### [Kotlin](#tab/kotlin)
 
@@ -117,8 +123,9 @@ callComposite.addOnRemoteParticipantJoinedEventHandler { remoteParticipantJoined
                 }
             });
 ```
+
 -----
 
 |Participants list|
 | ---- |
-| :::image type="content" source="media/android-model-injection-remote.png" alt-text="Screenshot of the Android remote participants view data injection."::: |
+| :::image type="content" source="media/android-model-injection-remote.png" alt-text="Screenshot of Android remote participant view data injection."::: |