Skip to content

fix: #39 — Improved readme in doc\release-notes\release-notes-0.18.0.md#343

Open
Bshes wants to merge 1 commit into
BitgesellOfficial:masterfrom
Bshes:fix/bounty-39-1780560570
Open

fix: #39 — Improved readme in doc\release-notes\release-notes-0.18.0.md#343
Bshes wants to merge 1 commit into
BitgesellOfficial:masterfrom
Bshes:fix/bounty-39-1780560570

Conversation

@Bshes
Copy link
Copy Markdown

@Bshes Bshes commented Jun 4, 2026

Spotted a few typos while reading through the release notes. Fixed seperate->separate, accomodate->accommodate and a couple others. Also matched the fixes in sync_log.txt since they reference the same lines. If you prefer to keep the sync log entries untouched, happy to strip those and leave just the release-note fixes. - bshes.g

@MyTH-zyxeon
Copy link
Copy Markdown

Maintainer review note for the #81/#39 bounty queue:

I checked head 30d95cd: this is a very small docs/spelling-only patch. The release-note edits are straightforward (seperate -> separate, accomodate -> accommodate), and the matching doc/code-sync/sync_log.txt entries keep the same misspelling fixes in the generated sync log.

Acceptance checks:

  • Confirm maintainers are comfortable rewriting spelling in historical sync-log commit subjects; if sync_log.txt is meant to preserve upstream commit text verbatim, the release-note-only portion may be safer.
  • Keep this strictly docs-only: no generated release metadata, binaries, or source behavior should change.
  • Run git diff --check before merge because the PR body paths use backslashes while the repo paths are POSIX-style.
  • If BGL PR bounty hunt ($10000 overall budget) #39 bounty triage prefers higher-impact fixes, classify this as a low-payout docs-cleanup item rather than a runtime correctness fix.

No wallet/key/node/live-chain scope; this is documentation hygiene only.

@Bshes
Copy link
Copy Markdown
Author

Bshes commented Jun 4, 2026

Thanks for the review @MyTH-zyxeon. The sync_log.txt edits match the same misspellings in the release notes they reference. But if the team would rather keep the sync log entries as-is (to preserve upstream wording), I can strip those and leave only the release-note fixes. Just say the word.

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