[airflow] 03/05: Minor grammar and sentence flow corrections in pip installation docs (#19468)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v2-2-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit b2c921795e6c64b1fb279284cd94701ae780529b
Author: Richard Pelgrim <68...@users.noreply.github.com>
AuthorDate: Tue Nov 9 22:38:12 2021 +0100

    Minor grammar and sentence flow corrections in pip installation docs (#19468)
    
    * Minor grammar and sentence flow corrections in pip installation docs (#19468)
    
    (cherry picked from commit 57863400837d4e8cc114df81343178c5bc9bef2e)
---
 docs/apache-airflow/installation/installing-from-pypi.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/apache-airflow/installation/installing-from-pypi.rst b/docs/apache-airflow/installation/installing-from-pypi.rst
index 8437e2b..95d0552 100644
--- a/docs/apache-airflow/installation/installing-from-pypi.rst
+++ b/docs/apache-airflow/installation/installing-from-pypi.rst
@@ -46,19 +46,19 @@ This is an example, see further for more explanation.
 Constraints files
 '''''''''''''''''
 
-Airflow installation might be sometimes tricky because Airflow is a bit of both a library and application.
+Airflow installation can be tricky sometimes because Airflow is both a library and an application.
 Libraries usually keep their dependencies open and applications usually pin them, but we should do neither
 and both at the same time. We decided to keep our dependencies as open as possible
 (in ``setup.cfg`` and ``setup.py``) so users can install different
 version of libraries if needed. This means that from time to time plain ``pip install apache-airflow`` will
-not work or will produce unusable Airflow installation.
+not work or will produce an unusable Airflow installation.
 
-In order to have repeatable installation, we also keep a set of "known-to-be-working" constraint files in the
-``constraints-main``, ``constraints-2-0``, ``constraints-2-1`` etc. orphan branches and then we create tag
-for each released version e.g. :subst-code:`constraints-|version|`. This way, when we keep a tested and working set of dependencies.
+In order to have a repeatable installation, we also keep a set of "known-to-be-working" constraint files in the
+``constraints-main``, ``constraints-2-0``, ``constraints-2-1`` etc. orphan branches and then we create a tag
+for each released version e.g. :subst-code:`constraints-|version|`. This way, we keep a tested and working set of dependencies.
 
 Those "known-to-be-working" constraints are per major/minor Python version. You can use them as constraint
-files when installing Airflow from PyPI. Note that you have to specify correct Airflow version
+files when installing Airflow from PyPI. Note that you have to specify the correct Airflow
 and Python versions in the URL.
 
 You can create the URL to the file substituting the variables in the template below.