- 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)
- of course ==> of course,
- core for ==> core of something
- is there and exists ==> repetitive
- learnt: ==> US English learned, UK and South African English: learnt, since there are more US readers than UK readers I would go with US English
- learnt already --> word order: already learned
- quite a bit : too fluffy, too relative ==> removed
- This will repeat some ==> sentence structure can be improved, restructured
* Scarcity, scarce resource differences between Bitcoin and Lightning
- added additional difference between BTC and LN
* softened
- replaced "each one according to its scarcity" with "... influenced by..." to soften it.
- added "primarily" to "pay primarily for block space" to soften it
- added "by and large" to "...pay by and large for channel capacity" to soften it
* removed last 3 lines according to suggestion
* minor cleanup, consistent naming, etc
- typo
- consistent naming:
- uppercased all "lightning" to "Lightning"
- all Lightning networks, to "Lightning Network"
- remove "oldid" URL REST parameter from wikipedia links
- added links where appropriate
- etc
* put the oldid argument in the 4 or 5 URLs back in
- I removed acronym from first sentence and put it into the second. I did not feel that it is a good start when the first sentence of the book already has an acronym.
- Removed LN acronym 4-5 times further down. It was not consistently used anyway. Sometimes yes, sometimes no. I also think it reads better spelled out. So, for a book I feel it is better to spell it out 4 times, than to abbreviate it 4 times.
* Added monetary limit to commonality of BTC and Lightning
As an alternative a new paragraph could be added with title "Monetary Limit" but I thought that adding two sentences to the "Monetary Unit" section would be enough.
* ch03: adjusted to incorporate comment
* Fee incentives as difference between Bitcoin and Lightning
- basically explaining that the $1M tx will always remain on BTC, ...
* improved following reviewers suggestion
- when I read this I thought twice that someone is trying to abbreviate "Lightning Node" with "LN".
- only on 3rd reading I realized that as usual "LN" stands for "Lightning Network" and the word "node" follows 3 words later
- anyway, to avoid confusion it should be replaced
- Acronym "LN" shows up 3 time in chapter 3
- Twice explained (the definition): these I left in, because further chapters will/might make use of the acronym
- The third occurrence I replaced, as it adds just 1 work to the book, increases readability, is inconsistent with rest of this chapter
- see also Issue #174
- see also Issue #175
- is is also "Bitcoin Node", not "Bitcoin Network Node"
- simpler is better, shorter is better
- 7 occurrences were replaced
- similar to PR #268 and PR #269
- issues #174 and #175
- 1 occurrence only
- "Lightning Invoice" was already used in text, this fixes also the inconsistency
- removed 3 times the word "very"
- see Issue #171
- low, high, cheap, expensive: is all very relative
- set expectations right
- who knows where the fees will be in 10 years
