Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 705980b

Browse files
committed
Some comment typo fixes
Found via `codespell`
1 parent b0994fd commit 705980b

21 files changed

Lines changed: 32 additions & 32 deletions

File tree

doc/api/api_changes.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ API Changes in 2.1.2
1919
`matplotlib.Figure.legend` used to check if a line had the
2020
same label as an existing legend entry. If it also had the same line color
2121
or marker color legend didn't add a new entry for that line. However, the
22-
list of conditions was incomplete, didn't handle RGB tupples,
22+
list of conditions was incomplete, didn't handle RGB tuples,
2323
didn't handle linewidths or linestyles etc.
2424

2525
This logic did not exist in `Axes.legend`. It was included (erroneously)
@@ -781,7 +781,7 @@ Default Behavior Changes
781781
Changed default ``autorange`` behavior in boxplots
782782
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
783783

784-
Prior to v1.5.2, the whiskers of boxplots would extend to the mininum
784+
Prior to v1.5.2, the whiskers of boxplots would extend to the minimum
785785
and maximum values if the quartiles were all equal (i.e., Q1 = median
786786
= Q3). This behavior has been disabled by default to restore consistency
787787
with other plotting packages.
@@ -3452,7 +3452,7 @@ Changes for 0.40
34523452
- Patches
34533453
* Initialized with a transx, transy which are Transform instances
34543454

3455-
- FigureBase attributes dpi is a DPI intance rather than scalar and
3455+
- FigureBase attributes dpi is a DPI instance rather than scalar and
34563456
new attribute bbox is a Bound2D in display coords, and I got rid
34573457
of the left, width, height, etc... attributes. These are now
34583458
accessible as, for example, bbox.x.min is left, bbox.x.interval()

doc/devel/MEP/MEP14.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ can be obtained from the `TextSpan` instance::
324324

