Skip to content

Commit 3667c9b

Browse files
migueldvbmigueldvb
committed
Fix some typos in documentation
Conflicts: docs/coordinates/distances.rst
1 parent 0422faf commit 3667c9b

32 files changed

Lines changed: 87 additions & 86 deletions

‎docs/constants/index.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ need, you can simply do:
2424

2525
>>> from astropy import constants as const
2626

27-
and then subsequently use for example ``const.G``. Constants are fully-fleged
27+
and then subsequently use for example ``const.G``. Constants are fully-fledged
2828
`~astropy.units.quantity.Quantity` objects, so you can easily convert them to
2929
different units for example::
3030

‎docs/convolution/index.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ and are both used as::
5353

5454
:func:`~astropy.convolution.convolve.convolve` is implemented as a
5555
direct convolution algorithm, while
56-
:func:`~astropy.convolution.convolve.convolve_fft` uses a fast fourier
56+
:func:`~astropy.convolution.convolve.convolve_fft` uses a fast Fourier
5757
transform (FFT). Thus, the former is better for small kernels, while the latter
5858
is much more efficient for larger kernels.
5959

‎docs/convolution/using.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ and are both used as::
1515

1616
:func:`~astropy.convolution.convolve.convolve` is implemented as a
1717
direct convolution algorithm, while
18-
:func:`~astropy.convolution.convolve.convolve_fft` uses a fast fourier
18+
:func:`~astropy.convolution.convolve.convolve_fft` uses a fast Fourier
1919
transform (FFT). Thus, the former is better for small kernels, while the latter
2020
is much more efficient for larger kernels.
2121

‎docs/coordinates/angles.rst‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ examples of valid ways to create an |Angle|::
2222

2323
>>> Angle('10.2345d') # String with 'd' abbreviation for degrees
2424
>>> Angle(['10.2345d', '-20d']) # Array of strings
25-
>>> Angle('1:2:30.43 degrees') # Sexigesimal degrees
26-
>>> Angle('1 2 0 hours') # Sexigesimal hours
25+
>>> Angle('1:2:30.43 degrees') # Sexagesimal degrees
26+
>>> Angle('1 2 0 hours') # Sexagesimal hours
2727
>>> Angle(np.arange(1, 8), unit=u.deg) # Numpy array from 0..7 in degrees
2828
>>> Angle(u'1°2′3″') # Unicode degree, arcmin and arcsec symbols
2929
>>> Angle('1d2m3.4s') # Degree, arcmin, arcsec.
@@ -93,11 +93,11 @@ Angles will also behave correctly for appropriate arithmetic operations::
9393
Wrapping and bounds
9494
^^^^^^^^^^^^^^^^^^^^^
9595

96-
There are two utility methods that simplify working with angles that should have bounds. The
97-
`~astropy.coordinates.angles.Angle.wrap_at()` method allows taking an angle or angles and
98-
wrapping to be within a single 360 degree slice. The
99-
`~astropy.coordinates.angles.Angle.is_within_bounds()` method returns a boolean indicatng
100-
whether an angle or angles is within the specified bounds.
96+
There are two utility methods that simplify working with angles that should
97+
have bounds. The `~astropy.coordinates.angles.Angle.wrap_at()` method allows
98+
taking an angle or angles and wrapping to be within a single 360 degree slice.
99+
The `~astropy.coordinates.angles.Angle.is_within_bounds()` method returns a
100+
boolean indicating whether an angle or angles is within the specified bounds.
101101

102102

103103
Longitude and Latitude objects

‎docs/coordinates/designing.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,5 @@ to or from. This will register the transformation, allowing any other
1717
coordinate object to use this converter. You can also use the
1818
`~astropy.coordinates.transformations.static_transform_matrix` and
1919
`~astropy.coordinates.transformations.dynamic_transform_matrix` decorators to
20-
specify the transformation in terms of 3 x 3 cartesian coordinate transformation
20+
specify the transformation in terms of 3 x 3 Cartesian coordinate transformation
2121
matrices (typically rotations).

‎docs/coordinates/distances.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ automatically convert to a `Distance`::
2626
>>> ICRSCoordinates('00h42m44.3s +41d16m9s', distance=770 * u.kpc)
2727
<ICRSCoordinates RA=10.68458 deg, Dec=41.26917 deg, Distance=7.7e+02 kpc>
2828

