Skip to content

fix: #32#344

Open
Bshes wants to merge 1 commit into
BitgesellOfficial:masterfrom
Bshes:fix/bounty-32-1780563593
Open

fix: #32#344
Bshes wants to merge 1 commit into
BitgesellOfficial:masterfrom
Bshes:fix/bounty-32-1780563593

Conversation

@Bshes

@Bshes Bshes commented Jun 4, 2026

Copy link
Copy Markdown

Spotted a few things to clean up in the docs while going through doc\code-sync\sync_log.txt, doc\release-notes\release-notes-0.18.0.md, doc\release-notes\release-notes-0.20.0.md. Fixed some typos and improved the wording in a couple places. The docs should be a bit clearer now. - bshes.g

@MyTH-zyxeon

Copy link
Copy Markdown

Maintainer review note for #32:

This is a narrow docs-only spelling cleanup (7 lines across doc/code-sync/sync_log.txt and two release-note files), and the PR is currently OPEN / MERGEABLE / CLEAN with no visible checks required.

The one acceptance point I would confirm before merge is whether doc/code-sync/sync_log.txt is intended to preserve upstream/historical commit subjects verbatim. If it is an audit-style sync log, rewriting historical titles from accomodate/seperate to corrected spelling may be less desirable than leaving exact upstream text intact. If maintainers treat it as editable Bitgesell documentation, the diff is low-risk.

Suggested lightweight validation before accepting:

  • git diff --check
  • rendered Markdown review for the two release-note files
  • explicit maintainer call on whether historical sync-log subjects may be normalized under the BGL PR bounty hunt #32 docs-cleanup bounty lane

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