Skip to content

docs: sync Infinity FAQ with current state (2026-04-20) — high-risk#113

Open
chef-eric wants to merge 1 commit intoenfrom
doc-sync/2026-04-20-infinity-reviewed
Open

docs: sync Infinity FAQ with current state (2026-04-20) — high-risk#113
chef-eric wants to merge 1 commit intoenfrom
doc-sync/2026-04-20-infinity-reviewed

Conversation

@chef-eric
Copy link
Copy Markdown

Documentation Sync — 2026-04-20 (high-risk, needs review)

Scan target: infinity-core. Two stale references in the PancakeSwap Infinity FAQ.

Changes applied

trade/trading-faq/pancakeswap-infinity-faq.md

  1. Q4 (line 40) — "Once launched in Q3, users can swap on Infinity..." predates Infinity's mainnet launch on BSC (Mar 2025). Rewritten in present tense.
  2. Q6 (line 48) — Whitepaper link pointed to github.com/pancakeswap/pancake-v4-core (GitHub redirects this but the repo was renamed to infinity-core in Feb 2025). Updated to canonical URL.

Source verification

Not changed (flagged but out of scope for this PR)

  • Blog article URLs with pancake-swap-v4 slug (lines 18, 30, 60, 64, 68) — those are blog.pancakeswap.finance URLs controlled by marketing, not the doc repo. Changing them could break links.
  • Utm-tagged pancakeswap.finance/v4 marketing URL in Q6 — same reason.

Pages scanned (no drift)

  • trade/pancakeswap-infinity/README.md
  • trade/pancakeswap-infinity/key-features.md
  • trade/pancakeswap-infinity/faqs.md
  • trade/pancakeswap-infinity/farms.md
  • trade/pancakeswap-infinity/how-to-guides.md
  • trade/pancakeswap-infinity/hooks/*
  • trade/pancakeswap-infinity/pool-types/*

Auto-generated by doc-sync agent. Merge to apply; close to reject; comment to request changes. @cheferic @chef-miso please review.

…FAQ (2026-04-20)

Q4: "Once launched in Q3, users can swap on Infinity..." predates Infinity's
mainnet launch. Rewrite in present tense.

Q6: Whitepaper link points to pancake-v4-core, which was renamed to
infinity-core in Feb 2025.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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