Edits to documentation per review feedback

Made intended use of event to ensure completion of submitted
operation from host side of the application explicit.

Removed note that lsplatform is new in dpctl 0.7

Update docs/docfiles/user_guides/QuickStart.rst

Streamlined notice about GPU drivers per PR review feedback.

Co-authored-by: Alexandra <[email protected]>

Author: oleksandr-pavlyk

docs/docfiles/user_guides/QuickStart.rst

@@ -38,12 +38,9 @@ On Windows OS
 
 .. note::
 
-    The ``dpctl.lsplatform()`` function is new in dpctl 0.7 and will be
-    available in oneAPI 2021.3. If you are following the guide on an older
-    oneAPI installation, use ``dpctl.dump()``. If no GPU platforms are shown,
-    make sure your system has a supported GPU and the necessary GPU drivers
-    installed. You can install GPU drivers by following the
-    `GPU driver installation guide <https://dgpu-docs.intel.com/installation-guides/index.html>`_.
+    If no GPU platforms are shown, make sure your system has a supported
+    GPU and the necessary GPU drivers installed.
+    See `GPU driver installation guide <https://dgpu-docs.intel.com/installation-guides/index.html>`_ to install GPU drivers.
 
 Install the Wheel Package from PyPi
 ====================================

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

@@ -42,11 +42,11 @@ This section introduces the basic concepts for XPU management used by `dpctl`.
    tasks are executed in the order in which they were submitted.
 
 * **Event**
-   Holds information related to computation or data movement operation
-   scheduled for the execution on a queue. An event can store the execution status or
-   profiling information of the queue, to which the task is submitted.
-   Events can be used to specify task
-   dependencies or to synchronize host and devices.
+   An event holds information related to computation/data movement operation
+   scheduled for execution on a queue, such as its execution status as well
+   as profiling information if the queue the task was submitted to allowed
+   for collection of such information. Events can be used to specify task
+   dependencies as well as to synchronize host and devices.
 
 * **USM**
    Unified Shared Memory (USM) refers to pointer-based device memory management.
@@ -67,6 +67,11 @@ This section introduces the basic concepts for XPU management used by `dpctl`.
    "Shared allocation", "Yes", "Accessible by both the host and device."
    "Host allocation", "Yes", "Accessible by both the host and device."
 
+   Depending on the capability of the device, USM allocations can be a "device"
+   allocation, a "shared" allocation, or a "host" allocation. A "device"
+   allocation is not accessible from host, while "shared" or "host" allocations
+   are. "Host" allocation refers to an allocation in host memory that is
+   accessible from a device.
 
 Runtime manages synchronization of the host's and device's view into shared allocations.
 The initial placement of the shared allocations is not defined.