Update some doc comment wording and release note wording.

Author: andriyDev

crates/bevy_asset/src/meta.rs

@@ -70,9 +70,8 @@ pub enum AssetAction<LoaderSettings, ProcessSettings> {
         processor: String,
         settings: ProcessSettings,
     },
-    /// This asset should fail to load, since the original unprocessed asset was decomposed into
-    /// multiple files. This provides a better error message rather than just saying the file is
-    /// missing.
+    /// This asset has been decomposed into multiple files. The original asset path can no longer be
+    /// loaded.
     Decomposed,
     /// Do nothing with the asset
     Ignore,

crates/bevy_asset/src/processor/process.rs

@@ -401,7 +401,7 @@ impl<'a> WriterContext<'a> {
 
     /// Start writing a single output file, which can be loaded with the `load_settings`.
     ///
-    /// Returns an error if you have previously started writing.
+    /// Returns an error if you have previously called [`Self::write_multiple`].
     pub async fn write_single(self) -> Result<SingleWriter<'a>, ProcessError> {
         let started_writes = self
             .init_context

release-content/release-notes/one_to_many_processing.md

@@ -48,7 +48,9 @@ impl Process for LineSplitterProcess {
 Then if you have an asset like `shakespeare.txt`, you can load these separate files as
 `shakespeare.txt/Line0.line`, `shakespeare.txt/Line1.line`, etc. These separate files can have
 different file extensions, be loaded as completely separate asset types, or be entirely produced
-from scratch within the asset processor!
+from scratch within the asset processor! These files are treated as completely distinct assets, so
+loading them looks like a regular asset load (e.g.,
+`asset_server.load("shakespeare.txt/Line1.line")`).
 
 We plan to use this to break apart large glTF files into smaller, easier-to-load pieces -
-particularly for producing meshlets.
+particularly for producing virtual geometry meshes.