diff --git a/plugins/woocommerce-blocks/docs/internal-developers/block-client-apis/checkout/checkout-flow-and-events.md b/plugins/woocommerce-blocks/docs/internal-developers/block-client-apis/checkout/checkout-flow-and-events.md
index 606712730f2..15b5c73eff7 100644
--- a/plugins/woocommerce-blocks/docs/internal-developers/block-client-apis/checkout/checkout-flow-and-events.md
+++ b/plugins/woocommerce-blocks/docs/internal-developers/block-client-apis/checkout/checkout-flow-and-events.md
@@ -267,7 +267,7 @@ When a payment method returns a non-truthy value, if it returns a valid response
 
 #### Success
 
-A response is considered a success response when it at a minimum is an object with this shape:
+A successful response should be given when the user's entered data is correct and the payment checks are successful. A response is considered successful if, at a minimum, it is an object with this shape:
 
 ```js
 const successResponse = { type: 'success' };
@@ -283,7 +283,7 @@ If `billingAddress` or `shippingAddress` properties aren't in the response objec
 
 #### Fail
 
-A response is considered a fail response when it at a minimum is an object with this shape:
+A fail response should be given when there is an error with the payment processing. A response is considered a fail response when it is an object with this shape:
 
 ```js
 const failResponse = { type: 'failure' };
@@ -298,7 +298,7 @@ When a fail response is returned by an observer, the payment method context stat
 
 #### Error
 
-A response is considered an error response when it at a minimum is an object with this shape:
+An error response should be given when there is an error with the user input on the checkout form. A response is considered an error response when it is an object with this shape:
 
 ```js
 const errorResponse = { type: 'error' };