docs: fix typo (recieve->receive (x14))

Android/docs/payment.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Android/docs/sms.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure Android.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure Android.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure Android.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure Android.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Nodejs/docs/payment.md

@@ -75,7 +75,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure NODEJS.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure NODEJS.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure NODEJS.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure NODEJS.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Nodejs/docs/sms.md

@@ -75,7 +75,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure NODEJS.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure NODEJS.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure NODEJS.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure NODEJS.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

PHP/docs/payment.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

PHP/docs/sms.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PHP.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PHP.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Payment.md

@@ -52,7 +52,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` in the figure abov
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PROTO.PAYMENT.7* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PROTO.PAYMENT.7* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Python/docs/payment.md

@@ -72,7 +72,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PROTO.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PROTO.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Python/docs/sms.md

@@ -72,7 +72,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PROTO.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PROTO.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Ruby/docs/payment.md

@@ -65,7 +65,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure RUBY.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure RUBY.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure RUBY.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure RUBY.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Ruby/docs/sms.md

@@ -65,7 +65,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure RUBY.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure RUBY.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure RUBY.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure RUBY.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

Sms.md

@@ -52,7 +52,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` in the figure abov
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PROTO.SMS.7* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PROTO.SMS.7* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PROTO.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

iOS/docs/payment.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure PHP.PAYMENT.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure PHP.PAYMENT.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and 

iOS/docs/sms.md

@@ -70,7 +70,7 @@ Before invoking your redirect, please replace `[YOUR APP ID]` and `[YOUR APP SEC
 ![Authorize](https://raw.github.com/Openovate/rest-docs/master/sms/assets/user.jpg)
 ====
 
-Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we recieve the code to continue the authentication process. *Figure Android.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure Android.SMS.3*.
+Once the user gives permission, Globe will redirect the user to your Redirect URI with a `code` parameter appended to the end of it. This is how we receive the code to continue the authentication process. *Figure Android.SMS.8* shows how this redirect will look like given that we set our redirect URI to `http://www.example.com/callback` in our app create form in *Figure Android.SMS.3*.
 
     **Important:** It is also possible that a user can give permissions to your app using just their 
     phone via SMS. Globe will call (not a phone call) your redirect URI with `access_token` and