Update README.md

Author: cacay

README.md

@@ -81,7 +81,7 @@ About the Code
 -------------------------
 Here are a few important points that you should know about the code:
 * This code handles alignment for the objects automatically, which is necessary for high performance memory access and may even be required on certain processors. However, it assumes the memory returned by `operator new` is "aligned enough" to store a pointer. This assumption was not necessary, but since it is reasonable enough, I decided to remove two lines of code. I am not sure if this is required by the standard, but all C code using `malloc` would crash (or run extremely slowly) if this was not the case.
-* The allocator does not free any memory until it is destructed (though it does re-use the memory that you deallocate).  This is fine if you only allocate objects, or if you deallocate and re-allocate objects equally. This is only a problem if you have peaks of high memory usage and you expect the memory to be freed during low memory periods. This was a design choice to substantially improve the performance, and under most cases you do not need to worry about this. It is good to keep this mind for projects that require special handling of the memory though.
+* The allocator does not free any memory until it is destructed (though it does re-use the memory that you deallocate).  This is fine if you only allocate objects, or if you deallocate and re-allocate objects equally often. This is only a problem if you have peaks of high memory usage and you expect the memory to be freed during low memory periods. This was a design choice to substantially improve the performance, and under most cases you do not need to worry about this. It is good to keep this mind for projects that require special handling of the memory though.
 
 License
 -------------------------