From b3a9b84b37c0c30f4411ad1e09d8f89e9aaa7434 Mon Sep 17 00:00:00 2001
From: littleyier <153109197+LittleYier@users.noreply.github.com>
Date: Thu, 10 Sep 2026 06:02:48 +0900
Subject: [PATCH] doc: Correct upstream-pull reference

---
 doc/productivity.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/productivity.md b/doc/productivity.md
index c436811a0a8..6bc5c22ec4b 100644
--- a/doc/productivity.md
+++ b/doc/productivity.md
@@ -156,7 +156,7 @@ As an alternative to fetching commits directly, when looking at pull requests by
         url = git@github.com:bitcoin/bitcoin.git
 ```
 
-This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. It will download and store on disk quite a lot of data (all PRs, including merged and closed ones). Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER.
+This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. It will download and store on disk quite a lot of data (all PRs, including merged and closed ones). Afterwards, you can use `upstream-pull/NUMBER` in arguments to `git show`, `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER.
 
 ### Fetch and update PRs individually