fix readme typos (#48)

Author: MasonProtter

README.md

@@ -99,7 +99,7 @@ BenchmarkTools.Trial: 10000 samples with 993 evaluations.
 So, using Bumper.jl in this benchmark gives a slight speedup relative to regular julia `Vector`s,
 and a major increase in performance *consistency* due to the lack of heap allocations.
 
-However, we can actually go a little faster better if we're okay with manually passing around a buffer.
+However, we can actually go a little faster if we're okay with manually passing around a buffer.
 The way I invoked `@no_escape` and `@alloc` implicitly used the task's default buffer, and fetching that
 default buffer is not as fast as using a `const` global variable, because Bumper.jl is trying to protect
 you against concurrency bugs (more on that later).
@@ -149,7 +149,7 @@ an error if you overfill them.
   corresponding `@no_escape` block uses.
 - You cannot use `@alloc` from a different concurrent task than its parent `@no_escape` block as this can cause concurrency bugs. 
 - If for some reason you need to be able to use `@alloc` outside of the scope of the `@no_escape` block, there is a
-  function  =`Bumper.alloc!(bug, T, n...)`= which takes in an explicit buffer `buf` and uses it to allocate an array of
+  function  `Bumper.alloc!(bug, T, n...)` which takes in an explicit buffer `buf` and uses it to allocate an array of
   element type `T`, and dimensions `n...`. Using this is not as safe as `@alloc` and not recommended.
 - Bumper.jl only supports `isbits` types. You cannot use it for allocating vectors containing mutable, abstract, or
   other pointer-backed objects.