Fix typos in comments and documentation (#750)

* Fix typos in comments and documentation
This commit is contained in:
hartmannathan
2020-04-08 08:45:35 -04:00
committed by GitHub
parent 9c7841aff1
commit bfc153ca27
54 changed files with 133 additions and 134 deletions
+13 -14
View File
@@ -167,7 +167,7 @@ http://nuttx.org/Documentation/NuttXConfigVariables.html.
Supported Boards
^^^^^^^^^^^^^^^^
boards/avr/atmeta/amber
boards/avr/atmega/amber
This is placeholder for the SoC Robotics Amber Web Server that is based
on the Atmel AVR ATMega128 MCU. There is not much there yet and what is
there is untested due to tool-related issues.
@@ -255,12 +255,11 @@ boards/arm/tiva/ekk-lm3s9b96
an EKK-LM3S9B96 which is a Cortex-M3.
boards/xtensa/esp32/esp-core
The ESP32 is a dual-core system from Expressif with two Harvard
architecture Xtensa LX6 CPUs. All embedded memory, external memory and
nd peripherals are located on the data bus and/or the instruction bus of
bus of these CPUs. With some minor exceptions, the address mapping of two
CPUs is symmetric, meaning they use the same addresses to access the same
memory.
The ESP32 is a dual-core system from Espressif with two Harvard architecture
Xtensa LX6 CPUs. All embedded memory, external memory and peripherals are
located on the data bus and/or the instruction bus of bus of these CPUs.
With some minor exceptions, the address mapping of two CPUs is symmetric,
meaning they use the same addresses to access the same memory.
boards/z80/ez80/ez80f0910200kitg
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200kitg
@@ -278,11 +277,11 @@ boards/arm/stm32/fire-stm32v2
the boards are supported but only version 2 has been tested.
boards/mips/pic32mz/flipnclick-pic32mz
Board support for the Mikroe Flip&Click PIC32MZ board. This board is an
Board support for the Mikroe Flip&Click PIC32MZ board. This board is a
chipKit Arduino-compatible board (but can also be used with the Mikroe
bootloader). It has with four Mikroe Click bus interfaces in addition to
standard Arduino connectors. This board features the Microchip
PIC32MZ2048EFH100 MCU running at 200 MHz (252Mhz capable).
PIC32MZ2048EFH100 MCU running at 200 MHz (252 MHz capable).
boards/arm/sam34/flipnclick-sam3x
Board support for the Mikroe Flip&Click STM32X board. This board is an
@@ -372,7 +371,7 @@ boards/arm/lpc17xx_40xx/lx_cpu
LPC1788) and Xilinx Spartan 6 XC6SLX9
boards/z80/ez80/makerlisp
This port use the MakerLips machine based on an eZ80F091 ez80Acclaim!
This port use the MakerLisp machine based on an eZ80F091 ez80Acclaim!
Microcontroller, and the Zilog ZDS-II Windows command line tools. The
development environment is Cygwin under Windows. A Windows native
development environment is available but has not been verified.
@@ -623,7 +622,7 @@ boards/arm/lpc17xx_40xx/pnev5180b
boards/x86/qemu/qemu-i486
Port of NuttX to QEMU in i486 mode. This port will also run on real i486
hardwared (Google the Bifferboard).
hardware (Google the Bifferboard).
boards/risc-v/nr5m100/nr5m100-nexys4
Port of NuttX to RISC-V platform on IQ-Analog NR5M100 RISC-V FPGA platform.
@@ -752,7 +751,7 @@ boards/arm/stm32/stm32f103-minimum
Generic STM32F103C8T6 Minimum ARM Development Board.
boards/arm/stm32/stm32f4discovery
STMicro STM32F4-Discovery board based on the STMIcro STM32F407VGT6 MCU.
STMicro STM32F4-Discovery board based on the STMicro STM32F407VGT6 MCU.
boards/arm/stm32/stm32f411e-disco
This is a minimal configuration that supports low-level test of the
@@ -771,7 +770,7 @@ boards/arm/stm32f7/stm32f746g-ws
boards/arm/stm32l4/stm32l476-mdk
Motorola Mods Development Board (MDK) features STM32L476ME MCU.
The STM32L476ME is a Cortex-M4 optimised for low-power operation
The STM32L476ME is a Cortex-M4 optimised for low-power operation
at up to 80MHz operation with 1024Kb Flash memory and 96+32Kb SRAM.
boards/arm/stm32f7/stm32f769i-disco
@@ -922,7 +921,7 @@ tools/configure.sh
See tools/README.txt for more information about these scripts.
And if your application directory is not in the standard loction (../apps
And if your application directory is not in the standard location (../apps
or ../apps-<version>), then you should also specify the location of the
application directory on the command line like: