summaryrefslogtreecommitdiff
path: root/bip-0002.mediawiki
diff options
context:
space:
mode:
authorGigi <109058+dergigi@users.noreply.github.com>2019-04-09 22:41:52 -0500
committerGitHub <noreply@github.com>2019-04-09 22:41:52 -0500
commit14834fa63c9de42140d1d70ed6dab0837a202186 (patch)
treed701b13afd43d9a94d6fbc81aaa4d25aec4acf41 /bip-0002.mediawiki
parent18f43a6b2a8423850c2cac617fa3053faf420007 (diff)
downloadbips-14834fa63c9de42140d1d70ed6dab0837a202186.tar.xz
is alive any working -> is alive and working
Diffstat (limited to 'bip-0002.mediawiki')
-rw-r--r--bip-0002.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0002.mediawiki b/bip-0002.mediawiki
index b4567c4..3bf5aec 100644
--- a/bip-0002.mediawiki
+++ b/bip-0002.mediawiki
@@ -240,7 +240,7 @@ What if a single merchant wishes to block a hard-fork?
How about a small number of merchants (maybe only two) who sell products to each other?
-* In this scenario, it would seem the previous Bitcoin is alive any working, and that the hard-fork has failed. How to resolve such a split is outside the scope of this BIP.
+* In this scenario, it would seem the previous Bitcoin is alive and working, and that the hard-fork has failed. How to resolve such a split is outside the scope of this BIP.
How can economic agreement veto a soft-fork?