Address review comments

Author: pinkeshmars

docs/ff-concepts/navigation-routing/nav-overview.md

@@ -10,11 +10,15 @@ sidebar_position: 0
 
 Navigation in FlutterFlow is a crucial aspect of app development, enabling users to move between different pages or screens. This is achieved through a system of routing, where each page is assigned a unique route identifier. Understanding how navigation works and what happens to the navigation stack under the hood can help you create a seamless user experience.
 
-## What is Routing?
+## What are Routes?
+Routes are essentially the paths that define different screens or pages within the app. Each route is associated with a specific screen and has a unique identifier that allows the app to recognize and navigate to it. For example, a route could point to the home screen, a product details page, or a user profile page.
 
-**Routing** refers to the mechanism of defining paths or routes for different screens in an app. Each screen is associated with a unique route name, making it easier to navigate to that screen on events like button clicks. In FlutterFlow, routes are automatically assigned to pages when they are created.
+| Page          | Route            |
+|------------------|------------------|
+| Home             | /home            | 
+| Product Details  | /product-details |
+| Cart             | /cart            |
 
-For example, if you have a home screen, a login screen, and a profile screen, each of these screens will be defined as separate routes in your FlutterFlow project.
 
 ## Navigation Stack Logic
 

docs/ff-concepts/navigation-routing/passing-data.md

@@ -12,7 +12,7 @@ import TabItem from '@theme/TabItem';
 
 As you build your app, you'll often encounter the need to pass through or transfer data from one page to another. For instance, when a user taps on a product item, you may want to send product data to the next page to display its details.
 
-## How to pass data
+## Page parameters
 This process of passing data between pages is accomplished using **Parameters**. When navigating
 from one page to another, you can send parameters to configure the destination
 page based on the data from the current page. This is useful for tasks like
@@ -125,12 +125,13 @@ Page parameters are thus essential for maintaining a seamless user experience,
 enabling the new page to function as intended based on the specific needs and
 inputs from a previous interaction.
 
-## What you can pass
+## Allowed Data Types
 
 You can pass any supported data from one page to another via *page parameter(s)*. You can think of a *page parameter* as a variable that holds the value being passed from one page to another.
 
+:::info
 If you are using Firestore Database, most of the time, you would pass the *Document* (an actual record inside the Firestore collection) and *Document Reference (points to actual document)* between the pages.
-
+:::
 ---
 
 ## Video guide

docs/resources/ui-building-blocks/pages/pages-configuration.md

@@ -20,15 +20,23 @@ This section allows you to define and manage parameters that your page can
 receive from other pages of the app. Parameters are essentially variables that
 hold values which can be passed between pages. For example, you might pass a
 user ID from a list page to a detail page to display specific information about
-that user. Learn more about passing data between pages [here](../../../ff-concepts/navigation-routing/passing-data).
+that user.
+
+:::info[LEARN MORE]
+Learn more about passing data between pages [**here**](../../../ff-concepts/navigation-routing/passing-data).
+:::
 
 ### Route Settings
 
 In FlutterFlow, Route Settings are essential for defining how pages within your
 application are accessed and interacted with. These settings allow you to
 customize the URL paths for web and mobile deep linking, set meaningful Page
 Names as unique identifiers, integrate dynamic parameters into your routes, and
-set access restrictions based on user authentication. Learn more about Routing [here](../../../ff-concepts/navigation-routing/overview).
+set access restrictions based on user authentication.
+
+:::info[LEARN MORE]
+Learn more about Routing [**here**](../../../ff-concepts/navigation-routing/overview).
+:::
 
 ## Advanced Configurations