aboutsummaryrefslogtreecommitdiff
path: root/src/secp256k1/examples/ecdsa.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/secp256k1/examples/ecdsa.c')
-rw-r--r--src/secp256k1/examples/ecdsa.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/secp256k1/examples/ecdsa.c b/src/secp256k1/examples/ecdsa.c
index d1d2b0e365..d5c4613d9c 100644
--- a/src/secp256k1/examples/ecdsa.c
+++ b/src/secp256k1/examples/ecdsa.c
@@ -128,7 +128,7 @@ int main(void) {
/* It's best practice to try to clear secrets from memory after using them.
* This is done because some bugs can allow an attacker to leak memory, for
- * example through "out of bounds" array access (see Heartbleed), Or the OS
+ * example through "out of bounds" array access (see Heartbleed), or the OS
* swapping them to disk. Hence, we overwrite the secret key buffer with zeros.
*
* Here we are preventing these writes from being optimized out, as any good compiler