From 6e8f8adcec7b51ff339b629bef9ca19db5914a79 Mon Sep 17 00:00:00 2001
From: klugier <klugier@f0d560ea-af0d-0410-9eb7-867de7ffcac7>
Date: Sat, 31 Oct 2020 13:47:52 +0000
Subject: [PATCH] Core, Doc: Polishing memory leaks article.

git-svn-id: svn://ultimatepp.org/upp/trunk@15338 f0d560ea-af0d-0410-9eb7-867de7ffcac7
---
 uppsrc/Core/srcdoc.tpp/Leaks_en-us.tpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/uppsrc/Core/srcdoc.tpp/Leaks_en-us.tpp b/uppsrc/Core/srcdoc.tpp/Leaks_en-us.tpp
index 82344d692..a9b819a6d 100644
--- a/uppsrc/Core/srcdoc.tpp/Leaks_en-us.tpp
+++ b/uppsrc/Core/srcdoc.tpp/Leaks_en-us.tpp
@@ -134,7 +134,8 @@ leak detection:&]
 [s0; &]
 [s5; The alternative simpler approach is to used [* MemoryIgnoreLeaksBlock] 
 structure. On construction it starts ignoring and on destruction 
-it cancels ignoring statement. Example below:&]
+it cancels ignoring statement. This is the classical RAII pattern. 
+Example below:&]
 [s0; &]
 [s0;l321; [C@5;1 #include <Core/Core.h>]&]
 [s7; &]