Skip to content

Commit d467dc5

Browse files
authored
changed to sentence case
1 parent f70c726 commit d467dc5

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/communication-services/concepts/ui-library/includes/mobile-ui-use-cases.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 09/14/2021
88

99
Use the `CallComposite` and the `ChatComposite` in the Azure Communication Services UI Library to create call experiences in your iOS and Android applications. By using a couple lines of code, you can easily integrate an entire call and chat experience in your application. Composites in Communication Services manage the entire lifecycle of the call and chat, from setup until the call and chat end.
1010

11-
## Calling Use Cases
11+
## Calling use cases
1212

1313
You can use the call composite in Communication Services to create these use cases:
1414

@@ -33,7 +33,7 @@ You can use the call composite in Communication Services to create these use cas
3333
| | End a call |
3434
| | Hold and resume a call after audio interruption |
3535

36-
### Teams Interoperability
36+
### Teams interoperability
3737

3838
For [Teams interoperability](../../teams-interop.md) scenarios, you can use UI Library composites to add a user to a Teams meeting via Communication Services. To enable Teams interoperability, use the call composite. The composite manages the entire lifecycle of joining a Teams interoperability call.
3939

@@ -71,13 +71,13 @@ Localization is key to making products for users around the world and who speak
7171

7272
Accessibility is a key focus of the call libraries. You can use a screen reader to make important announcements about call status and to help ensure that visually impaired users can effectively participate when they use the application.
7373

74-
### View Data Injection
74+
### View data injection
7575

7676
Use the UI Library for mobile native platforms to give local and remote participants the option to customize how they appear as users in a call. A local participant can choose a local avatar, custom display name, navigation's title and subtitle on Setup screen when a call begins. A remote user can create a customized avatar when they join the meeting. For more information, see [How to customize pre-meeting view](../../../how-tos/ui-library-sdk/data-model.md).
7777

7878
:::image type="content" source="../../media/mobile-ui/ios-composite.gif" alt-text="GIF animation that shows the pre-meeting experience and joining experience on iOS.":::
7979

80-
## Chat Use Cases
80+
## Chat use cases
8181

8282
[!INCLUDE [Public Preview Notice](../../../includes/public-preview-include.md)]
8383

@@ -99,11 +99,11 @@ The `ChatComposite` was designed to fit into different layouts and views in your
9999
| -------------------------------------------------------- | --------------------------------------------------------------- |
100100
| :::image type="content" source="../../media/mobile-ui/chat-fullscreen.png" alt-text="an image that shows the chat experience on iOS in a navigation view."::: | :::image type="content" source="../../media/mobile-ui/chat-modal.png" alt-text="an image that shows the chat experience on iOS in a modal view."::: |
101101

102-
## Supported Identities
102+
## Supported identities
103103

104104
To initialize a composite and authenticate to the service, a user must have an Azure Communication Services identity. For more information, see [Authenticate to Azure Communication Services](../../authentication.md) and [Quickstart: Create and manage access tokens](../../../quickstarts/access-tokens.md).
105105

106-
## Recommended Architecture
106+
## Recommended architecture
107107

108108
Initialize a composite by using an Azure Communication Services access token. It's important to get access tokens from Azure Communication Services through a trusted service that you manage. For more information, see [Quickstart: Create and manage access tokens](../../../quickstarts/access-tokens.md) and the [trusted service tutorial](../../../tutorials/trusted-service-tutorial.md).
109109

@@ -118,7 +118,7 @@ Call and chat client libraries must have the context for the call they join. Lik
118118
| Retrieve and pass join information for the call or chat | Pass through call and chat information to initialize components |
119119
| Retrieve and pass user information for any custom data model | Pass through a custom data model to components to render |
120120

121-
## Platform Support
121+
## Platform support
122122

123123
|Platform | Versions|
124124
|---------|---------|

0 commit comments

Comments
 (0)