milksad
/
rust-bitcoin-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity

chore: remove redundant words in CONTRIBUTING.md 

Signed-off-by: costcould <fliter@myyahoo.com>
This commit is contained in:
costcould 2025-02-26 00:13:07 +08:00
parent 6c286e32d4
commit 083a33af85
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -130,7 +130,7 @@ adhere to the ideas presented in the following two blog posts:
Whenever any part of your code wants to mention the version number the code will Whenever any part of your code wants to mention the version number the code will
be released in, primarily in deprecation notices, you should use the string be released in, primarily in deprecation notices, you should use the string
`TBD` (verbatim), so that the release preparation script can detect the `TBD` (verbatim), so that the release preparation script can detect the
change and the correct version number can be filled in in preparation of the change and the correct version number can be filled in preparation of the
release. release.
```rust ```rust
@ -360,7 +360,7 @@ All errors that live in an `error` module (eg, `foo/error.rs`) and appear in a p
With respect to `expect` messages, they should follow the With respect to `expect` messages, they should follow the
[Rust standard library guidelines](https://doc.rust-lang.org/std/option/enum.Option.html#recommended-message-style). [Rust standard library guidelines](https://doc.rust-lang.org/std/option/enum.Option.html#recommended-message-style).
More specifically, `expect` messages should be used to to describe the reason More specifically, `expect` messages should be used to describe the reason
you expect the operation to succeed. you expect the operation to succeed.
For example, this `expect` message clearly states why the operation should succeed: For example, this `expect` message clearly states why the operation should succeed: