doc: connectivity: networking: fix typo

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

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

doc/connectivity/networking/api/coap_server.rst

@@ -27,7 +27,7 @@ Some configuration is required to make sure services can be started using the Co
 
 All services are added to a predefined linker section and all resources for each service also get
 their respective linker sections. If you would have a service ``my_service`` it has to be
-prefixed wth ``coap_resource_`` and added to a linker file:
+prefixed with ``coap_resource_`` and added to a linker file:
 
 .. code-block:: c
     :caption: ``sections-ram.ld``

doc/connectivity/networking/api/mqtt_sn.rst

@@ -90,7 +90,7 @@ advertisement mechanism, this is not implemented yet in the library.
 
 Call the ``mqtt_sn_connect`` function, which will send a ``CONNECT`` message.
 The application should periodically call the ``mqtt_sn_input`` function to process
-the response received. The appliation does not have to call ``mqtt_sn_input`` if it
+the response received. The application does not have to call ``mqtt_sn_input`` if it
 knows that no data has been received (e.g. when using Bluetooth). Note that
 ``mqtt_sn_input`` is a non-blocking function, if the transport struct contains a
 ``poll`` compatible function pointer.

doc/connectivity/networking/api/tls_credentials_shell.rst

@@ -13,7 +13,7 @@ Commands
 Buffer Credential (``buf``)
 ===========================
 
-Buffer data incrementaly into the credential buffer so that it can be added using the :ref:`tls_credentials_shell_add_cred` command.
+Buffer data incrementally into the credential buffer so that it can be added using the :ref:`tls_credentials_shell_add_cred` command.
 
 Alternatively, clear the credential buffer.
 

doc/connectivity/networking/api/websocket.rst

@@ -63,7 +63,7 @@ is supported. In order to send BINARY data, the :c:func:`websocket_send_msg()`
 must be used.
 
 When done, the Websocket transport socket must be closed. User should handle
-the lifecycle(close/re-use) of tcp socket after websocket_disconnect.
+the lifecycle(close/reuse) of tcp socket after websocket_disconnect.
 
 .. code-block:: c
 

doc/connectivity/networking/conn_mgr/implementation.rst

@@ -281,7 +281,7 @@ If exceptions to this are absolutely necessary, they should be constrained to sp
 
    While connectivity implementations must not break, it is acceptable for implementations to have potentially unexpected behavior if applications attempt to directly control the association state.
 
-   For instance, if an application directly instructs an underlying technology to dissassociate, it would be acceptable for the connectivity implementation to interpret this as an unexpected connection loss and immediately attempt to re-associate.
+   For instance, if an application directly instructs an underlying technology to disassociate, it would be acceptable for the connectivity implementation to interpret this as an unexpected connection loss and immediately attempt to re-associate.
 
 .. _conn_mgr_impl_guidelines_non_blocking:
 

doc/connectivity/networking/conn_mgr/main.rst

@@ -197,7 +197,7 @@ Connectivity control
 
 Many network interfaces require a network association procedure to be completed before being usable.
 
-For such ifaces, connectivity control can provide a generic API to request network association (:c:func:`conn_mgr_if_connect`) and dissasociation (:c:func:`conn_mgr_if_disconnect`).
+For such ifaces, connectivity control can provide a generic API to request network association (:c:func:`conn_mgr_if_connect`) and disassociation (:c:func:`conn_mgr_if_disconnect`).
 Network interfaces implement support for this API by :ref:`binding themselves to a connectivity implementation <conn_mgr_impl_binding>`.
 
 Using this API, applications can associate with networks with minimal technology-specific boilerplate.
@@ -220,7 +220,7 @@ The following sections outline the basic operation of Connection Manager's conne
 Binding
 -------
 
-Before an iface can be commanded to associate or dissasociate using Connection Manager, it must first be bound to a :ref:`connectivity implementation <conn_mgr_impl>`.
+Before an iface can be commanded to associate or disassociate using Connection Manager, it must first be bound to a :ref:`connectivity implementation <conn_mgr_impl>`.
 Binding is performed by the provider of the iface, not by the application (see :ref:`conn_mgr_impl_binding`), and can be thought of as an extension of the iface declaration.
 
 Once an iface is bound, all connectivity commands passed to it (such as :c:func:`conn_mgr_if_connect` or :c:func:`conn_mgr_if_disconnect`) will be routed to the corresponding implementation function in the connectivity implementation.