doc:Fix typos #33148

1. 
   bethoffman commented at 2:09 am on August 7, 2025: none

   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

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

   Code Coverage & Benchmarks

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

   Reviews

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

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

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

   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.

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

    ---

Contributors
bethoffman DrahtBot l0rinc octavio12345300 fanquake

Labels
Docs CI failed