additional feedbacks

Author: sachin-sumologic

docs/integrations/web-servers/apache-tomcat.md

@@ -28,7 +28,7 @@ As part of the app installation process, the following fields will created by de
 * `webserver_farm`
 * `pod`
 
-Additionally, if you are using Apache Tomcat in the Kubernetes environment, these following additional fields will be created by default as a part of app installation process:
+Additionally, if you are using Apache Tomcat in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_webserver_system`
@@ -256,8 +256,8 @@ This section explains the steps to collect Apache Tomcat logs from a Kubernetes
 1. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
 1. Verify logs in Sumo Logic.
 
-<br />**FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Apache Tomcat Web Server Application Components named as **AppObservabilityApacheTomcatWebserverFER**
-<br />
+<br/>**FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Apache Tomcat Web Server Application Components named as **AppObservabilityApacheTomcatWebserverFER**
+<br/>
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/web-servers/apache.md

@@ -122,7 +122,7 @@ As part of the app installation process, the following fields will created by de
 * `webserver_system`
 * `webserver_farm`
 
-Additionally, if you are using Apache in the Kubernetes environment, these following additional fields will be created by default as a part of app installation process:
+Additionally, if you are using Apache in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_webserver_system`
@@ -246,9 +246,9 @@ This section explains the steps to collect Apache logs from a Kubernetes environ
    kubectl describe pod <apache_pod_name>
    ```
    The Sumo Logic Kubernetes Collection process will automatically capture the logs from `stdout`/`stderr` and will send the logs to Sumo Logic. For more information on deploying the Sumo Logic-Kubernetes-Collection, please see [this page](/docs/integrations/containers-orchestration/kubernetes#collecting-metrics-and-logs-for-the-kubernetes-app).
-<br />
+<br/>
 **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Apache Web Server Application Components named as **AppObservabilityApacheWebserverFER**
-<br />
+<br/>
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/web-servers/haproxy.md

@@ -86,7 +86,7 @@ As part of the app installation process, the following fields will created by de
   * `proxy_cluster`
   * `pod`
 
-Additionally, if you are using Haproxy in the Kubernetes environment, these following additional fields will be created by default as a part of app installation process:
+Additionally, if you are using Haproxy in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
   * `pod_labels_component`
   * `pod_labels_environment`
   * `pod_labels_proxy_system`
@@ -203,9 +203,9 @@ This section explains the steps to collect HAProxy logs from a Kubernetes enviro
    kubectl describe pod <haproxy_pod_name>
    ```
   5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-<br />
+<br/>
 **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Proxy Application Components named as **AppObservabilityHaproxyFER**
-<br />
+<br/>
 </TabItem>
 <TabItem value="non-k8s">
 

docs/integrations/web-servers/nginx-ingress.md

@@ -37,7 +37,7 @@ Configuring log and metric collection for the Nginx Ingress app includes the fol
 
 ### Step 1: Configure fields in Sumo Logic
 
-Additionally, if you are using Nginx Ingress in the Kubernetes environment, Following fields will be created automatically as a part of app installation process:
+Additionally, if you are using Nginx Ingress in the Kubernetes environment, Following fields will be created automatically as a part of the app installation process:
 
 * `pod_labels_component`
 * `pod_labels_environment`
@@ -68,9 +68,9 @@ It’s assumed that you are using the latest helm chart version if not please up
   **Do not modify** the following values set by this configuration as it will cause the Sumo Logic app to not function correctly.
      * `component: “webserver”`. This value is used by Sumo Logic apps to identify application components.
      * `webserver_system: “nginx_ingress”`. This value identifies the database system.
-<br />
+<br/>
 **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Nginx Application Components named as **AppObservabilityNginxIngressWebserverFER**
-<br />
+<br/>
 ## Installing the Nginx Ingress app
 
 This section demonstrates how to install the Nginx Ingress app. These instructions assume you have already set up the collection as described above.

docs/integrations/web-servers/nginx.md

@@ -63,7 +63,7 @@ As part of the app installation process, the following fields will created by de
 * `webserver_farm`
 * `pod`
 
-Additionally, if you are using Nginx in the Kubernetes environment, these following additional fields will be created by default as a part of app installation process:
+Additionally, if you are using Nginx in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_webserver_system`
@@ -197,9 +197,9 @@ This section explains the steps to collect Nginx logs from a Kubernetes environm
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
-<br />
+<br/>
 **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Nginx Application Components named as **AppObservabilityNginxWebserverFER**
-<br />
+<br/>
 </TabItem>
 <TabItem value="non-k8s">