Skip to content

Commit 6279311

Browse files
committed
Bulk update of SEO title length issues
1 parent daa985b commit 6279311

17 files changed

+37
-33
lines changed

articles/notification-hubs/configure-apple-push-notification-service.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ ms.reviewer: jowargo
1515
ms.lastreviewed: 03/25/2019
1616
---
1717

18-
# Configure Apple Push Notification Service (APNS) settings for a notification hub in the Azure portal
18+
# Configure Apple Push Notification Service settings for a notification hub in the Azure portal
19+
1920
This article shows you how to configure Apple Push Notification Service (APNS) settings for an Azure notification hub by using the Azure portal.
2021

2122
## Prerequisites

articles/notification-hubs/configure-google-firebase-cloud-messaging.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ ms.reviewer: jowargo
1515
ms.lastreviewed: 03/25/2019
1616
---
1717

18-
# Configure Google Firebase Cloud Messaging (FCM) settings for a notification hub in the Azure portal
18+
# Configure Google Firebase settings for a notification hub in the Azure portal
19+
1920
This article shows you how to configure Google Firebase Cloud Messaging (FCM) settings for an Azure notification hub by using the Azure portal.
2021

2122
## Prerequisites

articles/notification-hubs/configure-microsoft-push-notification-service.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ ms.reviewer: jowargo
1515
ms.lastreviewed: 03/25/2019
1616
---
1717

18-
# Configure Microsoft Push Notification Service (MPNS) settings for a notification hub in the Azure portal
18+
# Configure Microsoft Push Notification Service (MPNS) settings in the Azure portal
19+
1920
This article shows you how to configure Microsoft Push Notification Service (MPNS) settings for an Azure notification hub by using the Azure portal.
2021

2122
## Prerequisites

articles/notification-hubs/configure-windows-push-notification-service.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ ms.reviewer: jowargo
1515
ms.lastreviewed: 03/25/2019
1616
---
1717

18-
# Configure Windows Push Notification Service (WNS) settings for a notification hub in the Azure portal
18+
# Configure Windows Push Notification Service settings in the Azure portal
19+
1920
This article shows you how to configure Windows Notification Service (WNS) settings for an Azure notification hub by using the Azure portal.
2021

2122
## Prerequisites

articles/notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Send push notifications to Android using Azure Notification Hubs and Firebase Cloud Messaging | Microsoft Docs
2+
title: Send push notifications to Android using Azure Notification Hubs and Firebase | Microsoft Docs
33
description: In this tutorial, you learn how to use Azure Notification Hubs and Google Firebase Cloud Messaging to push notifications to Android devices.
44
services: notification-hubs
55
documentationcenter: android
@@ -21,7 +21,7 @@ ms.reviewer: jowargo
2121
ms.lastreviewed: 09/11/2019
2222
---
2323

24-
# Tutorial: Send push notifications to Android devices using Google Firebase Cloud Messaging
24+
# Tutorial: Send push notifications to Android devices using Firebase
2525

2626
[!INCLUDE [notification-hubs-selector-get-started](../../includes/notification-hubs-selector-get-started.md)]
2727

articles/notification-hubs/notification-hubs-aspnet-backend-android-xplat-segmented-gcm-push-notification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.reviewer: jowargo
2020
ms.lastreviewed: 01/04/2019
2121
---
2222

23-
# Tutorial: Push notifications to specific Android devices using Azure Notification Hubs and Google Cloud Messaging (deprecated)
23+
# Tutorial: Send push notifications to specific Android devices using Google Cloud Messaging (deprecated)
2424

