diff --git a/doc/release-notes/release-notes-0.10.0.md b/doc/release-notes/release-notes-0.10.0.md
--- a/doc/release-notes/release-notes-0.10.0.md
+++ b/doc/release-notes/release-notes-0.10.0.md
@@ -79,7 +79,7 @@
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
-confirmation times. Fees are added by default unless the 'sendfreetransactions'
+confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
@@ -93,7 +93,7 @@
- `-txconfirmtarget=n` : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
-- `-sendfreetransactions` : Send transactions as zero-fee transactions if possible
+- `-sendfreetransactions` : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
@@ -234,7 +234,7 @@
In its initial version the API includes two functions:
-- `bitcoinconsensus_verify_script` verifies a script. It returns whether the indicated input of the provided serialized transaction
+- `bitcoinconsensus_verify_script` verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
- `bitcoinconsensus_version` returns the API version, currently at an experimental `0`
@@ -306,8 +306,8 @@
- `-datacarriersize=n` : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
-The relay policy has changed to more properly implement the desired behavior of not
-relaying free (or very low fee) transactions unless they have a priority above the
+The relay policy has changed to more properly implement the desired behavior of not
+relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
@@ -499,7 +499,7 @@
- `a7d1f03` build: fix dynamic boost check when --with-boost= is used
- `d5fd094` build: fix qt test build when libprotobuf is in a non-standard path
- `2cf5f16` Add libbitcoinconsensus library
-- `914868a` build: add a deterministic dmg signer
+- `914868a` build: add a deterministic dmg signer
- `2d375fe` depends: bump openssl to 1.0.1k
- `b7a4ecc` Build: Only check for boost when building code that requires it
diff --git a/doc/release-notes/release-notes-0.10.1.md b/doc/release-notes/release-notes-0.10.1.md
--- a/doc/release-notes/release-notes-0.10.1.md
+++ b/doc/release-notes/release-notes-0.10.1.md
@@ -2,7 +2,7 @@
-This is a new minor version release, bringing bug fixes and translation
+This is a new minor version release, bringing bug fixes and translation
updates. It is recommended to upgrade to this version.
Please report bugs using the issue tracker at github:
diff --git a/doc/release-notes/release-notes-0.10.2.md b/doc/release-notes/release-notes-0.10.2.md
--- a/doc/release-notes/release-notes-0.10.2.md
+++ b/doc/release-notes/release-notes-0.10.2.md
@@ -2,7 +2,7 @@
-This is a new minor version release, bringing minor bug fixes and translation
+This is a new minor version release, bringing minor bug fixes and translation
updates. It is recommended to upgrade to this version.
Please report bugs using the issue tracker at github:
diff --git a/doc/release-notes/release-notes-0.10.3.md b/doc/release-notes/release-notes-0.10.3.md
--- a/doc/release-notes/release-notes-0.10.3.md
+++ b/doc/release-notes/release-notes-0.10.3.md
@@ -2,7 +2,7 @@
-This is a new minor version release, bringing security fixes and translation
+This is a new minor version release, bringing security fixes and translation
updates. It is recommended to upgrade to this version as soon as possible.
Please report bugs using the issue tracker at github:
diff --git a/doc/release-notes/release-notes-0.11.0.md b/doc/release-notes/release-notes-0.11.0.md
--- a/doc/release-notes/release-notes-0.11.0.md
+++ b/doc/release-notes/release-notes-0.11.0.md
@@ -69,7 +69,7 @@
For example, add the following to `bitcoin.conf`:
- minrelaytxfee=0.00005
+ minrelaytxfee=0.00005
limitfreerelay=5
More robust solutions are being worked on for a follow-up release.
@@ -80,50 +80,50 @@
Block file pruning
----------------------
-This release supports running a fully validating node without maintaining a copy
-of the raw block and undo data on disk. To recap, there are four types of data
-related to the blockchain in the bitcoin system: the raw blocks as received over
-the network (blk???.dat), the undo data (rev???.dat), the block index and the
+This release supports running a fully validating node without maintaining a copy
+of the raw block and undo data on disk. To recap, there are four types of data
+related to the blockchain in the bitcoin system: the raw blocks as received over
+the network (blk???.dat), the undo data (rev???.dat), the block index and the
UTXO set (both LevelDB databases). The databases are built from the raw data.
-Block pruning allows Bitcoin Core to delete the raw block and undo data once
-it's been validated and used to build the databases. At that point, the raw data
-is used only to relay blocks to other nodes, to handle reorganizations, to look
-up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or
-for rescanning the wallet. The block index continues to hold the metadata about
+Block pruning allows Bitcoin Core to delete the raw block and undo data once
+it's been validated and used to build the databases. At that point, the raw data
+is used only to relay blocks to other nodes, to handle reorganizations, to look
+up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or
+for rescanning the wallet. The block index continues to hold the metadata about
all blocks in the blockchain.
-The user specifies how much space to allot for block & undo files. The minimum
-allowed is 550MB. Note that this is in addition to whatever is required for the
-block index and UTXO databases. The minimum was chosen so that Bitcoin Core will
-be able to maintain at least 288 blocks on disk (two days worth of blocks at 10
-minutes per block). In rare instances it is possible that the amount of space
-used will exceed the pruning target in order to keep the required last 288
+The user specifies how much space to allot for block & undo files. The minimum
+allowed is 550MB. Note that this is in addition to whatever is required for the
+block index and UTXO databases. The minimum was chosen so that Bitcoin Core will
+be able to maintain at least 288 blocks on disk (two days worth of blocks at 10
+minutes per block). In rare instances it is possible that the amount of space
+used will exceed the pruning target in order to keep the required last 288
blocks on disk.
-Block pruning works during initial sync in the same way as during steady state,
-by deleting block files "as you go" whenever disk space is allocated. Thus, if
-the user specifies 550MB, once that level is reached the program will begin
-deleting the oldest block and undo files, while continuing to download the
+Block pruning works during initial sync in the same way as during steady state,
+by deleting block files "as you go" whenever disk space is allocated. Thus, if
+the user specifies 550MB, once that level is reached the program will begin
+deleting the oldest block and undo files, while continuing to download the
blockchain.
-For now, block pruning disables block relay. In the future, nodes with block
-pruning will at a minimum relay "new" blocks, meaning blocks that extend their
-active chain.
+For now, block pruning disables block relay. In the future, nodes with block
+pruning will at a minimum relay "new" blocks, meaning blocks that extend their
+active chain.
-Block pruning is currently incompatible with running a wallet due to the fact
-that block data is used for rescanning the wallet and importing keys or
-addresses (which require a rescan.) However, running the wallet with block
+Block pruning is currently incompatible with running a wallet due to the fact
+that block data is used for rescanning the wallet and importing keys or
+addresses (which require a rescan.) However, running the wallet with block
pruning will be supported in the near future, subject to those limitations.
-Block pruning is also incompatible with -txindex and will automatically disable
+Block pruning is also incompatible with -txindex and will automatically disable
it.
-Once you have pruned blocks, going back to unpruned state requires
-re-downloading the entire blockchain. To do this, re-start the node with
--reindex. Note also that any problem that would cause a user to reindex (e.g.,
-disk corruption) will cause a pruned node to redownload the entire blockchain.
-Finally, note that when a pruned node reindexes, it will delete any blk???.dat
+Once you have pruned blocks, going back to unpruned state requires
+re-downloading the entire blockchain. To do this, re-start the node with
+-reindex. Note also that any problem that would cause a user to reindex (e.g.,
+disk corruption) will cause a pruned node to redownload the entire blockchain.
+Finally, note that when a pruned node reindexes, it will delete any blk???.dat
and rev???.dat files in the data directory prior to restarting the download.
To enable block pruning on the command line:
@@ -133,10 +133,10 @@
Modified RPC calls:
- `getblockchaininfo` now includes whether we are in pruned mode or not.
-- `getblock` will check if the block's data has been pruned and if so, return an
+- `getblock` will check if the block's data has been pruned and if so, return an
error.
-- `getrawtransaction` will no longer be able to locate a transaction that has a
-UTXO but where its block file has been pruned.
+- `getrawtransaction` will no longer be able to locate a transaction that has a
+UTXO but where its block file has been pruned.
Pruning is disabled by default.
@@ -377,7 +377,7 @@
- #6074 `948beaf` Correct the PUSHDATA4 minimal encoding test in script_invalid.json
- #6032 `e08886d` Stop nodes after RPC tests, even with --nocleanup
- #6075 `df1609f` Add additional script edge condition tests
-- #5981 `da38dc6` Python P2P testing
+- #5981 `da38dc6` Python P2P testing
- #5958 `9ef00c3` Add multisig rpc tests
- #6112 `fec5c0e` Add more script edge condition tests
diff --git a/doc/release-notes/release-notes-0.12.1.md b/doc/release-notes/release-notes-0.12.1.md
--- a/doc/release-notes/release-notes-0.12.1.md
+++ b/doc/release-notes/release-notes-0.12.1.md
@@ -43,7 +43,7 @@
[BIP112][] and [BIP113][] using the [BIP9][] deployment mechanism.
The deployment sets the block version number to 0x20000001 between
-midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for
+midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for
deployment. The version number consists of 0x20000000 to indicate version
bits together with setting bit 0 to indicate support for this combined
deployment, shown as "csv" in the `getblockchaininfo` RPC call.
diff --git a/doc/release-notes/release-notes-0.13.0.md b/doc/release-notes/release-notes-0.13.0.md
--- a/doc/release-notes/release-notes-0.13.0.md
+++ b/doc/release-notes/release-notes-0.13.0.md
@@ -325,10 +325,10 @@
- Asm script outputs replacements for OP_NOP2 and OP_NOP3
- - OP_NOP2 has been renamed to OP_CHECKLOCKTIMEVERIFY by [BIP
+ - OP_NOP2 has been renamed to OP_CHECKLOCKTIMEVERIFY by [BIP
65](https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki)
- - OP_NOP3 has been renamed to OP_CHECKSEQUENCEVERIFY by [BIP
+ - OP_NOP3 has been renamed to OP_CHECKSEQUENCEVERIFY by [BIP
112](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki)
- The following outputs are affected by this change:
diff --git a/doc/release-notes/release-notes-0.13.1.md b/doc/release-notes/release-notes-0.13.1.md
--- a/doc/release-notes/release-notes-0.13.1.md
+++ b/doc/release-notes/release-notes-0.13.1.md
@@ -36,8 +36,8 @@
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
-From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended to work on 10.7+,
-but severe issues with the libc++ version on 10.7.x keep it from running reliably.
+From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended to work on 10.7+,
+but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes
diff --git a/doc/release-notes/release-notes-0.13.2.md b/doc/release-notes/release-notes-0.13.2.md
--- a/doc/release-notes/release-notes-0.13.2.md
+++ b/doc/release-notes/release-notes-0.13.2.md
@@ -35,8 +35,8 @@
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
-From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended to work on 10.7+,
-but severe issues with the libc++ version on 10.7.x keep it from running reliably.
+From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended to work on 10.7+,
+but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes
diff --git a/doc/release-notes/release-notes-0.14.0.md b/doc/release-notes/release-notes-0.14.0.md
--- a/doc/release-notes/release-notes-0.14.0.md
+++ b/doc/release-notes/release-notes-0.14.0.md
@@ -108,7 +108,7 @@
The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can
be nested (i.e. `getblock(getblockhash(1))`). Simple queries can be
-done with square brackets where object values are accessed with either an
+done with square brackets where object values are accessed with either an
array index or a non-quoted string (i.e. `listunspent()[0][txid]`). Both
commas and spaces can be used to separate parameters in both the bracket syntax
and normal RPC command syntax.
@@ -117,9 +117,9 @@
-----------------------
A RPC command and GUI toggle have been added to enable or disable all p2p
-network activity. The network status icon in the bottom right hand corner
+network activity. The network status icon in the bottom right hand corner
is now the GUI toggle. Clicking the icon will either enable or disable all
-p2p network activity. If network activity is disabled, the icon will
+p2p network activity. If network activity is disabled, the icon will
be grayed out with an X on top of it.
Additionally the `setnetworkactive` RPC command has been added which does
@@ -189,7 +189,7 @@
Final Alert
-----------
-The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in Bitcoin Core 0.12.1 and removed in 0.13.0.
+The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement) in Bitcoin Core 0.12.1 and removed in 0.13.0.
The Alert System was retired with a maximum sequence final alert which causes any nodes
supporting the Alert System to display a static hard-coded "Alert Key Compromised" message which also
prevents any other alerts from overriding it. This final alert is hard-coded into this release
@@ -198,15 +198,15 @@
GUI Changes
-----------
- - After resetting the options by clicking the `Reset Options` button
- in the options dialog or with the `-resetguioptions` startup option,
- the user will be prompted to choose the data directory again. This
- is to ensure that custom data directories will be kept after the
- option reset which clears the custom data directory set via the choose
+ - After resetting the options by clicking the `Reset Options` button
+ in the options dialog or with the `-resetguioptions` startup option,
+ the user will be prompted to choose the data directory again. This
+ is to ensure that custom data directories will be kept after the
+ option reset which clears the custom data directory set via the choose
datadir dialog.
- - Multiple peers can now be selected in the list of peers in the debug
- window. This allows for users to ban or disconnect multiple peers
+ - Multiple peers can now be selected in the list of peers in the debug
+ window. This allows for users to ban or disconnect multiple peers
simultaneously instead of banning them one at a time.
- An indicator has been added to the bottom right hand corner of the main
@@ -221,7 +221,7 @@
an optional third arg, which was always ignored. Make sure to never pass more
than two arguments.
- - The first boolean argument to `getaddednodeinfo` has been removed. This is
+ - The first boolean argument to `getaddednodeinfo` has been removed. This is
an incompatible change.
- RPC command `getmininginfo` loses the "testnet" field in favor of the more
@@ -231,8 +231,8 @@
precious. A precious block will be treated as if it were received earlier
than a competing block.
- - A new RPC command `importmulti` has been added which receives an array of
- JSON objects representing the intention of importing a public key, a
+ - A new RPC command `importmulti` has been added which receives an array of
+ JSON objects representing the intention of importing a public key, a
private key, an address and script/p2sh
- Use of `getrawtransaction` for retrieving confirmed transactions with unspent
@@ -254,7 +254,7 @@
-----------------
- UTXO set query (`GET /rest/getutxos//-/-
- /.../-.`) responses were changed to return status
+ /.../-.`) responses were changed to return status
code `HTTP_BAD_REQUEST` (400) instead of `HTTP_INTERNAL_SERVER_ERROR` (500)
when requests contain invalid parameters.
diff --git a/doc/release-notes/release-notes-0.14.5.md b/doc/release-notes/release-notes-0.14.5.md
--- a/doc/release-notes/release-notes-0.14.5.md
+++ b/doc/release-notes/release-notes-0.14.5.md
@@ -9,7 +9,7 @@
- Change currency units in user interface from BTC -> BCC
- Add NODE_BITCOIN_CASH service bit (0x20)
- Update BU backed seeder to btccash-seeder.bitcoinunlimited.info
-- Update ABC logos for About menu, and testnet icon
+- Update ABC logos for About menu, and testnet icon
- Various refactoring and cleanups
NOTE: Change in default value:
diff --git a/doc/release-notes/release-notes-0.18.8.md b/doc/release-notes/release-notes-0.18.8.md
--- a/doc/release-notes/release-notes-0.18.8.md
+++ b/doc/release-notes/release-notes-0.18.8.md
@@ -5,7 +5,7 @@
This release includes the following features and fixes:
- `dumpwallet` now includes hex-encoded scripts from the wallet in the dumpfile
- `importwallet` now imports these scripts, but corresponding addresses may not
- be added correctly or a manual rescan may be required to find relevant
+ be added correctly or a manual rescan may be required to find relevant
transactions
- `getblock 2` (verbosity = 2) now returns `hex` values in transaction JSON blobs
- Remove miner policy estimator in favor of minimum fees, also remove `fee_estimates.dat`.
diff --git a/doc/release-notes/release-notes-0.19.3.md b/doc/release-notes/release-notes-0.19.3.md
--- a/doc/release-notes/release-notes-0.19.3.md
+++ b/doc/release-notes/release-notes-0.19.3.md
@@ -6,7 +6,7 @@
- Added optional `blockhash` parameter to `getrawtransaction` to narrowly
search for a transaction within a given block. New returned field
`in_active_chain` will indicate if that block is part of the active chain.
- - `signrawtransaction` RPC is now deprecated. The new RPCs
- `signrawtransactionwithkey` and `signrawtransactionwithwallet` should
+ - `signrawtransaction` RPC is now deprecated. The new RPCs
+ `signrawtransactionwithkey` and `signrawtransactionwithwallet` should
be used instead. Use `-deprecatedrpc=signrawtransaction` to temporarily
re-enable the old behavior while you migrate.
diff --git a/doc/release-notes/release-notes-0.19.4.md b/doc/release-notes/release-notes-0.19.4.md
--- a/doc/release-notes/release-notes-0.19.4.md
+++ b/doc/release-notes/release-notes-0.19.4.md
@@ -3,7 +3,7 @@
This release includes the following features and fixes:
- - Added to `getblockchaininfo` `size_on_disk` and, when the prune option is
+ - Added to `getblockchaininfo` `size_on_disk` and, when the prune option is
enabled, `prune_height`, `automatic_pruning`, and `prune_target_size`.
- The help message also reflects this.
- Code standard updated to c++14.
diff --git a/doc/release-notes/release-notes-0.20.8.md b/doc/release-notes/release-notes-0.20.8.md
--- a/doc/release-notes/release-notes-0.20.8.md
+++ b/doc/release-notes/release-notes-0.20.8.md
@@ -3,7 +3,7 @@
This release includes the following features and fixes:
- - When running bitcoind without `-daemon`, logging to stdout is now the
+ - When running bitcoind without `-daemon`, logging to stdout is now the
default behavior. Setting `-printtoconsole=1` no longer implicitly disables
logging to debug.log. Instead, logging to file can be explicitly disabled by
setting `-debuglogfile=0`.
diff --git a/doc/release-notes/release-notes-0.3.18.md b/doc/release-notes/release-notes-0.3.18.md
--- a/doc/release-notes/release-notes-0.3.18.md
+++ b/doc/release-notes/release-notes-0.3.18.md
@@ -3,7 +3,7 @@
* IsStandard() check to only include known transaction types in blocks
* Jgarzik's optimisation to speed up the initial block download a little
-The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at http://www.bitcoin.org/smf/index.php?topic=1886.0).
+The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at http://www.bitcoin.org/smf/index.php?topic=1886.0).
* getaccountaddress
* sendfrom
* move
diff --git a/doc/release-notes/release-notes-0.3.19.md b/doc/release-notes/release-notes-0.3.19.md
--- a/doc/release-notes/release-notes-0.3.19.md
+++ b/doc/release-notes/release-notes-0.3.19.md
@@ -1,7 +1,7 @@
There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19.
- Added some DoS controls
-As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.
+As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.
I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.
diff --git a/doc/release-notes/release-notes-0.3.21.md b/doc/release-notes/release-notes-0.3.21.md
--- a/doc/release-notes/release-notes-0.3.21.md
+++ b/doc/release-notes/release-notes-0.3.21.md
@@ -13,7 +13,7 @@
* New rpc command "sendmany" to send bitcoins to more than one address in a single transaction.
-* Several bug fixes, including a serious intermittent bug that would sometimes cause bitcoind to stop accepting rpc requests.
+* Several bug fixes, including a serious intermittent bug that would sometimes cause bitcoind to stop accepting rpc requests.
* -logtimestamps option, to add a timestamp to each line in debug.log.
diff --git a/doc/release-notes/release-notes-0.6.0.md b/doc/release-notes/release-notes-0.6.0.md
--- a/doc/release-notes/release-notes-0.6.0.md
+++ b/doc/release-notes/release-notes-0.6.0.md
@@ -57,7 +57,7 @@
versions of Bitcoin-Qt/bitcoind.
New command-line argument -blocknotify=
-that will spawn a shell process to run
+that will spawn a shell process to run
when a new block is accepted.
New command-line argument -splash=0 to disable
diff --git a/doc/release-notes/release-notes-0.7.0.md b/doc/release-notes/release-notes-0.7.0.md
--- a/doc/release-notes/release-notes-0.7.0.md
+++ b/doc/release-notes/release-notes-0.7.0.md
@@ -13,7 +13,7 @@
https://github.com/bitcoin/bitcoin/zipball/v0.7.0 # .zip
Ubuntu Linux users can use the "Personal Package Archive" (PPA)
-maintained by Matt Corallo to automatically keep
+maintained by Matt Corallo to automatically keep
bitcoin up-to-date. Just type
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update
diff --git a/doc/release-notes/release-notes-0.7.1.md b/doc/release-notes/release-notes-0.7.1.md
--- a/doc/release-notes/release-notes-0.7.1.md
+++ b/doc/release-notes/release-notes-0.7.1.md
@@ -12,7 +12,7 @@
https://github.com/bitcoin/bitcoin/zipball/v0.7.1 # .zip
Ubuntu Linux users can use the "Personal Package Archive" (PPA)
-maintained by Matt Corallo to automatically keep
+maintained by Matt Corallo to automatically keep
up-to-date. Just type:
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update
diff --git a/doc/release-notes/release-notes-0.8.0.md b/doc/release-notes/release-notes-0.8.0.md
--- a/doc/release-notes/release-notes-0.8.0.md
+++ b/doc/release-notes/release-notes-0.8.0.md
@@ -90,7 +90,7 @@
Privacy leak: the position of the "change" output in most transactions was not being
properly randomized, making network analysis of the transaction graph to identify
-users' wallets easier.
+users' wallets easier.
Zero-confirmation transaction vulnerability: accepting zero-confirmation transactions
(transactions that have not yet been included in a block) from somebody you do not
diff --git a/doc/release-notes/release-notes-0.8.2.md b/doc/release-notes/release-notes-0.8.2.md
--- a/doc/release-notes/release-notes-0.8.2.md
+++ b/doc/release-notes/release-notes-0.8.2.md
@@ -24,7 +24,7 @@
Fee Policy changes
-The default fee for low-priority transactions is lowered from 0.0005 BTC
+The default fee for low-priority transactions is lowered from 0.0005 BTC
(for each 1,000 bytes in the transaction; an average transaction is
about 500 bytes) to 0.0001 BTC.
diff --git a/doc/release-notes/release-notes-0.8.6.md b/doc/release-notes/release-notes-0.8.6.md
--- a/doc/release-notes/release-notes-0.8.6.md
+++ b/doc/release-notes/release-notes-0.8.6.md
@@ -47,7 +47,7 @@
- Additional debug.log logging for diagnosis of network problems, log timestamps by default
-- Fix Bitcoin-Qt startup crash when clicking dock icon on OSX
+- Fix Bitcoin-Qt startup crash when clicking dock icon on OSX
- Fix memory leaks in CKey::SetCompactSignature() and Key::SignCompact()
diff --git a/doc/release-notes/release-notes-0.9.0.md b/doc/release-notes/release-notes-0.9.0.md
--- a/doc/release-notes/release-notes-0.9.0.md
+++ b/doc/release-notes/release-notes-0.9.0.md
@@ -18,7 +18,7 @@
over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run
-0.9.0 your blockchain files will be re-indexed, which will take anywhere from
+0.9.0 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.
On Windows, do not forget to uninstall all earlier versions of the Bitcoin
@@ -86,7 +86,7 @@
(q)makefiles.
Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and
-bitcoind makes it easier for experienced open source developers to contribute
+bitcoind makes it easier for experienced open source developers to contribute
to the project.
Be sure to check doc/build-*.md for your platform before building from source.
@@ -124,7 +124,7 @@
Transaction malleability-related fixes
--------------------------------------
-This release contains a few fixes for transaction ID (TXID) malleability
+This release contains a few fixes for transaction ID (TXID) malleability
issues:
- -nospendzeroconfchange command-line option, to avoid spending
@@ -270,7 +270,7 @@
Build system:
- Switch to autotools-based build system
-- Build without wallet by passing `--disable-wallet` to configure, this
+- Build without wallet by passing `--disable-wallet` to configure, this
removes the BerkeleyDB dependency
- Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more
recent versions
@@ -301,7 +301,7 @@
- Don't regenerate autostart link on every client startup
- Show and store message of normal bitcoin:URI
- Fix richtext detection hang issue on very old Qt versions
-- OS X: Make use of the 10.8+ user notification center to display Growl-like
+- OS X: Make use of the 10.8+ user notification center to display Growl-like
notifications
- OS X: Added NSHighResolutionCapable flag to Info.plist for better font
rendering on Retina displays.
diff --git a/doc/release-notes/release-notes-0.9.1.md b/doc/release-notes/release-notes-0.9.1.md
--- a/doc/release-notes/release-notes-0.9.1.md
+++ b/doc/release-notes/release-notes-0.9.1.md
@@ -24,7 +24,7 @@
bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run
-0.9.1 your blockchain files will be re-indexed, which will take anywhere from
+0.9.1 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.
0.9.1 Release notes
diff --git a/doc/release-notes/release-notes-0.9.2.1.md b/doc/release-notes/release-notes-0.9.2.1.md
--- a/doc/release-notes/release-notes-0.9.2.1.md
+++ b/doc/release-notes/release-notes-0.9.2.1.md
@@ -19,7 +19,7 @@
bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run
-0.9.2.1 your blockchain files will be re-indexed, which will take anywhere from
+0.9.2.1 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.
Downgrading warnings
diff --git a/doc/release-notes/release-notes-0.9.2.md b/doc/release-notes/release-notes-0.9.2.md
--- a/doc/release-notes/release-notes-0.9.2.md
+++ b/doc/release-notes/release-notes-0.9.2.md
@@ -19,7 +19,7 @@
bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run
-0.9.2 your blockchain files will be re-indexed, which will take anywhere from
+0.9.2 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.
Downgrading warnings
diff --git a/doc/release-notes/release-notes-0.9.3.md b/doc/release-notes/release-notes-0.9.3.md
--- a/doc/release-notes/release-notes-0.9.3.md
+++ b/doc/release-notes/release-notes-0.9.3.md
@@ -21,7 +21,7 @@
bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run
-0.9.3 your blockchain files will be re-indexed, which will take anywhere from
+0.9.3 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.
Downgrading warnings