doc: fix more spelling errors throughout docs

Change-Id: Ie76b51a3d0729159fa30c1fc9160b279d9f70b6c
Signed-off-by: David B. Kinder <[email protected]>

Author: dbkinder

doc/README.rst

@@ -18,10 +18,10 @@ Documentation Notes
 
 Zephyr Project content is written using the reStructuredText markup language
 (.rst file extension) with Sphinx extensions, and processed using sphinx to
-create a formatted standalone website. Developers can view this content either
+create a formatted stand-alone website. Developers can view this content either
 in its raw form as .rst markup files, or you can generate the HTML content and view it
 with a web browser directly on your workstations drive. This same .rst
-content is also fed into the Zephyr Project'ns public website documentation area
+content is also fed into the Zephyr Project's public website documentation area
 (with a different theme applied).
 
 You can read details about reStructuredText and about Sphinx extensions from

doc/application/application.rst

@@ -398,7 +398,7 @@ entries manually, using the configuration menu is a preferred method.
 
      .. note::
 
-       When a non-default entry is selected for options that are nonnumerical,
+       When a non-default entry is selected for options that are non-numerical,
        an asterisk :kbd:`*` appears between the square brackets in the display.
        There is nothing added added the display when you select the option's
        default.

doc/crypto/tinycrypt.rst

@@ -217,7 +217,7 @@ Specific Remarks
 
   * TinyCrypt ECC implementation is based on nano-ecc (see
     https://github.com/iSECPartners/nano-ecc) which in turn is based on
-    mciro-ecc (see https://github.com/kmackay/micro-ecc). In the original
+    micro-ecc (see https://github.com/kmackay/micro-ecc). In the original
     nano and micro-ecc documentation, there is an important remark about the
     way integers are represented:
 

doc/drivers/drivers.rst

@@ -49,7 +49,7 @@ Zephyr provides a set of device drivers for multiple boards. Each driver
 should support an interrupt-based implementation, rather than polling, unless
 the specific hardware does not provide any interrupt.
 
-High-level calls accessed through devices's specific API, such as i2c.h
+High-level calls accessed through device-specific APIs, such as i2c.h
 or spi.h, are usually intended as synchronous. Thus, these calls should be
 blocking.
 
@@ -147,7 +147,7 @@ the normal course of operation (such as a storage device full). Bad
 parameters, programming errors, consistency checks, pathological/unrecoverable
 failures, etc., should be handled by assertions.
 
-When it is appropriate to return error condtitions for the caller to check, 0
+When it is appropriate to return error conditions for the caller to check, 0
 should be returned on success and a POSIX errno.h code returned on failure.
 See https://wiki.zephyrproject.org/view/Coding_conventions#Return_Codes for
 details about this.
@@ -280,7 +280,7 @@ executed. Any driver will specify one of five initialization levels:
 `PRE_KERNEL_2`
         Used for devices that rely on the initialization of devices initialized
         as part of the PRIMARY level. These devices cannot use any kernel
-        services during configuration, since the kerne services are not yet
+        services during configuration, since the kernel services are not yet
         available. Init functions at this level run on the interrupt stack.
 
 `POST_KERNEL`

doc/getting_started/getting_started.rst

@@ -78,7 +78,7 @@ To build an example application follow these steps:
 
       $ cd zephyr-project
 
-#. Source the project environment file to set the project environtment
+#. Source the project environment file to set the project environment
    variables:
 
    .. code-block:: console

doc/getting_started/installation_mac.rst

@@ -94,7 +94,7 @@ Setting Up the Toolchain
 Creating a Case-sensitive File System
 =====================================
 
-Building the compiler requires a case-senstive file system. Therefore, use
+Building the compiler requires a case-sensitive file system. Therefore, use
 :program:`diskutil` to create an 8 GB blank sparse image making sure you select
 case-sensitive file system (OS X Extended (Case-sensitive, Journaled) and
 mount it.

doc/getting_started/installation_win.rst

@@ -36,7 +36,7 @@ for native Windows applications. The Zephyr build system will execute on top of
 this tool set.
 
 To install :program:`MinGW`, visit the site `MinGW Home`_ and install the
-following packages with their installler `mingw-get-setup.exe`:
+following packages with their installer `mingw-get-setup.exe`:
 
 * mingw-developer-toolkit
 * mingw32-base

doc/glossary.rst

@@ -66,4 +66,4 @@ Glossary of Terms
    XIP
       (eXecute In Place) a method of executing programs directly from long
       term storage rather than copying it into RAM, saving writable memory for
-      dynamic data and not the staic program code.
+      dynamic data and not the static program code.

doc/porting/application.rst

@@ -8,7 +8,7 @@ Legacy Applications Porting Guide
 
    This document is still work in progress.
 
-This guide will help you move your applications from the nanokerne/microkernel
+This guide will help you move your applications from the nanokernel/microkernel
 model to the unified kernel. The unified kernel was introduced with
 :ref:`zephyr_1.6` which was released late 2016.
 

doc/porting/arch.rst

@@ -83,7 +83,7 @@ When a device wants to signal the processor that there is some work to be done
 on its behalf, it raises an interrupt. When a thread does an operation that is
 not handled by the serial flow of the software itself, it raises an exception.
 Both, interrupts and exceptions, pass control to a handler. The handler is
-knowns as an :abbr:`ISR (Interrupt Service Routine)` in the case of
+known as an :abbr:`ISR (Interrupt Service Routine)` in the case of
 interrupts. The handler perform the work required the exception or the
 interrupt.  For interrupts, that work is device-specific. For exceptions, it
 depends on the exception, but most often the core kernel itself is responsible