Some more typo type fixes

Author: fodinabor

_posts/2021-04-11-hipsycl-091-buffer-policies.markdown

@@ -9,15 +9,15 @@ This post is part of a series where we discuss some features of the brandnew hip
 
 # Asynchronous buffers and explicit buffer policies
 
-This is a new extension in hipSYCL that can make code using `sycl::buffer` objects **much clearer while also improving performance**. Insterested? Then this blog post is for you.
+This is a new extension in hipSYCL that can make code using `sycl::buffer` objects **much clearer while also improving performance**. Interested? Then this blog post is for you.
 
 ## Motivation 1: Buffers are complicated
 
 A `sycl::buffer` is a very complicated object. Depending on a combination of multiple factors the semantics of a `sycl::buffer` can be very different. Will it operate directly on input pointers or will it copy input data to some internal storage? Will it submit a writeback in the destructor to copy data back to host?
 
 I have frequently noticed users getting this wrong. This can either lead to correctness issues, for example
 * the buffer operates directly on the input pointer, while the user has only intended to provide it as a source of initial data and wanted to reuse it after buffer construction
-* No writeback is issued even though the user expected data to be copied back to host.
+* no writeback is issued even though the user expected data to be copied back to host.
 
 Or performance bugs might be introduced - these are arguably even worse because you might not notice them right away and they might be difficult to find. Some performance bugs that I have seen in user code are:
 * The buffer issued an unexpected writeback, and thus copied data back to host without the user intending it