Skip to content

[fix] correct numbering and link errors in FAQ docs#3698

Merged
morningman merged 3 commits into
apache:masterfrom
boluor:fix-faq-batch7
May 20, 2026
Merged

[fix] correct numbering and link errors in FAQ docs#3698
morningman merged 3 commits into
apache:masterfrom
boluor:fix-faq-batch7

Conversation

@boluor
Copy link
Copy Markdown
Contributor

@boluor boluor commented May 19, 2026

Summary

Three small fixes to FAQ pages under docs/faq.

  • sql-faq.md — a ### Q5 section appeared twice consecutively with the same title and near-identical content (the second copy also contained a bitmp typo). The duplicate has been removed.
  • install-faq.md — question numbering jumped from Q13 straight to Q15 (no Q14). The trailing questions are renumbered down by one so the sequence is continuous.
  • load-faq.md — a PR reference in the optimization table had link text #3727 while the URL pointed to pull/40728. The text is corrected to #40728 to match the URL (consistent with the other PR references in the same table).

Test plan

  • CI doc build passes
  • Verify the FAQ pages render with continuous question numbering and no duplicate section

Batch fix for 3 issues found in a documentation audit:
- sql-faq.md: remove a duplicated "### Q5" section (same title and
  near-identical content, appeared twice consecutively)
- install-faq.md: question numbering jumped Q13 -> Q15; renumber the
  trailing questions so the sequence is continuous
- load-faq.md: PR link text "#3727" did not match its URL pull/40728;
  align the text with the URL

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
boluor added 2 commits May 19, 2026 17:04
The CI pipeline no longer builds these legacy versions, so changes there
cannot be merged. Restore those files to their base state.
The ja-source CI pipeline is not yet supported, so changes there cannot
be merged. Restore the affected ja-source files to their base state.
@morningman morningman merged commit 26b02c0 into apache:master May 20, 2026
3 of 4 checks passed
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.

2 participants