From b86084834a4e14af4b74876e8a521162f30e873a Mon Sep 17 00:00:00 2001 From: root Date: Sat, 21 Jul 2018 23:17:18 +0900 Subject: [PATCH] update readme --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 05ec147..2675a76 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ Nohang is a highly configurable daemon for Linux which is able to correctly prev ## What is the problem? -OOM killer doesn't prevent OOM conditions. And OOM conditions may cause [freezes](https://en.wikipedia.org/wiki/Hang_(computing)), [livelocks](https://en.wikipedia.org/wiki/Deadlock#Livelock), loss disk cache and killing multiple processes. +OOM killer doesn't prevent OOM conditions. And OOM conditions may cause [freezes](https://en.wikipedia.org/wiki/Hang_(computing)), [livelocks](https://en.wikipedia.org/wiki/Deadlock#Livelock), drop caches and killing multiple processes. Here are the statements of some users: @@ -45,7 +45,7 @@ Also look at [Why are low memory conditions handled so badly?](https://www.reddi ## Requirements -- `Linux 3.14+` and `Python 3.4+` for basic usage +- `Linux 3.14+` and `Python 3.4+` for basic use - `libnotify` (Fedora, Arch) or `libnotify-bin` (Debian, Ubuntu) to show GUI notifications ## Memory and CPU usage @@ -108,5 +108,5 @@ Just read the description of the parameters and edit the values. Please restart ## Feedback -Please create [issues](https://github.com/hakavlad/nohang/issues). Use cases, feature requests and any questions are welcome. +Please create [issues](https://github.com/hakavlad/nohang/issues). Use cases, feature uirequests and any questions are welcome.