Slightly generalise wording around validity

Author: DuncanMcBain

default-constructed-buffers/default-constructed-buffers.md

@@ -60,15 +60,15 @@ explicit conversion operator would call this same function but allow its use
 in `if` statements.
 
 Requesting access from a default-constructed buffer should throw an exception.
-It is not meaningful to use a default-constructed buffer on device. Since there
+It is not meaningful to use a default-constructed buffer. Since there
 is no allocation associated with a default-constructed `buffer`,
 `cl::sycl::buffer::set_final_data` and `cl::sycl::buffer::set_write_back`
 should behave as if the `buffer` had a final pointer of `nullptr` at all times.
 The other functions in the `buffer` API should behave as though the buffer were
 constructed with a `range` of size zero and otherwise behave normally.
 
 Explicitly constructing a buffer with a range of zero is not allowed. This does
-not correspond to a valid device allocation.
+not correspond to a valid allocation.
 
 ## Sample code