Repository: incubator-airflow Updated Branches: refs/heads/master 88f895aa6 -> 8d7297573
docfix: Fix a couple of minor typos. Project: http://git-wip-us.apache.org/repos/asf/incubator-airflow/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-airflow/commit/8d729757 Tree: http://git-wip-us.apache.org/repos/asf/incubator-airflow/tree/8d729757 Diff: http://git-wip-us.apache.org/repos/asf/incubator-airflow/diff/8d729757 Branch: refs/heads/master Commit: 8d72975734e66d6efa775cec62dd0aea87575c0d Parents: 88f895a Author: Mark Reid <mr...@mozilla.com> Authored: Mon May 23 09:16:03 2016 -0300 Committer: Mark Reid <mr...@mozilla.com> Committed: Mon May 23 09:16:38 2016 -0300 ---------------------------------------------------------------------- docs/concepts.rst | 2 +- docs/configuration.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-airflow/blob/8d729757/docs/concepts.rst ---------------------------------------------------------------------- diff --git a/docs/concepts.rst b/docs/concepts.rst index 405048a..6e15ff8 100644 --- a/docs/concepts.rst +++ b/docs/concepts.rst @@ -172,7 +172,7 @@ functionally equivalent: When using the bitshift to compose operators, the relationship is set in the direction that the bitshift operator points. For example, ``op1 >> op2`` means -that ``op1`` runs first and ``op2`` runs seconds. Multiple operators can be +that ``op1`` runs first and ``op2`` runs second. Multiple operators can be composed -- keep in mind the chain is executed left-to-right and the rightmost object is always returned. For example: http://git-wip-us.apache.org/repos/asf/incubator-airflow/blob/8d729757/docs/configuration.rst ---------------------------------------------------------------------- diff --git a/docs/configuration.rst b/docs/configuration.rst index 2d8a9fb..3eed553 100644 --- a/docs/configuration.rst +++ b/docs/configuration.rst @@ -107,7 +107,7 @@ Here are a few imperative requirements for your workers: ``MySqlOperator``, the required Python library needs to be available in the ``PYTHONPATH`` somehow - The worker needs to have access to its ``DAGS_FOLDER``, and you need to - synchronize the filesystems by your own mean. A common setup would be to + synchronize the filesystems by your own means. A common setup would be to store your DAGS_FOLDER in a Git repository and sync it across machines using Chef, Puppet, Ansible, or whatever you use to configure machines in your environment. If all your boxes have a common mount point, having your
