doc: apply doc related suggestions from code review

Co-authored-by: Alejandra González <[email protected]>

Author: kayagokalp

book/src/lint_configuration.md

@@ -843,20 +843,8 @@ that the test calls contains a call to any one of these, lint will mark the test
 
 
 ## `test-without-fail-case-include-indexing-as-fallible`
-Whether to consider indexing as a fallible operation while assesing if a test can fail.
-Indexing is fallible, and thus the a test that is doing that can fail but it is likely
-that tests that fail this way were not intended.
-
-If set true, the lint will consider indexing into a slice a failable case
-and won't lint tests that has some sort of indexing. This analysis still done
-in a interprocedural manner. Meaning that any indexing opeartion done inside of
-a function that the test calls will still result the test getting marked fallible.
-
-By default this is set to `false`. That is because from a usability perspective,
-indexing an array is not the intended way to fail a test. So setting this `true`
-reduces false positives but makes the analysis more focused on possible byproducts
-of a test. That is the set of operations to get the point we assert something rather
-than the existance of asserting that thing.
+Whether to consider indexing (`a[b]`) as a fallible operation while checking if a test can fail.
+Indexing is fallible, and thus it can panic, but this panic is likely not intended to be tested.
 
 **Default Value:** `false`
 
@@ -866,9 +854,9 @@ than the existance of asserting that thing.
 
 
 ## `test-without-fail-case-non-fallible-paths`
-List of full paths of macros and functions, that we want to mark as "not going to fail".
-This allows us to make the lint more focused on actual short comings of our test suite
-by marking common routines non-fallible, even though they are fallible.
+List of full paths of macros and functions, that will not count as fallible.
+This allows the user to make the lint more focused on actual short comings of the test suite
+by marking common routines non-fallible, even though they are.
 
 **Default Value:** `["std::print", "std::println", "std::dbg", "std::eprint", "std::eprintln"]`
 

clippy_lints/src/test_without_fail_case.rs

@@ -47,7 +47,7 @@ declare_clippy_lint! {
     #[clippy::version = "1.82.0"]
     pub TEST_WITHOUT_FAIL_CASE,
     restriction,
-    "test function cannot fail because it does not anyway to panic or assert"
+    "test function cannot fail because it does not call anywhere to panic or assert"
 }
 
 pub struct TestWithoutFailCase {
@@ -231,9 +231,7 @@ impl<'tcx> Visitor<'tcx> for SearchFailIntraFunction<'_, 'tcx> {
                     // unlikely that this is intended as the tests assertion. In the name of
                     // reducing false negatives we are giving out soundness.
                     //
-                    // This decision can be justified as it is highly unlikely that this lint is sound
-                    // without this additional check, and with this we are reducing the number of false
-                    // negatives.
+                    // This reduces the number of false positives
                     if self.search_config.non_fallible_paths.contains(&macro_with_path) {
                         return;
                     }