Skip to content

Commit 882702e

Browse files
dbkindernashif
authored andcommitted
doc: fix misspellings in docs
Fix misspelling in boards, samples, and doc missed during regular reviews. Signed-off-by: David B. Kinder <[email protected]>
1 parent cda6145 commit 882702e

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

boards/arm/mec2016evb_assy6797/doc/index.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Microchip to provide the schematic for this board.
7474
System Clock
7575
============
7676

77-
The MEC1701 MCU is configured to use the 48Mhz internal oscilator with the
77+
The MEC1701 MCU is configured to use the 48Mhz internal oscillator with the
7878
on-chip PLL to generate a resulting EC clock rate of 12 MHz. See Processor clock
7979
control register (chapter 4 in user manual)
8080

@@ -87,7 +87,7 @@ Jumper settings
8787
***************
8888

8989
Please follow the jumper settings below to properly demo this
90-
board. Advanced users may deviate from this recomendation.
90+
board. Advanced users may deviate from this recommendation.
9191

9292
Jump setting for MEC2016 EVB Assy 6797 Rev A1p0
9393
===============================================
@@ -151,7 +151,7 @@ Programming and Debugging
151151
*************************
152152

153153
This board comes with a Cortex ETM port which facilitates tracing and debugging
154-
using a single physical conection. In attidion, it comes with sockets for
154+
using a single physical connection. In addition, it comes with sockets for
155155
JTAG only sessions.
156156

157157
Flashing

boards/arm/nrf52840_pca10056/doc/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ To select the pin numbers for tx-pin and rx-pin:
209209
Open the `nRF52840 Product Specification`_, chapter 7 'Hardware and Layout'.
210210
In the table 7.1.1 'aQFN73 ball assignments' select the pins marked
211211
'General purpose I/O'. Note that pins marked as 'low frequency I/O only' can only be used
212-
in under-10KHz applications. They are not sutiable for 115200 speed of UART.
212+
in under-10KHz applications. They are not suitable for 115200 speed of UART.
213213

214214
Translate 'Pin' into number for Device tree by using the following formula::
215215

doc/application/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -708,7 +708,7 @@ The way that the script determines if a matching :file:`CMakeLists.txt` and
708708
- If the project contains a file named :file:`<path>/zephyr/Kconfig` the build
709709
system will match it
710710

711-
Example of a :file:`<path>/zephyr/module.yml` file refering to
711+
Example of a :file:`<path>/zephyr/module.yml` file referring to
712712
:file:`CMakeLists.txt` and :file:`Kconfig` files at the root of the module:
713713

714714
.. code-block:: console

samples/display/cfb_shell/README.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ column and row positions, and the text to be displayed in double quotation
124124
marks when it contains spaces. If the text hits the edge of the display, the
125125
remaining characters will be displayed in the next line. The text will scroll
126126
until it hits the display boundary, last column for horizontal and last row
127-
for vertical direction. The text passed with the srcoll command will be moved
127+
for vertical direction. The text passed with the scroll command will be moved
128128
vertically or horizontally on the display.
129129

130130

samples/net/google_iot_mqtt/README.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Overview
99
This sample application demonstrates a "full stack" application. This
1010
currently is able to
1111

12-
- Aquire a DHCPv4 lease.
12+
- Acquire a DHCPv4 lease.
1313
- Connect to an SNTP server and acquire current time
1414
- Establish a TLS connection with the Google IOT Cloud servers
1515
- Publish data to the Google IOT Cloud
@@ -38,7 +38,7 @@ Users will also be required to configure the following Kconfig options
3838
based on their Google Cloud IOT project:
3939

4040
- CLOUD_CLIENT_ID - created from <telemetry>/<region>/registries/<registry name>/devices/<device name>
41-
- CLOUD_AUDIENCE - created from telementry without projects on front
41+
- CLOUD_AUDIENCE - created from telemetry without projects on front
4242
- CLOUD_SUBSCRIBE_CONFIG - created from /devices/<device name>/config
4343
- CLOUD_PUBLISH_TOPIC - created from /devices/<device name>/state
4444

0 commit comments

Comments
 (0)