Update mobile coding challenge

Author: AlexGrafl

mobile-challenge.md

@@ -2,22 +2,22 @@
 
 ## Welcome!
 
-To give you an idea of how some of the work as mobile engineering team member will look and help us get an impression of how you might approach these tasks, we've put together a take-home assignment. We’re doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we wouldn't ask you if we didn't already think you're a great fit for the role.
+To give you an idea of how some of the work as mobile engineering team member will look and help us get an impression of how you might approach these tasks, we have put together a take-home assignment. We are doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we would not ask you if we did not already think you are a great fit for the role.
 
 The objective of this take-home assignment is to create a simplified version of the Mimo app that can retrieve a simplified version of our coding lessons from a server and display them.
 
 Fingers crossed!
 
 ## Implementation
 
-- You can write the challenge any way you want. (At Mimo, we use Reactive Extensions and MVVM to build our apps. If you know those technologies, it makes sense for you to use them for this assignment.)
-- We'll only evaluate your submission based on your code - there's no need to worry about the visual design.
+- You can write the challenge any way you want. (At Mimo, we use Kotlin Coroutines/Flow and MVVM or MVI to build our apps. If you know those technologies, it makes sense for you to use them for this assignment.)
+- We will only evaluate your submission based on your code - there is no need to worry about the visual design.
 - Part of this assignment is to work with the APIs we provide.
 - Use Git to track your changes and upload your Git repo on Github, and once you are done please share your private Repository with us via [email protected]
 
 ## Goal
 
-Your goal is to write a small app with three simplified Mimo lessons (in the apps, we call these lessons "exercises"). You can get the information for the lessons from the API we provide. The lessons have a specific format (documented below) that defines how they need to be rendered. If a lesson contains an interaction, display the interaction. At app startup, display the first lesson. Also display a "Next" button that, when pressed, checks that the lesson has been solved and continues to the next lesson.
+Your goal is to write a small app with three simplified Mimo lessons. You can get the information for the lessons from the API we provide. The lessons have a specific format (documented below) that defines how they need to be rendered. At app startup, display the first lesson. Also display a "Next" button that, when pressed, checks that the lesson has been solved and continues to the next lesson.
 
 When a lesson is solved, store this event in a mobile database of your choice on the device (see "Lesson completion event").
 
@@ -56,9 +56,9 @@ Every lesson contains content, formatted as JSON, that represents an array of co
 }
 ```
 
-Each object in the content array represents a text snippet, each of which can have a different color. If the `input` object exists, it represents the range where the user needs to type in the expected input. In this example, the user has to input "World" in order to proceed to the next lesson. If there's an input interaction in the lesson and the user hasn't typed in the input field yet, disable the button. As soon as the user has typed anything, enable the button to allow the user to check for the correct answer and go on to the next lesson or display a message if it is incorrect. If there's no input interaction, keep the button enabled.
+Each object in the content array represents a text snippet, each of which can have a different color. If the `input` object exists, it represents the range where the user needs to type in the expected input. In this example, the user has to input "World" in order to proceed to the next lesson. If there is an input interaction in the lesson and the user has not typed in the input field yet, disable the button. As soon as the user has typed anything, enable the button to allow the user to check for the correct answer and go on to the next lesson or display a message if it is incorrect. If there is no input interaction, keep the button enabled.
 
-Here's an example of how such a lesson might look:
+Here is an example of how such a lesson might look:
 
 <img width="217" alt="challengedisplay" src="https://user-images.githubusercontent.com/964691/39253366-fe542ad0-48a7-11e8-98c4-8e1c2c6a470d.PNG">
 
@@ -73,5 +73,5 @@ It contains the following properties:
 
 ## Server API
 
-To get the lessons from the server API is simple: just send a GET request to https://mimochallenge.azurewebsites.net/api/lessons and you'll receive a JSON object that contains all the lesson information.
+To get the lessons from the server API is simple: just send a GET request to https://mimochallenge.azurewebsites.net/api/lessons and you will receive a JSON object that contains all the lesson information.