replace ecommerce links (#316)

Author: PoojaB26

docs/ff-integrations/authentication/firebase-auth/google-login.md

@@ -126,7 +126,7 @@ To let users log out of your app, you can use the [**Logout**](auth-actions.md#l
       your [Project Credentials](https://console.cloud.google.com/apis/credentials?project=_) page.
 
     2. Ensure you are on the correct project. In our case, we are using the
-      [EcommerceFlow demo project](https://bit.ly/ff-docs-demo-v1), it will be different for you.
+      [EcommerceFlow demo project](https://bit.ly/ff-docs-demo-v2), it will be different for you.
 
     ![credential-page.png](../imgs/credential-page.png)
 

docs/generated-code/component-gen-code.md

@@ -9,7 +9,7 @@ sidebar_position: 5
 Similar to a [**Page**](pages-generated-code.md), when creating a **[component](../resources/ui/components/intro-components.md)** in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class. 
 
 :::info[Prerequisites]
-This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 ## ComponentModel class

docs/generated-code/custom-data-type-gen.md

@@ -7,7 +7,7 @@ sidebar_position: 2
 # DataTypeStruct class
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 

docs/generated-code/directory-structure.md

@@ -7,7 +7,7 @@ sidebar_position: 1
 # Directory Structure
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 When you download the code generated by FlutterFlow, you'll notice many additional files and folders beyond what you see in FlutterFlow's Code Viewer. These files make up the complete project structure, organized according to a specific architecture. Understanding this structure is like having a detailed map, guiding you through the code and making it easier to navigate and customize your FlutterFlow project later. So, let's dive in and explore this directory structure.

docs/generated-code/ff-app-state.md

@@ -6,14 +6,14 @@ sidebar_position: 4
 # FFAppState
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 The `FFAppState` class in FlutterFlow acts as a central hub for managing the application's global state. It's designed as a singleton, meaning there's only one instance of this class throughout the app's lifecycle. This class extends [**ChangeNotifier**](https://api.flutter.dev/flutter/foundation/ChangeNotifier-class.html), allowing widgets to listen and react to state changes.
 
 It includes methods for initializing and updating the app's persisted state and also defines various state variables with corresponding **getters and setters** for manipulating these values.
 
-Here is a basic template of the class, taken from the [**eCommerceFlow demo app**](https://bit.ly/ff-docs-demo-v1)'s generated code:
+Here is a basic template of the class, taken from the [**eCommerceFlow demo app**](https://bit.ly/ff-docs-demo-v2)'s generated code:
 
 ```js
 class FFAppState extends ChangeNotifier {

docs/generated-code/pages-generated-code.md

@@ -9,7 +9,7 @@ sidebar_position: 5
 When you create a new Page in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class. So if the name of the page you created is called **ProductListPage**, FlutterFlow generation backend will automatically create **ProductListPageWidget** class and **ProductListPageModel** class. 
 
 :::info[Prerequisites]
-This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 ## PageModel class

docs/resources/control-flow/functions/utility-functions.md

@@ -30,7 +30,7 @@ FlutterFlow has the following built-in functions:
 ## Combine Text
 
 Oftentimes, you will encounter scenarios where you need to show two variables in a single String or
-Text widget. For example, in our [Ecommerce Demo](https://bit.ly/ff-docs-demo-v1) app, we have a price object in the following
+Text widget. For example, in our [Ecommerce Demo](https://bit.ly/ff-docs-demo-v2) app, we have a price object in the following
 format:
 
 ```json

docs/resources/ui/components/intro-components.md

@@ -67,7 +67,7 @@ some common use-cases.
 - Design sections of a screen that are frequently repeated, such as testimonials, image galleries,
    or feature highlights, and reuse them to maintain a cohesive layout.
 
-Here's an example of all the widely used components used in the [EcommerceFlow demo](https://bit.ly/ff-docs-demo-v1) app.
+Here's an example of all the widely used components used in the [EcommerceFlow demo](https://bit.ly/ff-docs-demo-v2) app.
 
 
 <figure>

docs/resources/ui/overview.md

@@ -49,7 +49,7 @@ various UI elements to form a complete screen in the app. When you create a new
 FlutterFLow, an empty page called `HomePage` is the first thing you see on your canvas. 
 
 How you define your pages defines the flow of the app and user experience for the user. For 
-example, in our [**E-commerce Demo app**](https://bit.ly/ff-docs-demo-v1), after login, the user lands on `ProductListPage` which has a 
+example, in our [**E-commerce Demo app**](https://bit.ly/ff-docs-demo-v2), after login, the user lands on `ProductListPage` which has a 
 NavigationBar at the bottom that takes the user to different Pages in the app such as 
 `ProfilePage`, etc. 
 
@@ -98,7 +98,7 @@ you're creating an **instance** of the `Icon` widget class and providing differe
 each use.
 
 Think of classes as templates that outline the structure and features of
-something you want to create multiple times. For instance, in our demo app [EcommerceFlow](https://bit.ly/ff-docs-demo-v1), we
+something you want to create multiple times. For instance, in our demo app [EcommerceFlow](https://bit.ly/ff-docs-demo-v2), we
 have a reusable component called `ProductListCard` with specific characteristics such as image,
 product information text, and actions it should perform when clicked. Here, we've essentially
 created a **class**.