Tweak Release Notes

release-notes/release-notes-v10.0.0.md

@@ -5,7 +5,7 @@ Counterparty Core v10.0.0 is a very large release comprising many improvements a
 # Upgrade Procedure
 This release does not include any protocol changes, so there is no deadline for upgrading. However it is **strongly recommended** that all users upgrade as soon as possible, in particular to avoid consensus problems due to non-determinism in previous versions. The Counterparty Core API is also unchanged for this release.
 
-Because this release includes numerous changes to the database schema, a full database rebuild is required and the major version number has been bumped from 9 to 10. Follow the updated installation instructions in the [README](../README.md) to download and install the latest version of Counterparty Core, run `counterparty-server kickstart`, then start the server with `counterparty-server start`. The rebuild should happen automatically, and it should take between 8 and 24 hours hours to complete.
+Because this release includes numerous changes to the database schema, a full database rebuild is required and the major version number has been bumped from 9 to 10. Follow the updated installation instructions in the [README](../README.md) to download and install the latest version of Counterparty Core, run `counterparty-server kickstart` (while `bitcoind` is not running), then start the server with `counterparty-server start`. The rebuild should happen automatically, and it should take between 8 and 24 hours hours to complete.
 
 **IMPORTANT** Be certain that your instance of AddrIndexRs is running with the configuration parameter `TX_LIMIT=100` (the default value). This parameter may be set in an environment variable, in the CLI, or with a config file, and the value that AddrIndexRs is using will be visible on startup when the service is run with the option `-vvv`. This is a *consensus-critical* parameter, and if it is set incorrectly, your Counterparty node will not run.