Update number-executable-statements.md

Author: estevao-schultz-neto-SAP

docs/checks/number-executable-statements.md

@@ -1,31 +1,24 @@
-# code pal for ABAP
-
 [code pal for ABAP](../../README.md) > [Documentation](../check_documentation.md) > [Number of Executable Statements Check](number-executable-statements.md)
 
 ## Number of Executable Statements Check
 
 ### What is the Intent of the Check?
 
-The "Number of Executable Statements" Check counts the number of non-declarative ABAP Statements per modularization unit up to a maximum. If there are too many statements in a code block, it is probable that the [Single Responsibility Principle](https://en.wikipedia.org/wiki/Single_responsibility_principle) is violated.
+This check counts the number of non-declarative ABAP Statements per modularization unit up to a maximum. If there are too many statements in a code block, it is an indicator that the [Single Responsibility Principle](https://en.wikipedia.org/wiki/Single_responsibility_principle) is violated.
 
-A high number of executable statements is an indicator that the source code is not readable anymore in a way that maintaining and extending the code can be done efficiently. In addition, the risk of introducing bugs is higher with a high number of executable statements in the code.
+A high number of executable statements is an indicator that the source code might be not readable. In addition, the risk of introducing bugs is higher with a high number of executable statements in the code.
 
 ### How does the check work?
 
 The check counts the number of non-declarative ABAP Statements, that is ABAP Statements without data declarations, program introduction statements, etc.
 
-### Which attributes can be maintained?
-
-![Attributes](./imgs/number_of_executable_statements.png)
-
 ### How to solve the issue?
 
 Modularize your code. Follow the [Single Responsibility Principle](https://en.wikipedia.org/wiki/Single_responsibility_principle). Split the method into other smaller methods (create service classes whenever possible).
 
 ### What to do in case of exception?
 
-You can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC CI_NOES`.  
-The pseudo comment must be placed right after the `ENDMETHOD` statement.
+In exceptional cases, you can suppress this finding by using the pseudo comment `"#EC CI_NOES` which should be placed right after the `ENDMETHOD` statement:
 
 ```abap
 METHOD method_name.