8000 matplotlib > Matplotlib in devel docs · matplotlib/matplotlib@f88ae69 · GitHub
[go: up one dir, main page]
Skip to content

Commit f88ae69

Browse files
dstansbydstansby
committed
matplotlib > Matplotlib in devel docs
1 parent e8b40f9 commit f88ae69

File tree

5 files changed

+13
-13
lines changed

5 files changed

+13
-13
lines changed

‎doc/devel/add_new_projection.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ functions, e.g.::
2525
plot(x, y, projection="custom")
2626

2727
This document is intended for developers and advanced users who need
28-
to create new scales and projections for matplotlib. The necessary
28+
to create new scales and projections for Matplotlib. The necessary
2929
code for scales and projections can be included anywhere: directly
30-
within a plot script, in third-party code, or in the matplotlib source
30+
within a plot script, in third-party code, or in the Matplotlib source
3131
tree itself.
3232

3333
.. _creating-new-scale:
@@ -57,7 +57,7 @@ elements:
5757
- Formatters (major and minor) that specify how the tick labels
5858
should be drawn.
5959

60-
Once the class is defined, it must be registered with matplotlib so
60+
Once the class is defined, it must be registered with Matplotlib so
6161
that the user can select it.
6262

6363
A full-fledged and heavily annotated example is in
@@ -81,7 +81,7 @@ elements:
8181

8282
- Transformations for the gridlines, ticks and ticklabels. Custom
8383
projections will often need to place these elements in special
84-
locations, and matplotlib has a facility to help with doing so.
84+
locations, and Matplotlib has a facility to help with doing so.
8585

8686
- Setting up default values (overriding :meth:`~matplotlib.axes.Axes.cla`),
8787
since the defaults for a rectilinear axes may not be appropriate.

‎doc/devel/documenting_mpl.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -807,7 +807,7 @@ which was used to setup the github account but can be used for other
807807
purposes, like hosting Google docs or Youtube videos. You can embed a
808808
Matplotlib animation in the docs by first saving the animation as a
809809
movie using :meth:`matplotlib.animation.Animation.save`, and then
810-
uploading to `matplotlib's Youtube
810+
uploading to `Matplotlib's Youtube
811811
channel <https://www.youtube.com/user/matplotlib>`_ and inserting the
812812
embedding string youtube provides like:
813813

‎doc/devel/license.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ distributing L/GPL code through an separate channel, possibly a
1414
toolkit. If you include code, make sure you include a copy of that
1515
code's license in the license directory if the code's license requires
1616
you to distribute the license with it. Non-BSD compatible licenses
17-
are acceptable in matplotlib toolkits (e.g., basemap), but make sure you
17+
are acceptable in Matplotlib toolkits (e.g., basemap), but make sure you
1818
clearly state the licenses you are using.
1919

2020
Why BSD compatible?
@@ -50,8 +50,8 @@ Famous projects released under a BSD-style license in the permissive
5050
sense of the last paragraph are the BSD operating system, python and
5151
TeX.
5252

53-
There are several reasons why early matplotlib developers selected a
54-
BSD compatible license. matplotlib is a python extension, and we
53+
There are several reasons why early Matplotlib developers selected a
54+
BSD compatible license. Matplotlib is a python extension, and we
5555
choose a license that was based on the python license (BSD
5656
compatible). Also, we wanted to attract as many users and developers
5757
as possible, and many software companies will not use GPL code in
@@ -60,9 +60,9 @@ to open source development, such as `enthought
6060
<https://www.enthought.com>`_, out of legitimate concern that use of the
6161
GPL will "infect" their code base by its viral nature. In effect, they
6262
want to retain the right to release some proprietary code. Companies
63-
and institutions who use matplotlib often make significant
63+
and institutions who use Matplotlib often make significant
6464
contributions, because they have the resources to get a job done, even
65-
a boring one. Two of the matplotlib backends (FLTK and WX) were
65+
a boring one. Two of the Matplotlib backends (FLTK and WX) were
6666
contributed by private companies. The final reason behind the
6767
licensing choice is compatibility with the other python extensions for
6868
scientific computing: ipython, numpy, scipy, the enthought tool suite

‎doc/devel/release_guide.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@
77
===============
88

99

10-
.. admonition:: This document is only relevant for matplotlib release managers.
10+
.. admonition:: This document is only relevant for Matplotlib release managers.
1111

12-
A guide for developers who are doing a matplotlib release.
12+
A guide for developers who are doing a Matplotlib release.
1313

1414

1515
.. note::

‎doc/devel/testing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ sees these new commits. It looks for a YAML file called
209209
``.travis.yml`` in the root of the repository to see how to test the
210210
project.
211211

212-
Travis CI is already enabled for the `main matplotlib GitHub
212+
Travis CI is already enabled for the `main Matplotlib GitHub
213213
repository <https://github.com/matplotlib/matplotlib/>`_ -- for
214214
example, see `its Travis page
215215
<https://travis-ci.org/matplotlib/matplotlib>`_.

0 commit comments

Comments
 (0)
0