Merge pull request #1407 from prachi237/updates

minor edits in Rerendering feedstocks

Author: viniciusdc

src/maintainer/updating_pkgs.rst

@@ -103,32 +103,32 @@ Here we assume that you would like to update the feedstock ``<feedstock>``. Feed
 Updating recipes
 ================
 
-Please follow the following guidelines when updating recipes.
+Please follow the following guidelines while updating recipes:
 
-1. Always use a fork of the feedstock when updating the recipe.
+1. Always use a fork of the feedstock while updating the recipe.
 2. When a package's version is not changed, but other metadata or parts of the recipe are changed, increase the build number by ``1``.
-3. When shipping a new version of your package, reset the build number to ``0``.
+3. While shipping a new version of your package, reset the build number to ``0``.
 
 
 .. _dev_update_rerender:
 
 Rerendering feedstocks
 ======================
 
-Rerendering is conda-forge's way to update the files common to all feedstocks (e.g. README, :term:`CI` configuration, pinned dependencies)
+Rerendering is conda-forge's way to update the files common to all feedstocks (e.g. README, :term:`CI` configuration, pinned dependencies).
 
 Rerendering can be done in two ways:
 
- #. Using the webservice to run conda-smithy on the cloud by adding the comment ``@conda-forge-admin please rerender`` (see :ref:`dev_admservice`).
+ #. Using the webservice to run conda-smithy on the cloud by adding the comment ``@conda-forge-admin please rerender`` (See :ref:`dev_admservice`).
 
- #. Run conda-smithy locally on your machine (see :ref:`dev_rerender_local`).
+ #. Run conda-smithy locally on your machine (See :ref:`dev_rerender_local`).
 
 .. _dev_rerender_local:
 
 Rerendering with conda-smithy locally
 -------------------------------------
 
-The first step is to install ``conda-smithy`` in your root environment
+The first step is to install ``conda-smithy`` in your root environment.
 
 .. code-block:: shell
 
@@ -148,13 +148,13 @@ To do this drop ``-c auto`` from the command.
 When to rerender
 ----------------
 
-We need to re-render when there are changes to the following parts of the feedstock:
+We need to re-render when there are changes in the following parts of the feedstock:
 
-- the platform configuration (``skip`` sections);
-- the ``yum_requirements.txt``;
-- updates in the build matrix due to new versions of Python, NumPy, PERL, R, etc.
-- updates in conda-forge pinning that affect the feedstock
-- build issues that a feedstock configuration update will fix (follow us on `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ to know about those);
+- Platform configuration (``skip`` sections).
+- ``yum_requirements.txt`` or ``conda-forge.yml``.
+- Updates in the build matrix due to new versions of Python, NumPy, PERL, R, etc.
+- Updates in conda-forge pinning that affect the feedstock.
+- Build issues that a feedstock configuration update will fix (follow us on `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ to know about those).
 
 
 Testing changes locally