Cross-links to related functionality

Author: alice-i-cecile

crates/bevy_ecs/src/system/function_system.rs

@@ -63,6 +63,8 @@ impl SystemMeta {
 /// Borrow-checking is handled for you, allowing you to mutably acccess multiple compatible system parameters at once,
 /// and arbitrary system parameters (like [`EventWriter`](crate::event::EventWriter)) can be conveniently fetched.
 ///
+/// For an alternative approach to split mutable access to the world, see [`World::resource_scope`].
+///
 /// # Example
 /// ```rust
 /// use bevy::ecs::system::SystemState;

crates/bevy_ecs/src/world/mod.rs

@@ -34,6 +34,12 @@ pub use identifier::WorldId;
 /// component type. Entity components can be created, updated, removed, and queried using a given
 /// [World].
 ///
+/// For complex access patterns involving [`SystemParam`](crate::system::SystemParam),
+/// consider using [`SystemState`](crate::system::SystemState).
+///
+/// For split mutable access to the [`World`], use [`World::resource_scope`] or
+/// [`SystemState`](crate::system::SystemState).
+///
 /// # Resources
 ///
 /// Worlds can also store *resources*, which are unique instances of a given type that don't
@@ -926,9 +932,13 @@ impl World {
         }
     }
 
-    /// Temporarily removes the requested resource from this [World], then re-adds it before
+    /// Temporarily removes the requested resource from this [`World`], then re-adds it before
     /// returning. This enables safe mutable access to a resource while still providing mutable
     /// world access
+    ///
+    /// For more complex access patterns, consider using [`SystemState`](crate::system::SystemState).
+    ///
+    /// # Example
     /// ```
     /// use bevy_ecs::{component::Component, world::{World, Mut}};
     /// #[derive(Component)]