From 684c6c13c68db77ecb4d4d500cba9b50ff8a2bb5 Mon Sep 17 00:00:00 2001
From: olivekl <83081275+olivekl@users.noreply.github.com>
Date: Thu, 20 May 2021 14:28:04 -0400
Subject: [PATCH] Update new_project_guide.md (#5805)

* Update new_project_guide.md

Rewrite instructions under "Temporarily disabling code instrumentation during builds" section for greater clarity.

* Update new_project_guide.md
---
 docs/getting-started/new_project_guide.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md
index cd99e9172..e490d573b 100644
--- a/docs/getting-started/new_project_guide.md
+++ b/docs/getting-started/new_project_guide.md
@@ -253,11 +253,8 @@ alphanumeric characters, underscore(_) or dash(-). Otherwise, they won't run on
 
 ### Temporarily disabling code instrumentation during builds
 
-Sometimes not every 3rd party library might be needed to be instrumented or
-tools are being compiled that just support the target built.
+In some cases, it's not necessary to instrument every 3rd party library or tool that supports the build target. Use the following snippet to build tools or libraries without instrumentation:
 
-If for any reasons part of the build process should not be instrumented
-then the following code snippet can be used for this:
 
 ```
 CFLAGS_SAVE="$CFLAGS"