Final checks

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/irq-tuning-guide/_index.md

@@ -35,6 +35,22 @@ further_reading:
         title: Perf for Linux on Arm (LinuxPerf)
         link: https://learn.arm.com/install-guides/perf/
         type: website
+    - resource:
+        title: Tune network workloads on Arm-based bare-metal instances
+        link: /learning-paths/servers-and-cloud-computing/tune-network-workloads-on-bare-metal/
+        type: learning-path
+    - resource:
+        title: Get started with Arm-based cloud instances
+        link: /learning-paths/servers-and-cloud-computing/csp/
+        type: learning-path
+    - resource:
+        title: Linux kernel IRQ subsystem documentation
+        link: https://www.kernel.org/doc/html/latest/core-api/irq/index.html
+        type: website
+    - resource:
+        title: Microbenchmark and tune network performance with iPerf3
+        link: /learning-paths/servers-and-cloud-computing/microbenchmark-network-iperf3/
+        type: learning-path
 
 ### FIXED, DO NOT MODIFY
 # ================================================================================

content/learning-paths/servers-and-cloud-computing/irq-tuning-guide/checking.md

@@ -1,5 +1,5 @@
 ---
-title: Understand and Analyze network IRQ configuration
+title: Understand and analyze network IRQ configuration
 weight: 2
 
 ### FIXED, DO NOT MODIFY
@@ -10,11 +10,11 @@ layout: learningpathall
 
 In modern cloud environments, network performance is critical to overall system efficiency. Network interface cards (NICs) generate interrupt requests (IRQs) to notify the CPU when data packets arrive or need to be sent. These interrupts temporarily pause normal processing, allowing the system to handle network traffic.
 
-By default, Linux distributes these network interrupts across available CPU cores. However, this distribution is not always optimal for performance:
+By default, Linux distributes these network interrupts across available CPU cores. However, this distribution is not always optimal for performance, for the following reasons:
 
-- High interrupt rates: In busy servers, network cards can generate thousands of interrupts per second
-- CPU cache locality: Processing related network operations on the same CPU core improves cache efficiency
-- Resource contention: When network IRQs compete with application workloads for the same CPU resources, both can suffer
+- High interrupt rates: in busy servers, network cards can generate thousands of interrupts per second
+- CPU cache locality: processing related network operations on the same CPU core improves cache efficiency
+- Resource contention: when network IRQs compete with application workloads for the same CPU resources, both can suffer
 - Power efficiency: IRQ management can help reduce unnecessary CPU wake-ups, improving energy efficiency
 
 Understanding and optimizing IRQ assignment allows you to balance network processing loads, reduce latency, and maximize throughput for your specific workloads.