summaryrefslogtreecommitdiffstats
path: root/Documentation/admin-guide/reporting-issues.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/admin-guide/reporting-issues.rst')
-rw-r--r--Documentation/admin-guide/reporting-issues.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index 18d8e25ba9df..d7ac13f789cc 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -1248,7 +1248,7 @@ paragraph makes the severeness obvious.
In case you performed a successful bisection, use the title of the change that
introduced the regression as the second part of your subject. Make the report
-also mention the commit id of the culprit. In case of an unsuccessful bisection,
+also mention the commit id of the culprit. In case of an unsuccessful bisection,
make your report mention the latest tested version that's working fine (say 5.7)
and the oldest where the issue occurs (say 5.8-rc1).