From 2a4485f311e6f1f7e7fd822a646216f325faf4fb Mon Sep 17 00:00:00 2001 From: Cesar Alvarez Vallero Date: Fri, 17 Sep 2021 21:23:24 -0300 Subject: [PATCH] Fix typo --- 17_3_Using_BIP32_in_Libwally.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/17_3_Using_BIP32_in_Libwally.md b/17_3_Using_BIP32_in_Libwally.md index 1c9ca50..95ff3f0 100644 --- a/17_3_Using_BIP32_in_Libwally.md +++ b/17_3_Using_BIP32_in_Libwally.md @@ -97,7 +97,7 @@ Alternatively, you can use the `bip32_key_from_parent_alloc` function, which jus struct ext_key *key_address; lw_response = bip32_key_from_parent_alloc(key_external,0,BIP32_FLAG_KEY_PRIVATE,&key_address); ``` -> :warning: **WARNING::** At some point in this hierarchy, you might decide to generate `BIP32_FLAG_KEY_PUBLIC` instead of `BIP32_FLAG_KEY_PRIVATE`. Obviously this decision will be based on your security and your needs, but remember that you only need a public key to generate the actual address. +> :warning: **WARNING:** At some point in this hierarchy, you might decide to generate `BIP32_FLAG_KEY_PUBLIC` instead of `BIP32_FLAG_KEY_PRIVATE`. Obviously this decision will be based on your security and your needs, but remember that you only need a public key to generate the actual address. ### Generate an Address