lightsparkdev · mintlify · Sep 7, 2026
diff --git a/mintlify/global-accounts/agents/approvals-and-audit.mdx b/mintlify/global-accounts/agents/approvals-and-audit.mdx
@@ -111,6 +111,7 @@ Support at least two controls:
 Pause is useful for temporary uncertainty. Revoke is appropriate when a device is lost, a credential is exposed, or the customer no longer wants the agent connected.
 
 Grid enforces these controls. Your product should surface the current connection state and expose the relevant actions in your own experience.
+
 ## What to show in the approval UI
 
 Your approval UI should answer:

diff --git a/mintlify/global-p2p/onboarding/configuring-customers.mdx b/mintlify/global-p2p/onboarding/configuring-customers.mdx
@@ -18,7 +18,7 @@ This guide provides comprehensive information about creating customers in the Gr
 
 The only required field for all customers is `customerType` (`INDIVIDUAL` or `BUSINESS`). It's recommended to also pass a `platformCustomerId` to tie the customer to your internal identifier, but if you don't, one will be generated automatically.
 
-If using sending and receiving to just-in-time UMA addresses, you'll also need to specify the bank account information
+If using sending and receiving to just-in-time UMA addresses, you'll also need to specify the bank account information.
 
 ## Creating Customers
 

diff --git a/mintlify/payouts-and-b2b/index.mdx b/mintlify/payouts-and-b2b/index.mdx
@@ -52,7 +52,7 @@ Implementing cross-border payments with {payToBankProductName} is simple. Here's
 {payToBankProductName} has two customer onboarding options - one for non regulated entities where {payToBankProductName} handles the KYC/KYB process and one for regulated entities where you handle the KYC/KYB process.
 
 When creating customers, you'll be able to also connect external accounts or internal accounts to a specific customer and also add accounts for counterparties on the receiving end. 
-To learn more about accounts read our [internal accounts guide](/payouts-and-b2b/depositing-funds/internal-accounts) or setting up [external accounts guide](/payouts-and-b2b/depositing-funds/external-accounts)
+To learn more about accounts read our [internal accounts guide](/payouts-and-b2b/depositing-funds/internal-accounts) or setting up [external accounts guide](/payouts-and-b2b/depositing-funds/external-accounts).
 </Info>
 
 ### Funding Payments
