Apply suggestions from code review

WaffleLapkin · workingjubilee · web-flow · commit b73bfd26e4dd · 2024-04-27T00:47:23.000+02:00
Co-authored-by: Jubilee &lt;46493976+workingjubilee@users.noreply.github.com&gt;
diff --git a/library/core/src/primitive_docs.rs b/library/core/src/primitive_docs.rs
@@ -270,8 +270,8 @@ mod prim_bool {}
 ///
 /// # Never type fallback
 ///
-/// When the compiler sees a value of type `!` it implicitly inserts a coercion (if possible),
-/// to allow type check to infer any type:
+/// When the compiler sees a value of type `!` it implicitly inserts a coercion (if possible)
+/// to allow type checker to infer any type:
 ///
 /// ```rust,ignore (illustrative-and-has-placeholders)
 /// // this
@@ -297,8 +297,13 @@ mod prim_bool {}
 /// { absurd(panic!()) }; // error: can't infer the type of `absurd`
 /// ```
 ///
-/// To prevent such errors, compiler remembers where it inserted `absurd` calls, and if it can't
-/// infer their type, it sets the type to the fallback type. `{ absurd::<Fallback>(panic!()) };`.
+/// To prevent such errors, the compiler remembers where it inserted `absurd` calls, and
+/// if it can't infer their type, it sets the type to the fallback type:
+/// ```rust, ignore
+/// type Fallback = /* An arbitrarily selected type! */;
+/// { absurd::<Fallback>(panic!()) }
+/// ```
+///
 /// This is what is known as "never type fallback".
 ///
 /// Historically fallback was [`()`], causing confusing behavior where `!` spontaneously coerced
