Merge pull request #312 from pmsoltani/pmsoltani-patch-1

asottile · web-flow · commit 0bdbd03e9e58 · 2020-04-24T10:26:41.000-07:00
Minor grammatical improvements
diff --git a/docs/frameworks/flask.rst b/docs/frameworks/flask.rst
@@ -1,9 +1,9 @@
 Using with Flask
 ================
 
-This guide explains how to use libsass with Flask_ web framework.
+This guide explains how to use libsass with the Flask_ web framework.
 :mod:`sassutils` package provides several tools that can be integrated
-to web applications written in Flask.
+into web applications written in Flask.
 
 .. _Flask: http://flask.pocoo.org/
 
@@ -35,31 +35,31 @@ Defining manifest
 -----------------
 
 The :mod:`sassutils` defines a concept named :dfn:`manifest`.
-Manifest is building settings of Sass/SCSS.  It specifies some paths
+Manifest is the build settings of Sass/SCSS.  It specifies some paths
 related to building Sass/SCSS:
 
 - The path of the directory which contains Sass/SCSS source files.
-- The path of the directory compiled CSS files will go.
-- The path, is exposed to HTTP (through WSGI), of the directory that
-  will contain compiled CSS files.
+- The path of the directory which the compiled CSS files will go.
+- The path, exposed to HTTP (through WSGI), of the directory that
+  will contain the compiled CSS files.
 
-Every package may have their own manifest.  Paths have to be relative
+Every package may have its own manifest.  Paths have to be relative
 to the path of the package.
 
-For example, in the project the package name is :mod:`myapp`.
-The path of the package is :file:`myapp/`.  The path of Sass/SCSS directory
-is :file:`static/sass/` (relative to the package directory).
-The path of CSS directory is :file:`static/css/`.
+For example, in the above project, the package name is :mod:`myapp`.
+The path of the package is :file:`myapp/`.  The path of the Sass/SCSS
+directory is :file:`static/sass/` (relative to the package directory).
+The path of the CSS directory is :file:`static/css/`.
 The exposed path is :file:`/static/css`.
 
-This settings can be represented as the following manifests::
+These settings can be represented as the following manifests::
 
     {
         'myapp': ('static/sass', 'static/css', '/static/css')
     }
 
-As you can see the above, the set of manifests are represented in dictionary.
-Keys are packages names.  Values are tuples of paths.
+As you can see the above, the set of manifests are represented in dictionary,
+in which the keys are packages names and the values are tuples of paths.
 
 
 Building Sass/SCSS for each request
@@ -72,21 +72,21 @@ Building Sass/SCSS for each request
       Flask.
 
    Flask --- :ref:`flask:app-dispatch`
-      The documentation which explains how Flask dispatch each
+      The documentation which explains how Flask dispatches each
       request internally.
 
    __ http://flask.pocoo.org/docs/quickstart/#hooking-in-wsgi-middlewares
 
-In development, to manually build Sass/SCSS files for each change is
-so tiring.  :class:`~sassutils.wsgi.SassMiddleware` makes the web
-application to automatically build Sass/SCSS files for each request.
+In development, manually building Sass/SCSS files for each change is
+a tedious task.  :class:`~sassutils.wsgi.SassMiddleware` makes the web
+application build Sass/SCSS files for each request automatically.
 It's a WSGI middleware, so it can be plugged into the web app written in
 Flask.
 
 :class:`~sassutils.wsgi.SassMiddleware` takes two required parameters:
 
 - The WSGI-compliant callable object.
-- The set of manifests represented as dictionary.
+- The set of manifests represented as a dictionary.
 
 So::
 
@@ -99,8 +99,8 @@ So::
         'myapp': ('static/sass', 'static/css', '/static/css')
     })
 
-And then, if you want to link a compiled CSS file, use :func:`~flask.url_for()`
-function:
+And then, if you want to link a compiled CSS file, use the
+:func:`~flask.url_for()` function:
 
 .. sourcecode:: html+jinja
 
@@ -125,10 +125,10 @@ Building Sass/SCSS for each deployment
    Flask --- :ref:`flask:distribute-deployment`
       How to deploy Flask application using setuptools_.
 
-If libsass has been installed in the :file:`site-packages` (for example,
-your virtualenv), :file:`setup.py` script also gets had new command
+If libsass is installed in the :file:`site-packages` (for example,
+your virtualenv), the :file:`setup.py` script also gets a new command
 provided by libsass: :class:`~sassutils.distutils.build_sass`.
-The command is aware of ``sass_manifests`` option of :file:`setup.py` and
+The command is aware of the ``sass_manifests`` option of :file:`setup.py` and
 builds all Sass/SCSS sources according to the manifests.
 
 Add these arguments to :file:`setup.py` script::
@@ -141,35 +141,35 @@ Add these arguments to :file:`setup.py` script::
         }
     )
 
-The ``setup_requires`` option makes sure that the libsass is installed
+The ``setup_requires`` option makes sure that libsass is installed
 in :file:`site-packages` (for example, your virtualenv) before
-:file:`setup.py` script.  That means: if you run :file:`setup.py` script
-and libsass isn't installed yet at the moment, it will automatically
+the :file:`setup.py` script.  That means if you run the :file:`setup.py`
+script and libsass isn't installed in advance, it will automatically
 install libsass first.
 
 The ``sass_manifests`` specifies the manifests for libsass.
 
 Now :program:`setup.py build_sass` will compile all Sass/SCSS files
-in the specified path and generates compiled CSS files into the specified
+in the specified path and generates compiled CSS files inside the specified
 path (according to the manifests).
 
-If you use it with ``sdist`` or ``bdist`` command, a packed archive also
-will contain compiled CSS files!
+If you use it with ``sdist`` or ``bdist`` commands, the packed archive will
+also contain the compiled CSS files!
 
 .. sourcecode:: console
 
    $ python setup.py build_sass sdist
 
-You can add aliases to make these commands to always run ``build_sass``
-command before.  Make :file:`setup.cfg` config:
+You can add aliases to make these commands always run the ``build_sass``
+command first.  Make :file:`setup.cfg` config:
 
 .. sourcecode:: ini
 
    [aliases]
    sdist = build_sass sdist
    bdist = build_sass bdist
 
-Now it automatically builds Sass/SCSS sources and include compiled CSS files
+Now it automatically builds Sass/SCSS sources and include the compiled CSS files
 to the package archive when you run :program:`setup.py sdist`.
 
 .. _setuptools: https://pypi.org/pypi/setuptools/
