docs: sigh

interledger · Aug 21, 2024 · 86eaf46 · 86eaf46
1 parent f14d2da
commit 86eaf46
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 17 deletions.
diff --git a/packages/documentation/src/content/docs/components/open-payments.mdx b/packages/documentation/src/content/docs/components/open-payments.mdx
@@ -6,14 +6,7 @@ tableOfContents:
 
 import { LinkOut } from '@interledger/docs-design-system'
 
-<LinkOut href='https://openpayments.dev'>Open Payments</LinkOut> is the standard
-that Rafiki follows to enable third-party clients to securely retrieve account information
-and initiate payments from your customers’ accounts with their consent. The Open
-Payments standard describes a uniform way to create and manage grants and resources
-for <LinkOut href='https://openpayments.dev/introduction/op-concepts/#resource-types'>
-  incoming payments, quotes, and outgoing payments
-</LinkOut>
-.{' '}
+Rafiki follows the <LinkOut href='https://openpayments.dev'>Open Payments</LinkOut> standard to enable third-party clients to securely retrieve account information and initiate payments from your customers’ accounts with their consent. The standard describes a uniform way to create and manage grants and resources for <LinkOut href='https://openpayments.dev/introduction/op-concepts/#resource-types'>incoming payments, quotes, and outgoing payments</LinkOut>.
 
 ### Example use case - retrieve account information
 

diff --git a/...es/documentation/src/content/docs/services-and-aux-packages/backend-service.mdx b/...es/documentation/src/content/docs/services-and-aux-packages/backend-service.mdx
@@ -33,15 +33,7 @@ The following are required when using the `backend` service.
 
 The `backend` service exposes the Open Payments APIs, which are auth-protected using an opinionated version of the Grant Negotiation and Authorization Protocol (GNAP). Review the [`auth`](/services-and-aux-packages/auth-service) service page for more details about grant authorization and authentication.
 
-The `backend` service allows you to manage Open Payments <LinkOut href="https://openpayments.dev/introduction/op-concepts/#incoming-payment">incoming payments</LinkOut>, <LinkOut href="https://openpayments.dev/introduction/op-concepts/#quote">quotes</LinkOut>, and
-
-<LinkOut href='https://openpayments.dev/introduction/op-concepts/#outgoing-payment'>
-  outgoing payments
-</LinkOut>
-. Quotes and outgoing payments call the ILP connector, described in the next section,
-to send ILP packets. Quoting sends unfulfillable probe packets, for example to determine
-a transaction’s cost before executing the payment. Outgoing payments send packets
-as part of executing the payment.
+The `backend` service allows you to manage Open Payments <LinkOut href="https://openpayments.dev/introduction/op-concepts/#incoming-payment">incoming payments</LinkOut>, <LinkOut href="https://openpayments.dev/introduction/op-concepts/#quote">quotes</LinkOut>, and <LinkOut href='https://openpayments.dev/introduction/op-concepts/#outgoing-payment'>outgoing payments</LinkOut>. Quotes and outgoing payments call the ILP connector, described in the next section, to send ILP packets. Quoting sends unfulfillable probe packets, for example to determine a transaction’s cost before executing the payment. Outgoing payments send packets as part of executing the payment.
 
 :::note
 The calls to the ILP connector are made by calling the `makeIlpPlugin`, which is an implementation detail of an ILP connector that Rafiki will abstract. After calling the plugin, it will be passed to the <LinkOut href="https://github.com/interledgerjs/interledgerjs/tree/master/packages/pay">`@interledger/pay`</LinkOut> library to facilitate sending payments over Interledger using STREAM.