doc:Fix typos #33148

pull bethoffman wants to merge 1 commits into bitcoin:master from bethoffman:fix-typo changing 2 files +2 −2
  1. bethoffman commented at 2:09 AM on August 7, 2025: contributor

    Minor PR to fix spelling

  2. fix typo 30ea384cb5
  3. DrahtBot added the label Docs on Aug 7, 2025
  4. DrahtBot commented at 2:09 AM on August 7, 2025: contributor

    <!--e57a25ab6845829454e8d69fc972939a-->

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    <!--006a51241073e994b41acfe9ec718e94-->

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33148.

    <!--021abf342d371248e50ceaed478a90ca-->

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

    <!--5faf32d7da4f0f540f40219e4f7537a3-->

  5. in src/leveldb/README.md:52 in 30ea384cb5
      48 | @@ -49,7 +49,7 @@ mkdir build
      49 |  cd build
      50 |  cmake -G "Visual Studio 15" ..
      51 |  ```
      52 | -The default default will build for x86. For 64-bit run:
    


    l0rinc commented at 2:44 AM on August 7, 2025:

    This was already proposed upstream at https://github.com/google/leveldb/pull/769 and https://github.com/google/leveldb/pull/739/files - but since that repo is basically dead, you can propose it to our fork in https://github.com/bitcoin-core/leveldb-subtree instead (where it will also likely be ignored since there's an opportunity cost for spending time on these).

  6. DrahtBot added the label CI failed on Aug 7, 2025
  7. DrahtBot commented at 3:06 AM on August 7, 2025: contributor

    <!--85328a0da195eb286784d51f73fa0af9-->

    🚧 At least one of the CI tasks failed. <sub>Task lint: https://github.com/bitcoin/bitcoin/runs/47559074637</sub> <sub>LLM reason (✨ experimental): The CI failure is caused by a failed lint check related to subtree merging.</sub>

    <details><summary>Hints</summary>

    Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

    • Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

    • A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

    • An intermittent issue.

    Leave a comment here, if you need help tracking down a confusing failure.

    </details>

  8. octavio12345300 commented at 3:17 AM on August 7, 2025: none

    LIST

  9. fanquake commented at 8:04 AM on August 7, 2025: member

    PIcked the relevant change into #33125.

  10. fanquake closed this on Aug 7, 2025

  11. fanquake referenced this in commit 7116c65bba on Oct 16, 2025
  12. fanquake referenced this in commit 01af128ecd on Oct 16, 2025
  13. fanquake referenced this in commit 157ed16be9 on Oct 16, 2025
  14. fanquake referenced this in commit cad64b151d on Oct 16, 2025
  15. fanquake referenced this in commit e744fd1249 on Oct 16, 2025
  16. bitcoin locked this on Aug 7, 2026

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-08-23 22:51 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me