Skip to content

Commit

Permalink
word-smithing
Browse files Browse the repository at this point in the history
  • Loading branch information
cyberphone committed Sep 28, 2024
1 parent 36b01e6 commit 1f0baee
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 4 additions & 4 deletions doc/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -144,11 +144,11 @@ <h5 id='2.4.payer-authorization'>2.4.&nbsp; Payer&nbsp;Authorization</h5>
In addition, the HTTP <code style='white-space:nowrap'>Content-Type</code>
header parameter <b>must</b> be set to <code>application/cbor</code>.
<h5 id='2.5.calling-the-payment-network'>2.5.&nbsp; Calling&nbsp;the&nbsp;Payment&nbsp;Network</h5>
In this phase the <code class='entity'>Payee</code> uses the received
<a href='#3.3.authorization-response'>Authorization&nbsp;Response</a> in one or more
<i>payment-network-specific</i> requests to the designated
<code class='entity'>Payment</code>&nbsp;<code class='entity'>Network</code>
After receiving the <a href='#3.3.authorization-response'>Authorization&nbsp;Response</a>, the <code class='entity'>Payee</code>
includes this object in a <i>payment-network-specific</i> request to the designated
<code class='entity'>Payment</code>&#8201;<code class='entity'>Network</code>
(provided by the selected payment credential).
Note that this phase may constitute of <i>multiple</i> request-response pairs.
<h5 id='2.6.wallet-termination'>2.6.&nbsp; Wallet&nbsp;Termination</h5>
After successful (or failed) authorization, the
<a href='#3.3.authorization-response'>Authorization&nbsp;Response</a>
Expand Down
8 changes: 4 additions & 4 deletions docgen/document-template.html
Original file line number Diff line number Diff line change
Expand Up @@ -117,11 +117,11 @@ <h3>Table of Contents</h3>
In addition, the HTTP <code style='white-space:nowrap'>Content-Type</code>
header parameter <b>must</b> be set to <code>application/cbor</code>.
${calling-the-payment-network}
In this phase the <code class='entity'>Payee</code> uses the received
${href.authorization-response} in one or more
<i>payment-network-specific</i> requests to the designated
<code class='entity'>Payment</code>&nbsp;<code class='entity'>Network</code>
After receiving the ${href.authorization-response}, the <code class='entity'>Payee</code>
includes this object in a <i>payment-network-specific</i> request to the designated
<code class='entity'>Payment</code>&#8201;<code class='entity'>Network</code>
(provided by the selected payment credential).
Note that this phase may constitute of <i>multiple</i> request-response pairs.
${wallet-termination}
After successful (or failed) authorization, the
${href.authorization-response}
Expand Down

0 comments on commit 1f0baee

Please sign in to comment.