Update README.md (#18)

s/htlp/help/

README.md

@@ -29,7 +29,7 @@ If you would like to cache a pure computation in the same way as an effectful `S
 Both the input and the output types of named workflows are subject to the same restrictions as steps, that is they have to be in the Store type class. Naming workflows has two effects:
 
 * Named workflows are cached so they will not be repeated if the calculation is restarted. 
-* Names given to workflows htlp when you are logging or visualising the dependency graph
+* Names given to workflows help when you are logging or visualising the dependency graph
 
 ## Wiring 
 
@@ -54,4 +54,4 @@ Workflows can be executed in a variety of ways and you can define your own inter
 
 * A basic non-interruptible interpreter `runFlow` is given in [Control.FunFlow.Base](https://github.com/glutamate/funflow/blob/master/src/Control/FunFlow/Base.hs)
 * An interruptible and resumable interpreter where all state is stored in-process is given in [Control.FunFlow.Exec.Local](https://github.com/glutamate/funflow/blob/master/src/Control/FunFlow/Exec/Local.hs)
-* An execution engine based on Redis is given in [Control.FunFlow.Exec.Redis](https://github.com/glutamate/funflow/blob/master/src/Control/FunFlow/Exec/Redis.hs)
+* An execution engine based on Redis is given in [Control.FunFlow.Exec.Redis](https://github.com/glutamate/funflow/blob/master/src/Control/FunFlow/Exec/Redis.hs)