mirror of
https://github.com/saymrwulf/risc0-curve25519-dalek-source.git
synced 2026-09-04 20:03:40 +00:00
Fix a few typos (#281)
This commit is contained in:
parent
c33b49bf5a
commit
64b26ad074
2 changed files with 3 additions and 3 deletions
|
|
@ -83,9 +83,9 @@ fn gen_u128<R: RngCore>(rng: &mut R) -> u128 {
|
|||
///
|
||||
/// # Returns
|
||||
///
|
||||
/// * A `Result` whose `Ok` value is an emtpy tuple and whose `Err` value is a
|
||||
/// * A `Result` whose `Ok` value is an empty tuple and whose `Err` value is a
|
||||
/// `SignatureError` containing a description of the internal error which
|
||||
/// occured.
|
||||
/// occurred.
|
||||
///
|
||||
/// ## On Deterministic Nonces
|
||||
///
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@
|
|||
//! ## Serialisation
|
||||
//!
|
||||
//! `VerifyingKey`s, `SecretKey`s, `SigningKey`s, and `Signature`s can be serialised
|
||||
//! into byte-arrays by calling `.to_bytes()`. It's perfectly acceptible and
|
||||
//! into byte-arrays by calling `.to_bytes()`. It's perfectly acceptable and
|
||||
//! safe to transfer and/or store those bytes. (Of course, never transfer your
|
||||
//! secret key to anyone else, since they will only need the public key to
|
||||
//! verify your signatures!)
|
||||
|
|
|
|||
Loading…
Reference in a new issue