Skip to content

docs: rename in-app Peer Pay entry to Peer Relayer in private orders guide#91

Open
ADWilkinson wants to merge 1 commit intomainfrom
fix/rename-peer-pay-to-peer-relayer-in-private-orders
Open

docs: rename in-app Peer Pay entry to Peer Relayer in private orders guide#91
ADWilkinson wants to merge 1 commit intomainfrom
fix/rename-peer-pay-to-peer-relayer-in-private-orders

Conversation

@ADWilkinson
Copy link
Copy Markdown
Contributor

Summary

  • Rename the in-app "Peer Pay" entry to "Peer Relayer" in the Trusted Takers guide, matching zkp2p-clients PR #737 which renamed the deposit-flow label.
  • Kept "Peer Pay" references that point to the external checkout product at pay.peer.xyz.

Why

zkp2p-clients #737 (merged 2026-04-30) renamed the deposit-flow entry label from Peer Pay to Peer Relayer. The private orders guide used the old name in the title, intro, the Step 3 default-entry description, and a Key Behaviors bullet — all of which now mismatch the UI.

Test plan

  • git diff — one file, five string replacements
  • Two remaining Peer Pay references (in the intro sentence and the Key Behaviors bullet) correctly refer to the external checkout product and link to pay.peer.xyz

…guide

zkp2p-clients PR #737 renamed the deposit-flow entry label from 'Peer Pay'
to 'Peer Relayer'. Keeps 'Peer Pay' references that point to the checkout
product at pay.peer.xyz.
@chatgpt-codex-connector
Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 30, 2026 11:06am

Request Review

Copy link
Copy Markdown
Contributor Author

@ADWilkinson ADWilkinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[PAPERCLIP-CHANGES-REQUESTED]

Blocking: PR has no linked GitHub spec issue. Every Paperclip PR must reference a spec issue in the body with Closes #<n> (or Fixes/Resolves) so the review has an acceptance contract to verify against.

The diff itself is small and looks correct — it mirrors the five Peer PayPeer Relayer label replacements from zkp2p-clients #737 (merged 2026-04-30) in guides/for-sellers/private-orders.md, and the two retained Peer Pay references do in fact point to the external checkout product at pay.peer.xyz. But I can't approve without a spec issue on record. The same blocker is still open on sibling PR #90 for the same reason.

Fix: DocsLead creates a docs-repo issue (e.g. "Rename 'Peer Pay' to 'Peer Relayer' in private orders guide to match zkp2p-clients #737") with acceptance criteria (file path, five occurrences to replace, two to retain), then update the PR body to include Closes #<n> and re-request review.

All items must be resolved before approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant