From 61265b0c1401bd483ea3c04b9304ec36d98c29cd Mon Sep 17 00:00:00 2001
From: dmitry-bychkov <iamdbychkov@gmail.com>
Date: Tue, 24 Jun 2025 18:56:36 +0300
Subject: [PATCH] Add a link to PyPI FAQ to clarify what per-project token is.
 (#14242)

<!--
Thank you for contributing to uv! To help us out with reviewing, please
consider the following:

- Does this pull request include a summary of the change? (See below.)
- Does this pull request include a descriptive title?
- Does this pull request include references to any relevant issues?
-->

## Summary

This change adds a link to PyPI FAQ about API tokens on the package
publishing guide page. To me it wasn't clear what are meant in this
section of the docs and it required a little bit of research. Adding
explicit link might help beginners.

<!-- What's the purpose of the change? What does it do, and why? -->

Co-authored-by: Dmitry Bychkov <dbychkov@alarislabs.com>
---
 docs/guides/package.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guides/package.md b/docs/guides/package.md
index 0914d5750..ce5bae7f9 100644
--- a/docs/guides/package.md
+++ b/docs/guides/package.md
@@ -31,8 +31,8 @@ the effect of declaring a build system in the
     This setting makes PyPI reject your uploaded package from publishing. It does not affect
     security or privacy settings on alternative registries.
 
-    We also recommend only generating per-project tokens: Without a PyPI token matching the project,
-    it can't be accidentally published.
+    We also recommend only generating [per-project PyPI API tokens](https://pypi.org/help/#apitoken):
+    Without a PyPI token matching the project, it can't be accidentally published.
 
 ## Building your package