Fix typos (#41)

Author: diegotid

catalog/devicelocation/samplecode_devicelocation.md

@@ -6,7 +6,7 @@ category: 66aa4f941e51e7000fa353ce
 
 The following code shows, for didactic purposes, a hypothetical or sample SDK, in several programming languages, from a generic Open Gateway's channel partner, also known as aggregator. The final implementation will depend on the channel partner's development tools offering. Note that channel partners' Open Gateway SDKs are just code modules wrapping authorization and API calls providing an interface in your app's programming for convenience.
 
-> 📘 It is recomended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
+> 📘 It is recommended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
 
 ### Table of contents
 - [Backend flow](#backend-flow)

catalog/devicestatus/samplecode_devicestatus.md

@@ -10,7 +10,7 @@ This sample code consumes the API without an SDK, using direct HTTP requests. Ho
 
 Note that currently, our Sandbox SDK does not have Device Status implemented.
 
-> 📘 It is recomended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
+> 📘 It is recommended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
 
 ### Table of contents
 - [Backend flow](#backend-flow)

catalog/numberverification/samplecode_numberverification.md

@@ -14,7 +14,7 @@ The final implementation will depend on the channel partner's development tools
 
 Sample code on how to consume the API without an SDK, directly with HTTP requests, is also provided, and it is common and valid no matter what your partner is, thanks to the CAMARA standardization. If you do not use an SDK you need to code the HTTP calls and additional stuff like encoding your credentials, calling authorization endpoints, handling tokens, etc. You can check our sample [Postman collection](https://bxbucket.blob.core.windows.net/bxbucket/opengateway-web/uploads/OpenGateway.postman_collection.json) as a reference.
 
-> 📘 It is recomended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
+> 📘 It is recommended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
 
 ### Table of contents
 - [Frontend](#frontend)

catalog/simswap/samplecode_simswap.md

@@ -12,7 +12,7 @@ The following code shows, for didactic purposes, a hypothetical or sample SDK, i
 
 Sample code on how to consume the API without an SDK, directly with HTTP requests, is also provided, and it is common and valid no matter what your partner is, thanks to the CAMARA standardization. If you do not use an SDK you need to code the HTTP calls and additional stuff like encoding your credentials, calling authorization endpoints, handling tokens, etc. You can check our sample [Postman collection](https://bxbucket.blob.core.windows.net/bxbucket/opengateway-web/uploads/OpenGateway.postman_collection.json) as a reference.
 
-> 📘 It is recomended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
+> 📘 It is recommended to use the [API Reference tool](https://developers.opengateway.telefonica.com/reference/) for faster calls of our APIs
 
 ### Table of contents
 - [Backend flow](#backend-flow)

gettingstarted/apireference.md

@@ -26,7 +26,7 @@ Each API has a string called “purpose” that defines the intended use of that
 
 ## Config the API Reference step by step
 ### Step 1: Get the authorization code
-For a faster and easier authorization it is recomended to use a [CIBA](../about/glossary.md). This CIBA is going to authorize an application to access a resource from the backend:
+For a faster and easier authorization it is recommended to use a [CIBA](../about/glossary.md). This CIBA is going to authorize an application to access a resource from the backend:
 - <u>login_hint</u>: The phone number you own and provided when creating your application. If you are using [the Sandbox](https://sandbox.opengateway.telefonica.com/my-apps), it is the number you provided when requesting access to production. If your application is a mock, you can enter any invented number that does not end with 9. The sintax is <id_type>:<id_value> (tel:+34666555432)
 - <u>purpose</u>: The purpose string for the API you want to call. You can check the purpose by clicking on one of the test calls in this API reference. If not, you have a list in the *Before Getting Started* section of this page.
 - <u>credentials</u>: The username is your client_id and your password is you client_secret. You can get both from the info in your aplication. If you are using [a Sandbox app](https://sandbox.opengateway.telefonica.com/my-apps) you have this information in My Apps page, clicking in your app.