Fix. Readme updated.

readme.txt

@@ -326,15 +326,13 @@ This is required for the Security FireWall to function properly. Plugins that ar
 21. **Malware scanner results - cured**. There is a list of files that have been automatically cured.
 22. **Malware scanner results - frontend malware**. There is a list of frontend pages that contains malicious HTML/JavaScript code.
 23. **Malware scanner results - unsafe permissions**. There is a list of files that could be reached by a hacker because of unsafe permission set.
-24. **Malware scanner results - file monitoring**. There is a list of important files and their snapshots. You can use this to know if they were changed.
-25. **Malware scanner results - snapshot**. How the important file snapshot looks.
-26. **Malware scanner results - PFD report**. How the PDF report of scan results looks.
-27. **Templates interface**. Using this interface you can apply the settings from another site of your CleanTalk account or a template saved before.
-28. **Example of blocking page - Firewall**. If the visitor IP is in hazardous net list or blacklisted in your personal list, he will see this screen.
-29. **Example of blocking page - XSS**. If the visitor attempts to implement XXS, he will see this screen.
-30. **Example of blocking page - SQL**. If the visitor attempts to implement SQL injection, he will see this screen.
-31. **Example of blocking page - Brute-Force**. If the visitor tried to use wrong credentials for many times, he will see this screen.
-32. **Example of blocking page - Traffic Control**. If the visitor has requested site pages too often, he will see this screen.
+24. **Malware scanner results - PFD report**. How the PDF report of scan results looks.
+25. **Templates interface**. Using this interface you can apply the settings from another site of your CleanTalk account or a template saved before.
+26. **Example of blocking page - Firewall**. If the visitor IP is in hazardous net list or blacklisted in your personal list, he will see this screen.
+27. **Example of blocking page - XSS**. If the visitor attempts to implement XXS, he will see this screen.
+28. **Example of blocking page - SQL**. If the visitor attempts to implement SQL injection, he will see this screen.
+29. **Example of blocking page - Brute-Force**. If the visitor tried to use wrong credentials for many times, he will see this screen.
+30. **Example of blocking page - Traffic Control**. If the visitor has requested site pages too often, he will see this screen.