Converting AstroPy to Astropy

docs/development/developer_faq.rst

@@ -3,5 +3,5 @@ Developer FAQ
 *************
 
 
-Constants in TARDIS are all taken from AstroPy. The module tardis.constants import all constants currently
+Constants in TARDIS are all taken from Astropy. The module tardis.constants import all constants currently
 from astropy.constants.astropy13constants.

docs/development/git_workflow.rst

@@ -54,7 +54,7 @@ the `Generating SSH keys
 Create your own fork of a repository
 ------------------------------------
 
-The following example shows how to fork the core ``AstroPy`` repository, but
+The following example shows how to fork the core ``Astropy`` repository, but
 the same applies to other packages:
 
 #. Log into your GitHub_ account.
@@ -279,7 +279,7 @@ In more detail
 #. Make some changes
 
 #. Once you are a bit further along, test your changes do not lead to
-   regressions, and add new tests (see the AstroPy :ref:`testing-guidelines` we follow).::
+   regressions, and add new tests (see the Astropy :ref:`testing-guidelines` we follow).::
 
      python setup.py test
 
@@ -289,7 +289,7 @@ In more detail
      python setup.py build_sphinx
 
    The last line should just state ``build succeeded``, and should not mention
-   any warnings.  (For more details, see the AstroPy
+   any warnings.  (For more details, see the Astropy
    :ref:`documentation-guidelines` we follow.)
 
 #. See which files have changed with ``git status`` (see `git status`_).
@@ -442,7 +442,7 @@ remote called ``origin``, you use this command to force-push::
 
 Note that this will overwrite the branch on GitHub, i.e. this is one of the few
 ways you can actually lose commits with git. Also note that it is never allowed
-to force push to the main AstroPy repo (typically called ``upstream``), because
+to force push to the main Astropy repo (typically called ``upstream``), because
 this would re-write commit history and thus cause problems for all others.
 
 .. _recovering-from-mess-up:

docs/development/index.rst

@@ -4,9 +4,9 @@ Developer Workflow
 
 If you want to contribute to the development of TARDIS, please read through
 this page and follow the guidelines outlined here.  Many of the Development
-workflow is taken from `AstroPy <http://docs.astropy.org
+workflow is taken from `Astropy <http://docs.astropy.org
 /en/stable/development/workflow/development_workflow.html>`_, and credit belongs
-to the AstroPy team for designing it.
+to the Astropy team for designing it.
 
 .. toctree::
     :maxdepth: 2

docs/development/release_workflow.rst

@@ -26,5 +26,5 @@ Doing the actual release
 ========================
 
 This is best done in a clean environment (so a fresh checkout from the master).
-We again use the AstroPy instructions:
+We again use the Astropy instructions:
 `<http://astropy.readthedocs.org/en/latest/development/releasing.html>`_

docs/installation.rst

@@ -27,8 +27,8 @@ Requirements
 
 You can see a list of all the requirements of TARDIS in the `environment definition file <https://raw.githubusercontent.com/tardis-sn/tardis/master/tardis_env3.yml>`_.
 
-TARDIS is using AstroPy's excellent installation helpers and thus uses similar
-instructions to AstroPy.
+TARDIS is using Astropy's excellent installation helpers and thus uses similar
+instructions to Astropy.
 
 .. _anaconda_inst_label:
 

docs/physics/physical_quantities.rst

@@ -42,7 +42,7 @@ Examples of finding physical quantities
 
 For example, two of our important quantities are the parameters of the
 radiation field model, :math:`T_{\rm rad}` and :math:`W`. These exist
-as AstroPy `Quantities <http://astropy.readthedocs.org/en/v0.2.1/_generated/astropy.units.quantity.Quantity.html>`_. Thus
+as Astropy `Quantities <http://astropy.readthedocs.org/en/v0.2.1/_generated/astropy.units.quantity.Quantity.html>`_. Thus
 
 .. code-block:: python
 
@@ -124,11 +124,11 @@ of Si II:
 
 .. note::
 
-    If you prefer to work in SI units, all the AstroPy Quantities may
+    If you prefer to work in SI units, all the Astropy Quantities may
     instead be accessed with "xxx.si".
 
 .. note::
 
-    Information that is not stored as AstroPy Quantities (e.g. the ion
+    Information that is not stored as Astropy Quantities (e.g. the ion
     an level populations used in the example above) are usually stored
     in cgs units (i.e. :math:`{\rm cm}^{-3}` for the populations).

docs/team.rst

@@ -4,7 +4,7 @@
 Team
 ****
 
-TARDIS is developed by a multidisciplinary team. We adhere to the AstroPy
+TARDIS is developed by a multidisciplinary team. We adhere to the Astropy
 `code of conduct <https://www.astropy.org/code_of_conduct.html>`_.
 
 Principle Investigator