Apply suggestions from code review

Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <[email protected]>

Author: befeleme

source/guides/licensing-examples-and-user-scenarios.rst

@@ -10,9 +10,9 @@ Licensing examples and user scenarios
 license files and other legally required information.
 This document aims to provide clear guidance how to migrate from the legacy
 to the standardized way of declaring licenses.
-Make sure your preferred build backend supports PEP 639 before
+Make sure your preferred build backend supports :pep:`639` before
 trying to apply the newer guidelines.
-As of February 2025, setuptools and flit don't support PEP 639 yet.
+As of February 2025, setuptools and flit don't support :pep:`639` yet.
 
 
 Licensing Examples

source/guides/writing-pyproject-toml.rst

@@ -325,13 +325,13 @@ You can also specify the format explicitly, like this:
 ``license``
 -----------
 
-PEP 639 (accepted in August 2024) has changed the way the ``license`` field
-is declared. Make sure your preferred build backend supports PEP 639 before
+:pep:`639` (accepted in August 2024) has changed the way the ``license`` field
+is declared. Make sure your preferred build backend supports :pep:`639` before
 trying to apply the newer guidelines.
-As of February 2025, setuptools and flit don't support PEP 639 yet.
+As of February 2025, setuptools and flit don't support :pep:`639` yet.
 
-PEP 639 license declaration
-'''''''''''''''''''''''''''
+:pep:`639` license declaration
+''''''''''''''''''''''''''''''
 
 This is a valid :term:`SPDX license expression <License Expression>` consisting
 of one or more :term:`license identifiers <License Identifier>`.
@@ -364,7 +364,7 @@ Legacy license declaration
 ''''''''''''''''''''''''''
 
 This can take two forms. You can put your license in a file, typically
-``LICENSE`` or ``LICENSE.txt``, and link that file here:
+:file:`LICENSE` or :file:`LICENSE.txt`, and link that file here:
 
 .. code-block:: toml
 
@@ -388,10 +388,10 @@ whose license is unapproved.)
 ``license-files``
 -----------------
 
-PEP 639 (accepted in August 2024) has introduced the ``license-files`` field.
-Make sure your preferred build backend supports PEP 639 before declaring the
+:pep:`639` (accepted in August 2024) has introduced the ``license-files`` field.
+Make sure your preferred build backend supports :pep:`639` before declaring the
 field.
-As of February 2025, setuptools and flit don't support PEP 639 yet.
+As of February 2025, setuptools and flit don't support :pep:`639` yet.
 
 This is a list of license files and files containing other legal
 information you want to distribute with your package.