@@ -61,7 +61,7 @@ To learn more about accounts read our [internal accounts guide](/payouts-and-b2b
 With real-time funding, you'll receive payment instructions as part of the quote. Once payment is received by our services, we'll initiate the payment to the receiver. 
 
 ### Sending Payments
-To send with {payToBankProductName}, onboard an account for a customer and the counter party, then execute and fund a quote. {payToBankProductName} resolves the receiver by external bank details, returns min/max and an exchange rate, and provides funding instructions. Once funded, {payToBankProductName} handles FX and delivery to the receiving account.
+To send with {payToBankProductName}, onboard an account for a customer and the counterparty, then execute and fund a quote. {payToBankProductName} resolves the receiver by external bank details, returns min/max and an exchange rate, and provides funding instructions. Once funded, {payToBankProductName} handles FX and delivery to the receiving account.
 
 ### Environments
 

diff --git a/mintlify/payouts-and-b2b/onboarding/configuring-customers.mdx b/mintlify/payouts-and-b2b/onboarding/configuring-customers.mdx
@@ -106,7 +106,7 @@ Common use cases for `platformAccountId`:
 <AccordionGroup>
   <Accordion title="FBO Accounts">
     FBO accounts are used when the platform has a single omnibus account that is used to fund all customers. Account details
-    must be provided manually at the platform level. For each customer, during you should simply provide:
+    must be provided manually at the platform level. For each customer, you should simply provide:
 
     ```json
     "bankAccountInfo": {

diff --git a/mintlify/payouts-and-b2b/onboarding/implementation-overview.mdx b/mintlify/payouts-and-b2b/onboarding/implementation-overview.mdx
@@ -22,7 +22,7 @@ Onboard customers and accounts. There are two patterns:
 - Regulated entities can directly create customers by providing KYC/KYB data via API
 - Unregulated entities should request a KYC link and embed the hosted KYC flow; once completed, the customer can transact.
 
-You'll also need to persist the Grid customer IDs for use in payment flows
+You'll also need to persist the Grid customer IDs for use in payment flows.
 
 
 ## Account funding
@@ -36,7 +36,7 @@ You can mix models as necessary. But it may make reconciliation more complex.
 </Tip>
 
 ## External account creation
-Register accounts your customers will send to or receive from, such as CLABE (MX), IBAN (EU/UK), ACH/RTP(US), UPI (IN), Spark address, and others.
+Register accounts your customers will send to or receive from, such as CLABE (MX), IBAN (EU/UK), ACH/RTP (US), UPI (IN), Spark address, and others.
 - Capture beneficiary details (individual or business) and required banking fields
 - Validate account formats where applicable and map them to your internal customer
 

diff --git a/mintlify/payouts-and-b2b/platform-tools/sandbox-testing.mdx b/mintlify/payouts-and-b2b/platform-tools/sandbox-testing.mdx
@@ -249,8 +249,8 @@ GET /transactions/{transactionId}
 
 While sandbox closely mimics production, there are some differences:
 
-- **Instant settlement**: All transfers complete immediately (success cases) or fail immediately (error cases), except timeout scenarios (005)
-- **No real bank validation**: Account numbers aren't validated against real banking networks
+- **Instant settlement**: All transfers complete immediately (success cases) or fail immediately (error cases), except timeout scenarios (005).
+- **No real bank validation**: Account numbers aren't validated against real banking networks.
 - **Simplified KYC**: KYC processes are simulated and complete instantly. You must add customers via the `/customers` endpoint, rather than using the KYC link flow.
 - **Fixed exchange rates**: Currency conversion rates may not reflect real-time market rates.
 

diff --git a/mintlify/snippets/country-support.mdx b/mintlify/snippets/country-support.mdx
@@ -69,7 +69,7 @@ import { FeatureCard, FeatureCardGrid, FeatureCardList, FeatureCardContainer } f
 | 🇸🇰 Slovakia | SK | `SEPA` `SEPA Instant` `SWIFT` |
 | 🇸🇮 Slovenia | SI | `SEPA` `SEPA Instant` |
 | 🇿🇦 South Africa | ZA | `Bank Transfer` `SWIFT` |
-| 🇪🇸 Spain | ES | `SEPA`  `SEPA Instant` `SWIFT` |
+| 🇪🇸 Spain | ES | `SEPA` `SEPA Instant` `SWIFT` |
 | 🇸🇪 Sweden | SE | `SEPA` `SEPA Instant` `SWIFT` |
 | 🇨🇭 Switzerland | CH | `SEPA` `SEPA Instant` `SWIFT` |
 | 🇹🇿 Tanzania | TZ | `Mobile Money` (Airtel, Vodacom) `SWIFT` |

diff --git a/mintlify/snippets/creating-customers/customers.mdx b/mintlify/snippets/creating-customers/customers.mdx
@@ -18,7 +18,7 @@ export const Customers = ({ individualEnabled = true, businessEnabled = true, um
 
       The only required field for all customers is `customerType` (`INDIVIDUAL` or `BUSINESS`). It's recommended to also pass a `platformCustomerId` to tie the customer to your internal identifier, but if you don't, one will be generated automatically.
 
-      If using sending and receiving to just-in-time UMA addresses, you'll also need to specify the bank account information
+      If using sending and receiving to just-in-time UMA addresses, you'll also need to specify the bank account information.
 
       ### Individual customers
 

diff --git a/mintlify/snippets/platform-config-currency-api-webhooks.mdx b/mintlify/snippets/platform-config-currency-api-webhooks.mdx
@@ -30,8 +30,8 @@ Base URL: `https://api.lightspark.com/grid/2025-10-13` (same for Sandbox and Pro
 Configure your webhook endpoint to receive payment lifecycle events. Webhooks use asymmetric (public/private key) signatures; verify each webhook using the Grid public key available in your dashboard.
 
 - Expose a public HTTPS endpoint (for development, reverse proxies like ngrok can help). You'll also need to set your webhook endpoint in the Grid dashboard.
-- When receiving webhooks, verify the `X-Grid-Signature` header against the exact request body using the dashboard-provided public key
-- Process events idempotently and respond with 2xx on success
+- When receiving webhooks, verify the `X-Grid-Signature` header against the exact request body using the dashboard-provided public key.
+- Process events idempotently and respond with 2xx on success.
 
 You can trigger a test delivery from the API to validate your endpoint setup. The public key for verification is shown in the dashboard; rotate and update it when instructed by Lightspark.
 

diff --git a/mintlify/snippets/terminology.mdx b/mintlify/snippets/terminology.mdx
@@ -57,7 +57,7 @@ Internal accounts:
 **External accounts** are traditional bank accounts, crypto wallets, or other payment instruments connected to customers
 for on-ramping or off-ramping funds. Each external account:
 
-- Are associated with a specific customer or the platform
+- Is associated with a specific customer or the platform
 - Represents a real-world bank account (with routing number, account number, IBAN, etc.), wallet, or payment instrument
 - Has an associated beneficiary (individual or business) who receives payments from the customer or platform
 - Has a status indicating screening status (ACTIVE, PENDING, INACTIVE, etc.)

diff --git a/mintlify/snippets/uma-test-wallet.mdx b/mintlify/snippets/uma-test-wallet.mdx
@@ -12,9 +12,9 @@ The UMA Test Wallet is an external tool that demonstrates UMA payment flows end
 </FeatureCardGrid>
 
 ### What UMA Test Wallet can do
-- **Experience UMA flows**: Send and receive cross-currency UMA payments
+- **Experience UMA flows**: Send and receive cross-currency UMA payments.
 - **Preview UX best practices**: See recommended entry points, confirmations, and error handling.
-- **Develop and test**: Use the wallet as a counterparty FI when building UMA integrations
+- **Develop and test**: Use the wallet as a counterparty FI when building UMA integrations.
 
 <Note>
 For background on UMA itself, see the UMA Standard: [UMA Standard—Introduction](https://docs.uma.me/uma-standard/introduction).