linguistic-corrections

Author: WriteMayur

src/install/mysql/aurora/enable-mysql-server.mdx

@@ -31,6 +31,6 @@ To capture data from the MySQL integration, you must first create a MySQL user w
    mysql -e "GRANT PROCESS ON *.* TO 'newrelic'@'AWS-or-Azure-instance-name' WITH MAX_USER_CONNECTIONS 5;"
    ```
 
-   <Callout variant="tip" title="Tip">
+   <Callout variant="tip">
       Each command sets a maximum of 5 user connections.
    </Callout>

src/install/mysql/aurora/query-monitoring.mdx

@@ -14,7 +14,11 @@ Follow these instructions to enable Performance Schema for Aurora MySQL:
     2. Select `Parameter groups` and either:
 
         * Create two new DB Parameter Groups: one for the Aurora cluster and another for the Aurora instance, with a family matching your Aurora MySQL version For example, `aurora-mysql8.0`.
-        * Modify existing custom DB Parameter Groups already associated with your Aurora DB setup. Do not modify the default parameter group.
+        * Modify existing custom DB Parameter Groups already associated with your Aurora DB setup. 
+
+            <Callout variant="tip">
+                Don't modify the default parameter group.
+            </Callout>
 
     3. Configure the DB Parameter Groups by setting the following consumer parameters:
 
@@ -30,9 +34,12 @@ Follow these instructions to enable Performance Schema for Aurora MySQL:
             performance_schema_max_sql_text_length = 4096
         ```
 
-    4. Associate the modified or newly created DB Parameter Groups with your Aurora DB cluster and instance. (Select your DB cluster and instance in the RDS console, click `Modify`, and find the `DB instance parameter group` and `DB cluster parameter group` settings.)
+    4. Associate the parameter groups with your Aurora DB cluster and instance: 
+        
+        * In the RDS console, select your DB cluster or instance and click Modify.
+        * In DB instance parameter group and DB cluster parameter group, choose the groups you edited. 
 
-    5. Reboot your Aurora DB instance for the changes to take effect. For more information, refer to [Working with DB Parameter Groups documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html).
+    5. Reboot your Aurora DB instance for the changes to take effect. For more information, refer to AWS Documentation on [Working with DB Parameter Groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html).
 
 2. To enable query-level monitoring, you must also enable the Performance Schema consumers and instruments using one of the following methods:
 
@@ -56,13 +63,7 @@ Follow these instructions to enable Performance Schema for Aurora MySQL:
                 GRANT EXECUTE ON newrelic.* TO 'newrelic'@'AWS-or-Azure-instance-name';
             ```
 
-        2. To set up procedure for runtime activation of consumers and instruments:
-        
-            <Callout variant="tip">
-            
-                New Relic recommends that you create the following procedure to grant the Agent the ability to enable `performance_schema.events_* consumers` and `instruments` at runtime.
-
-            </Callout>
+        2. To create stored procedure as New Relic agent uses this procedure to enable the required `performance_schema` consumers and instruments at runtime:
 
             ```sql
                 DELIMITER $$
@@ -84,7 +85,7 @@ Follow these instructions to enable Performance Schema for Aurora MySQL:
         >
 
             <Callout variant="tip">
-                Grants the monitoring user direct UPDATE privileges on `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. This allows the New Relic agent to manage required Performance Schema settings directly.
+                Grants the monitoring user `UPDATE` privileges on the `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. The New Relic agent uses these privileges to manage Performance Schema settings.
             </Callout>
 
                 ```sql

src/install/mysql/linux/query-monitoring.mdx

@@ -131,13 +131,7 @@ Query-level monitoring is supported only on MySQL version 8.0 and later.
                 GRANT EXECUTE ON newrelic.* TO 'newrelic'@'localhost';
             ```
 
