[LTP] [PATCH] doc: Add testers guide

[Cyril Hrubis]

Hi!
> The paragraph above seems a bit vague or misleading, especially given that
> the upstream kernel itself is tested with LTP and many other test suites.

I've pushed the patch with more typos fixed and slightly adjusted version:

diff --git a/doc/users/testers_guide.rst b/doc/users/testers_guide.rst
index fef8c9697..82ce907a2 100644
--- a/doc/users/testers_guide.rst
+++ b/doc/users/testers_guide.rst
@@ -19,15 +19,15 @@ that upstream releases generally go through extensive validation, including
 test suites like LTP, stability is only guaranteed when you use the upstream
 kernel sources and configuration exactly as released.

-However, this assumption breaks down once you apply any changes: whether that's
+This assumption however down once you apply any changes: whether that's
 modifying the source code, enabling/disabling different `.config` options, or
-backporting patches. Such deviations can introduce subtle bugs or unintended
+backporting patches. Such changes can introduce subtle bugs or unintended
 behavior, even if the upstream kernel is stable.

 For example, backporting patches without their full dependency chain can lead
 to unexpected regressions. Therefore, it’s crucial to test your own kernel
 builds in the environment where they will actually run, using tools like LTP to
-help catch issues that upstream testing might not cover in your specific
+catch issues that does not exists or are not triggered in the upstream
 configuration.


Thanks everyone for the fixes and suggestions!

-- 
Cyril Hrubis
chrubis@suse.cz