Update README.md

Typos

README.md

@@ -1,7 +1,7 @@
 # Omise, OmiseGO & GO.Exchange Code Challenges
 
-This repository houses the code challenges for Omise, OmiseGO & GO.Exchange. These are small hands-on
-projects that are very relevant to the tasks you will be working on at us.
+This repository houses the code challenges for Omise, OmiseGO & GO.Exchange. These are
+small hands-on projects that are very relevant to the tasks you will be working on here.
 
 ### Ground Rules
 
@@ -12,16 +12,30 @@ projects that are very relevant to the tasks you will be working on at us.
   Send your patch to the hiring team.
 
 ### What to expect
-We do understand that our code challenges are time intensive and not always easy to execute. We do recognize and value the time and effort applicants put into their submission. Our Code Challenges reflect some of the tasks and skills you'd need while working with us. We believe that these *take-home* challenges will give you a deeper understanding of our product, what you'd be working on in the future and what level of commitment we look for in applicants.
+
+We do understand that our code challenges are time intensive and not always easy to
+execute. We do recognize and value the time and effort applicants put into their
+submission. Our Code Challenges reflect some of the tasks and skills you'd need while
+working with us. We believe that these *take-home* challenges will give you a deeper
+understanding of our product, what you'd be working on in the future and what level of
+commitment we look for in applicants.
 
 ### What we look for
-Rather than a complex solution, which added a million features and is written in 10,000 lines of code, we look for:
+
+Rather than a complex solution, which added a million features and is written in 10,000
+lines of code, we look for:
+
 * **Clarity:** You can write clear code that any devs could read and understand in one go
 * **Simplicity:** You can write gimmick-free and straightforward code with no ambiguities
 * **Defensiveness:** You can cover edge cases and treat user inputs with care
 
 ### What happens after your submission
-Once you have submitted your solution by sending us the **git-format-patch**, our Engineers will review the code. Due to the number of submissions we receive, and time-intensive review process, it might take us **1 week** to give you feedback on the submission. Based on the feedback, we will invite you for a meeting to talk more about your submission and continue the recruitment process.
+
+Once you have submitted your solution by sending us the **git-format-patch**, our
+Engineers will review the code. Due to the number of submissions we receive, and
+time-intensive review process, it might take us **1 week** to give you feedback on the
+submission. Based on the feedback, we will invite you for a meeting to talk more about
+your submission and continue the recruitment process.
 
 ### Challenges
 
@@ -53,10 +67,9 @@ Pick the one that most suites the position you wish to apply.
 * Devops / Kubernetes [challenge-devops](https://github.com/omise/challenges/tree/challenge-devops)
 
 ### Have fun and we look forward to your submission!
-  
+
 
 <h2>
 ᕙ(⇀‸↼‶)ᕗ
 </h2>
-