325325
def get_path(self):
326326
"""
327-
Returns a single Path object of the entire layed out text.
327+
Returns a single Path object of the entire laid out text.
328328

329329
[Not strictly necessary, but might be useful for textpath
330330
functionality]

doc/devel/MEP/MEP19.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ has a number of shortcomings:
3434
- It often fails for inexplicable reasons.
3535

3636
- build or test products can only be saved from build off of branches
37-
on the main repo, not pull requsts, so it is often difficult to
37+
on the main repo, not pull requests, so it is often difficult to
3838
"post mortem" analyse what went wrong. This is particularly
3939
frustrating when the failure can not be subsequently reproduced
4040
locally.
@@ -114,7 +114,7 @@ This section outlines the requirements that we would like to have.
114114
(This would not replace the static documentation for stable
115115
releases as a default).
116116

117-
#. The test systems should be managable by multiple developers, so
117+
#. The test systems should be manageable by multiple developers, so
118118
that no single person becomes a bottleneck. (Travis-CI's design
119119
does this well -- storing build configuration in the git
120120
repository, rather than elsewhere, is a very good design.)

doc/devel/MEP/MEP22.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ the shortcuts out of the `Canvas`. This actions and shortcuts will be
5858
in the form of `Tools`.
5959

6060
A new class `Navigation` will be the bridge between the events from
61-
the `Canvas` and `Toolbar` and redirect them to the appropiate `Tool`.
61+
the `Canvas` and `Toolbar` and redirect them to the appropriate `Tool`.
6262

6363
At the end the user interaction will be divided into three classes:
6464

@@ -170,7 +170,7 @@ ToolbarBase
170170
Methods for **Backend implementation**
171171
* add_toolitem(self, name, group, position, image, description,
172172
toggle): Add a toolitem to the toolbar. This method is a callback
173-
from `tool_added_event` (emited by navigation)
173+
from `tool_added_event` (emitted by navigation)
174174
* set_message(self, s): Display a message on toolbar or in status bar
175175
* toggle_toolitem(self, name): Toggle the toolitem without firing
176176
event.

doc/devel/MEP/MEP23.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,8 @@ implemented the **MultiFigure** magic yet.
109109
Alternatives
110110
============
111111

112-
Insted of modifing the `FigureManagerBase` it could be possible to add
112+
Insted of modifying the `FigureManagerBase` it could be possible to add
113113
a parallel class, that handles the cases where
114114
`rcParams['backend.multifigure'] = True`. This will warranty that
115115
there won't be any problems with custom made backends, but also makes
116-
bigger the code, and more things to mantain.
116+
bigger the code, and more things to maintain.

doc/devel/MEP/MEP26.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ on the artist object, which is quite laborious, especially if no
3939
reference to the artist(s) has been stored. The new style sheets
4040
introduced in 1.4 allow styling before a plot is created, but do not
4141
offer any means to dynamically update plots or distinguish between
42-
artists of the same type (i.e. to specifiy the `line color` and `line
42+
artists of the same type (i.e. to specify the `line color` and `line
4343
style` separately for differing `Line2D` objects).
4444

4545
The initial development should concentrate on allowing styling of

doc/devel/MEP/MEP28.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ Variations on the theme
246246

247247
This MEP can be divided into a few loosely coupled components:
248248

249-
#. Allowing pre- and post-computation tranformation function in ``cbook.boxplot_stats``
249+
#. Allowing pre- and post-computation transformation function in ``cbook.boxplot_stats``
250250
#. Exposing that transformation in the ``Axes.boxplot`` API
251251
#. Removing redundant statistical options in ``Axes.boxplot``
252252
#. Shifting all styling parameter processing from ``Axes.boxplot`` to ``Axes.bxp``.
@@ -334,7 +334,7 @@ Users could also pass their own function to compute the stats:
334334
ax1.boxplot(data, statfxn=my_box_stats, bootstrap_method='BCA',
335335
whisker_method='dynamic')
336336
337-
From the examples above, Option Two seems to have only marginal benifit,
337+
From the examples above, Option Two seems to have only marginal benefit,
338338
but in the context of downstream libraries like seaborn, its advantage
339339
is more apparent as the following would be possible without any patches
340340
to seaborn:

doc/devel/MEP/MEP29.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Problems
5858
--------
5959

6060
* One serious problem is how to deal with text having both latex and
61-
html-like tags. For example, consider the follwing::
61+
html-like tags. For example, consider the following::
6262

6363
$<b>Bold$</b>
6464

doc/devel/contributing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ development environment, using the something like `virtual environments in pytho
6767
`conda environment <http://conda.pydata.org/docs/using/envs.html>`_.
6868

6969
If you choose to use an already existing environment, and not a clean virtual or
70-
conda environment, uninstall the current version of Matplotlib in that enviroment
70+
conda environment, uninstall the current version of Matplotlib in that environment
7171
using the same method used to install it.
7272

7373
If working on Matplotlib documentation only, the above steps are *not* absolutely

doc/mpl_toolkits/mplot3d/faq.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ How is mplot3d different from MayaVi?
88
=====================================
99
`MayaVi2 <http://code.enthought.com/projects/mayavi/documentation.php>`_
1010
is a very powerful and featureful 3D graphing library. For advanced
11-
3D scenes and excellent rendering capabilities, it is highly recomended to
11+
3D scenes and excellent rendering capabilities, it is highly recommended to
1212
use MayaVi2.
1313

1414
mplot3d was intended to allow users to create simple 3D graphs with the same
@@ -24,7 +24,7 @@ is that -- from some viewing angles -- a 3D object would appear in front
2424
of another object, even though it is physically behind it. This can result in
2525
plots that do not look "physically correct."
2626

27-
Unfortunately, while some work is being done to reduce the occurance of this
27+
Unfortunately, while some work is being done to reduce the occurrence of this
2828
artifact, it is currently an intractable problem, and can not be fully solved
2929
until matplotlib supports 3D graphics rendering at its core.
3030

0 commit comments

Comments
 (0)