doc: services: fix typo

Utilize a code spell-checking tool to scan for and correct spelling errors
in all files within the doc/services directory.

Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com>

doc/services/binary_descriptors/index.rst

@@ -5,7 +5,7 @@ Binary Descriptors
 
 Binary Descriptors are constant data objects storing information about the binary executable.
 Unlike "regular" constants, binary descriptors are linked to a known offset in the binary, making
-them accesible to other programs, such as a different image running on the same device or a host tool.
+them accessible to other programs, such as a different image running on the same device or a host tool.
 A few examples of constants that would make useful binary descriptors are: kernel version, app version,
 build time, compiler version, environment variables, compiling host name, etc.
 
@@ -105,7 +105,7 @@ configs should be enabled:
    CONFIG_BINDESC_DEFINE_BUILD_TIME=y
    CONFIG_BINDESC_BUILD_DATE_TIME_STRING=y
 
-To avoid collisions with user defined descriptors, the standard descriptors were alloted
+To avoid collisions with user defined descriptors, the standard descriptors were allotted
 the range between ``0x800-0xfff``. This leaves ``0x000-0x7ff`` to users.
 For more information read the ``help`` sections of these Kconfig symbols.
 By convention, each Kconfig symbol corresponds to a binary descriptor whose

doc/services/debugging/debugmon.rst

@@ -33,7 +33,7 @@ of the interrupt.
 Usage
 *****
 
-When monitor mode debuging is enabled, entering a breakpoint will not halt the
+When monitor mode debugging is enabled, entering a breakpoint will not halt the
 processor, but rather generate an interrupt with ISR implemented under
 ``z_arm_debug_monitor`` symbol.  :kconfig:option:`CONFIG_CORTEX_M_DEBUG_MONITOR_HOOK` config configures this interrupt
 to be the lowest available priority, which will allow other interrupts to execute

doc/services/ipc/ipc_service/ipc_service.rst

@@ -67,7 +67,7 @@ See the following example:
 
    static void bound_cb(void *priv)
    {
-      /* Endpint bounded */
+      /* Endpoint bounded */
    }
 
    static void recv_cb(const void *data, size_t len, void *priv)
@@ -93,7 +93,7 @@ See the following example:
       ret = ipc_service_open_instance(inst0);
       ret = ipc_service_register_endpoint(inst0, &ept0, &ept0_cfg);
 
-      /* Wait for endpint bound (bound_cb called) */
+      /* Wait for endpoint bound (bound_cb called) */
 
       unsigned char message[] = "hello world";
       ret = ipc_service_send(&ept0, &message, sizeof(message));
@@ -117,7 +117,7 @@ See the following example:
 
    static void bound_cb(void *priv)
    {
-      /* Endpint bounded */
+      /* Endpoint bounded */
    }
 
    static void recv_cb_nocopy(const void *data, size_t len, void *priv)
@@ -146,7 +146,7 @@ See the following example:
       ret = ipc_service_open_instance(inst0);
       ret = ipc_service_register_endpoint(inst0, &ept0, &ept0_cfg);
 
-      /* Wait for endpint bound (bound_cb called) */
+      /* Wait for endpoint bound (bound_cb called) */
       void *data;
       unsigned char message[] = "hello world";
       uint32_t len = sizeof(message);

doc/services/shell/index.rst

@@ -654,7 +654,7 @@ RTT Backend Channel Selection
 *****************************
 
 Instead of using the shell as a logger backend, RTT shell backend and RTT log
-backend can also be used simulatenously, but over different channels. By
+backend can also be used simultaneously, but over different channels. By
 separating them, the log can be captured or monitored without shell output or
 the shell may be scripted without log interference. Enabling both the Shell RTT
 backend and the Log RTT backend does not work by default, because both default

doc/services/storage/disk/nvme.rst

@@ -36,7 +36,7 @@ NVMe configuration
 DTS
 ===
 
-Any board exposing an NVMe disk should provide a DTS overlay to enable its use whitin Zephyr
+Any board exposing an NVMe disk should provide a DTS overlay to enable its use within Zephyr
 
 .. code-block:: devicetree
 

doc/services/zbus/index.rst

@@ -402,7 +402,7 @@ rate by following design tips:
    subscribers. So, chose carefully the configurations
    :kconfig:option:`CONFIG_ZBUS_MSG_SUBSCRIBER_NET_BUF_POOL_SIZE` and
    :kconfig:option:`CONFIG_HEAP_MEM_POOL_SIZE`. They are crucial to a proper VDED execution
-   (delivery garantee) considering message subscribers.
+   (delivery guarantee) considering message subscribers.
 
 .. warning::
    Subscribers will receive only the reference of the changing channel. A data loss may be perceived