This PR is to fix some spelling mistakes i found of the word occurrences! there are two occurrences of this mistake.
thanks!
This PR is to fix some spelling mistakes i found of the word occurrences! there are two occurrences of this mistake.
thanks!
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32961.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | delta1, maflcko, willcl-ark |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
9 | @@ -10,7 +10,7 @@ 10 | "notes" : { 11 | "ArithmeticError" : { 12 | "bugType" : "EDGE_CASE", 13 | - "description" : "Some implementations of ECDSA have arithmetic errors that occur when intermediate results have extreme values. This test vector has been constructed to test such occurences.", 14 | + "description" : "Some implementations of ECDSA have arithmetic errors that occur when intermediate results have extreme values. This test vector has been constructed to test such occurrences.",
it has come to my attention that i cant change this file, so i can remove this one if thats a problem
I removed the occurrence of the spelling mistake in this commit https://github.com/bitcoin/bitcoin/commit/84ef5524d5abaf07cc9970f42e74ee15bd381e3d
I think this change would have to be upstream at bitcoin-core/secp256k1
<!--85328a0da195eb286784d51f73fa0af9-->
🚧 At least one of the CI tasks failed.
<sub>Task lint: https://github.com/bitcoin/bitcoin/runs/45887606487</sub>
<sub>LLM reason (✨ experimental): The CI failure is caused by errors in the lint step, specifically related to subtree merging issues.</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>
ACK 84ef5524d5abaf07cc9970f42e74ee15bd381e3d
just a typo fix in a markdown file
lgtm ACK 84ef5524d5abaf07cc9970f42e74ee15bd381e3d
ACK 84ef5524d5abaf07cc9970f42e74ee15bd381e3d