diff --git a/content/21.From-Audio/to-fix-transcription/AppSec/Why SAST rules need to be customized.md b/content/21.From-Audio/to-fix-transcription/AppSec/Why SAST rules need to be customized.md
index b8629c9..b52d503 100644
--- a/content/21.From-Audio/to-fix-transcription/AppSec/Why SAST rules need to be customized.md	
+++ b/content/21.From-Audio/to-fix-transcription/AppSec/Why SAST rules need to be customized.md	
@@ -1,9 +1,7 @@
 **Why SAST rules need to be customized**
 
-The reason why it is so important to customize static analysis engines is because we need to teach the tools where resources and things are. Where the assets are, what matters, and what we really want to know.
+It is very important to customize static analysis engines because we need to teach the tools where resources and assets are, what matters, and what we really want to know.
 
-So by customizing rules, it allows the people who understand the application to actually indicate the areas of concern. And eventually what you have is highly defensible, highly robust results that when they occur, they can be actionable.
+Customizing rules allows the people who understand the application to indicate the areas of real concern. This eventually gives you highly defensible, and highly robust, results that are actionable when they occur.
 
-By not allowing customization, making customization hard or a second class citizen, what the tools do is they promote the idea that it is a one button click which will do the job of which of course it doesn't.
-
-And it really short changes the quality and the value of those engines capabilities.
\ No newline at end of file
+By not allowing customization, by making it difficult, or by ignoring the importance of customization, the tools promote the idea that one click of a button will do the job, which of course is not the case. Not allowing customization undermines the quality and the value of those engines' capabilities.