- 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
