Address review comments

Author: pinkeshmars

docs/ff-concepts/notifications/imgs/pn-with-data-2.avif

@@ -9,18 +9,18 @@ keywords: [FlutterFlow, Notifications, Concepts]
 
 # Notifications
 
-**Mobile Notifications** are alerts or messages that appear on a user's device outside the normal UI flow of an app. They can inform the user of time-sensitive or high-priority messages, events, or actions that require attention. Notifications may appear as banners, alerts, pop-ups, or lock-screen notifications, depending on user preferences and platform design guidelines.
+**Notifications** are alerts or messages that appear on a user's device outside the normal UI flow of an app. They can inform the user of time-sensitive or high-priority messages, events, or actions that require attention. Notifications may appear as banners, alerts, pop-ups, or lock-screen notifications, depending on user preferences and platform design guidelines.
 
-Notifications enhance your mobile app by increasing user engagement and delivering critical information in real time. Whether it’s an urgent alert or a gentle nudge, these timely messages:
+Notifications enhance your app by increasing user engagement and delivering critical information in real time. Whether it’s an urgent alert or a gentle nudge, these timely messages:
 
 - **Prompt User Action**: Remind users to perform tasks or revisit the app, ensuring higher retention and conversion.
 - **Foster Engagement**: Encourage ongoing interaction through updates, promotions, or new content notifications.
 - **Deliver Value**: Provide relevant insights—such as location-specific alerts or personalized reminders—at the right moment.
 
 ## Types of Notifications
 
-Generally, mobile notifications can be divided into two main categories: **Local Notifications** and **Push (remote) Notifications**.
+Generally, notifications can be divided into two main categories: **Local Notifications** and **Push (remote) Notifications**.
 
-**Local Notifications** are scheduled directly on the device and do not require a server component. They are commonly used for time-based reminders or location-based triggers, such as a daily workout reminder at 7:00 AM. To implement local notifications in FlutterFlow, you can integrate the [flutter_local_notifications](https://pub.dev/packages/flutter_local_notifications) package using custom actions.
+**Local Notifications** are scheduled directly on the device and do not require a server component. They are commonly used for time-based reminders or location-based triggers, such as a daily workout reminder at 7:00 AM. To implement local notifications in FlutterFlow, you can integrate the [flutter_local_notifications](https://pub.dev/packages/flutter_local_notifications) package using [custom actions](../../ff-concepts/adding-customization/custom-actions.md).
 
 **[Push Notifications](push-notifications.md)**, on the other hand, are delivered from a remote server through a platform-specific push notification service. They are primarily used for real-time updates, such as chat messages, social media alerts, or news updates. In FlutterFlow, [Firebase Cloud Messaging](https://firebase.google.com/docs/cloud-messaging) (FCM) is used to handle push notifications, enabling seamless communication between your app and users.

docs/ff-concepts/notifications/notifications.md

@@ -17,18 +17,18 @@ keywords: [FlutterFlow, Actions, Notifications, Push Notifications]
 
 Push notifications involve several key components working together to deliver messages to users' devices. In FlutterFlow, you can construct and send notification payloads—such as title, message body, and additional data like image—to a push service, Firebase Cloud Messaging (FCM). FCM receives notifications and routes them to the appropriate devices.
 
-Each device is identified by a unique **Device Token/Registration Token** generated by the FCM to target specific devices. The Mobile App on the user's device receives these notifications and handles the payload by displaying messages or navigating the user to specific screens.
+Each device is identified by a unique **Device Token/Registration Token** generated by the FCM to target specific devices. The user's device receives these notifications and handles the payload by displaying messages or navigating the user to specific screens.
 
 
-## Add Push Notifications
+## Push Notifications Setup
 
 You can add and send push notifications manually or trigger them based on user actions within the app. Here are the steps in detail:
 
 :::info[General Prerequisites]
-Before you begin, ensure that you have:
-- Completed all steps in the 
+Before you begin, ensure that you:
+- Complete all the steps in 
 [**Firebase Setup**](../../ff-integrations/firebase/connect-to-firebase-setup.md).
-- Upgraded your Firebase project to the [**Blaze plan**](https://firebase.google.com/pricing) to enable cloud functions required for push notifications.
+- Upgrade your Firebase project to the [**Blaze plan**](https://firebase.google.com/pricing) to enable [**Cloud Functions**](https://firebase.google.com/docs/functions), which are required specifically for FlutterFlow’s push notification setup, such as retrieving the FCM token and sending notifications trigger from FlutterFlow.  
 :::
 
 :::info[iOS Prerequisites]
@@ -60,7 +60,7 @@ To enable push notifications:
 
 
 
-:::tip
+:::warning[Upgrading to Blaze Plan]
 If you encounter deployment errors instructing you to contact support, it could be because you recently upgraded your Firebase project to the **Blaze plan**. After upgrading, Firebase may take approximately **10-15 minutes** to propagate the changes. If you receive this error, wait **10-15 minutes** and then try deploying again.
 :::
 
@@ -147,7 +147,7 @@ Click **Upload** and select your APNs auth key file (that you downloaded in the
 </div>
 <p></p>
 
-### Send Push Notifications
+## Send Push Notifications
 
 To send push notifications, go to **FlutterFlow** > **Settings and Integrations** > **Push Notifications**, then open the **Manually Trigger Notifications** section. Enter the notification details and click **Send Notification**. A confirmation popup will appear—type **"Send Notification"** and click **Send Notification** again to deliver your message.
 
@@ -160,7 +160,13 @@ To send push notifications, you need to provide the following details:
 - **Deliver With Sound** **(Optional):** Enable this option if you want the notification to play a sound.
 - **Batch Notifications** **(Optional):** Toggle this setting if you want to send the notification in batches. Enable this only when you have over 10K users.
 - **Scheduled Time (Optional):** Choose the specific date and time for the notification to be sent. This option is available only when the **Allow Scheduling** option is enabled, and the selected date and time follow your timezone.
-- **User References (Optional):** Send push notifications to a specific user or a few users. Enter the user document reference (from the 'users' collection in Firestore) into the *User References*.
+- **User References (Optional):** Send push notifications to a specific user or a few users. Enter the user document reference (from the 'users' collection in Firestore) into the *User References* in this format: `/users/user_id`.
+
+    :::tip
+    You can easily copy and paste the document reference directly from the [**Firestore Data Manager**](../../ff-integrations/database/cloud-firestore/firebase-content-manager.md) in FlutterFlow.
+    
+    ![pn-with-data-2](imgs/pn-with-data-2.avif)
+    :::
 - **Initial Page (Optional):** Choose the page the app should open when the user taps the notification.
 
 <div style={{
@@ -205,7 +211,7 @@ To send a push notification with data, you need a page that accepts a parameter
 
 :::tip
 
-On the page that receives the DocumentReference, you can fetch additional details of the item using the [**Backend Query**](#).
+On the page that receives the DocumentReference, you can fetch additional details of the item using the [**Backend Query**](../../resources/control-flow/backend-logic/backend-query/document-from-reference.md).
 
 :::
 

docs/ff-concepts/notifications/push-notifications.md

@@ -14,7 +14,7 @@ This backend query would help you in retrieving information from a document refe
 :::info[Prerequisites]
 In order to use this backend query, you should have:
 * Completed all the steps of 
-[Firebase Setup](../../../../../docs/ff-integrations/firebase/connect-to-firebase-setup.md) for 
+[**Firebase Setup**](../../../../../docs/ff-integrations/firebase/connect-to-firebase-setup.md) for 
   your project.
 * At least one **Firestore Collection** is defined in your project.
 :::