summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorstefanwouldgo <stefan@sblbs.de>2019-11-28 13:41:28 +0100
committerPieter Wuille <pieter.wuille@gmail.com>2020-01-19 14:47:33 -0800
commit8baf6f5952d4a1fe1020de075ab93179e6236a55 (patch)
tree352c1b597401c18ab6aedfc9637a2a2a47fe7e24
parenta65101ff6d803feb582c8f21788fe5341cbff07d (diff)
downloadbips-8baf6f5952d4a1fe1020de075ab93179e6236a55.tar.xz
fix singular/plural ambiguity
-rw-r--r--bip-taproot.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-taproot.mediawiki b/bip-taproot.mediawiki
index ba8d048..d3e2222 100644
--- a/bip-taproot.mediawiki
+++ b/bip-taproot.mediawiki
@@ -114,7 +114,7 @@ The following use of <code>hash_type</code> are invalid, and fail execution:
As the message for signature verification, transaction digest is ''hash<sub>TapSighash</sub>'' of the following values (size in byte) serialized. Numerical values in 2, 4, or 8-byte are encoded in little-endian.
* Control:
-** <code>epoch</code> (1): always 0. <ref>'''What's the purpose of the epoch?''' The <code>epoch</code> can be increased to allow securely creating a new transaction digest algorithm with large changes to the structure or interpretation of <code>hash_type</code> if needed.</ref>
+** <code>epoch</code> (1): always 0. <ref>'''What's the purpose of the epoch?''' The <code>epoch</code> can be increased to allow securely creating new transaction digest algorithms with large changes to the structure or interpretation of <code>hash_type</code> if needed.</ref>
** <code>hash_type</code> (1).
* Transaction data:
** <code>nVersion</code> (4): the <code>nVersion</code> of the transaction.