On 16.08.24 12:49, SurajSonawane2415 wrote: > Fix grammatical errors and improve phrasing in the `reporting-issues.rst` > documentation file. These changes enhance readability and ensure the > accuracy of the instructions provided. > > Signed-off-by: SurajSonawane2415 <surajsonawane0215@xxxxxxxxx> Ha, moving that "the" in the last change would not have been necessary now that the "be" is gone, but whatever: Acked-by: Thorsten Leemhuis <linux@xxxxxxxxxxxxx> Thx again for this. Ciao, Thorsten > --- > V3 -> V4: Adjust line wrapping to split the long line properly. > V2 -> V3: Re-added the fix for the line: "That's why you might be need to uninstall the". > V1 -> V2: Removed the unwanted change to the line: "try search terms like". > > Documentation/admin-guide/reporting-issues.rst | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst > index 2fd5a030235a..d0e645fc845a 100644 > --- a/Documentation/admin-guide/reporting-issues.rst > +++ b/Documentation/admin-guide/reporting-issues.rst > @@ -56,7 +56,7 @@ developers. It might be all that's needed for people already familiar with > reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For > everyone else there is this section. It is more detailed and uses a > step-by-step approach. It still tries to be brief for readability and leaves > -out a lot of details; those are described below the step-by-step guide in a > +out a lot of details; those are described below in the step-by-step guide in a > reference section, which explains each of the steps in more detail. > > Note: this section covers a few more aspects than the TL;DR and does things in > @@ -299,7 +299,7 @@ face, even if they look small or totally unrelated. That's why you should report > issues with these kernels to the vendor. Its developers should look into the > report and, in case it turns out to be an upstream issue, fix it directly > upstream or forward the report there. In practice that often does not work out > -or might not what you want. You thus might want to consider circumventing the > +or might not be what you want. You thus might want to consider circumventing the > vendor by installing the very latest Linux kernel core yourself. If that's an > option for you move ahead in this process, as a later step in this guide will > explain how to do that once it rules out other potential causes for your issue. > @@ -472,8 +472,8 @@ before proceeding. > Note, you might not be aware that your system is using one of these solutions: > they often get set up silently when you install Nvidia's proprietary graphics > driver, VirtualBox, or other software that requires a some support from a > -module not part of the Linux kernel. That why your might need to uninstall the > -packages with such software to get rid of any 3rd party kernel module. > +module not part of the Linux kernel. That's why you might need to uninstall > +the packages with such software to get rid of any 3rd party kernel module. > > > Check 'taint' flag
