summaryrefslogtreecommitdiff
path: root/docs/design_guide.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/design_guide.rst')
-rw-r--r--docs/design_guide.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/design_guide.rst b/docs/design_guide.rst
index 1c0f5dbbd..1a4a08a52 100644
--- a/docs/design_guide.rst
+++ b/docs/design_guide.rst
@@ -305,10 +305,11 @@ For example, if you are writing a driver for an I2C device, then take in an I2C
object instead of the pins themselves. This allows the calling code to provide
any object with the appropriate methods such as an I2C expansion board.
-Another example is to expect a `DigitalInOut` for a pin to toggle instead of a
-`microcontroller.Pin` from `board`. Taking in the `~microcontroller.Pin` object
-alone would limit the driver to pins on the actual microcontroller instead of pins
-provided by another driver such as an IO expander.
+Another example is to expect a :py:class:`~digitalio.DigitalInOut` for a pin to
+toggle instead of a :py:class:`~microcontroller.Pin` from `board`. Taking in the
+:py:class:`~microcontroller.Pin` object alone would limit the driver to pins on
+the actual microcontroller instead of pins provided by another driver such as an
+IO expander.
Lots of small modules
--------------------------------------------------------------------------------