Update README.md

README.md

@@ -1,5 +1,5 @@
 
-<h1>LFI<img src="assets/lfi-logo.svg" alt="logo" width="30px"/></h1>
+<h1>LFI <img src="assets/lfi-logo.svg" alt="logo" width="30px"/></h1>
 
 ![Test Workflow](https://github.com/zyedidia/lfi/actions/workflows/test.yaml/badge.svg)
 [![MPL License](https://img.shields.io/badge/license-MPL%202.0-blue)](https://github.com/zyedidia/lfi/blob/master/LICENSE)
@@ -38,7 +38,7 @@ LFI-compatible programs are performant: on the SPEC 2017 benchmark suite, we
 measured a runtime overhead of 7% and a code size overhead of 14% for full
 isolation. This compares well with LLVM-based ahead-of-time WebAssembly
 compilers, which incur upwards of 20% runtime overhead. Additionally, LFI can
-be used purely for fault isolation, where sandboxes may read, but not write,
+be used for pure fault isolation, where sandboxes may read, but not write,
 each other's memory. In this case, we measured a runtime overhead of around 1%.
 
 LFI is also secure: the compiler toolchain used to