Apply suggestions from code review

Co-authored-by: Miguel Ojeda <[email protected]>

Author: nbdd0121

lib/Kconfig.debug

@@ -2648,8 +2648,8 @@ choice
 	help
 	  Controls how are `build_error!` and `build_assert!` handled during build.
 
-	  If calls to them exist in the binary, it may indicates a violated invariant
-	  or that the optimizer fails to verify the invariant during compilation.
+	  If calls to them exist in the binary, it may indicate a violated invariant
+	  or that the optimizer failed to verify the invariant during compilation.
 	  You can choose to abort compilation or ignore them during build and let the
 	  check be carried to runtime.
 

rust/build_error.rs

@@ -2,9 +2,9 @@
 
 //! Build-time error.
 //!
-//! This crate provides a method `build_error`, which will panic in
+//! This crate provides a function `build_error`, which will panic in
 //! compile-time if executed in const context, and will cause a build error
-//! if not executed in compile time and optimizer does not optimise away the
+//! if not executed at compile time and the optimizer does not optimise away the
 //! call.
 //!
 //! It is used by `build_assert!` in the kernel crate, allowing checking of

rust/kernel/build_assert.rs

@@ -2,8 +2,7 @@
 
 //! Build-time assert.
 
-/// Causes build to fail if the code path calling `build_error!` can possibly be
-/// executed.
+/// Fails the build if the code path calling `build_error!` can possibly be executed.
 ///
 /// If the macro is executed in const context, `build_error!` will panic.
 /// If the compiler or optimizer cannot guarantee that `build_error!` can never
@@ -36,7 +35,7 @@ macro_rules! build_error {
 ///
 /// # Examples
 ///
-/// This examples show that different types of [`assert!`] will trigger errors
+/// These examples show that different types of [`assert!`] will trigger errors
 /// at different stage of compilation. It is preferred to err as early as
 /// possible, so [`static_assert!`] should be used whenever possible.
 /// ```no_run
@@ -47,7 +46,7 @@ macro_rules! build_error {
 /// }
 /// ```
 ///
-/// When condition refers to generic parameter or parameter of an inline function,
+/// When the condition refers to generic parameters or parameters of an inline function,
 /// [`static_assert!`] cannot be used. Use `build_assert!` in this scenario.
 /// ```no_run
 /// fn foo<const N: usize>() {