From 02e9055cfed080da59b8528b996bcb07bd5e2429 Mon Sep 17 00:00:00 2001
From: Chandan Mali <88288584+Chandanmali@users.noreply.github.com>
Date: Wed, 25 Oct 2023 23:11:45 +0530
Subject: [PATCH] Update CONCEPTS.md

---
 doc/CONCEPTS.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/CONCEPTS.md b/doc/CONCEPTS.md
index abe7bef7..4e862d69 100644
--- a/doc/CONCEPTS.md
+++ b/doc/CONCEPTS.md
@@ -7,7 +7,7 @@ The text below is under construction.
 This page describes leak tracking concepts.
 See other information on memory leaks [here](../README.md).
 
-Before reading about leak tracking, understand [Dart memory concepts](https://docs.flutter.dev/development/tools/devtools/memory#basic-memory-concepts).
+Before reading about leak-tracking, understand [Dart memory concepts](https://docs.flutter.dev/development/tools/devtools/memory#basic-memory-concepts).
 
 ## Addressed leak types
 
@@ -50,7 +50,7 @@ the following types of leaks:
 ### Disposed, but not GCed, without path (not-GCed-without-path)
 
 - **Definition**: an object
-   was disposed and not GCed when expected, but retaining path
+   was disposed and not GCed when expected, but the retaining path
    is not detected; that means that the object will be most likely GCed in
    the next GC cycle,
    and the leak will convert to [GCed-late](#gced-late) leak.
@@ -62,7 +62,7 @@ something is wrong with the tool.
 
 ## Culprits and victims
 
-If you have a set of not-GCed objects, some of them (victims)
+If you have a set of non-GCed objects, some of them (victims)
 might not be GC-ed because they are held by others (culprits).
 Normally, to fix the leaks, you need to only fix the culprits.