[PATCH] docs: admin-guide: fix typos in reporting-issues.rst

[PATCH] docs: admin-guide: fix typos in reporting-issues.rst

[10sharmashivam]

From: Shivam Sharma <10sharmashivam@gmail.com>

Correct pin-point to pinpoint, If that the case to If that is the case,
and its only slightly modified to it's only slightly modified in
Documentation/admin-guide/reporting-issues.rst for proper spelling and grammar.

Signed-off-by: Shivam Sharma <10sharmashivam@gmail.com>
---
 Documentation/admin-guide/reporting-issues.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index 2fd5a030235a..9a847506f6ec 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -41,7 +41,7 @@ If you are facing multiple issues with the Linux kernel at once, report each
 separately. While writing your report, include all information relevant to the
 issue, like the kernel and the distro used. In case of a regression, CC the
 regressions mailing list (regressions@lists.linux.dev) to your report. Also try
-to pin-point the culprit with a bisection; if you succeed, include its
+to pinpoint the culprit with a bisection; if you succeed, include its
 commit-id and CC everyone in the sign-off-by chain.
 
 Once the report is out, answer any questions that come up and help where you
@@ -206,7 +206,7 @@ Reporting issues only occurring in older kernel version lines
 This subsection is for you, if you tried the latest mainline kernel as outlined
 above, but failed to reproduce your issue there; at the same time you want to
 see the issue fixed in a still supported stable or longterm series or vendor
-kernels regularly rebased on those. If that the case, follow these steps:
+kernels regularly rebased on those. If that is the case, follow these steps:
 
  * Prepare yourself for the possibility that going through the next few steps
    might not get the issue solved in older releases: the fix might be too big
@@ -312,7 +312,7 @@ small modifications to a kernel based on a recent Linux version; that for
 example often holds true for the mainline kernels shipped by Debian GNU/Linux
 Sid or Fedora Rawhide. Some developers will also accept reports about issues
 with kernels from distributions shipping the latest stable kernel, as long as
-its only slightly modified; that for example is often the case for Arch Linux,
+it's only slightly modified; that for example is often the case for Arch Linux,
 regular Fedora releases, and openSUSE Tumbleweed. But keep in mind, you better
 want to use a mainline Linux and avoid using a stable kernel for this
 process, as outlined in the section 'Install a fresh kernel for testing' in more
-- 
2.43.0

Re: [PATCH] docs: admin-guide: fix typos in reporting-issues.rst

[Randy Dunlap]

On 5/18/25 10:26 AM, 10sharmashivam@gmail.com wrote:
> From: Shivam Sharma <10sharmashivam@gmail.com>
> 
> Correct pin-point to pinpoint, If that the case to If that is the case,
> and its only slightly modified to it's only slightly modified in
> Documentation/admin-guide/reporting-issues.rst for proper spelling and grammar.
> 
> Signed-off-by: Shivam Sharma <10sharmashivam@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  Documentation/admin-guide/reporting-issues.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
> index 2fd5a030235a..9a847506f6ec 100644
> --- a/Documentation/admin-guide/reporting-issues.rst
> +++ b/Documentation/admin-guide/reporting-issues.rst
> @@ -41,7 +41,7 @@ If you are facing multiple issues with the Linux kernel at once, report each
>  separately. While writing your report, include all information relevant to the
>  issue, like the kernel and the distro used. In case of a regression, CC the
>  regressions mailing list (regressions@lists.linux.dev) to your report. Also try
> -to pin-point the culprit with a bisection; if you succeed, include its
> +to pinpoint the culprit with a bisection; if you succeed, include its
>  commit-id and CC everyone in the sign-off-by chain.
>  
>  Once the report is out, answer any questions that come up and help where you
> @@ -206,7 +206,7 @@ Reporting issues only occurring in older kernel version lines
>  This subsection is for you, if you tried the latest mainline kernel as outlined
>  above, but failed to reproduce your issue there; at the same time you want to
>  see the issue fixed in a still supported stable or longterm series or vendor
> -kernels regularly rebased on those. If that the case, follow these steps:
> +kernels regularly rebased on those. If that is the case, follow these steps:
>  
>   * Prepare yourself for the possibility that going through the next few steps
>     might not get the issue solved in older releases: the fix might be too big
> @@ -312,7 +312,7 @@ small modifications to a kernel based on a recent Linux version; that for
>  example often holds true for the mainline kernels shipped by Debian GNU/Linux
>  Sid or Fedora Rawhide. Some developers will also accept reports about issues
>  with kernels from distributions shipping the latest stable kernel, as long as
> -its only slightly modified; that for example is often the case for Arch Linux,
> +it's only slightly modified; that for example is often the case for Arch Linux,
>  regular Fedora releases, and openSUSE Tumbleweed. But keep in mind, you better
>  want to use a mainline Linux and avoid using a stable kernel for this
>  process, as outlined in the section 'Install a fresh kernel for testing' in more

