memcg-debugging-facility-to-access-dangling-memcgs-fix

fix up Kconfig text

Cc: Glauber Costa <glommer@parallels.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/init/Kconfig b/init/Kconfig
index 0085fc49effeb99229b6a92b539bc7a44741cb77..934ef7519f039c25df30e67c4ef989389fa539fa 100644 (file)
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -930,14 +930,14 @@ config MEMCG_KMEM
          will ever exhaust kernel resources alone.
 
 config MEMCG_DEBUG_ASYNC_DESTROY
-       bool "Memory Resource Controller Debug assynchronous object destruction"
+       bool "Memory Resource Controller Debug asynchronous object destruction"
        depends on MEMCG_KMEM || MEMCG_SWAP
        default n
        help
-         When a memcg is destroyed, the memory
-         consumed by it may not be immediately freed. This is because when some
-         extensions are used, such as swap or kernel memory, objects can
-         outlive the group and hold a reference to it.
+         When a memcg is destroyed, the memory consumed by it may not be
+         immediately freed. This is because when some extensions are used, such
+         as swap or kernel memory, objects can outlive the group and hold a
+         reference to it.
 
          If this is the case, the dangling_memcgs file will show information
          about what are the memcgs still alive, and which references are still