diff --git a/platform/network-diagnostic-tools.mdx b/platform/network-diagnostic-tools.mdx
index 979db1c8..82f1236b 100644
--- a/platform/network-diagnostic-tools.mdx
+++ b/platform/network-diagnostic-tools.mdx
@@ -10,13 +10,13 @@ That's where network diagnostic tools come in. They help you understand how data
 
 Checkly provides:
 
-- **TCP Dumps:** capture network traffic to inspect packet-level behavior
+- **TCP dumps:** capture network traffic to inspect packet-level behavior
 - **Traceroute report:** trace the path your request takes across the internet
 {/* - **Ping (ICMP):** test basic reachability and measure latency to a target host */}
 
-Whether you're debugging a slow response or tracing a connection failure, these tools help you get to the root of the problem.
+Whether you're debugging a slow response or tracing a connection failure, these tools can help you get to the root of the problem.
 
-## TCP Dumps
+## TCP dumps
 
 TCP dumps give you a detailed look at what's happening at the packet level when a request fails. They capture the packets exchanged between Checkly and your target, letting you analyze things like:
 
@@ -32,7 +32,7 @@ This level of visibility is especially helpful for diagnosing flaky networking b
 TCP dumps are currently only available for API checks.
 </Note>
 
-For checks that fail due to network errors (e.g. DNS resolution issues, TCP handshake failures, connection timeouts), you'll find a Download PCAP button in the *Network Diagnostics* section of the check results page. This gives you a `.pcap` file with the raw packet data from that request.
+For checks that fail due to network errors (e.g. DNS resolution issues, TCP handshake failures, connection timeouts), you'll find a *Download PCAP* button in the **Network Diagnostics** section of the check results page. This gives you a `.pcap` file with the raw packet data from that request.
 
 You can open this file using tools like Wireshark to inspect each packet in detail.
 
@@ -55,7 +55,8 @@ This makes it especially useful for diagnosing:
 Traceroute is currently only available for API checks.
 </Note>
 
-On checks that fail due to network errors (e.g. DNS resolution issues, TCP handshake failures, connection timeouts), a traceroute report is displayed directly in the Network Diagnostics section of the check results page. The table shows each hop, its IP or hostname, along with metrics such as packet loss, latency, and jitter.
+On checks that fail due to network errors (e.g. DNS resolution issues, TCP handshake failures, connection timeouts), a traceroute report is displayed in the **Network Diagnostics** section of the check results page.
+The table shows each hop, its IP or hostname, along with metrics such as packet loss, latency, and jitter.
 
 {/* ### Ping (ICMP)