anchor.diff:  A Celos workflow always has an Oozie workflow
   (`/wordcount/workflow.xml` in this case) as its "meat".
   
  -If we were to receive data from two datacenters, in `/input/nyc` and
  -`/input/lax`, we can define a helper function and use that to quickly
  -define two workflows, sharing the same Oozie workflow definition, with
  -the IDs `wordcount-nyc` and `wordcount-lax`:
  +If we were to receive data from two sources, say two datacenters in
  +`/input/nyc` and `/input/lax`, we can define a helper function and use
  +that to quickly define two workflows with the IDs `wordcount-nyc` and
  +`wordcount-lax`:
   
   [source,javascript]
   ....
  
positive.code: Simple: It solves my use case.
  ....
  
  === Related Tools
  
  Two similar, programmable schedulers:
  
  * link:https://github.com/airbnb/airflow[Airbnb Airflow]
  
  * link:https://github.com/spotify/luigi[Spotify Luigi]
  
  === Acknowledgements
  
  Thanks to our in-house users and to the developers of the many fine
  
negative.code: 
  == Miscellaneous
  
  === Related Tools
  
  Two similar, programmable schedulers:
  
  * link:https://github.com/airbnb/airflow[Airbnb Airflow]
  
  * link:https://github.com/spotify/luigi[Spotify Luigi]
  
  === The Celos Name
  
  