fix references

Author: PoojaB26

docs/generated-code/state-mgmt-gen-code.md

@@ -1,5 +1,5 @@
 ---
-slug: /generated-code/state-management-generated-code
+slug: /generated-code/state-management
 title: FlutterFlow State Management
 description: Learn about the state management used in FlutterFlow's generated code.
 tags: [Generated Code, Concepts, State Management]

docs/marketplace/creators-hub/submission-criteria.md

@@ -334,7 +334,7 @@ Building a solid app template goes beyond surface-level design. It's about creat
 - **Criteria:** Implement state management effectively to ensure data is updated and reflected correctly across your application.
 - **Why it Matters:** Proper state management is crucial for building responsive and dynamic Flutter apps. It helps prevent data inconsistencies, improves performance, and makes your code easier to maintain.
 - **What To Do:**
-    - **Choose the right state management scope:** FlutterFlow supports (1) [App State](../../resources/data-representation/app-state.md) (2) [Page State](../../resources/ui/pages/page-lifecycle.md#page-state) and (3) [Component State](../../ff-concepts/state-management/generated-code.md#component-state) variables. Familiarize yourself with these options and scope any state variables to where they are needed. For instance, do not use App State to control the value of a checkbox within a component.
+    - **Choose the right state management scope:** FlutterFlow supports (1) [App State](../../resources/data-representation/app-state.md) (2) [Page State](../../resources/ui/pages/page-lifecycle.md#page-state) and (3) [Component State](../../resources/ui/components/component-lifecycle.md#creating-a-component-state) variables. Familiarize yourself with these options and scope any state variables to where they are needed. For instance, do not use App State to control the value of a checkbox within a component.
     - **Rebuild efficiently:** Ensure changes to state rebuild only the necessary scope for efficiency.
 
 #### 5.10 Organized Widget Tree

docs/resources/control-flow/backend-logic/api/create-test-api-calls.md

@@ -122,7 +122,7 @@ The PUT and PATCH API calls can be defined similarly; make sure you enter a vali
 You can create a group of API calls that share the same base URL. Grouping the API calls helps you add all request headers (e.g., auth token) at once, and they will be automatically added for all the API calls inside the group.
 
 :::warning
-For [**private APIs**](rest-api.md#making-an-api-call-private), headers defined within the group will not be automatically included. You'll need to manually add headers for APIs marked as private.
+For [**private APIs**](rest-api.md#private-api-calls), headers defined within the group will not be automatically included. You'll need to manually add headers for APIs marked as private.
 :::
 
 To create the API Group:

docs/resources/data-representation/app-state.md

@@ -16,7 +16,7 @@ App state variables are specific variables that hold the current state of an app
 
 App state variables should be used in scenarios where the same data needs to be accessed and modified from multiple locations within the app. For instance, in a shopping cart app, items in a user's cart are usually accessible across different pages.
 
-App state variables should not be used for temporary data that doesn't impact the overall state of the application. For instance, a user's temporary input in a form should not be stored in an app state variable. It would be more appropriate to use a [page state](../../resources/ui/pages/page-lifecycle.md#page-state) or [component state](../../ff-concepts/state-management/generated-code.md#component-state) variable instead.
+App state variables should not be used for temporary data that doesn't impact the overall state of the application. For instance, a user's temporary input in a form should not be stored in an app state variable. It would be more appropriate to use a [page state](../../resources/ui/pages/page-lifecycle.md#page-state) or [component state](../../generated-code/state-mgmt-gen-code.md#component-state) variable instead.
 
 ## App State Variables
 
@@ -58,7 +58,7 @@ Head over to the left-side navigation menu and follow the steps below to create
 - **Persisted:** Whether this app state is saved to disk so that it can be loaded when the app is restarted. Otherwise the field will be reset on restart.
 
 :::tip[Generated Code]
-  Curious about what happens when the **Persisted** toggle is on? Check out the [**Generated Code**](../../ff-concepts/state-management/generated-code.md#persisting-app-state) guide.
+  Curious about what happens when the **Persisted** toggle is on? Check out the [**Generated Code**](../../generated-code/state-mgmt-gen-code.md#persisting-app-state) guide.
  :::
 
 

docs/resources/data-representation/global-properties.md

@@ -48,7 +48,7 @@ A list of all the available global properties is as follows:
 - **Current Environment**: Gives you the current [development environment](../../testing-deployment-publishing/development-environments/development-environments.md) value.
 
 :::tip[Generated Code]
-Learn more about the [**Generated Code**](../../ff-concepts/state-management/generated-code.md#global-state) behind Global Properties.
+Learn more about the [**Generated Code**](../../generated-code/state-mgmt-gen-code.md#global-state) behind Global Properties.
 :::
 
 ### Current Time

docs/resources/projects/libraries.md

@@ -325,7 +325,7 @@ To set library values, navigate to **Settings and Integrations > Project Setup >
 <p></p>
 
 :::tip
-For different [**development environments**](../../testing-deployment-publishing/development-environments/development-environments.md) (e.g., development vs. production), you can bind Library Values to [**environment values**](../../testing-deployment-publishing/development-environments/development-environments.md#use-environment-values). For instance, you could have two different Library Values for an API key, such as `DEV_OPENAI_API_KEY` and `PROD_OPENAI_API_KEY`, and bind them to the development and production environments to track API usage separately.
+For different [**development environments**](../../testing-deployment-publishing/development-environments/development-environments.md) (e.g., development vs. production), you can bind Library Values to [**environment values**](../../testing-deployment-publishing/development-environments/development-environments.md#environment-values). For instance, you could have two different Library Values for an API key, such as `DEV_OPENAI_API_KEY` and `PROD_OPENAI_API_KEY`, and bind them to the development and production environments to track API usage separately.
 :::
 
 ## Libraries with Firebase

docs/testing-deployment-publishing/development-environments/development-environments.md

@@ -55,7 +55,7 @@ You can create and switch environments in the **Dev Environments** page in **App
 </div>
 <p></p>
 
-The selected environment is used to generate the proper app code when you run, test, deploy or export your app. The only things that change between environment are the [Firebase Project](#configuring-firebase-or-supabase-for-each-environment) or variables that are tied to [Environment Values](#use-environment-values)
+The selected environment is used to generate the proper app code when you run, test, deploy or export your app. The only things that change between environment are the [Firebase Project](#configuring-firebase-or-supabase-for-each-environment) or variables that are tied to [Environment Values](#environment-values)
 
 
 ### Environment Values

firebase.json

@@ -2322,6 +2322,11 @@
         "source": "/firebase-content-manager",
         "destination": "/integrations/database/cloud-firestore/firestore-content-manager/",
         "type": 301
+      },
+      {
+        "source": "/concepts/state-management/generated-code",
+        "destination": "/generated-code/state-management",
+        "type": 301
       }
     ]
   }