improved conda_forge_yml.rst

Author: hitblunders

src/maintainer/conda_forge_yml.rst

@@ -1,7 +1,7 @@
 Configuring conda-forge.yml
 ***************************
 
-You can configure how conda-forge is setup and builds via the ``conda-forge.yml``
+You can configure how conda-forge is set up and built via the ``conda-forge.yml``
 file that is present in the root directory of a feedstock.
 
 Rerendering the feedstock after you modify this file is usually required and always a good idea (see :ref:`dev_update_rerender`).
@@ -204,7 +204,7 @@ circle
 --------
 The top-level ``circle`` key specifies configurations for the Circle
 CI service.  This is usually **read-only** and should not normally be manually
-modified.  Tools like conda-smithy may modify this, as need.  It has a single
+modified.  Tools like conda-smithy may modify this, as needed.  It has a single
 ``secure`` field which contains the binstar token.  For example:
 
 .. code-block:: yaml
@@ -393,7 +393,7 @@ remote_ci_setup
 ---------------
 This option can be used to override the default ``conda-forge-ci-setup`` package.
 Can be given with ``${url or channel_alias}::package_name``, defaults to conda-forge
-channel_alias if no prefix given.
+channel_alias if no prefix is given.
 
 .. code-block:: yaml
 
@@ -406,7 +406,7 @@ skip_render
 This option specifies a list of files which conda smithy will skip rendering.
 The possible values can be a subset of ``.gitignore``, ``.gitattributes``, ``README.md``, ``LICENSE.txt``.
 The default value is an empty list [ ], i.e. all these four files will be generated by conda smithy.
-For example, if you want to customize .gitignore and LICENSE.txt file by your own, you should have the following configuration.
+For example, if you want to customize .gitignore and LICENSE.txt files on your own, you should have the following configuration.
 
 .. code-block:: yaml
 
@@ -437,7 +437,7 @@ travis
 ------
 The top-level ``travis`` key specifies configurations for the Travis
 CI service.  This is usually **read-only** and should not normally be manually
-modified.  Tools like conda-smithy may modify this, as need.  It has a single
+modified.  Tools like conda-smithy may modify this, as needed.  It has a single
 ``secure`` field which contains the binstar token.  For example:
 
 .. code-block:: yaml