Skip to content

Commit 0c94fea

Browse files
woodruffwwillingc
andauthored
Apply suggestions from code review
Co-authored-by: Carol Willing <[email protected]>
1 parent b24d423 commit 0c94fea

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/specifications/well-known-project-urls.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Well-known Project URLs in Metadata
1313

1414
Metadata *producers* (such as build tools and individual package
1515
maintainers) may continue to use any labels they please, within the
16-
overall ``Project-URL`` length restrictions. However, users are
16+
overall ``Project-URL`` length restrictions. However, when possible, users are
1717
*encouraged* to pick meaningful labels that normalize to well-known
1818
labels.
1919

@@ -33,7 +33,7 @@ lookup procedure for determining whether a ``Project-URL`` is
3333
``Download-URL``, or other common project URLs.
3434

3535
This allows indices (such as the Python Package Index) and other downstream
36-
metadata consumers to specialize their presentations of project URLs in a
36+
metadata consumers to present project URLs in a
3737
consistent manner.
3838

3939
.. _project-url-label-normalization:
@@ -47,7 +47,7 @@ Label normalization
4747
producers.
4848

4949
To determine whether a ``Project-URL`` label is "well-known," metadata
50-
consumers should first normalize the label before comparing it to the
50+
consumers should normalize the label before comparing it to the
5151
:ref:`list of well-known labels <well-known-labels>`.
5252

5353
The normalization procedure for ``Project-URL`` labels is defined

0 commit comments

Comments
 (0)