diff options
author | Mike Causer <mcauser@gmail.com> | 2021-04-30 16:53:36 +1000 |
---|---|---|
committer | Damien George <damien@micropython.org> | 2021-05-04 22:58:00 +1000 |
commit | 31ac410a4fbf18b38b6f4557045959140026680e (patch) | |
tree | af61c304a48aa064205c185e5043e80ac5543f45 /docs/library/machine.TimerWiPy.rst | |
parent | 6e776a671061130d86a300fcd72173d9b93f521a (diff) |
docs: Fix some spelling mistakes.
Diffstat (limited to 'docs/library/machine.TimerWiPy.rst')
-rw-r--r-- | docs/library/machine.TimerWiPy.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/library/machine.TimerWiPy.rst b/docs/library/machine.TimerWiPy.rst index f5b748c62..39afc23bc 100644 --- a/docs/library/machine.TimerWiPy.rst +++ b/docs/library/machine.TimerWiPy.rst @@ -16,7 +16,7 @@ the most flexible and heterogeneous kind of hardware in MCUs and SoCs, differently greatly from a model to a model. MicroPython's Timer class defines a baseline operation of executing a callback with a given period (or once after some delay), and allow specific boards to define more -non-standard behavior (which thus won't be portable to other boards). +non-standard behaviour (which thus won't be portable to other boards). See discussion of :ref:`important constraints <machine_callbacks>` on Timer callbacks. @@ -115,7 +115,7 @@ Methods .. method:: timerchannel.irq(*, trigger, priority=1, handler=None) - The behavior of this callback is heavily dependent on the operating + The behaviour of this callback is heavily dependent on the operating mode of the timer channel: - If mode is ``TimerWiPy.PERIODIC`` the callback is executed periodically |