aboutsummaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorpracticalswift <practicalswift@users.noreply.github.com>2017-07-30 21:42:17 +0200
committerpracticalswift <practicalswift@users.noreply.github.com>2017-08-08 17:12:57 +0200
commit9d5e98ff80479628492329b3b6bdce56d255baa0 (patch)
tree14a3c69da4329598561316541c6e8d770810b9e0 /contrib
parent2507fd55568b361080e9127f40584af2df64f76e (diff)
downloadbitcoin-9d5e98ff80479628492329b3b6bdce56d255baa0.tar.xz
Fix typos.
Diffstat (limited to 'contrib')
-rw-r--r--contrib/linearize/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/linearize/README.md b/contrib/linearize/README.md
index f2a2ab2768..2985106982 100644
--- a/contrib/linearize/README.md
+++ b/contrib/linearize/README.md
@@ -46,7 +46,7 @@ linearize-hashes.py.
(Default: `1000*1000*1000 bytes`)
* `netmagic`: Network magic number.
* `out_of_order_cache_sz`: If out-of-order blocks are being read, the block can
-be written to a cache so that the blockchain doesn't have to be seeked again.
+be written to a cache so that the blockchain doesn't have to be sought again.
This option specifies the cache size. (Default: `100*1000*1000 bytes`)
* `rev_hash_bytes`: If true, the block hash list written by linearize-hashes.py
will be byte-reversed when read by linearize-data.py. See the linearize-hashes