summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorPatrick O'Leary <patrick.oleary@gmail.com>2017-07-02 20:02:19 -0500
committerGitHub <noreply@github.com>2017-07-02 20:02:19 -0500
commit45b127e7ac95308b51364b22f174c8b15d1f8e89 (patch)
tree4eba268ddbf5252c20a97d2a354b41f99cb788fd
parentffb13cc63366a4356a3a26df8e4b27632fd71f76 (diff)
downloadmicropython-45b127e7ac95308b51364b22f174c8b15d1f8e89.tar.gz
micropython-45b127e7ac95308b51364b22f174c8b15d1f8e89.zip
docs/esp8266/general.rst: Fix name of NTP module.
The simple NTP client module is named "ntptime.py".
-rw-r--r--docs/esp8266/general.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/esp8266/general.rst b/docs/esp8266/general.rst
index 47df80d7ba..6d186fcd2f 100644
--- a/docs/esp8266/general.rst
+++ b/docs/esp8266/general.rst
@@ -116,7 +116,7 @@ Real-time clock
RTC in ESP8266 has very bad accuracy, drift may be seconds per minute. As
a workaround, to measure short enough intervals you can use
``utime.time()``, etc. functions, and for wall clock time, synchronize from
-the net using included ``ntpdate.py`` module.
+the net using included ``ntptime.py`` module.
Due to limitations of the ESP8266 chip the internal real-time clock (RTC)
will overflow every 7:45h. If a long-term working RTC time is required then