Spelling fixes

Some found in review, some identified by spell-checker tool.

Author: oleksandr-pavlyk

docs/doc_sources/beginners_guides/index.rst

@@ -36,7 +36,7 @@ Miscellaneous
 -------------
 
 * History of ``"dpctl"`` :ref:`name <beginners_guide_why_dpctl>`
-* Frequenty asked questions
+* Frequently asked questions
 
 .. toctree::
     :hidden:

docs/doc_sources/beginners_guides/installation.rst

@@ -104,7 +104,7 @@ instructions on how to install required drivers on Linux.
 .. _gpu_stack_installation_guide: https://dgpu-docs.intel.com/
 
 .. note::
-    Instructions for setting up GPU drivers in Windows Subsytem for Linux is forthcoming.
+    Instructions for setting up GPU drivers in Windows Subsystem for Linux (WSL) is forthcoming.
 
 Building from source
 ====================

docs/doc_sources/beginners_guides/managing_devices.rst

@@ -147,7 +147,7 @@ of valid settings are:
 Device selection
 ================
 
-DPC++ runtime provides a way to select a device with a highest score to for a set of selection scroring strategies.
+DPC++ runtime provides a way to select a device with a highest score to for a set of selection scoring strategies.
 Amongst these are a default selector, CPU selector, GPU selector, as well as filter-string selector.
 
 Using fixed device selectors

docs/doc_sources/beginners_guides/tensor_intro.rst

@@ -84,7 +84,7 @@ each one corresponds to the same underlying ``sycl::queue`` object. In such a ca
 
 .. note::
     Two instances :class:`dpctl.SyclQueue` may target the same ``sycl::device`` and be using the same ``sycl::context``, but correspond
-    to different scheduling enties, and hence be in violation of the compute-follows-data requirement. One common example of this are
+    to different scheduling entries, and hence be in violation of the compute-follows-data requirement. One common example of this are
     ``SyclQueue`` corresponding to default-selected device and using platform default context but created using different properties, e.g.
     one with `"enable_profiling"` set and another without it.
 
@@ -207,7 +207,7 @@ using the following coercion rule:
 | "host"     | "device" | "shared" | "host"   |
 +------------+----------+----------+----------+
 
-If assignign USM-type "device" a score of 0, USM-type "shared" a score of 1, and USM-type "host" a score of 2,
+If assigning USM-type "device" a score of 0, USM-type "shared" a score of 1, and USM-type "host" a score of 2,
 the USM-type of the output array has the smallest score of all its inputs.
 
 .. currentmodule:: dpctl.utils

docs/doc_sources/contributor_guides/building.rst

@@ -4,13 +4,13 @@ Building from the Source
 ========================
 
 To build :py:mod:`dpctl` from the source, you need DPC++ compiler.
-To run expamples and test suite you would need GPU drivers and/or CPU
+To run examples and test suite you would need GPU drivers and/or CPU
 OpenCL drivers. It is preferable to use the Intel(R) oneAPI DPC++ compiler
 available as part of oneAPI Base-Kit. However, it is possible to use a custom
-build of dpcpp to build :py:mod:`dpctl`, especially if you want to enable
+build of DPC++ to build :py:mod:`dpctl`, especially if you want to enable
 CUDA support or try latest features.
 
-Building using oneAPI dpcpp
+Building using oneAPI DPC++
 ---------------------------
 
 Install oneAPI and graphics drivers to the system prior

docs/doc_sources/contributor_guides/memory_ownership_sycl_interface.rst

@@ -21,7 +21,7 @@ with the object to which the token applies. Deletion functions, such as
 :c:func:`DPCTLDevice_Delete`, represent set of such functions.
 
 The token ``__dpctl_keep`` indicates that the library does not alter allocation associated
-with the object to which the tocken applies. Functions to query integral device descriptors,
+with the object to which the token applies. Functions to query integral device descriptors,
 such as :c:func:`DPCTLDevice_GetMaxComputeUnits`, are examples of such functions.
 
 .. code-block:: C

docs/doc_sources/user_guides/basic_concepts.rst

@@ -97,7 +97,7 @@ To obtain all platforms available on a system programmatically, use
 :func:`dpctl.lsplatform` function. Refer to :ref:`Enumerating available devices <beginners_guide_enumerating_devices>`
 for more information.
 
-It is possible to select devices from spefic backend, and hence belonging to
+It is possible to select devices from specific backend, and hence belonging to
 the same platform, by :ref:`using <beginners_guide_oneapi_device_selector>`
 ``ONEAPI_DEVICE_SELECTOR`` environment variable, or by using
 a :ref:`filter selector string <filter_selector_string>`.
@@ -124,7 +124,7 @@ working of :func:`dpctl.tensor.from_dlpack` function is only supported for devic
 platforms that support default platform context SYCL extension `sycl_ext_oneapi_default_platform_context`_,
 and only of those allocations that are bound to this default context.
 
-To query where a particular device ``dev`` belongs to a plaform that implements
+To query where a particular device ``dev`` belongs to a platform that implements
 the default context, check whether ``dev.sycl_platform.default_context`` returns an instance
 of :class:`dpctl.SyclContext` or raises an exception.
 
@@ -141,7 +141,7 @@ SYCL queue is an entity associated with scheduling computational tasks for execu
 on a targeted SYCL device and using some specific SYCL context.
 
 Queue constructor generally requires both to be specified. For platforms that support the
-default platform context, a shortcut queue constuctor call that specifies only a device would
+default platform context, a shortcut queue constructor call that specifies only a device would
 use the default platform context associated with the platform given device is a part of.
 
 .. code-block:: python
@@ -161,7 +161,7 @@ they do not compare equal, since they correspond to two independent scheduling e
 
 .. note::
    :class:`dpctl.tensor.usm_ndarray` objects one associated with ``q1`` and another associated with ``q2``
-   could not be combined in a call to the same function that implementes
+   could not be combined in a call to the same function that implements
    :ref:`compute-followed-data programming model <dpctl_tensor_compute_follows_data>` in :mod:`dpctl.tensor`.
 
 

docs/doc_sources/user_guides/environment_variables.rst

@@ -10,7 +10,7 @@ affect DPC++ compiler runtime.
 Variable ``ONEAPI_DEVICE_SELECTOR``
 -----------------------------------
 
-The varible ``ONEAPI_DEVICE_SELECTOR`` can be used to limit the choice of devices
+The variable ``ONEAPI_DEVICE_SELECTOR`` can be used to limit the choice of devices
 available to :py:mod:`dpctl`. Please refer to
 :ref:`Managing Devices <beginners_guide_oneapi_device_selector>` for detailed
 description and :ref:`uses <beginners_guide_oneapi_device_selector_usecase>`.

docs/doc_sources/user_guides/execution_model.rst

@@ -99,7 +99,7 @@ case it is the execution queue used. Alternatively :exc:`dpctl.utils.ExecutionPl
             raise dpctl.utils.ExecutionPlacementError
         ...
 
-In order to ensure that compute-follows-data works seemlessly out-of-the-box, :mod:`dpctl` maintains
+In order to ensure that compute-follows-data works seamlessly out-of-the-box, :mod:`dpctl` maintains
 a cache of with context and device as keys and queues as values used by :class:`dpctl.tensor.Device` class.
 
 .. code-block:: python