29-
If a `distance` is present, the coordinate can be converted into cartesian
29+
If a `distance` is present, the coordinate can be converted into Cartesian
3030
coordinates using the `x`/`y`/`z` attributes (which are
3131
`~astropy.units.Quantity` objects)::
3232

@@ -56,7 +56,7 @@ unit sphere::
5656
systems, but for common celestial coordinate systems it is often
5757
the Earth center (or for precision work, the Earth/Moon barycenter).
5858

59-
The cartesian coordinates can also be accessed via the
59+
The Cartesian coordinates can also be accessed via the
6060
`~astropy.coordinates.distances.CartesianPoints` object, which has
6161
additional capabilities like arithmetic operations::
6262

‎docs/coordinates/index.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ available::
6060

6161
Distances from the origin (which is system-dependent, but often the
6262
Earth center) can also be assigned to a coordinate. This specifies a
63-
unique point in 3D space, which also allows conversion to cartesian
63+
unique point in 3D space, which also allows conversion to Cartesian
6464
coordinates::
6565

6666
>>> c = coord.ICRSCoordinates(ra=10.68458, dec=41.26917,

‎docs/coordinates/sgr-example.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This document describes in detail how to subclass and define a custom spherical
77
coordinate system, as mentioned in :doc:`designing` and the docstring for
88
`~astropy.coordinates.coordsystems.SphericalCoordinatesBase`. In this example,
99
we will define a coordinate system defined by the plane of orbit of the
10-
Sagitarrius Dwarf Galaxy (hereafter Sgr; as defined in Majewski et al. 2003).
10+
Sagittarius Dwarf Galaxy (hereafter Sgr; as defined in Majewski et al. 2003).
1111
The Sgr coordinate system is often referred to in terms of two angular
1212
coordinates, :math:`\Lambda,B`.
1313

‎docs/cosmology/index.rst‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Getting Started
2020

2121
There are many functions available to calculate cosmological quantities.
2222
They generally take a redshift as input. For example, the two cases
23-
below give you the value of the hubble constant at z=0 (i.e., `H0`), and
23+
below give you the value of the Hubble constant at z=0 (i.e., `H0`), and
2424
the number of transverse proper kpc corresponding to an arcminute at z=3:
2525

2626
>>> from astropy import cosmology
@@ -66,15 +66,15 @@ Using `cosmology`
6666

6767
Most of the functionality is enabled by the
6868
`~astropy.cosmology.core.FLRW` object. This represents a
69-
homogenous and isotropic cosmology (a cosmology characterized by the
69+
homogeneous and isotropic cosmology (a cosmology characterized by the
7070
Friedmann-Lemaitre-Robertson-Walker metric, named after the people who
7171
solved Einstein's field equation for this special case). However,
7272
you can't work with this class directly, as you must specify a
7373
dark energy model by using one of its subclasses instead,
7474
such as `~astropy.cosmology.core.FlatLambdaCDM`.
7575

7676
You can create a new `~astropy.cosmology.core.FlatLambdaCDM` object with
77-
arguments giving the hubble parameter and omega matter (both at z=0):
77+
arguments giving the Hubble parameter and omega matter (both at z=0):
7878

7979
>>> from astropy.cosmology import FlatLambdaCDM
8080
>>> cosmo = FlatLambdaCDM(H0=70, Om0=0.3)
@@ -250,7 +250,7 @@ Relativistic Species
250250
====================
251251
The cosmology classes include the contribution to the energy density
252252
from both photons and massless neutrinos. The two parameters
253-
controlling the proporties of these species are Tcmb0 (the temperature
253+
controlling the properties of these species are Tcmb0 (the temperature
254254
of the CMB at z=0) and Neff, the effective number of neutrino species.
255255
Both have standard default values (2.725 and 3.04, respectively; the
256256
reason that Neff is not 3 has to do with a small bump in the neutrino

‎docs/development/codeguide.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -521,7 +521,7 @@ you see::
521521
because both ``B.method()`` and ``C.method()`` call ``A.method()`` unaware of
522522
the fact that they're being called as part of a chain in a hierarchy. When
523523
``C.method()`` is called it is unaware that it's being called from a subclass
524-
that inherts from both ``B`` and ``C``, and that ``B.method()`` should be
524+
that inherits from both ``B`` and ``C``, and that ``B.method()`` should be
525525
called next. By calling :func:`super` the entire method resolution order for
526526
``D`` is precomputed, enabling each superclass to cooperatively determine which
527527
class should be handed control in the next :func:`super` call::

0 commit comments

Comments
 (0)