fix: some comments from PM

Author: ohad-perets

content/nap-waf/v4/configuration-guide/configuration.md

@@ -661,7 +661,7 @@ To prevent brute force attacks, NGINX App Protect WAF monitors IP addresses, use
 When brute force patterns are detected, the NGINX App Protect WAF policy either trigger an alarm or block the attack if the failed 
 login attempts reached a maximum threshold for a specific username or coming from a specific IP address.
 To enable brute force protection, at least one login page must be created. 
-The login page entity is created separately and is not included in the brute force configuration block
+The login page entity is created separately and is not included in the brute force configuration block.
 
 ---
 
@@ -724,7 +724,7 @@ Example1: A single brute force configuration is applied universally to all login
 ```
 
 Example2: Different brute force configurations can be defined for individual login pages. 
-          with each configuration referencing a specific login page.
+          With each configuration referencing a specific login page.
 ```json
 {
     "policy": {

content/nap-waf/v5/configuration-guide/configuration.md

@@ -863,7 +863,7 @@ Example1: A single brute force configuration is applied universally to all login
 ```
 
 Example2: Different brute force configurations can be defined for individual login pages. 
-          with each configuration referencing a specific login page.
+          With each configuration referencing a specific login page.
 ```json
 {
     "policy": {