From 42566c6befcd65be2490f9867413f2c26fc7c30c Mon Sep 17 00:00:00 2001
From: Chen <50514813+dota17@users.noreply.github.com>
Date: Mon, 17 Feb 2020 15:40:52 +0800
Subject: [PATCH] Update README.md

---
 README.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index e4183f14..bb65bc0d 100644
--- a/README.md
+++ b/README.md
@@ -1383,15 +1383,12 @@ By default, the library does not preserve the **insertion order of object elemen
 
 ### Memory Release
 
-We checked with Valgrind and the Clang Sanitizers that there are no memory leaks. 
+We checked with Valgrind and the Address Sanitizer (ASAN) that there are no memory leaks. 
 
-If you find that a prasering program with this library does not release memory, please consider these case and it maybe unrelated to this library. 
+If you find that a prasering program with this library does not release memory, please consider the following case and it maybe unrelated to this library. 
 
-- Case 1: Your program is compiled with glibc. 
-
-	> There is a tunable threshold that glibc uses to decide whether to actually return memory to the system or whether to cache it for later reuse. If in your program you make lots of small allocations and those small allocations are not a contiguous block and are presumably below the threshold, then they will not get returned to the OS.
+**Your program is compiled with glibc.** There is a tunable threshold that glibc uses to decide whether to actually return memory to the system or whether to cache it for later reuse. If in your program you make lots of small allocations and those small allocations are not a contiguous block and are presumably below the threshold, then they will not get returned to the OS.
 Here is a related issue [#1924](https://github.com/nlohmann/json/issues/1924).
-Also you can check your program under windows to ensure whether there are memory leaks.
 
 ### Further notes