commit 9f244e5830a7e4b636e96bf56e8708c276fb0930
author Gourav Shenoy <shenoy.200@gmail.com> Thu Jun 22 15:29:08 2017 -0400
committer Gourav Shenoy <shenoy.200@gmail.com> Thu Jun 22 15:29:08 2017 -0400
tree 90fe562f1e23727a40988a1c174a2cc21e348bfb
parent ad8cde1f4c5c3a2a89bd2642a470e70e366c9d08

Update README for helix-playground

helix-playground/README.md

diff --git a/helix-playground/README.md b/helix-playground/README.md
index 3be47ce..7fad1c1 100644
--- a/helix-playground/README.md
+++ b/helix-playground/README.md
@@ -14,7 +14,7 @@
 * Workflow – A combination of jobs arranged in a DAG. In a ONE-TIME workflow, once all jobs are completed, the workflow ends. In a RECURRING workflow, you can schedule workflows to run periodically.
 * Job Queues – Another type of workflow, but never ends – keeps accepting new incoming jobs. Ends only when user terminates it.
 
-[helix-tas-framework](images/helix-task-framework.png)
+![helix-task-framework](images/helix-task-framework.png "Helix Task Framework Workflow")
 
 * Helix also allows users to share data (key-value pairs) across Tasks/Jobs/Workflows. The content stored at workflow layer can shared by different jobs belong to this workflow. Similarly content persisted at job layer can shared by different tasks nested in this job.
 * Helix provides APIs to POLL either a JOB or WORKFLOW to reach a particular state.