updated

Author: mrdavidorok

docs/troubleshooting/migrate-widget-issues/configure_text_widget_auto_size_behavior.md

@@ -21,23 +21,21 @@ The `Auto Size` option allows the `Text` widget to automatically reduce its font
   2. Check its parent widget.
   3. Ensure both width and height are explicitly defined.
 
+  :::warning
   Without defined dimensions, the `Auto Size` feature may not behave as expected.
+  :::
 
   **Behavior Scenarios:**
 
     The following examples illustrate how `Auto Size` behaves under different container configurations:
 
-      - Container with width set to `infinity` and height set to `100px`, `Auto Size` disabled.  
-        The text may overflow beyond the container.
+      - Container with width set to `infinity` and height set to `100px`, `Auto Size` disabled. The text may overflow beyond the container.
 
-      - Container with width set to `infinity` and height set to `100px`, `Auto Size` enabled.  
-        The font size adjusts to fit the defined height.
+      - Container with width set to `infinity` and height set to `100px`, `Auto Size` enabled. The font size adjusts to fit the defined height.
 
-      - Container with width set to `30%` and no height defined, `Auto Size` enabled.  
-        The feature has no visible effect due to missing height constraint.
+      - Container with width set to `30%` and no height defined, `Auto Size` enabled. The feature has no visible effect due to missing height constraint.
 
-      - Container with width set to `70%` and height set to `50px`, `Auto Size` enabled.  
-        The text is resized to the minimum allowed font size to remain within the container.
+      - Container with width set to `70%` and height set to `50px`, `Auto Size` enabled. The text is resized to the minimum allowed font size to remain within the container.
 
         ![](../assets/20250430121459696014.png)
 

docs/troubleshooting/migrate-widget-issues/custom_widget_errors.md

@@ -31,7 +31,9 @@ This article demonstrates common errors and issues that may occur when creating
 
     - **Widget Name Conflicts with Package Name**
 
-        One common issue is using a widget name that conflicts with the name of a package you have imported as a dependency.
+        A common issue is using a widget name that conflicts with the name of an imported package.
+
+        Avoid generic or conflicting names like `main` or `widget`. Use unique widget names that do not overlap with package names.
 
         ![](../assets/20250430121324152439.png)
 
@@ -41,7 +43,7 @@ This article demonstrates common errors and issues that may occur when creating
 
     - **Missing Package Imports in Code**
 
-        After adding an external package as a dependency, it is required to import the package at the top of your code. If you forget to do this, you may encounter errors such as:
+        After adding an external package as a dependency, you must import it at the top of your custom widget code. Failure to do so results in errors such as:
 
         ```js
         The method 'AnimatedText' isn't defined...
@@ -71,7 +73,7 @@ This article demonstrates common errors and issues that may occur when creating
         
     - **Widget Name Mismatch Between UI and Code**
 
-        If you forget to update the widget name in the boilerplate code, a mismatch may occur between the widget name defined in FlutterFlow and the class name in your code. This will lead to compilation errors.
+        A mismatch between the widget name in FlutterFlow and the class name in your code will cause compilation errors.
 
         Incorrect example:
 

docs/troubleshooting/migrate-widget-issues/emoji-size-on-ios-devices.md

@@ -32,11 +32,11 @@ On iOS devices, emojis can appear oversized when rendered inside text widgets, d
    This ensures that the emoji will resize according to the container's constraints and not exceed the intended bounds.
 
    :::tip
-   Auto-sizing works best when paired with fixed dimensions. This combination allows the emoji to scale appropriately while avoiding oversized rendering.
+   Auto-Size works best when combined with fixed container dimensions. This approach prevents oversized emojis and supports responsive layouts.
    :::
 
    ![](../assets/20250430121252902305.png)
 
 :::info
-For more context and support, refer to the **[official FlutterFlow guide on emoji rendering](https://intercom.help/flutterflow/en/articles/7044370-text-emoji-is-very-large-on-some-ios-devices)**.
+For more details and troubleshooting, see the **[official FlutterFlow guide on emoji rendering](https://intercom.help/flutterflow/en/articles/7044370-text-emoji-is-very-large-on-some-ios-devices)**.
 :::

docs/troubleshooting/migrate-widget-issues/infinite_scroll_pagination_in_listview.md

@@ -13,14 +13,14 @@ If a `ListView` with **Infinite Scroll** enabled loads all items at once instead
 - The widget is placed inside a layout that allows height constraints to be respected.
 :::
 
-Follow the steps below to configure listView for pagination:
+Follow the steps below to configure ListView for pagination:
 
 1. **Ensure ListView Has a Defined Height**  
    A `ListView` must have a height constraint to determine the viewport size and paginate correctly. Without a defined height, it will attempt to load all items.
 
 2. **Let ListView Handle Its Own Scrolling**  
    - Disable scrolling in any parent `Column` or scrollable container.  
-   - Enable the **Primary** option and wrap `ListView` in an `Expanded` widget.  
+   - Enable the **Primary** option, and wrap `ListView` in an `Expanded` widget.  
    - This allows `ListView` to control scroll behavior and calculate items to load per page.
 
       ![](../assets/20250430121248035007.png)

docs/troubleshooting/migrate-widget-issues/rive_animation_loading_errors.md

@@ -18,7 +18,7 @@ Rive animations may fail to render when the source file is incorrectly linked. T
 1. **Verify the Rive File URL**  
    Ensure the file URL ends with `.riv` and points directly to a hosted Rive file.
 
-   ```js
+   ```text
    https://public.rive.app/community/runtime-files/1199-2317-jack-olantern.riv
     ```
 
@@ -27,7 +27,7 @@ Rive animations may fail to render when the source file is incorrectly linked. T
 2. **Copy the Correct Link from Rive Community:**
 
     - Go to the animation page on the **[Rive Community](https://rive.app/community/)**.
-    - Right-click the Download button.
+    - Right-click the **Download** button.
     - Select Copy Link Address.
 
         The copied link must end with `.riv`. Any URL that redirects to a webpage or file viewer will fail to render.

docs/troubleshooting/migrate-widget-issues/scroll_to_action_on_page_load.md

@@ -16,7 +16,7 @@ When a `Scroll To Action` fails to trigger during a page load, it is often becau
 ## Steps to Ensure Reliable Scroll Behavior:
 
 1. **Add a Delay Before the Scroll Action**  
-   Insert a `Delay Action` before the `Scroll To Action` to allow the widget tree to complete rendering. Recommended delay duration is `500–700 ms`.
+   Insert a `Delay Action` before the `Scroll To Action` to allow the widget tree to complete rendering. Recommended delay duration is 500 to 700 ms.
 
    ![](../assets/20250430121250453056.png)
 
@@ -33,5 +33,5 @@ When a `Scroll To Action` fails to trigger during a page load, it is often becau
    :::
 
 :::info[Additional Resources]
-**[Scroll To Action Failing on Page Load](https://intercom.help/flutterflow/en/articles/7047006-scroll-to-action-is-not-working-when-used-on-page-load)**
+Refer to **[Scroll To Action Failing on Page Load](https://intercom.help/flutterflow/en/articles/7047006-scroll-to-action-is-not-working-when-used-on-page-load)** for more troubleshooting help.
 :::