-        2. To set up procedure for runtime activation of consumers and instruments:
-        
-            <Callout variant="tip">
-            
-                Newrelic recommends that you create the following procedure to grant the Agent the ability to enable performance_schema.events_* `consumers` and `instruments` at runtime.
-
-            </Callout>
+        2. To create the procedure to allow the New Relic agent to `enable performance_schema.events_*` `consumers` and `instruments` at runtime:
 
             ```sql
                 DELIMITER $$
@@ -159,7 +153,7 @@ Query-level monitoring is supported only on MySQL version 8.0 and later.
         >
 
             <Callout variant="tip">
-                Grants the monitoring user direct UPDATE privileges on `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. This allows the New Relic agent to manage required Performance Schema settings directly.
+                Grants the monitoring user `UPDATE` privileges on the `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. The New Relic agent uses these privileges to manage Performance Schema settings.
             </Callout>
 
                 ```sql

src/install/mysql/rds/query-monitoring.mdx

@@ -3,7 +3,7 @@ componentType: default
 headingText: (Optional) Enable MySQL query-level monitoring 
 ---
 
-Configure your integration to enable query-level monitoring in New Relic. By setting the appropriate parameters, you can capture detailed metrics on query performance, which allows you to identify and optimize slow or inefficient queries. For more information, refer [Query-Level monitoring](/docs/infrastructure/infrastructure-data/query-level-monitoring).
+Configure your integration to enable query-level monitoring in New Relic. By setting the appropriate parameters, you can capture detailed metrics on query performance, which allows you to identify and optimize slow or inefficient queries. For more information, refer to [Query-Level monitoring](/docs/infrastructure/infrastructure-data/query-level-monitoring).
 
 Follow these instructions to enable the Performance Schema. The configuration method outlined here applies specifically to MySQL RDS.
 
@@ -51,13 +51,7 @@ Follow these instructions to enable the Performance Schema. The configuration me
                 GRANT EXECUTE ON newrelic.* TO 'newrelic'@'AWS-or-Azure-instance-name';
             ```
 
-        2. To set up procedure for runtime activation of consumers and instruments:
-        
-            <Callout variant="tip">
-            
-                New Relic recommends that you create the following procedure to grant the Agent the ability to enable `performance_schema.events_* consumers` and `instruments` at runtime.
-
-            </Callout>
+        2. To create the procedure to allow the New Relic agent to `enable performance_schema.events_*` `consumers` and `instruments` at runtime:
 
             ```sql
                 DELIMITER $$
@@ -79,7 +73,7 @@ Follow these instructions to enable the Performance Schema. The configuration me
         >
 
             <Callout variant="tip">
-                Grants the monitoring user direct UPDATE privileges on `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. This allows the New Relic agent to manage required Performance Schema settings directly.
+                Grants the monitoring user `UPDATE` privileges on the `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. The New Relic agent uses these privileges to manage Performance Schema settings.
             </Callout>
 
                 ```sql

src/install/mysql/windows/query-monitoring.mdx

@@ -73,11 +73,7 @@ Query-level monitoring is supported only on MySQL version 8.0 and later.
                GRANT EXECUTE ON newrelic.* TO 'newrelic'@'AWS-or-Azure-instance-name';
          ```
 
-      2. To set up procedure for runtime activation of consumers and instruments:
-
-         <Callout variant="tip">
-         
-               New Relic recommends that you create the following procedure to grant the Agent the ability to enable `performance_schema.events_* consumers` and `instruments` at runtime.
+      2. To create the procedure to allow the New Relic agent to `enable performance_schema.events_*` `consumers` and `instruments` at runtime:
 
          </Callout>
 
@@ -101,7 +97,7 @@ Query-level monitoring is supported only on MySQL version 8.0 and later.
       >
 
          <Callout variant="tip">
-            Grants the monitoring user direct UPDATE privileges on `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. This allows the New Relic agent to manage required Performance Schema settings directly.
+            Grants the monitoring user `UPDATE` privileges on the `performance_schema.setup_consumers` and `performance_schema.setup_instruments` tables. The New Relic agent uses these privileges to manage Performance Schema settings.
          </Callout>
 
                ```sql