manual/files/asset_libraries/introduction.rst

@@ -209,18 +209,33 @@ Included in this library are:
 
 .. _asset-libraries-design-limitations:
 
+.. _asset-system-files
+
+Asset System Files (`.asset.blend` Extention)
+=============================================
+
+Some types of assets can be edited without having to open a blend-file inside of an asset library.
+Blender saves these assets to libraries in special files using the `.asset.blend` extension. They
+are entirely managed by Blender's asset system, and only contain a single asset and its
+dependencies.
+
+`.asset.blend` files may be deleted or overwritten by Blender's asset system at any time. Hence,
+saving changes to them is highly discouraged, as they can easily be lost. Attempting to save edits
+to such a file will spawn a warning popup, giving you the choice to use
+:ref:`Save As <bpy.ops.wm.save_as_mainfile>` to instead save the changes in a new, regular
+blend-file.
+
+Currently, only brush assets support this feature.
+
+
 Design Limitations
 ==================
 
-Blender is **not allowed to write to other blend-files** than the one you have currently open.
-This means that to edit an asset, you have to open its blend-file.
-Fortunately this is only a single click away, both in the Source List region of the Asset Browser
+Blender is **not allowed to write to other blend-files** than the one you have currently open, or
+the special `.asset.blend` files explained above. This means that to edit an asset, you have to
+open its blend-file. Fortunately this is only a single click away, both in the Source List region of the Asset Browser
 and in the asset context menu.
 
-This also means that **Blender does not copy assets into the asset library** for you.
-You are responsible for placing the blend-file with the asset in an asset library directory,
-and marking the asset as such. See :ref:`asset-pushing` for more on this topic.
-
 
 .. _asset-libraries-future-development: