Merge pull request #103782 from sethmanheim/wk

Tweak wording per PM feedback

Author: PRMerger18

includes/notification-hubs-enable-apple-push-notifications.md

@@ -5,7 +5,7 @@ services: notification-hubs
 author: sethmanheim
 ms.service: notification-hubs
 ms.topic: include
-ms.date: 11/21/2019
+ms.date: 02/10/2020
 ms.author: sethm
 ms.custom: include file
 ---
@@ -20,10 +20,9 @@ Generate the Certificate Signing Request (CSR) file, which Apple uses to generat
 1. Select **Keychain Access**, expand **Certificate Assistant**, and then select **Request a Certificate from a Certificate Authority**.
 
     ![Use Keychain Access to request a new certificate](./media/notification-hubs-enable-apple-push-notifications/notification-hubs-request-cert-from-ca.png)
-    
-> [!NOTE]
-> OS X by default selects the first item in the category that you have selected in the Keychain Access tool. This might be problematic  if you’re in the **Certificates** section and **Apple Worldwide Developer Relations Certification Authority** is *not* the first item in the list. Before you request a certificate, be sure that you’re in the **Certificates** section, and then select **Apple Worldwide Developer Relations Certification Authority**.
 
+   > [!NOTE]
+   > By default, Keychain Access selects the first item in the list. This can be a problem if you're in the **Certificates** category and **Apple Worldwide Developer Relations Certification Authority** is not the first item in the list. Make sure you have a non-key item, or the **Apple Worldwide Developer Relations Certification Authority** key is selected, before generating the CSR (Certificate Signing Request).
 
 1. Select your **User Email Address**, enter your **Common Name** value, make sure that you specify **Saved to disk**, and then select **Continue**. Leave **CA Email Address** blank as it isn't required.