From fe8c70871d774eee0a7995833f14fdcc62ccff41 Mon Sep 17 00:00:00 2001 From: Arthur O'Dwyer Date: Sun, 25 Mar 2018 20:22:49 -0700 Subject: [PATCH] Spelling nit: s/Berkley/Berkeley/ --- chapters/mining.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/mining.adoc b/chapters/mining.adoc index 6c7810d0..588f5797 100644 --- a/chapters/mining.adoc +++ b/chapters/mining.adoc @@ -1714,7 +1714,7 @@ signatures. Finally, the consensus rules may differ in unanticipated ways because of implicit consensus constraints imposed by system limitations or implementation details. An example of the latter was seen in the unanticipated hard fork during the upgrade of Bitcoin Core 0.7 to -0.8, which was caused by a limitation in the Berkley DB implementation +0.8, which was caused by a limitation in the Berkeley DB implementation used to store blocks. Conceptually, we can think of a hard fork as developing in four stages: