Firebase Issues: grammatical errors fixed, improved formatting, added assets

docs/troubleshooting/firebase-issues/_category_.json

@@ -1,3 +1,3 @@
 {
-  "label": "Firebase Issues"
+  "label": "Firebase Troubleshooting"
 }

docs/troubleshooting/firebase-issues/client_access_to_firestore_expired.md

@@ -11,7 +11,7 @@ You may receive an email from Firebase with the subject:
 
 This message typically appears when your Firestore database is in **Test Mode** and the access duration has expired.
 
-**Why Am I Seeing This Message?**
+Reason for This Message
 
     When setting up Firestore for the first time, Firebase offers two rule options:
 

docs/troubleshooting/firebase-issues/configuring_cors_for_firebase_storage.md

@@ -28,37 +28,37 @@ Follow these steps to configure CORS for your Firebase Storage bucket:
 
 3. **Run the following Command:**
 
-    ```js
+    ```jsx
     gcloud config set project <your-project-id>
     ```
 
 4. **Navigate to your Firebase Storage bucket:**
 
-    ```js
+    ```jsx
     cd gs://<your-bucket-name>
     ```
 
 5. **Run the `cors` Command to Configure CORS:**
 
-    ```js
+    ```jsx
     gsutil cors set cors.json gs://<your-bucket-name>
     ```
 
     You can also specify a list of allowed headers by running the following command:
 
-    ```js
+    ```jsx
     gsutil cors set cors.json gs://<your-bucket-name> --allowed-headers="Content-Type, Authorization"
     ```
 
     The `cors.json` file contains a list of origins that are allowed to access your resources. Each origin is a string that identifies a domain or port. For example, the following origin allows access from the domain `www.example.com`:
 
-    ```js
+    ```jsx
     "origins": ["https://www.example.com"]
     ```
 
     You can also specify a list of allowed headers. The following example allows access to the `Content-Type` and `Authorization` headers:
 
-    ```js
+    ```jsx
     "origins": ["https://www.example.com"], "allowedHeaders": ["Content-Type", "Authorization"]
     ```
 

docs/troubleshooting/firebase-issues/content_manager_firestore_error.md

@@ -32,9 +32,9 @@ This error typically occurs when Firebase permissions or authentication settings
 
     FlutterFlow requires the following roles to be granted to `[email protected]` for proper functionality:
 
-    - **Editor**
-    - **Cloud Functions Admin**
-    - **Service Account Admin**
+    - Editor
+    - Cloud Functions Admin
+    - Service Account Admin
 
     To add these permissions:
 
@@ -78,15 +78,13 @@ This error typically occurs when Firebase permissions or authentication settings
 
 
 
-:::info[Still Not Working?]
-Try Reconfiguring Permissions from Scratch
-:::
+:::info[Still not working?]
+Try reconfiguring permissions from scratch.
 
 If none of the steps resolve the issue:
-
 1. Remove existing Firebase permissions.
 2. Re-add all necessary roles from scratch.
 3. Follow the full setup instructions in the **[official FlutterFlow Firebase integration guide](/integrations/firebase/connect-to-firebase/)**.
-
+:::
 
 By following the steps above, you should be able to resolve the error and continue using FlutterFlow CMS without interruptions.

docs/troubleshooting/firebase-issues/firebase_storage_limits_in_flutterflow.md

@@ -12,7 +12,7 @@ Managing Firebase Storage properly is essential for controlling your app's file
 
 - **Spark Plan (Free)**
 
-    - Includes up to **5 GB** of storage.
+    - Includes up to **1 GB** of storage.
     - Exceeding this limit requires upgrading to a paid plan.
 
 - **Blaze Plan (Pay-as-you-go)**

docs/troubleshooting/firebase-issues/what_to_do if_firestore_indexes_are_not_deployed.md → docs/troubleshooting/firebase-issues/resolving_firestore_index_deployment_issues.md

@@ -1,9 +1,9 @@
 ---
-keywords: ['firebase', 'deployed', 'firestore']
-slug: /what-to-do-if-firestore-indexes-are-not-deployed
-title: What to Do If Firestore Indexes Are Not Deployed
+keywords: ['firebase', 'deployment', 'firestore']
+slug: /resolving-firestore-index-deployment-issues
+title: Resolving Firestore Index Deployment Issues
 ---
-# What to Do If Firestore Indexes Are Not Deployed
+# Resolving Firestore Index Deployment Issues
 
 If your Firestore indexes are not being deployed as expected, follow these troubleshooting steps to resolve the issue and ensure your app performs correctly.
 
@@ -30,7 +30,7 @@ If your Firestore indexes are not being deployed as expected, follow these troub
 
     - Update your Firestore rules in both Firebase Console and FlutterFlow.
     - Ensure they match your app’s data access requirements.
-    - **[How to Update Firestore Rules](../integrations/database/cloud-firestore/firestore-rules/)**.
+    - Follow the detailed steps in the **[Firestore Rules documentation](../integrations/database/cloud-firestore/firestore-rules/)** to correctly configure your rules.
 
     ![](../assets/20250430121118592064.png)
 
@@ -45,7 +45,6 @@ If your Firestore indexes are not being deployed as expected, follow these troub
 
 :::tip[Additional Tips]
 - Make sure you completed all the steps above before retrying deployment.
-- If the issue persists, review the **[FlutterFlow help article](https://intercom.help/flutterflow/en/articles/9127351-what-to-do-if-firestore-indexes-are-not-deployed)**.
 - For advanced troubleshooting, check Firebase logs and permissions in Google Cloud Console.
 :::