CH01::Receving: remove misleading claim about address identity association

Original text claimed that there is no association between a user's
identity and their addresses prior to using that address in most
wallets, but many lightweight wallets send even their not-yet-used
addresses to remote servers to scan for incoming payments.  This is
often done over IPv4 or IPv6, which creates a link between the user's
connection and their addresses.  Update text by simply dropping this
claim.

ch01.asciidoc

@@ -423,8 +423,6 @@ should generate a new invoice with a new address each time you request a
 payment.
 ====
 
-In most wallets, there is no association between a Bitcoin address and any externally identifiable information including the user's identity. Until the moment an address is referenced as the recipient of value in a transaction posted on the bitcoin ledger, the Bitcoin address is simply part of the vast number of possible addresses that are valid in bitcoin. Only once an address has been associated with a transaction does it become part of the known addresses in the network.
-
 ==== Receiving bitcoin
 
 Alice uses the _Receive_ button, which displays a QR code along with a Bitcoin address, shown in <<wallet_receive>>.