2525
> [!WARNING]
2626
> As of April 10, 2018, Google has deprecated Google Cloud Messaging (GCM). The GCM server and client APIs are deprecated and will be removed as soon as May 29, 2019. For more information, see [GCM and FCM Frequently Asked Questions](https://developers.google.com/cloud-messaging/faq).

articles/notification-hubs/notification-hubs-aspnet-backend-gcm-android-push-to-user-google-notification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.reviewer: jowargo
2020
ms.lastreviewed: 01/04/2019
2121
---
2222

23-
# Tutorial: Push notification to specific Android application users by using Azure Notification Hubs and Google Cloud Messaging (deprecated)
23+
# Tutorial: Send push notification to specific Android users using Azure Notification Hubs and Google Cloud Messaging (deprecated)
2424

2525
> [!WARNING]
2626
> As of April 10, 2018, Google has deprecated Google Cloud Messaging (GCM). The GCM server and client APIs are deprecated and will be removed as soon as May 29, 2019. For more information, see [GCM and FCM Frequently Asked Questions](https://developers.google.com/cloud-messaging/faq).

articles/notification-hubs/notification-hubs-aspnet-cross-platform-notification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.reviewer: jowargo
1919
ms.lastreviewed: 10/02/2019
2020
---
2121

22-
# Send cross-platform notifications to users with Notification Hubs
22+
# Send cross-platform notifications with Azure Notification Hubs
2323

2424
This tutorial builds on the previous tutorial, [Send notifications to specific users by using Azure Notification Hubs]. That tutorial describes how to push notifications to all devices that are registered to a specific authenticated user. That approach required multiple requests to send a notification to each supported client platform. Azure Notification Hubs supports templates, with which you can specify how a specific device wants to receive notifications. This method simplifies sending cross-platform notifications.
2525

articles/notification-hubs/notification-hubs-gcm-to-fcm.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,29 +17,29 @@ ms.reviewer: jowargo
1717
ms.lastreviewed: 04/10/2019
1818
---
1919

20-
# Azure Notification Hubs and the Google Firebase Cloud Messaging (FCM) migration
20+
# Azure Notification Hubs and Google Firebase Cloud Messaging migration
2121

2222
## Current state
2323

2424
When Google announced its migration from Google Cloud Messaging (GCM) to Firebase Cloud Messaging (FCM), push services like ours had to adjust how we sent notifications to Android devices to accommodate the change.
2525

2626
We updated our service backend, then published updates to our API and SDKs as needed. With our implementation, we made the decision to maintain compatibility with existing GCM notification schemas to minimize customer impact. This means that we currently send notifications to Android devices using FCM in FCM Legacy Mode. Ultimately, we want to add true support for FCM, including the new features and payload format. That is a longer-term change and the current migration is focused on maintaining compatibility with existing applications and SDKs. You can use either the GCM or FCM SDKs in your app (along with our SDK) and we make sure the notification is sent correctly.
2727

28-
Some customers recently received an email from Google warning about apps using a GCM endpoint for notifications. This was just a warning, and nothing is broken – your apps Android notifications are still sent to Google for processing and Google still processes them. Some customers who specified the GCM endpoint explicitly in their service configuration were still using the deprecated endpoint. We had already identified this gap and were working on fixing the issue when Google sent the email.
28+
Some customers recently received an email from Google warning about apps using a GCM endpoint for notifications. This was just a warning, and nothing is broken – your app's Android notifications are still sent to Google for processing and Google still processes them. Some customers who specified the GCM endpoint explicitly in their service configuration were still using the deprecated endpoint. We had already identified this gap and were working on fixing the issue when Google sent the email.
2929

3030
We replaced that deprecated endpoint and the fix is deployed.
3131

3232
## Going forward
3333

34-
Googles FCM FAQ says you don't have to do anything. In the [FCM FAQ](https://developers.google.com/cloud-messaging/faq), Google said "client SDKs and GCM tokens will continue to work indefinitely. However, you won't be able to target the latest version of Google Play Services in your Android app unless you migrate to FCM."
34+
Google's FCM FAQ says you don't have to do anything. In the [FCM FAQ](https://developers.google.com/cloud-messaging/faq), Google said "client SDKs and GCM tokens will continue to work indefinitely. However, you won't be able to target the latest version of Google Play Services in your Android app unless you migrate to FCM."
3535

36-
If your app uses the GCM library, go ahead and follow Googles instructions to upgrade to the FCM library in your app. Our SDK is compatible with either, so you wont have to update anything in your app on our side (as long as youre up to date with our SDK version).
36+
If your app uses the GCM library, go ahead and follow Google's instructions to upgrade to the FCM library in your app. Our SDK is compatible with either, so you won't have to update anything in your app on our side (as long as you're up to date with our SDK version).
3737

3838
## Questions and answers
3939

40-
Heres some answers to common questions weve heard from customers:
40+
Here's some answers to common questions we've heard from customers:
4141

42-
**Q:** What do I need to do to be compatible by the cutoff date (Googles current cutoff date is May 29th and may change)?
42+
**Q:** What do I need to do to be compatible by the cutoff date (Google's current cutoff date is May 29th and may change)?
4343

4444
**A:** Nothing. We will maintain compatibility with existing GCM notification schema. Your GCM key will continue to work as normal as will any GCM SDKs and libraries used by your application.
4545

articles/notification-hubs/notification-hubs-ios-push-notifications-swift-apps-get-started.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Push notifications to Swift iOS apps that use Azure Notification Hubs | Microsoft Docs
2+
title: Send push notifications to Swift iOS apps that use Azure Notification Hubs | Microsoft Docs
33
description: Learn how to push notifications to Swift iOS apps that use Azure Notification Hubs.
44
services: notification-hubs
55
documentationcenter: ios
@@ -19,7 +19,7 @@ ms.reviewer: jowargo
1919
ms.lastreviewed: 05/21/2019
2020
---
2121

22-
# Tutorial: Push notifications to Swift iOS apps that use the Notification Hubs REST API
22+
# Tutorial: Send push notifications to Swift iOS apps using Notification Hubs REST API
2323

2424
> [!div class="op_single_selector"]
2525
> * [Objective-C](notification-hubs-ios-apple-push-notification-apns-get-started.md)
@@ -307,7 +307,7 @@ To add and configure the bridging header:
307307
#endif /* BridgingHeader_h */
308308
```
309309

310-
1. Update the Targets **Build Settings** to reference the bridging header:
310+
1. Update the Target's **Build Settings** to reference the bridging header:
311311

312312
1. Open the **Building Settings** tab and scroll down to the **Swift Compiler** section.
313313

0 commit comments

Comments
 (0)