Address review comments

Co-authored-by: bader <[email protected]>
Signed-off-by: Sergey Kanaev <[email protected]>

Author: Sergey Kanaev

sycl/doc/Assert.md

@@ -38,17 +38,17 @@ int main() {
 }
 ```
 
-In this use-case every work-item with even X dimension will trigger assertion
-failure. Assertion failure should trigger a call to `std::abort()` at host as
-described in
+In this use-case every work-item with even index along 0 dimension will trigger
+assertion failure. Assertion failure should trigger a call to `std::abort()` at
+host as described in
 [extension](extensions/Assert/SYCL_INTEL_ASSERT.asciidoc).
 Even though multiple failures of the same or different assertions can happen in
-multiple workitems, implementation is required to deliver at least one
+multiple work-items, implementation is required to deliver at least one
 assertion. The assertion failure message is printed to `stderr` by DPCPP
 Runtime or underlying backend.
 
 When multiple kernels are enqueued and more than one fail at assertion, at least
-single assertion should be reported.
+one assertion should be reported.
 
 
 ## User requirements

sycl/doc/extensions/Assert/SYCL_ONEAPI_ASSERT.asciidoc

@@ -21,9 +21,10 @@
 :cpp: C++
 
 == Notice
+
 IMPORTANT: This specification is a draft.
 
-Copyright (c) 2021-2021 Intel Corporation. All rights reserved.
+Copyright (c) 2021 Intel Corporation. All rights reserved.
 
 NOTE: Khronos(R) is a registered trademark and SYCL(TM) and SPIR(TM) are
 trademarks of The Khronos Group Inc.  OpenCL(TM) is a trademark of Apple Inc.
@@ -49,6 +50,7 @@ subject to change they are not intended to be used by shipping software
 products.
 
 == Introduction
+
 This extension adds the ability for device code to call the C++ `assert()`
 macro. The behavior of `assert()` in device code is similar to its behavior in
 host code. If the asserted condition is false, a message is printed to `stderr`