michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: Fix spelling errors in .rst files

Browse source 
Fix spelling errors in assorted .rst files. The errors were found
using a tool called 'codespell'.

Signed-off-by: Aleksandar Markovic <aleksandar.markovic.sa@gmail.com>
This commit is contained in:
Aleksandar Markovic 2022-04-13 09:48:18 +02:00 • committed by Carles Cufí
commit 8a32b05905
23 changed files with 27 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/connectivity/bluetooth/autopts/autopts-linux.rst
View file

@ -353,7 +353,7 @@ In this case, choose rather VMWare Workstation.
:width: 650
:align: center
One or more of the fallowing steps should help:
One or more of the following steps should help:
- Close all PTS Windows.

2
doc/connectivity/networking/api/lwm2m.rst
View file

@ -264,7 +264,7 @@ Create callback functions for LwM2M resource exuctions:
LOG_INF("Device rebooting.");
LOG_PANIC();
sys_reboot(0);
return 0; /* wont reach this */
return 0; /* won't reach this */
}
The LwM2M RD client can send events back to the sample. To receive those

2
doc/develop/west/west-apis.rst
View file

@ -192,7 +192,7 @@ Deprecated APIs
The following APIs also use :py:class:`west.configuration.ConfigFile`, but they
operate by default on a global object which stores the current workspace
configuration. This has proven to be a bad design descision since west's APIs
configuration. This has proven to be a bad design decision since west's APIs
can be used from multiple workspaces. They were deprecated in west v0.13.0.
These APIs are preserved for compatibility with older extensions. They should

2
doc/hardware/peripherals/sensor.rst
View file

@ -87,7 +87,7 @@ To configure a trigger, an application needs to supply a
:c:struct:`sensor_trigger` and a handler function. The structure contains the
trigger type and the channel on which the trigger must be configured.
Because most sensors are connected via SPI or I2C busses, it is not possible
Because most sensors are connected via SPI or I2C buses, it is not possible
to communicate with them from the interrupt execution context. The
execution of the trigger handler is deferred to a thread, so that data
fetching operations are possible. A driver can spawn its own thread to fetch

2
doc/services/logging/index.rst
View file

@ -207,7 +207,7 @@ formatted to *hh:mm:ss:mmm,uuu*. Otherwise is printed in raw format.
Backend options:
:kconfig:option:`CONFIG_LOG_BACKEND_UART`: Enabled build-in UART backend.
:kconfig:option:`CONFIG_LOG_BACKEND_UART`: Enabled built-in UART backend.
.. _log_usage:

2
doc/services/shell/index.rst
View file

@ -263,7 +263,7 @@ Commands execution
Each command or subcommand may have a handler. The shell executes the handler
that is found deepest in the command tree and further subcommands (without a
handler) are passed as arguments. Characters within parentheses are treated
as one argument. If shell wont find a handler it will display an error message.
as one argument. If shell won't find a handler it will display an error message.
Commands can be also executed from a user application using any active backend
and a function :c:func:`shell_execute_cmd`, as shown in this example:

2
doc/services/tfm/build.rst
View file

@ -63,7 +63,7 @@ key, which is stored inside the secure bootloader firmware image.
By default, ``<tfm-dir>/bl2/ext/mcuboot/root-rsa-3072.pem`` is used to sign secure
images, and ``<tfm-dir>/bl2/ext/mcuboot/root-rsa-3072_1.pem`` is used to sign
non-secure images. Theses default .pem keys can (and **should**) be overridden
non-secure images. These default .pem keys can (and **should**) be overridden
using the :kconfig:option:`CONFIG_TFM_KEY_FILE_S` and
:kconfig:option:`CONFIG_TFM_KEY_FILE_NS` config flags.

4
doc/services/tracing/index.rst
View file

@ -204,7 +204,7 @@ Using RAM backend
=================
For devices that do not have available I/O for tracing such as USB or UART but have
enough RAM to collect trace datas, the ram backend can be enabled with configuration
enough RAM to collect trace data, the ram backend can be enabled with configuration
:kconfig:option:`CONFIG_TRACING_BACKEND_RAM`.
Adjust :kconfig:option:`CONFIG_RAM_TRACING_BUFFER_SIZE` to be able to record enough traces for your needs.
Then thanks to a runtime debugger such as gdb this buffer can be fetched from the target
@ -267,7 +267,7 @@ I/O Taxonomy
Examples:
- sync unbuffered
E.g. PIO via GPIOs having steady stream, no extra FIFO memory needed.
Low jitter but may be less efficient (cant amortize the overhead of
Low jitter but may be less efficient (can't amortize the overhead of
writing).
- sync buffered