Updated a few details.

README.md

@@ -2,70 +2,75 @@
 
 Make sure you read **all** of this document carefully, and follow the guidelines in it.
 
-## Background
+## Context
 
-Use HTML, CSS and JavaScript to implement the following mockup.
+Use HTML, CSS, and JavaScript to implement the following mockup.
 
 ![wiredcraft-front-end-test-mock](https://cldup.com/JM3lLBAS5V.jpg)
 
 [Mockup source Sketch file](https://cldup.com/2wo0ktkbxJ.sketch)
 
+## Requirements
+
 ### Page Structure
 
 ```
 Header(Navigation)
 
 Main
   - Table Filter
-    - Search Filter(dropdown component)
-    - Search Keywords(input field)
+    - Search Filter (dropdown component)
+    - Search Keywords (input field)
   - Table
     - Table Header
     - Table Body
       - Table Row
-        - Collapsable Row(State -> Distract -> Township)
-          - State Level(Show by default)
-            - District Level(Hide by default, show by clicking the button in state level)
-              - Township Level(Hide by default, show by clicking the button in district level)
+        - Collapsable Row (State -> Distract -> Township)
+          - State Level (Show by default)
+            - District Level (Hide by default, show by clicking the button in state level)
+              - Township Level (Hide by default, show by clicking the button in district level)
 ```
 
 ### Functionality
 
-* Static page header(navigation bar), no extra features needed.
+* Static page header (navigation bar), no extra features needed.
 * The table filter needs to be able to filter the result in the table by the type and keywords.
 * The table is nested, and grouped by state, district, township.
 
-## Getting Started
+### Tech stack
 
-There's nothing here, we leave it to you to choose the build tool, code structure, framework, testing approach...
-
-## Requirements
+- JS oriented
+    - Use **React**.
+    - Use CSS or SASS/SCSS or any **CSS** framework as you like.
+- CSS oriented
+    - Use any **JS** framework as you like.
+    - Use **SASS/SCSS**.
 
-- Clear documentation, including but not limited to how to test your code.
-
-- Proper unit tests.
+### Bonus
 
+- Write clear **documentation** on how it's designed and how to run the code.
+- Provide proper unit tests.
+- Write good commit messages.
+- An online demo is always welcome.
 
 ## What We Care About
 
-Feel free to use any libraries you would use if this were a real production app, but remember we're interested in your code & the way you solve the problem, not how well you can use a particular library.
+Feel free to use any libraries you would use if this were a real production App, but remember we're interested in your code & the way you solve the problem, not how well you can use a particular library.
 
 We're interested in your method and how you approach the problem just as much as we're interested in the end result.
 
 Here's what you should aim for:
 
-- Good use of current HTML, CSS and JavaScript & performance best practices.
-
+- Good use of current HTML, CSS, and JavaScript & performance best practices.
 - Solid testing approach.
-
 - Extensible code.
 
 ## Q&A
 
-* Where should I send back the result when I'm done?
+> Where should I send back the result when I'm done?
 
-Fork this repo and send us a pull request when you think you are done. We don't have deadline for the task.
+Fork this repo and send us a pull request when you think you are done. We don't have a deadline for the task.
 
-* What if I have question?
+> What if I have a question?
 
 Create a new issue in the repo and we will get back to you very quickly.