From 4a0ca077c986ace7991bb4d76ebe265a1c3fe6ac Mon Sep 17 00:00:00 2001
From: EsthvnFerrtn <46089981+EsthvnFerrtn@users.noreply.github.com>
Date: Thu, 29 Aug 2019 20:58:24 -0300
Subject: [PATCH] fix typo

changed the word "whitten" to "written"
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index a086d4f..77f1ae1 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ Also look at [Why are low memory conditions handled so badly?](https://www.reddi
 ## Solution
 
 - Use of [earlyoom](https://github.com/rfjakob/earlyoom). This is a simple, stable and tiny OOM preventer written in C (the best choice for emedded and old servers). It has a minimum dependencies and can work with oldest kernels.
-- Use of [oomd](https://github.com/facebookincubator/oomd). This is a userspace OOM killer for linux systems whitten in C++ and developed by Facebook. This is the best choice for use in large data centers. It needs Linux 4.20+.
+- Use of [oomd](https://github.com/facebookincubator/oomd). This is a userspace OOM killer for linux systems written in C++ and developed by Facebook. This is the best choice for use in large data centers. It needs Linux 4.20+.
 - Use of `nohang` (maybe this is a good choice for modern desktops and servers if you need fine tuning).
 
 ## Some features