Clarify back-end track

charlax · charlax · commit d35d2190dc79 · 2014-03-25T18:57:20.000-07:00
diff --git a/README.md b/README.md
@@ -82,9 +82,9 @@ respected.
 Choose **one** of the following technical tracks (full stack is preferred):
 
 1. **Full-stack**: include both front-end and back-end.
-2. **Back-end track**: include a minimal front-end (e.g. a static view). Write,
-   document and test your API as if it will be used by other services and
-   front-ends.
+2. **Back-end track**: include a minimal front-end (e.g. a static view, API
+   docs, etc. - do not spend time on it). Write, document and test your API as
+   if it will be used by other services and front-ends.
 3. **Front-end track**: include a minimal back-end, or use the data service
    directly. Focus on making the interface as polished as possible.
 
