Update snmp-performance-monitoring.mdx

style changes

src/content/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring.mdx

@@ -67,7 +67,7 @@ Before you can start, you'll need to [sign up for a New Relic account](https://n
     </Collapser>
 
     <Collapser id="snmp" title="SNMP devices prerequisites">
-      Target devices must be configured to accept SNMP polling from the agent's host IP address. Some samples of basic SNMP configurations can be found here (this is not an all-inclusive list):
+     You must configure target devices to accept SNMP polling from the agent's host IP address. You can find some samples of basic SNMP configurations here (this is not an all-inclusive list):
       * Cisco
         * [IOS](https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/snmp/configuration/xe-16/snmp-xe-16-book/nm-snmp-cfg-snmp-support.html#GUID-98F0633A-F3BA-4C59-B886-F523099D3AE5)
         * [NX-OS](https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/4_2/nx-os/system_management/configuration/guide/sm_nx_os_cli/sm_9snmp.html#wp1056898)
@@ -323,7 +323,7 @@ Our network monitoring container supports all major versions of SNMP (v1, v2c, a
 
           3. Edit the `snmp-base.yaml` file and define the `discovery.cidrs` and `discovery.default_communities` attributes to appropriate values for your network.
             <Callout variant="tip">
-              We recommend to set `discovery.add_mibs: true` to automate the addition of all discovered MIBs into the `global.mibs_enabled` attribute. Additionally, it is recommended to set `discovery.check_all_ips: true` to avoid discovery issues on [devices with tightened security postures](/docs/network-performance-monitoring/troubleshooting/snmp-discovery-no-devices).
+              We recommend setting `discovery.add_mibs: true` to automate the addition of all discovered MIBs into the `global.mibs_enabled` attribute. Additionally, we recommend setting `discovery.check_all_ips: true` to avoid discovery issues on [devices with tightened security postures](/docs/network-performance-monitoring/troubleshooting/snmp-discovery-no-devices).
             </Callout>
 
           4. Start the network monitoring agent to poll target devices and listen for incoming SNMP trap messages. Replace `$CONTAINER_SERVICE` with a unique name for the container and substitute`$YOUR_NR_LICENSE_KEY` and `$YOUR_NR_ACCOUNT_ID` with your values:
@@ -344,8 +344,8 @@ Our network monitoring container supports all major versions of SNMP (v1, v2c, a
             ```
 
             <Callout variant="tip">
-              It is not necessary to run a dedicated agent for trap collection as all SNMP polling agents will run a passive listener. By default the container will listen on the host's port 162 (UDP); but you can change the [published port](https://docs.docker.com/network/#published-ports) mapping in the docker run command - `-p 162:1620/udp`.
-              If you do want a dedicated container, you can follow the steps in [this section](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring/#optional-installation-for-snmp-traps).
+              It isn't necessary to run a dedicated agent for trap collection as all SNMP polling agents will run a passive listener. By default the container will listen on the host's port 162 (UDP); but you can change the [published port](https://docs.docker.com/network/#published-ports) mapping in the docker run command - `-p 162:1620/udp`.
+              If you want to set up a dedicated container, you can follow the steps in [this section](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring/#optional-installation-for-snmp-traps).
             </Callout>
 
           5. Investigate your network performance data in the New Relic <InlinePopover type="networkMonitoring" /> UI.
@@ -369,10 +369,10 @@ Our network monitoring container supports all major versions of SNMP (v1, v2c, a
 
           3. Edit the `snmp-base.yaml` file and define the `discovery.cidrs` and `discovery.default_communities` attributes to appropriate values for your network.
             <Callout variant="tip">
-              We recommend to set `discovery.add_mibs: true` to automate the addition of all discovered MIBs into the `global.mibs_enabled` attribute. Additionally, it is recommended to set `discovery.check_all_ips: true` to avoid discovery issues on [devices with tightened security postures](/docs/network-performance-monitoring/troubleshooting/snmp-discovery-no-devices).
+              We recommend setting `discovery.add_mibs: true` to automate the addition of all discovered MIBs into the `global.mibs_enabled` attribute. Additionally, we recommend setting `discovery.check_all_ips: true` to avoid discovery issues on [devices with tightened security postures](/docs/network-performance-monitoring/troubleshooting/snmp-discovery-no-devices).
             </Callout>
 
-          4. Rootless Podman containers are not able to bind to ports under 1024. To handle packet redirection for trap messages, you will need to create an `iptables` rule that targets packets arriving on UDP port 162:
+          4. Rootless Podman containers arn't able to bind to ports under 1024. To handle packet redirection for trap messages, you'll need to create an `iptables` rule that targets packets arriving on UDP port 162:
             ```shell
             sudo iptables -t nat -A PREROUTING -p udp --dport 162 -j REDIRECT --to-port 1620
             ``` 
@@ -393,22 +393,22 @@ Our network monitoring container supports all major versions of SNMP (v1, v2c, a
               nr1.snmp
             ```
             <Callout variant="tip">
-              It is not necessary to run a dedicated agent for trap collection as all SNMP polling agents will run a passive listener. By default the container will listen on the host's port 162 (UDP); but you can change the [published port](https://docs.docker.com/network/#published-ports) mapping in the docker run command - `-p 162:1620/udp`.
-              If you do want a dedicated container, you can follow the steps in [this section](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring/#optional-installation-for-snmp-traps).
+              It isn't necessary to run a dedicated agent for trap collection as all SNMP polling agents will run a passive listener. By default, the container will listen on the host's port 162 (UDP), but you can change the [published port](https://docs.docker.com/network/#published-ports) mapping in the docker run command - `-p 162:1620/udp`.
+              If want to set up a dedicated container, you can follow the steps in [this section](/docs/network-performance-monitoring/setup-performance-monitoring/snmp-performance-monitoring/#optional-installation-for-snmp-traps).
             </Callout>
 
           6. Investigate your network performance data in the New Relic <InlinePopover type="networkMonitoring" /> UI.
         </TabsPageItem>
 
         <TabsPageItem id="linuxInstall">
-          1. Depending on your package manager, use of the commands below to install `ktranslate`
+          1. Depending on your package manager, use one of the commands below to install `ktranslate`
 
-            **Yum**:
+            * Yum:
             ```shell
               curl -s https://packagecloud.io/install/repositories/kentik/ktranslate/script.rpm.sh | sudo bash && \
               sudo yum install ktranslate
             ```
-            **Apt**:
+            * Apt:
             ```shell
               curl -s https://packagecloud.io/install/repositories/kentik/ktranslate/script.deb.sh | sudo bash && \
               sudo apt-get install ktranslate