Documentation review fixes. (#2428)

Signed-off-by: Tomas Langer <tomas.langer@oracle.com>

docs/mp/security/03_configuration-secrets.adoc

@@ -29,7 +29,7 @@ This example configures a basic authentication provider and
 
 == Protecting Configuration Secrets
 
-In Helidon MP, the config encryption filter ** enabled by default**. However, if you don't configure it, the filter
+In Helidon MP, the config encryption filter is ** enabled by default**. However, if you don't configure it, the filter
  only supports a template for aliasing that checks that no clear text passwords are
  present (template ${CLEAR=...}.
 

docs/shared/security/helidon-endpoints.adoc

@@ -38,7 +38,7 @@ The following section describes configuration of such protection using configura
 The configuration is usually placed under `security.web-server` (this can be
 customized in Helidon SE).
 
-The following example shows an example we will explain in detail:
+The following shows an example we will explain in detail:
 
 [source,yaml]
 .application.yaml
@@ -70,7 +70,7 @@ security:
 <6> Protection of `/openapi` and all nested paths with `openapi` scope required
 <7> Protection of static content configured on `/static` path with either `user` or `monitor` role required
 
-If you need to use a properties file, such as for `microprofile-config.properties`, you
+If you need to use a properties file, such as `microprofile-config.properties`, you
 can convert the file by using index based numbers for arrays, such as:
 
 [source,properties]

examples/security/basic-auth-with-static-content/README.md

@@ -1,6 +1,6 @@
 # Web Server Integration and Basic Authentication
 
-This example demonstrates Integration of WebServer
+This example demonstrates integration of Web Server
 based application with Security component and Basic authentication (from HttpAuthProvider), including
 protection of a static resource.