Address comments

Signed-off-by: Larsen, Steffen <[email protected]>

Author: Larsen, Steffen

adoc/chapters/architecture.adoc

@@ -1424,13 +1424,13 @@ must include the <<backend>>-specific headers for said <<backend>>.
 A <<command-group-function-object>> can be submitted either to a single queue to
 be executed on, or to a secondary queue.
 If a <<command-group-function-object>> fails to be enqueued to the primary
-queue, then the system may attempt to enqueue it to the secondary queue, if
-given as a parameter to the submit function.  It is implementation defined
+queue, then the implementation may attempt to enqueue it to the secondary queue,
+if given as a parameter to the submit function.  It is implementation defined
 whether the secondary queue is used as a fallback in this manner.
-If the <<command-group-function-object>> fails to be queued to both of these
-queues, or if it fails to be queued to the primary queue and the implementation
-elects not to enqueue it to the secondary queue, then a synchronous SYCL
-exception will be thrown.
+If the <<command-group-function-object>> fails to be enqueued to both of these
+queues, or if it fails to be enqueued to the primary queue and the
+implementation elects not to enqueue it to the secondary queue, then a
+synchronous SYCL exception will be thrown.
 
 It is possible that a command group may be successfully enqueued, but then
 asynchronously fail to run, for some reason.

adoc/chapters/programming_interface.adoc

@@ -5442,7 +5442,7 @@ placeholder) or from [code]#handler::require()# (if the accessor is a
 placeholder).  If the accessor is bound to a <<command-group>> with a secondary
 queue, the sub-buffer's alignment must be compatible with both the primary
 queue's device and the secondary queue's device. If the implementation supports
-the secondary queue fallback, it also throws this exception if the sub-buffer's
+secondary queue fallback, it also throws this exception if the sub-buffer's
 alignment is not compatible with the secondary queue's device.
 
 _Throws:_
@@ -14227,7 +14227,7 @@ the primary queue.
 If the <<sycl-runtime>> fails to enqueue or execute a command group on a primary
 queue, it can attempt to run the command group on the secondary queue.
 The circumstances in which the <<sycl-runtime>> may elect to
-fall-back from primary to secondary queue are unspecified in the specification.
+fall-back from primary to secondary queue are unspecified.
 Even if a command group is run on the secondary queue, the requirement that host
 code within the command group is executed exactly once remains, regardless of
 whether the fallback queue is used for execution.
@@ -14523,8 +14523,8 @@ code if the [code]#kernelObject# is not compatible with the device
 associated with the primary queue of the <<command-group>>.
 Throws an [code]#exception# with the [code]#errc::kernel_not_supported# error
 code if the <<command-group>> has a secondary queue, the implementation supports
-the secondary queue fallback, and the [code]#kernelObject# is not compatible
-with the device associated with the secondary queue.
+secondary queue fallback, and the [code]#kernelObject# is not compatible with
+the device associated with the secondary queue.
 
 a@
 [source]
@@ -14548,8 +14548,8 @@ code if the [code]#kernelObject# is not compatible with the device associated
 with the primary queue of the <<command-group>>.
 Throws an [code]#exception# with the [code]#errc::kernel_not_supported# error
 code if the <<command-group>> has a secondary queue, the implementation supports
-the secondary queue fallback, and the [code]#kernelObject# is not compatible
-with the device associated with the secondary queue.
+secondary queue fallback, and the [code]#kernelObject# is not compatible with
+the device associated with the secondary queue.
 
 a@
 [source]
@@ -14578,8 +14578,8 @@ code if the [code]#kernelObject# is not compatible with the device associated
 with the primary queue of the <<command-group>>.
 Throws an [code]#exception# with the [code]#errc::kernel_not_supported# error
 code if the <<command-group>> has a secondary queue, the implementation supports
-the secondary queue fallback, and the [code]#kernelObject# is not compatible
-with the device associated with the secondary queue.
+secondary queue fallback, and the [code]#kernelObject# is not compatible with
+the device associated with the secondary queue.
 
 |====
 
@@ -15211,10 +15211,9 @@ compatible device image in [code]#execBundle#, the <<kernel-invocation-command>>
 throws a synchronous [code]#exception# with the
 [code]#errc::kernel_not_supported# error code.
 If the <<command-group>> has a secondary queue and the implementation supports
-the secondary queue fallback, then the [code]#execBundle# must contain a kernel
-that is compatible with both the primary queue's device and the secondary
-queue's device, otherwise the <<kernel-invocation-command>> throws this
-exception.
+secondary queue fallback, then the [code]#execBundle# must contain a kernel that
+is compatible with both the primary queue's device and the secondary queue's
+device, otherwise the <<kernel-invocation-command>> throws this exception.
 
 Since the handler method for setting specialization constants is incompatible
 with the kernel bundle method, applications should not call this function if
@@ -15230,7 +15229,7 @@ _Throws:_
 
   * An [code]#exception# with the [code]#errc::invalid# error code if the
     <<handler>> has an associated secondary <<queue>>, the implementation
-    supports the secondary queue fallback, and the <<context>> of the secondary
+    supports secondary queue fallback, and the <<context>> of the secondary
     queue is different from the <<context>> associated with the
     <<kernel-bundle>> specified by [code]#execBundle#.