diff options
| author | Howard Lovatt <howard.lovatt@gmail.com> | 2020-10-10 08:18:24 +1100 |
|---|---|---|
| committer | Damien George <damien@micropython.org> | 2020-10-20 17:21:30 +1100 |
| commit | cf6845b1cf4680bb2eade175aaab00428bedf8ba (patch) | |
| tree | 46c1fcc0d727ce271ec5b6d4d038ebd8f89fcbe8 /docs/library/machine.Signal.rst | |
| parent | 23f9439f441173dae961de4d2fe73986c166ff8f (diff) | |
docs/library/machine.Signal.rst: Correct typo: usecases to use cases.
Diffstat (limited to 'docs/library/machine.Signal.rst')
| -rw-r--r-- | docs/library/machine.Signal.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/library/machine.Signal.rst b/docs/library/machine.Signal.rst index 651c8c849..1e1fcb548 100644 --- a/docs/library/machine.Signal.rst +++ b/docs/library/machine.Signal.rst @@ -55,7 +55,7 @@ Following is the guide when Signal vs Pin should be used: * Use Pin: If you implement a higher-level protocol or bus to communicate with more complex devices. -The split between Pin and Signal come from the usecases above and the +The split between Pin and Signal come from the use cases above and the architecture of MicroPython: Pin offers the lowest overhead, which may be important when bit-banging protocols. But Signal adds additional flexibility on top of Pin, at the cost of minor overhead (much smaller |