Tweak

sethmanheim · sethmanheim · commit 02196bbece06 · 2024-01-16T09:31:39.000-08:00
diff --git a/includes/notification-hubs-firebase-deprecation.md b/includes/notification-hubs-firebase-deprecation.md
@@ -11,7 +11,7 @@ title: include file
 ---
 
 > [!NOTE]
-> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 is ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.
+> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 are ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.
 >
 > To help with this transition, we invite you to join our preview program and test the FCM v1 onboarding process for REST APIs in February 2024. This gives you early access to the new features and capabilities, as well as the opportunity to provide feedback and report any issues.
 >

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,7 @@ title: include file`
`11`	`11`	`---`
`12`	`12`
`13`	`13`	`> [!NOTE]`
`14`		`-> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 is ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.`
	`14`	`+> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 are ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.`
`15`	`15`	`>`
`16`	`16`	`> To help with this transition, we invite you to join our preview program and test the FCM v1 onboarding process for REST APIs in February 2024. This gives you early access to the new features and capabilities, as well as the opportunity to provide feedback and report any issues.`
`17`	`17`	`>`