improved formating.

Author: mrdavidorok

docs/troubleshooting/deployment/codemagic_deployment_error_identification.md

@@ -30,10 +30,11 @@ Follow the steps below to identify your codemagic error:
 - Now, press **Cmd/Ctrl + F** to search for the term **"error"** in the logs to find the root cause of the issue. Keep pressing **"Enter"** till you find the error ( this is usually at the bottom of the logs ).
 
   If you search for "error" and still don't find an error message that makes sense to you then you can also try with the following keyword:
-    - message
+    
+    **message**
 
-      ![](../assets/20250430121347925706.png)
+    ![](../assets/20250430121347925706.png)
 
-    - Now select and copy this error message and paste it in the Help Center search in the chat icon in the bottom-right corner to search the error. This will help you find the help article for this issue and then you can find the fix for it. 
+- Now select and copy this error message and paste it in the Help Center search in the chat icon in the bottom-right corner to search the error. This will help you find the help article for this issue and then you can find the fix for it. 
 
-      ![](../assets/20250430121348293622.gif)
+  ![](../assets/20250430121348293622.gif)

docs/troubleshooting/deployment/codemagic_deployment_tips.md

@@ -8,7 +8,8 @@ title: CodeMagic Deployment Tips
 Here are some tips to avoid Deployment issues:
 
 :::tip
-- Make sure you've followed all the steps for setting up deployment in your project.
+- Make sure you've followed all the steps for [setting up deployment](http://localhost:3000/deployment/deploy-for-environments/#mobile-deployment)
+ in your project.
 - If you choose a deployment source from a GitHub Repository then please make sure that it's associated with FlutterFlow's GitHub integration.
 - If you are deploying to the Play Store from a GitHub repo, make sure to modify your build.gradle file to sign in release mode.
 - Setting a version number is optional but may be required for specific cases. If you are updating an existing app that has not been deployed using FlutterFlow yet, you will want to specify a version number.

docs/troubleshooting/deployment/resolve_errors_in_downloaded_code.md

@@ -29,7 +29,7 @@ When you download your project from FlutterFlow and run it locally in your IDE,
 
 3. **Upgrading or Downgrading to the correct Flutter version**
 
-    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about upgrading our Flutter [here](https://docs.flutterflow.io/deploying-your-app/testing-your-app/testing-on-mobile-device#id-2.-verify-correct-flutter-version). ​By following these steps, you can fix the errors that you face after downloading the code and run locally. 
+    If the current version on your machine is different than what is currently supported by FlutterFlow, you can downgrade or upgrade to the supported version. You can learn more about [**upgrading Flutter**](https://docs.flutterflow.io/deploying-your-app/testing-your-app/testing-on-mobile-device#id-2.-verify-correct-flutter-version). ​By following these steps, you can fix the errors that you face after downloading the code and run locally. 
 
 If you continue to experience issues, contact the FlutterFlow support team via live chat or email at [email protected].
 

docs/troubleshooting/deployment/run_mode_build_failure.md

@@ -9,13 +9,13 @@ Encountering a "Run mode: Build failed" error can be frustrating when you're eag
 
 This guide provides a structured approach to troubleshooting and resolving "Run mode: Build failed" errors, ensuring a smooth development process for your projects.
 
-1. **Recognizing the Error**
+- **Recognizing the Error**
 
     Here's what the "Run mode: Build failed" error looks like inside of FlutterFlow:
 
     ![](../assets/20250430121148301014.png)
 
-2. **Understanding Test Mode vs. Run Mode**
+- **Understanding Test Mode vs. Run Mode**
 
     Here's a little background on run mode vs. test mode in FlutterFlow. Test mode runs as a "test" to help you identify errors before deployment. These features include a debugger and display warnings. Alternatively, run mode attempts to run the app in **release mode** to better mimic what your users can expect in production. In release mode, **warnings are mostly suppressed**, meaning it's important to ensure you are acknowledging and addressing warnings in debug mode before you enter run mode.
 
@@ -33,7 +33,7 @@ This guide provides a structured approach to troubleshooting and resolving "Run
 
 ## Common Scenarios and Solutions
 
-1. **Custom Code Failures**
+- **Custom Code Failures**
 
     - **Issue**: Your project's custom code doesn't show errors within the editor, but errors appear when you try to run the app.
 
@@ -43,7 +43,7 @@ This guide provides a structured approach to troubleshooting and resolving "Run
 
     - **Best practice**: Consider running the code locally on a sample Flutter project before implementing the custom code inside FlutterFlow to identify possible errors logged.
 
-2. **Widget Failures**
+- **Widget Failures**
 
     - **Issue**: A widget within your app causes the build to fail due to errors.
 
@@ -57,43 +57,43 @@ This guide provides a structured approach to troubleshooting and resolving "Run
 
             - Verify that widgets are named clearly for easy identification
 
-3. **Build Fails Without Error Messages**
+- **Build Fails Without Error Messages**
 
     - **Issue**: The build process fails without displaying an error message, making it challenging to diagnose the problem.
 
     - **Solution**: Download and run the project code locally with a debugger to identify and resolve the issue. If downloading the code is problematic, check your browser's console for errors that might indicate the cause.
 
         ![](../assets/20250430121148811672.png)
 
-4. **Grey Screen in Run Mode**
+- **Grey Screen in Run Mode**
 
     - **Issue**: Encountering a grey screen in run mode usually indicates an error suppressed by the release mode.
 
     - **Solution**: Run the app in test mode to potentially reveal the error for troubleshooting. If test mode does not display errors, use the browser's developer console for clues.
 
 ## Checklist for Troubleshooting
 
-1. **Identify when and where the error occurs**: 
+- **Identify when and where the error occurs**: 
 
     Determine if the error is specific to run mode, test mode, or other instances like APK download or code download.
 
-2. **Locate the source of the error**: 
+- **Locate the source of the error**: 
 
     The error message often provides clues about where the problem lies, whether in custom code, a specific widget, or elsewhere.
 
-3. **Check for platform support**:
+- **Check for platform support**:
 
     For issues related to custom code, ensure compatibility with your target platforms.
 
-4. **Examine widget configuration**: 
+- **Examine widget configuration**: 
 
     Verify that all actions and configurations associated with widgets are complete and correct.
 
-5. **Utilize local debugging**: 
+- **Utilize local debugging**: 
 
     If the error is elusive, running the debugger locally on your downloaded code can help identify the issue.
 
-6. **Leverage browser tools**: 
+- **Leverage browser tools**: 
 
     The browser's console and developer tools can offer insights, especially when dealing with errors that don't manifest in traditional debug outputs.