@@ -141,7 +141,7 @@ statement will ensure hardware isn't enabled longer than needed.
141
141
Verify your device
142
142
--------------------------------------------------------------------------------
143
143
144
- Whenever possible, make sure device you are talking to is the device you expect.
144
+ Whenever possible, make sure the device you are talking to is the device you expect.
145
145
If not, raise a RuntimeError. Beware that I2C addresses can be identical on
146
146
different devices so read registers you know to make sure they match your
147
147
expectation. Validating this upfront will help catch mistakes.
@@ -202,7 +202,7 @@ interchangeably with the CPython name. This is confusing. Instead, think up a
202
202
new name that is related to the extra functionality you are adding.
203
203
204
204
For example, storage mounting and unmounting related functions were moved from
205
- ``uos `` into a new `storage ` module. Terminal related functions were moved into
205
+ ``uos `` into a new `storage ` module. Terminal- related functions were moved into
206
206
`multiterminal `. These names better match their functionality and do not
207
207
conflict with CPython names. Make sure to check that you don't conflict with
208
208
CPython libraries too. That way we can port the API to CPython in the future.
@@ -213,7 +213,7 @@ Example
213
213
When adding extra functionality to CircuitPython to mimic what a normal
214
214
operating system would do, either copy an existing CPython API (for example file
215
215
writing) or create a separate module to achieve what you want. For example,
216
- mounting and unmount drives is not a part of CPython so it should be done in a
216
+ mounting and unmounting drives is not a part of CPython so it should be done in a
217
217
module, such as a new ``storage `` module, that is only available in CircuitPython.
218
218
That way when someone moves the code to CPython they know what parts need to be
219
219
adapted.
0 commit comments