Update docs/api-docs/payments/payments-api-overview.mdx

Co-authored-by: Sarah Riehl <[email protected]>

docs/api-docs/payments/payments-api-overview.mdx

@@ -349,7 +349,7 @@ The payment gateway your application uses must be able to send raw card data thr
 
 <Callout type="info">
 #### Implementation note
-3D Secure is a storefront experience that requires the shopper's (end-customer) interaction. As this API is a server-to-server API (not a storefront API), attempting to process any payment that requires 3D Secure verification will fail, as these payments inherently require shopper interaction. Whenever 3D Secure is required, you must save cards via a shopper-initiated transaction before they can be charged as a stored payment instrument using this API.
+3D Secure is a storefront-based experience that requires the shopper's interaction to authenticate the transaction. Because requests to our Payments API must be initiated in a server-to-server context, rather than from the storefront, you must save any 3D Secure-enabled card during a shopper-initiated transaction, then charge it as a stored payment instrument. Attempts to process any payment that requires 3D Secure verification prior to saving the instrument will be unsuccessful.
 </Callout>
 
 ### Create an access token