Fix spelling

adoc/chapters/programming_interface.adoc

@@ -412,7 +412,7 @@ a@
       required for the underlying <<native-backend-object>> specified in
       the <<backend>> specification document, if this SYCL [code]#T# instance
       was originally constructed using one of the backend interoperability
-      [code]#make_*# functions specified in 
+      [code]#make_*# functions specified in
       <<sec:backend-interoperability-make>>.
       See the relevant backend specification for details.
 
@@ -10207,7 +10207,7 @@ modification of shared allocations through the aspect
 See <<table.device.aspect>> in <<sec:device-aspects>> for more details.
 
 Performance hints for shared allocations may be specified by the user by
-enqueueing [code]#prefetch# operations on a device.
+enqueuing [code]#prefetch# operations on a device.
 These operations inform the SYCL runtime that the specified shared allocation is
 likely to be accessed on the device in the future, and that it is free to
 migrate the allocation to the device.
@@ -16478,7 +16478,7 @@ executions are decoupled from one another except at specific points.
 For example, device code executions often begin when dependencies in the SYCL
 task graph are satisfied, which occurs asynchronously from host code execution.
 As a result of this the errors that occur on a device cannot be thrown directly
-from a host API call, because the call enqueueing a device action has typically
+from a host API call, because the call enqueuing a device action has typically
 already returned by the time that the error occurs.
 Such errors are not detected until the error-causing task executes or tries to
 execute, and we refer to these as <<async-error,asynchronous errors>>.