Refine out-of-order command-buffer enqueue wording

Author: EwanC

api/cl_khr_command_buffer.asciidoc

@@ -107,10 +107,11 @@ command-buffers to define command dependencies. This allows the commands of a
 command-buffer to execute out-of-order on a single <<compatible, compatible>>
 command-queue. The command-buffer itself has no inherent in-order/out-of-order
 property, this ordering is inferred from the command-queue used on command
-recording. Out-of-order enqueues without event dependencies of both regular
-commands, such as {clEnqueueFillBuffer}, and command-buffers are allowed to
-execute concurrently, and it is up to the user to express any dependencies using
-events.
+recording. {clEnqueueCommandBufferKHR} submissions to an out-of-order queue
+have the same execution semantics are other operations enqueued to an
+out-of-order queue, such as {clEnqueueFillBuffer}. Where execution between
+enqueued operations may happen concurrently unless dependencies between the
+operations are expressed with events.
 
 The {cl_sync_point_khr_TYPE} type is defined as a `cl_uint`, giving a hard
 upper limit on the number of commands a command-buffer can hold as