GitHub/nodemcu-firmware
1
0
Fork 0
mirror of https://github.com/nodemcu/nodemcu-firmware.git synced 2025-02-06 21:18:25 +08:00
Code Issues Projects Releases Wiki Activity

Minor typo and wording fixes (#2991)

Browse Source
This commit is contained in:
M.K 2020-01-01 23:31:04 +01:00 committed by Marcel Stör
parent 6926c66b16
commit 27e127e7ea
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
app/include/user_config.h
View File

@ -59,7 +59,7 @@
// NodeMCU supports two file systems: SPIFFS and FATFS, the first is available // NodeMCU supports two file systems: SPIFFS and FATFS, the first is available
// on all ESP8266 modules. The latter requires extra H/W so is less common. // on all ESP8266 modules. The latter requires extra H/W so it is less common.
// If you use SPIFFS then there are a number of options which impact the // If you use SPIFFS then there are a number of options which impact the
// RAM overhead and performance of the file system. // RAM overhead and performance of the file system.
@ -101,8 +101,8 @@
// GPIO_INTERRUPT_ENABLE needs to be defined if your application uses the // GPIO_INTERRUPT_ENABLE needs to be defined if your application uses the
// gpio.trig() or related GPIO interrupt service routine code. Likewise the // gpio.trig() or related GPIO interrupt service routine code. Likewise the
// GPIO interrupt hook is requited for a few modules such as rotary. If you // GPIO interrupt hook is required for a few modules such as rotary. If you
// don't require this functionality, then commenting out these options out // don't require this functionality, then commenting out these options
// will remove any associated runtime overhead. // will remove any associated runtime overhead.
#define GPIO_INTERRUPT_ENABLE #define GPIO_INTERRUPT_ENABLE
@ -170,7 +170,7 @@
#define I2C_MASTER_OLD_VERSION #define I2C_MASTER_OLD_VERSION
// The following sections are only relevent for those developers who are // The following sections are only relevant for those developers who are
// developing modules or core Lua changes and configure how extra diagnostics // developing modules or core Lua changes and configure how extra diagnostics
// are enabled in the firmware. These should only be configured if you are // are enabled in the firmware. These should only be configured if you are
// building your own custom firmware and have full access to the firmware // building your own custom firmware and have full access to the firmware