michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: fix misspellings in docs

Browse source 
Fix misspellings missed in regular reviews.

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
David B. Kinder 2019-02-07 15:41:43 -08:00 • committed by Anas Nashif
commit c1dce2f799
11 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

2
boards/arc/iotdk/doc/board.rst
View file

@ -197,4 +197,4 @@ References
.. _Digilent Pmod Modules: http://store.digilentinc.com/pmod-modules .. _Digilent Pmod Modules: http://store.digilentinc.com/pmod-modules
.. _Putty website: http://www.putty.org .. _Putty website: http://www.putty.org

2
boards/arm/nrf52840_blip/doc/nrf52840_blip.rst
View file

@ -123,7 +123,7 @@ SPI
* MOSI = P1.02 * MOSI = P1.02
* MISO = P0.24 * MISO = P0.24
Microsd is connected to these pins, and CS pin is connected to P0.17. MicroSD is connected to these pins, and CS pin is connected to P0.17.
Programming and Debugging Programming and Debugging
************************* *************************

4
boards/arm/nrf52840_pca10059/doc/nrf52840_pca10059.rst
View file

@ -153,7 +153,7 @@ the steps above. Then, prepare to compile an application with MCUBoot support.
Select :option: `CONFIG_BOOTLOADER_MCUBOOT`, under "Boot options" and set Select :option: `CONFIG_BOOTLOADER_MCUBOOT`, under "Boot options" and set
:option: `CONFIG_TEXT_SECTION_OFFSET` under "Build and Link features", :option: `CONFIG_TEXT_SECTION_OFFSET` under "Build and Link features",
"Linker options" to 0x200 to ensure the code is offset to account for MCUboot "Linker options" to 0x200 to ensure the code is offset to account for MCUboot
firwmare image metadata. firmware image metadata.
Sign the resulting firmware image using the imgtool utility as follows:: Sign the resulting firmware image using the imgtool utility as follows::
@ -233,4 +233,4 @@ References
.. _Nordic Semiconductor USB DFU: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.2.0%2Fsdk_app_serial_dfu_bootloader.html .. _Nordic Semiconductor USB DFU: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.2.0%2Fsdk_app_serial_dfu_bootloader.html
.. _nrfutil GitHub: https://github.com/NordicSemiconductor/pc-nrfutil .. _nrfutil GitHub: https://github.com/NordicSemiconductor/pc-nrfutil
.. _MCUboot: https://github.com/runtimeco/mcuboot/blob/master/docs/readme-zephyr.md .. _MCUboot: https://github.com/runtimeco/mcuboot/blob/master/docs/readme-zephyr.md
.. _mcumgr: https://github.com/apache/mynewt-mcumgr-cli .. _mcumgr: https://github.com/apache/mynewt-mcumgr-cli

2
boards/arm/nrf52840_pca10090/doc/nrf52840_pca10090.rst
View file

@ -152,7 +152,7 @@ By default, the board controller firmware will route the following:
| MCU Interface 2 | COEX interface | | MCU Interface 2 | COEX interface |
+-----------------+----------------------------------+ +-----------------+----------------------------------+
It is possbile to configure the behavior of the board controller firmware by It is possible to configure the behavior of the board controller firmware by
using Kconfig and editing its options under "Board options". using Kconfig and editing its options under "Board options".

2
boards/arm/nrf9160_pca10090/doc/nrf9160_pca10090.rst
View file

@ -137,7 +137,7 @@ The process requires the following steps:
When building a Secure/Non-Secure application, the Secure application will When building a Secure/Non-Secure application, the Secure application will
have to set the IDAU (SPU) configuration to allow Non-Secure access to all have to set the IDAU (SPU) configuration to allow Non-Secure access to all
CPU reources utilized by the Non-Secure application firmware. SPU CPU resources utilized by the Non-Secure application firmware. SPU
configuration shall take place before jumping to the Non-Secure application. configuration shall take place before jumping to the Non-Secure application.
Building a Secure only application Building a Secure only application

2
boards/arm/v2m_musca/doc/v2m_musca.rst
View file

@ -362,7 +362,7 @@ Building a secure/non-secure with Trusted Firmware
The process requires five steps: The process requires five steps:
1. Build Trusted Firmware (tfm). 1. Build Trusted Firmware (tfm).
2. Import it as a library to the Zepyhr source folder. 2. Import it as a library to the Zephyr source folder.
3. Build Zephyr with a non-secure configuration. 3. Build Zephyr with a non-secure configuration.
4. Merge the two binaries together and sign them. 4. Merge the two binaries together and sign them.
5. Concatenate the bootloader with the signed image blob. 5. Concatenate the bootloader with the signed image blob.

2
boards/riscv32/hifive1/doc/hifive1.rst
View file

@ -34,7 +34,7 @@ RISC-V support. Download the tarball for your OS from the `SiFive website
<https://www.sifive.com/boards>`_ and extract it. <https://www.sifive.com/boards>`_ and extract it.
The Zephyr SDK uses a bundled version of OpenOCD by default. You can The Zephyr SDK uses a bundled version of OpenOCD by default. You can
overwrite that behaviour by adding the ``OPENOCD`` parameter to the overwrite that behavior by adding the ``OPENOCD`` parameter to the
``cmake`` command: ``cmake`` command:
.. code-block:: bash .. code-block:: bash

2
doc/development_process/index.rst
View file

@ -201,7 +201,7 @@ Developers are expected to fix issues and rework their patches and submit again.
The CI infrastructure currently runs the following tests: The CI infrastructure currently runs the following tests:
- Run '''checkpatch''' for code style issues (can vote -1 on errors) - Run '''checkpatch''' for code style issues (can vote -1 on errors)
- Gitlint: Git commit style based on project requorements - Gitlint: Git commit style based on project requirements
- License Check: Check for conflicting licenses - License Check: Check for conflicting licenses
- Run '''sanitycheck''' script: - Run '''sanitycheck''' script:

2
doc/guides/coccinelle.rst
View file

@ -261,7 +261,7 @@ information required during transformation.
For example: For example:
``Z_SYSCALL_HANDLER`` is not recognized by coccinelle. Therefore, we ``Z_SYSCALL_HANDLER`` is not recognized by coccinelle. Therefore, we
put its prototype in a header file, say for eg ``mymacros.h``. put its prototype in a header file, say for example ``mymacros.h``.
.. code-block:: console .. code-block:: console

2
samples/boards/96b_argonkey/microphone/README.rst
View file

@ -124,6 +124,6 @@ Play PCM Audio
-------------- --------------
Now that we have a binary PCM file (say sound.raw), you can use, Now that we have a binary PCM file (say sound.raw), you can use,
for example, the audicity open source editor/player to load and play it. for example, the audacity open source editor/player to load and play it.
Use the 'Import->Raw Data' menu to load the sound.raw file as Use the 'Import->Raw Data' menu to load the sound.raw file as
signed 16 bit PCM, Little Endian, mono format @16KHz. signed 16 bit PCM, Little Endian, mono format @16KHz.

2
samples/subsys/fs/README.rst
View file

@ -30,4 +30,4 @@ to work:
To run this sample, a FAT formatted microSD card should be present in the To run this sample, a FAT formatted microSD card should be present in the
microSD slot of ``nrf52840_blip`` board. If there are any files or directories microSD slot of ``nrf52840_blip`` board. If there are any files or directories
present in the card, the sample lists them out on the debug serial output. present in the card, the sample lists them out on the debug serial output.