Address PR comments: update rx.asset documentation

Co-Authored-By: Alek Petuskey <[email protected]>

Author: devin-ai-integration[bot]

docs/assets/overview.md

@@ -58,7 +58,7 @@ Shared assets are placed next to your Python file and are linked to the app's ex
 # my_component.py
 import reflex as rx
 
-# my_script.js is located next to this Python file
+# my_script.js is located in the same directory as this Python file
 def my_component():
     return rx.box(
         rx.script(src=rx.asset("my_script.js", shared=True)),

docs/assets/upload_and_download_files.md

@@ -57,7 +57,7 @@ rx.table.root(
         rx.table.row(
             rx.table.cell(rx.text("When to Use", font_weight="bold")),
             rx.table.cell(rx.text("For files that are part of your application's codebase")),
-            rx.table.cell(rx.text("For files that users upload through your application")),
+            rx.table.cell(rx.text("For files that users upload or generate through your application")),
         ),
         rx.table.row(
             rx.table.cell(rx.text("Availability", font_weight="bold")),
@@ -69,11 +69,7 @@ rx.table.root(
 )
 ```
 
-```md alert
-# Assets are primarily intended for frontend use
 
-Assets in Reflex are primarily intended for frontend use and are not expected to be read from the backend. When assets are needed in both frontend and backend, they are currently copied to the backend (though this behavior may change in future versions).
-```
 
 For more information about assets, see the [Assets Overview](/docs/assets/overview/).
 

docs/wrapping-react/guide.md

@@ -441,28 +441,26 @@ def index():
 
 ## Assets
 
-_Experimental feature added in v0.5.3_.
-
 If a wrapped component depends on assets such as images, scripts, or
-stylesheets, these can kept adjacent to the component code and
-included in the final build using the `rx._x.asset` function.
+stylesheets, these can be kept adjacent to the component code and
+included in the final build using the `rx.asset` function.
 
-`rx._x.asset` returns a relative path that references the asset in the compiled
+`rx.asset` returns a relative path that references the asset in the compiled
 output. The target files are copied into a subdirectory of `assets/external`
 based on the module where they are initially used. This allows third-party
 components to have external assets with the same name without conflicting
 with each other.
 
 For example, if there is an SVG file named `wave.svg` in the same directory as
-this component, it can be rendered using `rx.image` and `rx._x.asset`.
+this component, it can be rendered using `rx.image` and `rx.asset`.
 
 ```python
 class Hello(rx.Component):
     @classmethod
     def create(cls, *children, **props) -> rx.Component:
         props.setdefault("align", "center")
         return rx.hstack(
-            rx.image(src=rx._x.asset("wave.svg"), width="50px", height="50px"),
+            rx.image(src=rx.asset("wave.svg", shared=True), width="50px", height="50px"),
             rx.heading("Hello ", *children),
             **props
         )
@@ -471,4 +469,4 @@ class Hello(rx.Component):
 
 ## Debugging
 
-If you encounter an error while wrapping a component it is recommended to check the Console in the browser developer tools. You can access this by going to inspect element and then clicking on the Console tab on Mac. This is because the Console is where most Javascript errors are logged.
+If you encounter an error while wrapping a component it is recommended to check the Console in the browser developer tools. You can access this by going to inspect element and then clicking on the Console tab on Mac. This is because the Console is where most Javascript errors are logged.