Update

Author: aepanchi

docs/docfiles/user_guides/QuickStart.rst

@@ -181,7 +181,7 @@ instead of the DPC++ compiler that comes with oneAPI.
 
 Do this, to enable support for CUDA* devices.
 
-Following steps in the :ref:`Build and Install with scikit-build<Build and Install with scikit-build>` use a command-line option to set
+Following steps in the *Build and Install with scikit-build* use a command-line option to set
 the relevant CMake variables, for example:
 
 .. code-block:: bash

docs/docfiles/user_guides/manual/dpctl/basic_concepts.rst

@@ -59,22 +59,13 @@ This section introduces the basic concepts for XPU management used by `dpctl`.
 
    Depending on the capability of the device, USM allocations can be:
 
-   .. list-table:: 
-   :widths: 25 25 50 
-   :header-rows: 1
-
-   * - Name
-     - Allocation accessible
-     - Access 
-   * - Device allocation
-     - Shared allocation 
-     - Host allocation
-   * - No
-     - Yes
-     - Yes 
-   * - Refers to an allocation in host memory that is
-       accessible from a device.
-     - Accessible by both the host and device.
+.. csv-table::
+   :header: "Name", "Allocation accessible", "Access"
+   :widths: 25, 25, 50
+
+   "Device allocation", "No","Refers to an allocation in host memory that is accessible from a device."
+   "Shared allocation", "Yes", "Accessible by both the host and device."
+   "Host allocation", "Yes", "Accessible by both the host and device."
 
 
 Runtime manages synchronization of the host's and device's view into shared allocations. 

docs/docfiles/user_guides/manual/dpctl/device_selection.rst

@@ -95,25 +95,14 @@ A possible output for the :ref:`fig-adv-device-selection` example:
 A **filter string** is a three-tuple that may specify the *backend*,
 *device type*, and *device number* as a colon (:) separated string. 
 
+.. csv-table::
+   :header: "String", "Usage", "Values"
+   :widths: 25, 25, 50
+
+   "*backend*", "Specifies the type of device driver.", "``host``, ``opencl``, ``level-zero``, ``cuda``"
+   "*device type*", "Specifies the type of device.", "``host``, ``gpu``, ``cpu``, ``accelerator``"
+   "*device number*", "Specifies the ordinality of the device in the listing of devices as determined by the SYCL* runtime.", "Numeric value"
 
-.. list-table:: Title
-   :widths: 50 50
-   :header-rows: 1
-
-   * - String
-     - Usage
-     - Value
-   * - *backend*
-     - *device type*
-     - *device number*
-   * - Specifies the type of device driver.
-     - Specifies the type of device.
-     - Specifies the ordinality of the device in the listing of devices as
-       determined by the SYCL* runtime.
-   * - ``host``, ``opencl``, ``level-zero``, ``cuda``
-     - ``host``, ``gpu``, ``cpu``, ``accelerator``
-     - Numeric value
-   
 The backend, device type, and device number value are optional but provide at least one of them. 
 That is, ``opencl:gpu:0``, ``gpu:0``, ``gpu``, ``0``, and ``opencl:0`` are all valid filter strings.
 

docs/docfiles/user_guides/manual/dpctl/devices.rst

@@ -65,12 +65,11 @@ Device Aspects and Information Descriptors
 A device can have various *aspects* and *information descriptors* that describe
 its hardware characteristics:
 
-* :sycl_aspects:`Aspects <>` are boolean
-characteristics of the device
+* :sycl_aspects:`Aspects <>` are boolean characteristics of the device
 * :sycl_device_info:`information descriptors <>` are non-boolean characteristics
-that provide more verbose information about the device
+  that provide more verbose information about the device
 * :class:`dpctl.SyclDevice` exposes various Python* properties that describe a
-device's aspects and information descriptors. 
+  device's aspects and information descriptors. 
 
 For example, the property ``has_aspect_fp16`` returns a boolean expression indicating if:
 

docs/docfiles/user_guides/manual/dpctl/queues.rst

@@ -31,11 +31,11 @@ tasks. A SYCL* queue stores the needed data to manage the scheduling operations.
 There are two types of queues: 
 
 * **Out-of-order.** Unless specified otherwise during the constriction of a queue, a SYCL* runtime
-executes tasks, which dependencies are met in an unspecified order, with the
-possibility for some of the tasks to be executed concurrently.
+  executes tasks, which dependencies are met in an unspecified order, with the
+  possibility for some of the tasks to be executed concurrently.
 * **In-order.** You can specify SYCL* queues to indicate that runtime must execute tasks in the
-order, in which they are submitted. In this case, tasks submitted to such a
-queue are never executed concurrently.
+  order, in which they are submitted. In this case, tasks submitted to such a
+  queue are never executed concurrently.
 
 
 Creating a New Queue