fix spelling (#513)

source/elements/oneDNN/source/data_model/data_types/int8.rst

@@ -45,7 +45,7 @@ computation. Those should be provided by the user through the
 These quantization parameters can either be computed ahead of time
 using calibration tools (*static* quantization) or at runtime based on
 the actual minimum and maximum values of a tensor (*dynamic*
-quantization). Either method can be used in conjuction with oneDNN, as
+quantization). Either method can be used in conjunction with oneDNN, as
 the quantization parameters are passed to the oneDNN primitives at
 execution time.
 

source/elements/oneMKL/source/domains/dft/config_params/data_layouts.rst

@@ -77,7 +77,7 @@ its configuration value for ``config_param::COMPLEX_STORAGE`` (first 2 columns).
     :class: longtable
 
     * -   Object type
-      -   Configuration value for configuration paramer ``config_param::COMPLEX_STORAGE``
+      -   Configuration value for configuration parameter ``config_param::COMPLEX_STORAGE``
       -   Implicitly-assumed elementary data type in forward domain
       -   Implicitly-assumed elementary data type in backward domain
     * -   ``descriptor<precision::SINGLE, domain::COMPLEX>``

source/elements/oneMKL/source/domains/dft/descriptor.rst

@@ -277,7 +277,7 @@ The copy assignment operator results in a deep copy.
 
    .. rubric:: Throws
 
-   The assignment opererators shall throw the following exceptions if the
+   The assignment operators shall throw the following exceptions if the
    associated condition is detected. An implementation may throw additional
    implementation-specific exception(s) in case of error conditions not covered
    here:
@@ -325,7 +325,7 @@ type like ``std::int64_t`` or ``float`` (more details available
 
    param
       One of the possible values of type :ref:`onemkl_dft_enum_config_param`
-      representing the (writable) configuraton parameter to be set.
+      representing the (writable) configuration parameter to be set.
 
    ...
       An element of the appropriate type for the configuration value
@@ -395,7 +395,7 @@ type ``oneapi::mkl::dft::domain``, ``oneapi::mkl::dft::precision``,
 
    param
       One of the possible values of type :ref:`onemkl_dft_enum_config_param`
-      representing the configuraton parameter being queried.
+      representing the configuration parameter being queried.
 
    ...
       A pointer to a writable element of the appropriate type for the

source/elements/oneMKL/source/domains/dft/dft.rst

@@ -56,7 +56,7 @@ forward domains:
 
 Similarly, we refer to DFTs of complex (resp. real) forward domain as "complex
 DFTs" (resp. "real DFTs"). Regardless of the type of forward domain, the
-backward domain's data sequences are alway complex.
+backward domain's data sequences are always complex.
 
 The calculation of the same DFT for several, *i.e.*, :math:`M > 1`, data sets of
 the same type of forward domain, using the same precision is referred to as a
@@ -151,7 +151,7 @@ relevant configuration setting (*e.g.*, the number :math:`M` of sequences to
 consider in case of a batched DFT). Once configured as desired, the
 :ref:`onemkl_dft_descriptor_commit` member function of ``desc``, requiring a
 ``sycl::queue`` object ``Q``, may be invoked. The successful completion of the
-latter makes ``desc`` comitted to the desired (batched) DFT *as configured*, for
+latter makes ``desc`` committed to the desired (batched) DFT *as configured*, for
 the particular device and context encapsulated by ``Q``. The
 :ref:`onemkl_dft_compute_forward` (resp. :ref:`onemkl_dft_compute_backward`)
 function may then be called and provided with ``desc`` to enqueue operations
@@ -166,7 +166,7 @@ user-provided, device-accessible data.
   - must be re-committed to account for any change in configuration after
     it was already successfully committed;
   - deliver best performance for DFT calculations when created, configured and
-    comitted outside applications' hotpath(s) that use them multiple times for
+    committed outside applications' hotpath(s) that use them multiple times for
     identically-configured (batched) DFTs. :ref:`onemkl_dft_compute_forward`
     and/or :ref:`onemkl_dft_compute_backward` should be the only oneMKL DFT-related
     routines invoked in programs' hotpaths.