line 58:
originally: "This mechanism would allow two users to engage into several smaller transactions..."
corrected: "This mechanism would allow two users to engage in several smaller transactions..."
* travis: Add linter to make sure Unix style line endings are used
* Fix typos
* travis: Add linter to detect trailing spaces at end of line
* Remove trailing whitespace
* Use consistent indentation
* travis: Add linter guarding against use of tabs
* Fix intent
* Update ch01.asciidoc
* basically rephrased the entire pargragraph to make it more readable
gave A and B the names of Alice and Bob.
Simplified / split sentences.
moved a scentence
* Stylistic change to Meni Rosenfeld paragraph.
Propose to change the word order and a few words to make it easier to read.
* removed the word and to make the text shorter
Proposed some edits to the initial paragraphs on the 'nSequence' number. Aim is to make it slightly more accurate and readable. Happy to break these proposals down into smaller chunks if there is too much in a single pull request.
* Update ch01.asciidoc
I'm proposing to change the word refugee to economic migrant. Refugee suggests that someone has had to leave their own country without a choice, where-as I think most people submitting remittances do so by their own choice.
I think economic migrant is a step towards the right wording, but could also carry other unwanted connotations. Maybe "remittance sender" would be more accurate and less controversial...
* Update ch01.asciidoc
* Update ch01.asciidoc
Updated the merchant example and put it into the right place. Thanks @RicardoM17 for your contributions! I've replaced the names, as I think the Alice / Bob notation brings some baggage with it that we probably don't need. (Or if we do want to use it, we should re-apply the names in correct order at the end of the writing process.)
* Update ch01.asciidoc
Corrected Typo in customers
* removed the client side demanding fixed / low fees
Separated out from previous pull request - (now closed). Changed the name in this description and incorporated the feedback from @RicardoM17 (thank you!). Use case is still valid and moving towards being generic enough to include.
