Reflect explicit macro import in reference

Author: Voultapher

src/names/preludes.md

@@ -79,12 +79,11 @@ alloc/test limitation.
 r[names.preludes.extern.no_std]
 ### The `no_std` attribute
 
-r[names.preludes.extern.no_std.intro]
-By default, the standard library is automatically included in the crate root
-module. The [`std`] crate is added to the root, along with an implicit
-[`macro_use` attribute] pulling in all macros exported from `std` into the
-[`macro_use` prelude]. Both [`core`] and [`std`] are added to the [extern
-prelude].
+r[names.preludes.extern.no_std.intro] By default, the standard library is
+automatically included in the crate root module. The [`std`] crate is added to
+the root. Both [`core`] and [`std`] are added to the [extern prelude]. Standard
+library macros are imported via [use declarations] and are *not* part of the
+[`macro_use` prelude].
 
 r[names.preludes.extern.no_std.allowed-positions]
 The *`no_std` [attribute]* may be applied at the crate level to prevent the
@@ -97,8 +96,7 @@ r[names.preludes.extern.no_std.extern]
 r[names.preludes.extern.no_std.module]
 * Affects which module is used to make up the [standard library prelude] (as described above).
 r[names.preludes.extern.no_std.core]
-* Injects the [`core`] crate into the crate root instead of [`std`], and pulls
-  in all macros exported from `core` in the [`macro_use` prelude].
+* Injects the [`core`] crate into the crate root instead of [`std`].
 
 > [!NOTE]
 > Using the core prelude over the standard prelude is useful when either the crate is targeting a platform that does not support the standard library or is purposefully not using the capabilities of the standard library. Those capabilities are mainly dynamic memory allocation (e.g. `Box` and `Vec`) and file and network capabilities (e.g. `std::fs` and `std::io`).