Documentation: fix two typos in latest update to the security report howto

In previous patch "Documentation: clarify the mandatory and desirable
info for security reports" I left two typos that I didn't detect in local
checks. One is "get_maintainers.pl" (no 's' in the script name), and the
other one is a missing closing quote after "Reported-by", which didn't
have effect here but I don't know if it can break rendering elsewhere
(e.g. on the public HTML page). Better fix it before it gets merged.

Signed-off-by: Willy Tarreau <w@1wt.eu>
Link: https://patch.msgid.link/20260404082033.5160-1-w@1wt.eu
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/Documentation/process/security-bugs.rst b/Documentation/process/security-bugs.rst
index 0b1f6d8e3cbe71d68c3900bc21171499891954c4..27b028e858610415c00b1d0d21023c08cfe3d303 100644 (file)
--- a/Documentation/process/security-bugs.rst
+++ b/Documentation/process/security-bugs.rst
@@ -59,7 +59,7 @@ In addition, the following information are highly desirable:
     immediately merged (see Documentation/process/submitting-patches.rst).
     This will save some back-and-forth exchanges if it is accepted, and you
     will be credited for finding and fixing this issue.  Note that in this case
-    only a ``Signed-off-by:`` tag is needed, without ``Reported-by:` when the
+    only a ``Signed-off-by:`` tag is needed, without ``Reported-by:`` when the
     reporter and author are the same.
 
   * **mitigations**: very often during a bug analysis, some ways of mitigating
@@ -88,7 +88,7 @@ recipients to send a report to.  In the Linux kernel, all official maintainers
 are trusted, so the consequences of accidentally including the wrong maintainer
 are essentially a bit more noise for that person, i.e. nothing dramatic.  As
 such, a suitable method to figure the list of maintainers (which kernel
-security officers use) is to rely on the get_maintainers.pl script, tuned to
+security officers use) is to rely on the get_maintainer.pl script, tuned to
 only report maintainers.  This script, when passed a file name, will look for
 its path in the MAINTAINERS file to figure a hierarchical list of relevant
 maintainers.  Calling it a first time with the finest level of filtering will