Clarity (#38)

* Initial commit of compatibility notices page; added to index

* Replace references to Anaconda with Miniconda

* Add pipeline release description

* We no longer keep things like new. We update them.

* Use more targeted wording

* Replace or enhance references to anaconda with miniconda, or just conda depending on context

* Reword/improve config section

1 files changed, 3 insertions, 3 deletions

diff --git a/source/contributing.rst b/source/contributing.rst
index 4e861c3..e0930c0 100644
--- a/source/contributing.rst
+++ b/source/contributing.rst
@@ -71,7 +71,7 @@ If you have taken the liberty of looking around the astroconda-contrib directory
 
 .. note::
 
-    This is not an Anaconda packaging tutorial. For more information about creating recipes from scratch, please refer to the `conda-build documentation <http://conda.pydata.org/docs/build_tutorials/pkgs2.html>`_.
+    This is not an full Conda packaging tutorial. For more information about creating recipes from scratch, please refer to the `conda-build documentation <http://conda.pydata.org/docs/build_tutorials/pkgs2.html>`_.
 
     **Hint:** Investigate the contents of the recipes in astroconda-contrib. For most cases, copying an existing recipe and changing its values will suffice.
 
@@ -271,7 +271,7 @@ Python 3.5:
 
 That's probably a bit more involved than you thought. Let's break it down. We issue ``-c [URL]`` which instructs the build to utilize the AstroConda channel while checking for package dependencies (i.e. the recipe's ``requirements`` section). Secondly, we issue ``--skip-existing`` to prevent ``conda build`` from rebuilding dependencies discovered in the local astroconda-contrib directory. That is to say, if a package defined as a requirement exists remotely, it will then download and install it, rather than rebuild it from scratch. ``--python=`` is self-explanatory, and the final argument is the name of the recipe(s) we intend to build.
 
-At this point, if the build was successful, our Conda package (a bzipped tarball) called ``sympy-1.0-py35_0.tar.bz2`` is emitted to ``/path/to/anaconda/conda-bld/[os-arch]/``. This directory is a local Conda package repository.
+At this point, if the build was successful, our Conda package (a bzipped tarball) called ``sympy-1.0-py35_0.tar.bz2`` is emitted to ``/path/to/miniconda3/conda-bld/[os-arch]/``. This directory is a local Conda package repository.
 
 To install this new ``sympy`` package and interact with it ourselves you could run the following:
 
@@ -292,7 +292,7 @@ And checking it out for yourself:
 
     >>> import sympy
     >>> sympy.__file__
-    '/path/to/anaconda/envs/sympy_test/lib/python3.5/site-packages/sympy/__init__.py'
+    '/path/to/miniconda3/envs/sympy_test/lib/python3.5/site-packages/sympy/__init__.py'
 
 Now that you have verified the recipe is fully functional and are happy with the outcome, it's time to create a pull request against astroconda-contrib main repository.