Fixed some minor typos

docs/tutorial.rst

@@ -77,12 +77,12 @@ at first) is that this Airflow Python script is really
 just a configuration file specifying the DAG's structure as code.
 The actual tasks defined here will run in a different context from
 the context of this script. Different tasks run on different workers
-at different point it time, which means this script cannot be directly
-to cross communicate between tasks for instance. Note that for this
+at different points in time, which means that this script cannot be used
+to cross communicate between tasks. Note that for this
 purpose we have a more advanced feature called ``XCom``.
 
 People sometimes think of the DAG definition file as a place where they
-can do some actual data processing, that is not the case at all!
+can do some actual data processing - that is not the case at all!
 The script's purpose is to define a DAG object. It needs to evaluate
 quickly (seconds, not minutes) since the scheduler will execute it
 periodically to reflect the changes if any.
@@ -420,7 +420,7 @@ running against it should get it to get triggered and run every day.
 
 Here's a few things you might want to do next:
 
-* Take an in-depth tour of the UI, click all the things!
+* Take an in-depth tour of the UI - click all the things!
 * Keep reading the docs! Especially the sections on:
 
     * Command line interface