Editorial changes #465
Merged
Editorial changes #465
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Payment methods describe data; they are not participants in a transaction.
Therefore, recast the description of parties as payers/payees/providers
of payment methods. (Both in Intro and Goals)
* The word "buyer" was used in the intro and not used elsewhere in the
spec. Therefore, I use payer/payee which are used further down.
* The first examples the reader should encounter in the PaymentRequest
interface description should be those most likely found in practice.
The "Buy" button should come first. The other examples of in-app
and POS are much further out and so I have listed them after.
* Updated example 2 as follows:
- We have network id values; we should use those instead of fictitious
ones.
- bobpay.com does not confirm (I believe) to the PMI spec. So I have
used an example URL instead.
marcoscaceres
requested changes
Mar 20, 2017
|
I have just installed HTML Tidy version 5.5.10. What options should I run it with? I used '-i' but the result seems very different from the input file. That is: a lot more is changed by tidy than I changed via my edit. Please advise. Ian |
|
@ianbjacobs, run: |
char-encoding: utf8 indent: yes wrap: 80 tidy-mark: no
marcoscaceres
requested changes
Mar 21, 2017
index.html
Outdated
| a transaction:</p> | ||
|
|
||
| <ul> | ||
| <li>the payee, such as a merchant with an online store,</li> |
There was a problem hiding this comment.
I'd prefer these ended in full stop.
index.html
Outdated
| </p> | ||
| <ul> | ||
| <li>the payee, such as a merchant with an online store, |
There was a problem hiding this comment.
I'd still like this to be:
- The payee: bla bla bla.
- The payer: bla bla bla.
- The provider: bla bla bla.
marcoscaceres
approved these changes
Mar 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some editorial changes:
Payment methods describe data; they are not participants in a transaction.
Therefore, recast the description of parties as payers/payees/providers
of payment methods. (Both in Intro and Goals)
The word "buyer" was used in the intro and not used elsewhere in the
spec. Therefore, I use payer/payee which are used further down.
The first examples the reader should encounter in the PaymentRequest
interface description should be those most likely found in practice.
The "Buy" button should come first. The other examples of in-app
and POS are much further out and so I have listed them after.
Updated example 2 as follows:
We have network id values; we should use those instead of fictitious
ones.
bobpay.com does not confirm (I believe) to the PMI spec. So I have
used an example URL instead.
Preview | Diff