mirrors/xonsh
1
0
Fork 0
mirror of https://github.com/xonsh/xonsh.git synced 2025-03-04 00:14:41 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Fix some typos

Browse source
This commit is contained in:
Danny Sepler 2020-10-03 23:02:39 -04:00
parent 580b675f1a
commit b59b0ceed2
3 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CONTRIBUTING.rst
View file

@ -117,9 +117,9 @@ is open to interpretation.
* Test generators make more dots and the dots must flow!
You can easily check for style issues, including some outright bugs such
as mispelled variable names, using `flake8 <https://flake8.pycqa.org/>`_. If you're using Anaconda you'll
as misspelled variable names, using `flake8 <https://flake8.pycqa.org/>`_. If you're using Anaconda you'll
need to run "conda install flake8" once. You can easily run flake8 on
the edited files in your uncommited git change::
the edited files in your uncommitted git change::
$ git status -s | awk '/\.py$$/ { print $2 }' | xargs flake8

4
docs/advanced_events.rst
View file

@ -13,12 +13,12 @@ Why Unordered?
==============
Yes, handler call order is not guaranteed. Please don't file bugs about this.
This was chosen because the order of handler registration is dependant on load order, which is
This was chosen because the order of handler registration is dependent on load order, which is
stable in a release but not something generally reasoned about. In addition, xontribs mean that we
don't know what handlers could be registered. So even an "ordered" event system would be unable to
make guarantees about ordering because of the larger system.
Because of this, the event system is not ordered; this is a form of abstraction. Order-dependant
Because of this, the event system is not ordered; this is a form of abstraction. Order-dependent
semantics are not encouraged by the built-in methods.
So how do I handle results?

6
docs/tutorial.rst
View file

@ -1528,10 +1528,10 @@ or ``{BOLD_BLUE}``. Colors have the form shown below:
and ``BACKGROUND_#123456`` can both be used.
* ``bg#HEX`` or ``BG#HEX`` are shortcuts for setting a background hex color.
Thus you can set ``bg#0012ab`` or the uppercase version.
* ``BOLD_`` is a prefix modifier that increases the intesnity of the font.
* ``BOLD_`` is a prefix modifier that increases the intensity of the font.
It may be used with any foreground color.
For example, ``BOLD_RED`` and ``BOLD_#112233`` are OK!
* ``FAINT_`` is a prefix modifier that decreases the intesnity of the font.
* ``FAINT_`` is a prefix modifier that decreases the intensity of the font.
For example, ``FAINT_YELLOW``.
* ``ITALIC_`` is a prefix modifier that switches to an italic font.
For example, ``ITALIC_BLUE``.
@ -1547,7 +1547,7 @@ or ``{BOLD_BLUE}``. Colors have the form shown below:
widely supported. For example, ``CONCEAL_BLACK``.
* ``STRIKETHROUGH_`` is a prefix modifier which draws a line through the text.
For example, ``STRIKETHROUGH_RED``.
* ``BOLDOFF_`` is a prefix modifier for removing the intesnity of the font.
* ``BOLDOFF_`` is a prefix modifier for removing the intensity of the font.
It may be used with any foreground color.
For example, ``BOLDOFF_RED`` and ``BOLD_#112233`` are OK!
* ``FAINTOFF_`` is a prefix modifier for removing the faintness of the font.