Skip to content

Commit 913d318

Browse files
Attempt to address comment
1 parent e5d443e commit 913d318

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

ux-guidelines.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ implementor experience and payment industry feedback.
2121

2222
Relevant fields: [payeeName], [payeeOrigin]
2323

24-
The payee information fields are intended to communicate to the user who will
25-
be the recipient of the funds. In most cases this would be the merchant (or
26-
other entity) that the user has already been interacting with in the current
27-
session (e.g., checkout flow). The `payeeName` field, if present, communicates
28-
a natural language name, such as "Big Shoe Store Inc.", whilst the
24+
The payee information fields are intended to communicate to the user which
25+
entity will be the recipient of the funds. In most cases this would be the
26+
merchant (or other entity) that the user has already been interacting with in
27+
the current session (e.g., checkout flow). The `payeeName` field, if present,
28+
communicates a natural language name, such as "Big Shoe Store Inc.", whilst the
2929
`payeeOrigin`, if present, communicates the web URL at which the payee can be
3030
found, such as "https://bigshoestore.example".
3131

0 commit comments

Comments
 (0)