unicodeveloper
diff --git a/‎README.md
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions b/‎README.md
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
@@ -100,7 +100,7 @@ return [
 Though there are multiple ways to pay an order, most payment gateways expect you to follow the following flow in your checkout process:
 
 ### 1. The customer is redirected to the payment provider
-After the customer has gone through the checkout process and is ready to pay, the customer must be redirected to site of the payment provider.
+After the customer has gone through the checkout process and is ready to pay, the customer must be redirected to the site of the payment provider.
 
 The redirection is accomplished by submitting a form with some hidden fields. The form must send a POST request to the site of the payment provider. The hidden fields minimally specify the amount that must be paid, the order id and a hash.
 
@@ -111,7 +111,7 @@ The hash is calculated using the hidden form fields and a non-public secret. The
 The customer arrives on the site of the payment provider and gets to choose a payment method. All steps necessary to pay the order are taken care of by the payment provider.
 
 ### 3. The customer gets redirected back to your site
-After having paid the order the customer is redirected back. In the redirection request to the shop-site some values are returned. The values are usually the order id, a paymentresult and a hash.
+After having paid the order the customer is redirected back. In the redirection request to the shop-site some values are returned. The values are usually the order id, a payment result and a hash.
 
 The hash is calculated out of some of the fields returned and a secret non-public value. This hash is used to verify if the request is valid and comes from the payment provider. It is paramount that this hash is thoroughly checked.