Merge tag 'docs-6.3-2' of git://git.lwn.net/linux

Pull Documentation stragglers from Jonathan Corbet:
 "A handful of documentation patches that were ready before the merge
  window, but which I didn't get merged for the first round:

   - A recommendation from Thorsten (also akpm) on use of Link tags to
     point out problem reports

   - Some front-page formatting tweaks

   - Another Spanish translation

   - One typo(ish) fix"

* tag 'docs-6.3-2' of git://git.lwn.net/linux:
  docs: recommend using Link: whenever using Reported-by:
  Documentation: front page: use recommended heading adornments
  docs/sp_SP: Add process programming-language translation
  docs: locking: refer to the actual existing config names

diff --combined Documentation/process/submitting-patches.rst
index fab44ae732e3f859b5f7e2414b276e77515c59d9,1e009dbe6991b45a105a06d9b5f69ae74c0e8fd5..eac7167dce83d0fd7665a874aceaa4c9fa5d9e83
--- 1/Documentation/process/submitting-patches.rst
--- 2/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@@ -407,7 -407,7 +407,7 @@@ then you just add a line saying:
  
        Signed-off-by: Random J Developer <random@developer.example.org>
  
 -using your real name (sorry, no pseudonyms or anonymous contributions.)
 +using a known identity (sorry, no anonymous contributions.)
  This will be done for you automatically if you use ``git commit -s``.
  Reverts should also include "Signed-off-by". ``git revert -s`` does that
  for you.
@@@ -496,10 -496,11 +496,11 @@@ Using Reported-by:, Tested-by:, Reviewe
  ----------------------------------------------------------------------
  
  The Reported-by tag gives credit to people who find bugs and report them and it
- hopefully inspires them to help us again in the future.  Please note that if
- the bug was reported in private, then ask for permission first before using the
- Reported-by tag. The tag is intended for bugs; please do not use it to credit
- feature requests.
+ hopefully inspires them to help us again in the future. The tag is intended for
+ bugs; please do not use it to credit feature requests. The tag should be
+ followed by a Link: tag pointing to the report, unless the report is not
+ available on the web. Please note that if the bug was reported in private, then
+ ask for permission first before using the Reported-by tag.
  
  A Tested-by: tag indicates that the patch has been successfully tested (in
  some environment) by the person named.  This tag informs maintainers that