summaryrefslogtreecommitdiffstatshomepage
path: root/docs/wipy
diff options
context:
space:
mode:
Diffstat (limited to 'docs/wipy')
-rw-r--r--docs/wipy/quickref.rst4
-rw-r--r--docs/wipy/tutorial/reset.rst6
-rw-r--r--docs/wipy/tutorial/timer.rst2
-rw-r--r--docs/wipy/tutorial/wlan.rst6
4 files changed, 9 insertions, 9 deletions
diff --git a/docs/wipy/quickref.rst b/docs/wipy/quickref.rst
index f9ea3d501e..4c3b969bd1 100644
--- a/docs/wipy/quickref.rst
+++ b/docs/wipy/quickref.rst
@@ -154,7 +154,7 @@ See :ref:`machine.RTC <machine.RTC>` ::
pass
# do some non blocking operations
# warning printing on an irq via telnet is not
- # possible, only via UART
+ # possible, only via UART
# create a RTC alarm that expires after 5 seconds
rtc.alarm(time=5000, repeat=False)
@@ -179,7 +179,7 @@ See :ref:`machine.SD <machine.SD>`. ::
sd = SD()
os.mount(sd, '/sd')
-WLAN (WiFi)
+WLAN (WiFi)
-----------
See :ref:`network.WLAN <network.WLAN>` and :mod:`machine`. ::
diff --git a/docs/wipy/tutorial/reset.rst b/docs/wipy/tutorial/reset.rst
index ece28498b8..1715d3e297 100644
--- a/docs/wipy/tutorial/reset.rst
+++ b/docs/wipy/tutorial/reset.rst
@@ -1,10 +1,10 @@
Reset and boot modes
====================
-There are soft resets and hard resets.
+There are soft resets and hard resets.
- - A soft reset simply clears the state of the MicroPython virtual machine,
- but leaves hardware peripherals unaffected. To do a soft reset, simply press
+ - A soft reset simply clears the state of the MicroPython virtual machine,
+ but leaves hardware peripherals unaffected. To do a soft reset, simply press
**Ctrl+D** on the REPL, or within a script do::
import sys
diff --git a/docs/wipy/tutorial/timer.rst b/docs/wipy/tutorial/timer.rst
index c87ac44959..7cd7d0f134 100644
--- a/docs/wipy/tutorial/timer.rst
+++ b/docs/wipy/tutorial/timer.rst
@@ -5,7 +5,7 @@ Timers can be used for a great variety of tasks, calling a function periodically
counting events, and generating a PWM signal are among the most common use cases.
Each timer consists of two 16-bit channels and this channels can be tied together to
form one 32-bit timer. The operating mode needs to be configured per timer, but then
-the period (or the frequency) can be independently configured on each channel.
+the period (or the frequency) can be independently configured on each channel.
By using the callback method, the timer event can call a Python function.
Example usage to toggle an LED at a fixed frequency::
diff --git a/docs/wipy/tutorial/wlan.rst b/docs/wipy/tutorial/wlan.rst
index 434367cd93..bdfd3e0a54 100644
--- a/docs/wipy/tutorial/wlan.rst
+++ b/docs/wipy/tutorial/wlan.rst
@@ -13,9 +13,9 @@ You can check the current mode (which is always ``WLAN.AP`` after power up)::
>>> wlan.mode()
-.. warning::
- When you change the WLAN mode following the instructions below, your WLAN
- connection to the WiPy will be broken. This means you will not be able
+.. warning::
+ When you change the WLAN mode following the instructions below, your WLAN
+ connection to the WiPy will be broken. This means you will not be able
to run these commands interactively over the WLAN.
There are two ways around this::