- Explain something that looks like a version number ("2.13").
- Explain how to skip tests, which are fragile on master and not run for the other clients.
- 10 cents, hence 10 satoshis (different is : a 10 cent coin, a 20 dollar suit), but in an amount: use plural: one dollar and 32 cents. Here 10,000 satoshiS (s)
- "a bunch of", very colloquial, --> "several"
- Oxford comma in list of 3 or more
- "funny" --> "unusual"
- "could" --> "can", more encouraging
- "cheap long" and "expensive short" --> add comma, comma should be placed between two adjectives of equal rank
- "it's own" (incorrect) --> its (possessive)
- "explore and dig deeper" (one does not explore deeper) --> explore further and dig deeper
- Oxford comma for consistency (see PR #340)
- sentence restructuring (one does not compose by routing a payment)
- no comma in list of 2
- only the top of the config is listed, we should say so. --> The top looks like ...
- in most cases, no comma before "because" or "since", exceptions apply
- it's (wrong) --> its (possessive)
- commas
- reorg of sentences
- "Check to..." sentence is copy-paste from above, changed it slightly to avoid repetition
- OK, Eclair is uppercase, but here we refer to a directory which is lowercase, so "eclair" (just because it is the lowercase name of the dir)
- etc
- commas
- "by this point" --> "at this point" or "by this time". Maybe best "by now"
- "... you have seen previously to build the Eclair container" is ambiguous. Rephrased
- "directly" .... word order
- it's: incorrect, --> its
- "unlike the LND or c-lightning containers": did not read well, reordered sub-phrases
- eclair vs Eclair: ok, the logo is lower cased. But when you read their https://github.com/ACINQ/eclair page ALL occurrences of Eclair are UPPERCASED.
- Based on their own use of "Eclair" in English text I have upper-cased all "Eclair" occurrences
- up to line 779 it was already upper-case, then suddenly it was lower-case
- rephrasing
- etc
- again commas
- sentence simplifications
- typo
- "at minimum" : that's wrong, "at a minimum", "at least" but I rephrased anyway to avoid it altogether because it does not read well in any case due to the following "or later"
- "distributed" repetitive, changed to "available"
- "It doesn't matter where the GOPATH points" ... this is misleading or could be misunderstood. I rephrased.
- ERROR: "git clone" should be "go get"
- replaced ", as is often the case," with "common"
- "prerequisite" has no hyphen
- in most cases no comma in front of "which"
- replaced "that we can do" with "available"
- if there is a list of 3 choices, one can place (optional) a comma before the "and". This is called the Oxford comma. It is optional, but it should be used consistently, always in the book or never. Since above it was used, I set it below as well.
- replaced "aggressively" with "heavily", we are not aggressive :)
- etc.
- usually there is no comma in front of because, as, etc. (exceptions exist)
- other commas
- "Let's" sounds very colloquial. It shows up a lot. In a couple of locations I replaced it with "let us" to make it a bit more formal, but I did not want to replace all. Maybe colloquialisms create some closeness to the reader.
- "also" seemed out of place
- local area network has no hyphen
- "not important, but has ...": either no comma or a subject (it) has to be added after "but"
- "like this" was also a bit repetitive, I replaced it once with "as follows"
- no comma in front of "and" in a list of 2
- same for "or" in list of 2
- list of 3: yes, we want a comma there to be consistent (Oxford comma, see PR #340
- many many --> many
- 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
