- feerate vs "fee rate" : so far we have always used "fee rate" (2 words). I would stick with this for consistency. Also it is better English as feerate is an invented term.
- you wrote "FREERATE" --> ha ha very funny, a Freudian slip, but sorry, it will not be free. ;) smiling
- uppercasing
- commas
- avoid extremes and hype, avoid "very" : very expensive --> expensive
- successfull -> ...ful (one L)
- sentence simplifications
- Onion vs onion, lowercase or uppercase, since this is not a product name it should be lowercase
- the example does not contain the information needed, added "forward" field in onion
- some part missing from a sentence
- etc
- this sentence already called out to me yesterday for change. As written it appears to be out of context leaving various interpretations of emphasis open. The reader might end up with "What is the author trying to say?" I think the emphasis is "it's the *sender's* job to compute the path".
- If the sentence is taken out completely then the sentence before becomes hanging, so I decided to rephrase to give the sentence a single focus: the sender has to compute route. IMHO it reads better now and has a better flow of argument.
- commas
- avoid word repetition of 'any'
- "balance information of all channels is and cannot be available " --> that would have to be "balance information of all channels is not and cannot be available". But that makes it too long, too clumsy. Shorten to "balance information of all channels cannot be available". If it can't be then obviously it isn't.
- etc
* Wrote Section on Source-Based Routing
Wrote an explanation for Source-Based Routing, why it is used and other methods are not, and some words on the drawbacks of using it
* Update path-finding.asciidoc
* Update path-finding.asciidoc
* Update path-finding.asciidoc
* Update path-finding.asciidoc
* Update path-finding.asciidoc
* Update path-finding.asciidoc
