From 0bc6945186ac733d959f761092fcf2be5f6e77a1 Mon Sep 17 00:00:00 2001
From: cyrgani <85427285+cyrgani@users.noreply.github.com>
Date: Sun, 5 Oct 2025 13:58:11 +0200
Subject: [PATCH] give a better example why `std` modules named like primitives
 are needed

---
 library/std/src/lib.rs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/library/std/src/lib.rs b/library/std/src/lib.rs
index da41c1216c4d5..46eb120d65de3 100644
--- a/library/std/src/lib.rs
+++ b/library/std/src/lib.rs
@@ -63,10 +63,10 @@
 //!    type, but not the all-important methods.
 //!
 //! So for example there is a [page for the primitive type
-//! `i32`](primitive::i32) that lists all the methods that can be called on
-//! 32-bit integers (very useful), and there is a [page for the module
-//! `std::i32`] that documents the constant values [`MIN`] and [`MAX`] (rarely
-//! useful).
+//! `char`](primitive::char) that lists all the methods that can be called on
+//! characters (very useful), and there is a [page for the module
+//! `std::char`] that documents iterator and error types created by these methods
+//! (rarely useful).
 //!
 //! Note the documentation for the primitives [`str`] and [`[T]`][prim@slice] (also
 //! called 'slice'). Many method calls on [`String`] and [`Vec<T>`] are actually