Update number-methods.md

Author: estevao-schultz-neto-SAP

docs/checks/number-methods.md

@@ -1,29 +1,22 @@
-# code pal for ABAP
-
 [code pal for ABAP](../../README.md) > [Documentation](../check_documentation.md) > [Number of Methods Check](number-methods.md)
 
 ## Number of Methods Check
 
 ### What is the Intent of the Check?
 
-The "Number of Methods" Check counts the number of methods up to a maximum. If there are too many methods in a class, it is probable that the [single responsibility principle](https://en.wikipedia.org/wiki/Single_responsibility_principle) is violated.
+This check counts the number of methods up to a maximum. If there are too many methods in a class, it is an indicator that the [single responsibility principle](https://en.wikipedia.org/wiki/Single_responsibility_principle) is violated.
 
 ### How does the check work?
 
-This check counts `METHODS` and `CLASS-METHODS` within a global or local, `CLASS DEFINITION` or `INTERFACE`. Inherited methods aren't counted, however `REDEFINED METHODS` increment the counter.
-
-### Which attributes can be maintained?
-
-![Attributes](./imgs/number_of_methods.png)
+This check counts `METHODS` and `CLASS-METHODS` within a global or local, `CLASS DEFINITION` or `INTERFACE`. Inherited methods are not counted, however `REDEFINED METHODS` increment the counter.
 
 ### How to solve the issue?
 
 The solution is to split the class or interface into multiple classes or interfaces which then contain less methods.
 
 ### What to do in case of exception?
 
-You can suppress Code Inspector findings generated by this check using the pseudo comment `"#EC NUMBER_METHODS`.  
-The pseudo comment must be placed right after the class definition header.
+In exceptional cases, you can suppress this finding by using the pseudo comment `"#EC NUMBER_METHODS` which should be placed right after the class definition header:
 
 ```abap
 CLASS class_name DEFINITION.   "#EC NUMBER_METHODS