Took a stab at writing about the importance of hardware, the kinds of hardware nodes, and what's needed. I decided not to mention particular Node projects as this can easily change. Although to note: we could mention MyNodeBTC, Raspiblitz, and Casa Node
Maybe this section should go higher up in this chapter.
Note: this commit is a response to my previous issue here:
https://github.com/lnbook/lnbook/issues/143
Wrote up this section, describing how the onion layers are peeled as it moves across the route, as well as giving examples of how malicious entities could potentially use packet size to spy on and de-anonymize users
- added "simulated" to make sure readers understand that they are not mining real blocks
- 1st --> first, general guideline is to spell numbers up to 12 out
- "now" ==> used twice ==> repetitive ==> removed second "now"
- "refer to" ==> "by some name"
- removed also
- comma ... no comma in front of "for"
- which, which ... repetitive, improved
- comma
- instructions to install ==> installation instructions
- another comma
- "not worry" ==> "need not worry"
- removed ( ) ==> replaced with "i.e." to make it more formal
- "we want to work with a distribution that is familiar to many developers" ==> not correct linguistically; "familiar with" is better English than "familiar to"; this should be changed. I took this as reason to rephrase the whole sentence.
- "beneath" ==> "as can be seen below"
- putting emphasis on repository being online
- "the" article required in this case
- removed "version" from "ebook version" to simplify
- green: work order corrected
- no comma with "..., to"
- removed ( ) and replaced it with "or" ... better style
- added 2 words to make it read better
- restructured a sentence
- plural seems more appropriate
- Similarily ==> correspondingly ... fits the meaning better
- show ==> present ... more elegant
- BOLTS ==> BOLT standards ... to make it more clear to the novice reader
- removed comma ... no comma when subject is same in both parts of sentence
- recommend ==> endorse ... better, recommend one over the other is at best used colloquially
First time on GitHub. Thanks for all your work!
I’ve changed capitalization of the entries that are not proper nouns. Words like “transaction” or “receipt” do not need capital letters. If you get the glossary right, it’s a useful reference for the rest of the book. (Note that glossaries only capitalise proper nouns - see here: https://www.pearson.ch/download/media/9781405881357_glossary_ml_int.pdf)
