Wording #451

6 years ago · 2d33df073e
parent 93645d1a5b
commit 2d33df073e
1 changed files with 1 additions and 1 deletions
--- a/ch10.asciidoc
+++ b/ch10.asciidoc
@ -996,7 +996,7 @@ The term _soft fork_ was introduced to distinguish this upgrade method from a "h

 One aspect of soft forks that is not immediately obvious is that soft fork upgrades can only be used to constrain the consensus rules, not to expand them. In order to be forward compatible, transactions and blocks created under the new rules must be valid under the old rules too, but not vice versa. The new rules can only limit what is valid; otherwise, they will trigger a hard fork when rejected under the old rules.

-Soft forks can be implemented in a number of ways&#x2014;the term does not define a single method, rather a set of methods that all have one thing in common: they don't require all nodes to upgrade or force nonupgraded nodes out of consensus.
+Soft forks can be implemented in a number of ways&#x2014;the term does not specify a particular method, rather a set of methods that all have one thing in common: they don't require all nodes to upgrade or force nonupgraded nodes out of consensus.

 ===== Soft forks redefining NOP opcodes