Skip to content

Docs copy cleanup — banned-word + marketing-copy rewrites #34

@vraspar

Description

@vraspar

Two small copy issues surfaced during the x402r-sdk PR #123 (authCapture migration) Round 4 review. Filing here since both are in this repo, not the SDK.

index.mdx:7 — banned word "enables"

Current (line 7):

x402r is a refundable payments protocol extension for x402. It enables secure, reversible transactions with built-in buyer protection through smart contract escrow on Base.

The reviewer's suggested rewrite swapped "It enables" → "x402r adds":

x402r adds secure, reversible transactions with built-in buyer protection through smart contract escrow on Base.

Either way works for the banned-word fix. Whoever picks this up should also match the broader writing-style preference: flowing prose, no scaffolding, no "worth flagging" filler, no em dashes if you can avoid them.

sdk/limitations.mdx:5 — marketing copy

Current (line 5):

The SDK provides full coverage of core payment flows...

Reviewer's rewrite:

Core payment flows (authorization, capture, charge, refund, dispute resolution, evidence submission) are fully supported. This page documents known limitations.

The rewrite is more direct and concrete. Same style preference applies.


Both items are low-priority style nits; not blocking anything. Filed during the x402r-sdk PR #123 Round 4 review since the reviewer correctly tagged them out of that PR's scope.

PR #123: BackTrackCo/x402r-sdk#123
Round 4 review: BackTrackCo/x402r-sdk#123 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions