two-communication-services-articles

Author: ShawnJackson

articles/communication-services/how-tos/calling-sdk/includes/install-sdk/install-sdk-ios.md

@@ -10,9 +10,9 @@ ms.author: rifox
 
 ### Create the Xcode project
 
-In Xcode, create a new iOS project and select the **Single View App** template. This quickstart uses the [SwiftUI framework](https://developer.apple.com/xcode/swiftui/), so you should set **Language** to **Swift** and set **Interface** to **SwiftUI**.
+In Xcode, create a new iOS project and select the **Single View App** template. This article uses the [SwiftUI framework](https://developer.apple.com/xcode/swiftui/), so you should set **Language** to **Swift** and set **Interface** to **SwiftUI**.
 
-You're not going to create tests during this quickstart. Feel free to clear the **Include Tests** checkbox.
+You're not going to create tests in this article. Feel free to clear the **Include Tests** checkbox.
 
 :::image type="content" source="../../../../quickstarts/voice-video-calling/media/ios/xcode-new-ios-project.png" alt-text="Screenshot that shows the window for creating a project within Xcode.":::
 
@@ -27,7 +27,9 @@ You're not going to create tests during this quickstart. Feel free to clear the
         pod 'AzureCommunicationCalling', '~> 1.0.0'
     end
     ```
+
 2. Run `pod install`.
+
 3. Open `.xcworkspace` by using Xcode.
 
 ### Request access to the microphone

articles/communication-services/how-tos/calling-sdk/push-notifications.md

@@ -20,11 +20,11 @@ Push notifications send information from your application to users' devices. You
 
 In this article, you learn how to enable push notifications for Azure Communication Services calls. Communication Services provides integrations with [Azure Event Grid](../../../event-grid/overview.md) and [Azure Notification Hubs](../../../notification-hubs/notification-hubs-push-notification-overview.md) that enable you to add push notifications to your apps.
 
-## Overview of TTL tokens
+## <a name = "ttl-token"></a> Overview of TTL tokens
 
 The time-to-live (TTL) token is a setting that determines the length of time that a notification token stays valid before becoming invalid. This setting is useful for applications where user engagement doesn't require daily interaction but remains critical over longer periods.
 
-The TTL configuration allows the management of push notifications' lifecycle. It reduces the need for frequent token renewals while helping to ensure that the communication channel between the application and its users remains open and reliable for extended durations.
+The TTL configuration allows the management of push notifications' life cycle. It reduces the need for frequent token renewals while helping to ensure that the communication channel between the application and its users remains open and reliable for extended durations.
 
 Currently, the maximum value for TTL is **180 days (15,552,000 seconds)**, and the minimum value is **5 minutes (300 seconds)**. You can enter this value and adjust it to fit your needs. If you don't provide a value, the default value is **24 hours (86,400 seconds)**.
 
@@ -33,15 +33,18 @@ After the Register Push Notification API is called, the device token information
 If you want to revoke an identity, follow [this process](../../concepts/identity-model.md#revoke-or-update-access-token). After the identity is revoked, the registrar entry should be deleted.
 
 > [!NOTE]
-> For a Microsoft Teams user, the maximum TTL value is **24 hrs (86,400 seconds)**. There's no way to increase this value. You should wake up the application every 24 hours in the background and perform the registration of the device token.
+> For a Microsoft Teams user, the maximum TTL value is **24 hrs (86,400 seconds)**. There's no way to increase this value. You should wake up the application every 24 hours in the background and register the device token.
 >
 > To wake up the application, fetch the new token, and perform the registration, follow the [instructions for the iOS platform](https://developer.apple.com/documentation/uikit/app_and_environment/scenes/preparing_your_ui_to_run_in_the_background/using_background_tasks_to_update_your_app) or the [instructions for the Android platform](https://developer.android.com/develop/background-work/background-tasks).
 
 ## 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 calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
+
 - Optional: Completion of the [quickstart to add voice calling to your application](../../quickstarts/voice-video-calling/getting-started-with-calling.md).
 
 ::: zone pivot="platform-web"
@@ -62,8 +65,8 @@ If you want to revoke an identity, follow [this process](../../concepts/identity
 
 ## Related content
 
-- [Learn how to subscribe to events](./events.md)
-- [Learn how to manage calls](./manage-calls.md)
-- [Learn how to manage video](./manage-video.md)
-- [Migrate Android SDK push notifications to FCM v1](../../tutorials/call-chat-migrate-android-push-fcm-v1.md)
-- [Register for Android SDK push notifications using FCM v1](../../tutorials/call-chat-register-android-push-fcm-v1.md)
+- [Subscribe to SDK events](./events.md)
+- [Manage calls](./manage-calls.md)
+- [Manage video during calls](./manage-video.md)
+- [Migrate Android SDK push notifications to Firebase Cloud Messaging HTTP v1](../../tutorials/call-chat-migrate-android-push-fcm-v1.md)
+- [Register for Android SDK push notifications using Firebase Cloud Messaging HTTP v1](../../tutorials/call-chat-register-android-push-fcm-v1.md)