Acrolinc

Author: sethmanheim

articles/notification-hubs/ios-sdk-get-started.md

@@ -25,7 +25,7 @@ This tutorial is a prerequisite to the subsequent Objective C and Swift iOS tuto
 
 To complete this tutorial, you must have an active Azure account. If you don't have an account, you can create a free trial account in just a couple of minutes. For details, see [Azure Free Trial](https://azure.microsoft.com/free/).
 
-You'll also need the following:
+You also need the following:
 
 - An active [Apple Developer](https://developer.apple.com/) account.
 - A Mac running [Xcode](https://go.microsoft.com/fwLink/p/?LinkID=266532), along with a valid developer certificate installed into your Keychain.
@@ -67,7 +67,7 @@ Next, register your app with Apple, enable push notifications, and upload the ex
 To send push notifications to an iOS app, register your application with
 Apple, and also register for push notifications.
 
-1. If you haven't already registered your app, browse to the [iOS Provisioning Portal](https://go.microsoft.com/fwlink/p/?LinkId=272456) at the Apple Developer Center. Sign in to the portal with your Apple ID, and select **Identifiers**. Then select **+** to register a new app.
+1. If you didn't register your app yet, browse to the [iOS Provisioning Portal](https://go.microsoft.com/fwlink/p/?LinkId=272456) at the Apple Developer Center. Sign in to the portal with your Apple ID, and select **Identifiers**. Then select **+** to register a new app.
 
    :::image type="content" source="media/ios-sdk-get-started/image4.png" alt-text="App IDs page":::
 
@@ -103,7 +103,7 @@ A certificate is required to enable the notification hub to work with **APNS**.
 
 - Create a **.p8** file that can be used for [token-based authentication](notification-hubs-push-notification-http2-token-authentication.md) (the newer approach).
 
-The second option has a number of benefits compared to using certificates, as documented in [Token-based (HTTP/2) authentication for APNS](notification-hubs-push-notification-http2-token-authentication.md). However, steps are provided for both approaches.
+The second option has many benefits compared to using certificates, as documented in [Token-based (HTTP/2) authentication for APNS](notification-hubs-push-notification-http2-token-authentication.md). However, steps are provided for both approaches.
 
 ### Option 1: Create a .p12 push certificate that can be uploaded directly to Notification Hubs
 
@@ -155,7 +155,7 @@ The second option has a number of benefits compared to using certificates, as do
    > [!IMPORTANT]
    > Be sure to keep your .p8 file in a secure place (and save a backup). After downloading your key, it cannot be re-downloaded; the server copy is removed.
 
-1. On **Keys**, click on the key that you just created (or an existing key if you have chosen to use that instead).
+1. On **Keys**, click on the key that you just created (or an existing key if you chose to use that instead).
 
 1. Make note of the **Key ID** value.
 
@@ -167,7 +167,7 @@ The second option has a number of benefits compared to using certificates, as do
    -----END PRIVATE KEY-----
    ```
 
-   This is the token value that will be used later to configure Notification Hubs.
+   This is the token value that's used later to configure Notification Hubs.
 
 At the end of these steps you should have the following information for
 use later in [Configure your notification hub with APNS information](#configure-the-notification-hub-with-apns-information):
@@ -214,7 +214,7 @@ use later in [Configure your notification hub with APNS information](#configure
 
 ## Create a notification hub
 
-In this section, you create a notification hub and configure authentication with APNS by using either the .p12 push certificate or token-based authentication. If you want to use a notification hub that you've already created, you can skip to step 5.
+In this section, you create a notification hub and configure authentication with APNS by using either the .p12 push certificate or token-based authentication. If you want to use a notification hub that you already created, you can skip to step 5.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 
@@ -240,7 +240,7 @@ In this section, you create a notification hub and configure authentication with
 
    :::image type="content" source="media/ios-sdk-get-started/image21.png" alt-text="Portal notifications":::
 
-1. Select **Access Policies** from the list. Note that the two connection strings are available to you. You'll need them later to handle push notifications.
+1. Select **Access Policies** from the list. Note that the two connection strings are available to you. You need them later to handle push notifications.
 
    > [!IMPORTANT]
    > Do not use the **DefaultFullSharedAccessSignature** policy in your application. This is meant to be used in your back end only.

articles/notification-hubs/notification-hubs-push-notification-faq.yml

@@ -29,7 +29,7 @@ sections:
 
           * **Free**: This tier is a good starting point for exploring push capabilities. It's not recommended for production apps. You get 500 devices and 1 million pushes included per subscription per month, with no service level agreement (SLA) guarantee.
           * **Basic**: This tier (or the Standard tier) is recommended for smaller production apps. You get 200,000 devices and 10 million pushes included per subscription per month as a baseline.
-          * **Standard**: This tier is recommended for medium to large production apps. You get 10 million devices and 10 million pushes included per subscription per month as a baseline. Includes rich telemetry (additional data about push status provided).
+          * **Standard**: This tier is recommended for medium to large production apps. You get 10 million devices and 10 million pushes included per subscription per month as a baseline. Includes rich telemetry (more data about push status provided).
 
           Standard tier features:
 
@@ -98,12 +98,12 @@ sections:
           The PNS does not guarantee any SLA for delivering notifications. However, most push notifications are delivered to target devices within a few minutes (typically within 10 minutes) from the time they are sent to Notification Hubs. A few notifications might take more time.
 
           > [!NOTE]
-          > Azure Notification Hubs has a policy in place to drop any push notifications that aren't delivered to the PNS within 30 minutes. This delay can happen for a number of reasons, but most commonly because the PNS is throttling your application.
+          > Azure Notification Hubs has a policy in place to drop any push notifications that aren't delivered to the PNS within 30 minutes. This delay can happen for many reasons, but most commonly because the PNS is throttling your application.
 
       - question: |
           Is there any latency guarantee?
         answer: |
-          Because of the nature of push notifications (they are delivered by an external, platform-specific PNS), there is no latency guarantee. Typically, the majority of push notifications are delivered within a few minutes.
+          Because of the nature of push notifications (they are delivered by an external, platform-specific PNS), there is no latency guarantee. Typically, most push notifications are delivered within a few minutes.
 
       - question: |
           Where does Azure Notification Hubs store data?
@@ -172,19 +172,19 @@ sections:
       - question: |
           Is all of my data stored in encrypted form?
         answer: |
-          Azure Notification Hubs encrypts all customer data at rest with the exception of registration tags. For this reason, you should not store personal or confidential data using tags.
+          Azure Notification Hubs encrypts all customer data at rest except for registration tags. For this reason, you should not store personal or confidential data using tags.
 
       - question: |
           Is there audit log capability?
         answer: |
-          Yes. All Notification Hubs management operations update the Azure Activity Log to which is exposed in the [Azure portal](https://portal.azure.com). The Azure Activity Log offers insights into the operations performed on resources in your subscriptions. Using the Activity Log, you can determine the what, who, and when for any write operations (PUT, POST, DELETE) made for the resources in your subscription. You can also understand the status of the operations and other relevant properties. However. the Activity Log does not include read (GET) operation.
+          Yes. All Notification Hubs management operations update the Azure Activity Log to which is exposed in the [Azure portal](https://portal.azure.com). The Azure Activity Log offers insights into the operations performed on resources in your subscriptions. Using the Activity Log, you can determine the what, who, and when for any write operations (PUT, POST, DELETE) made for the resources in your subscription. You can also understand the status of the operations and other relevant properties. However, the Activity Log does not include read (GET) operations.
 
       - question: |
           Does Notification Hubs detect uninstallation?
         answer: |
           If you stored the device as a `Registration`, the first time you send to that registration and the PNS responds with an error status code that indicates the device is not valid, the device is deleted from your notification hub.
 
-          If you stored your devices using the `Installation` APIs, they are not deleted in the scenario above. This decision was made to preserve tags and other metadata about a particular user that might be relevant if the user reinstalls.
+          If you stored your devices using the `Installation` APIs, they are not deleted in this scenario. This decision was made to preserve tags and other metadata about a particular user that might be relevant if the user reinstalls.
 
           For both registrations and installations, you can set an expiration so that the device is automatically cleaned up at a given time. A common pattern is to have your client application update that expiration date once a day to move it back as long as the user is using your application.
 
@@ -207,4 +207,4 @@ sections:
           - [Azure Monitoring REST API walkthrough](/azure/azure-monitor/essentials/rest-api-walkthrough)
 
           > [!NOTE]
-          > Successful notifications mean simply that push notifications have been delivered to the external PNS (for example, APNs for iOS and macOS or FCM for Android devices). It is the responsibility of the PNS to deliver the notifications to target devices. Typically, the PNS does not expose delivery metrics to third parties.
+          > Successful notifications mean simply that push notifications were delivered to the external PNS (for example, APNs for iOS and macOS or FCM for Android devices). It is the responsibility of the PNS to deliver the notifications to target devices. Typically, the PNS does not expose delivery metrics to third parties.