-- 
~Randy

Re: [PATCH] docs: admin-guide: fix typos in reporting-issues.rst

[Thorsten Leemhuis]

On 18.05.25 19:26, 10sharmashivam@gmail.com wrote:
> From: Shivam Sharma <10sharmashivam@gmail.com>
> 
> Correct pin-point to pinpoint, If that the case to If that is the case,
> and its only slightly modified to it's only slightly modified in
> Documentation/admin-guide/reporting-issues.rst for proper spelling and grammar.
> 
> Signed-off-by: Shivam Sharma <10sharmashivam@gmail.com>

Many thx for this, change looks good.

Acked-by: Thorsten Leemhuis <linux@leemhuis.info>

That being said: I wonder if the the changelog could or should be
improved, as it IMHO just describes what is quite obvious from the
change itself. I'd go with "Fix three spelling/grammar mistakes."
instead[1]. Yes, it's feels like "too short" and "what the subject
already says". But well, there is not much to say here, so why bore
readers with more? But it's just a detail and for a small change like
this likely not worth bothering much about.

Ciao, Thorsten

> ---
>  Documentation/admin-guide/reporting-issues.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
> index 2fd5a030235a..9a847506f6ec 100644
> --- a/Documentation/admin-guide/reporting-issues.rst
> +++ b/Documentation/admin-guide/reporting-issues.rst
> @@ -41,7 +41,7 @@ If you are facing multiple issues with the Linux kernel at once, report each
>  separately. While writing your report, include all information relevant to the
>  issue, like the kernel and the distro used. In case of a regression, CC the
>  regressions mailing list (regressions@lists.linux.dev) to your report. Also try
> -to pin-point the culprit with a bisection; if you succeed, include its
> +to pinpoint the culprit with a bisection; if you succeed, include its
>  commit-id and CC everyone in the sign-off-by chain.
>  
>  Once the report is out, answer any questions that come up and help where you
> @@ -206,7 +206,7 @@ Reporting issues only occurring in older kernel version lines
>  This subsection is for you, if you tried the latest mainline kernel as outlined
>  above, but failed to reproduce your issue there; at the same time you want to
>  see the issue fixed in a still supported stable or longterm series or vendor
> -kernels regularly rebased on those. If that the case, follow these steps:
> +kernels regularly rebased on those. If that is the case, follow these steps:
>  
>   * Prepare yourself for the possibility that going through the next few steps
>     might not get the issue solved in older releases: the fix might be too big
> @@ -312,7 +312,7 @@ small modifications to a kernel based on a recent Linux version; that for
>  example often holds true for the mainline kernels shipped by Debian GNU/Linux
>  Sid or Fedora Rawhide. Some developers will also accept reports about issues
>  with kernels from distributions shipping the latest stable kernel, as long as
> -its only slightly modified; that for example is often the case for Arch Linux,
> +it's only slightly modified; that for example is often the case for Arch Linux,
>  regular Fedora releases, and openSUSE Tumbleweed. But keep in mind, you better
>  want to use a mainline Linux and avoid using a stable kernel for this
>  process, as outlined in the section 'Install a fresh kernel for testing' in more

Re: [PATCH] docs: admin-guide: fix typos in reporting-issues.rst

[Jonathan Corbet]

10sharmashivam@gmail.com writes:

> From: Shivam Sharma <10sharmashivam@gmail.com>
>
> Correct pin-point to pinpoint, If that the case to If that is the case,
> and its only slightly modified to it's only slightly modified in
> Documentation/admin-guide/reporting-issues.rst for proper spelling and grammar.
>
> Signed-off-by: Shivam Sharma <10sharmashivam@gmail.com>
> ---
>  Documentation/admin-guide/reporting-issues.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Applied, thanks.

jon