Browse Source

Fix some typos

master
Neil Booth 9 years ago
parent
commit
64b7554b73
  1. 2
      ACKNOWLEDGEMENTS
  2. 4
      HOWTO.rst
  3. 2
      README.rst
  4. 2
      lib/coins.py
  5. 2
      lib/hash.py
  6. 2
      lib/script.py
  7. 2
      lib/tx.py
  8. 2
      lib/util.py
  9. 2
      server/db.py
  10. 2
      server/env.py
  11. 2
      server/server.py
  12. 2
      server_main.py

2
ACKNOWLEDGEMENTS

@ -1,5 +1,5 @@
Thanks to Thomas Voegtlin for creating the Electrum software and
infrastructure and for maintaining it so diligently. Electrum is the
infrastructure and for maintaining it so diligently. Electrum is
probably the best desktop Bitcoin wallet solution for most users. My
faith in it is such that I use Electrum software to store most of my
Bitcoins.

4
HOWTO.rst

@ -247,7 +247,7 @@ this:
These are just informational messages about addresses that have very
large histories that are generated as those histories are being
written outt. After the flush has completed a few stats are printed
written out. After the flush has completed a few stats are printed
about cache hits, the number of writes and deletes, and the number of
writes that were elided by the cache::
@ -261,7 +261,7 @@ You may see one or two logs about ambiguous UTXOs or hash160s::
2016-10-08 07:24:34.068609500 INFO:DB:UTXO compressed key collision at height 252943 utxo 115cc1408e5321636675a8fcecd204661a6f27b4b7482b1b7c4402ca4b94b72f / 1
These are an informational message about artefact of the compression
These are informational messages about an artefact of the compression
scheme ElectrumX uses and are harmless. However, if you see more than
a handful of these, particularly close together, something is very
wrong and your DB is probably corrupt.

2
README.rst

@ -110,7 +110,7 @@ Miscellany
As I've been researching where the time is going during block chain
indexing and how various cache sizes and hardware choices affect it,
I'd appreciate it if anyone trying to synchronize could tell me their::
I'd appreciate it if anyone trying to synchronize could tell me::
- their O/S and filesystem
- their hardware (CPU name and speed, RAM, and disk kind)

2
lib/coins.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.

2
lib/hash.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
import hashlib

2
lib/script.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
from binascii import hexlify

2
lib/tx.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
from collections import namedtuple

2
lib/util.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.

2
server/db.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
import array

2
server/env.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
import logging

2
server/server.py

@ -1,4 +1,4 @@
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
import asyncio

2
server_main.py

@ -1,6 +1,6 @@
#!/usr/bin/env python3
# See the file "COPYING" for information about the copyright
# See the file "LICENSE" for information about the copyright
# and warranty status of this software.
import asyncio

Loading…
Cancel
Save