--- a/examples/wireless/wifi-aggregation.cc	Fri Jan 20 14:50:37 2017 +0100
+++ b/examples/wireless/wifi-aggregation.cc	Fri Jan 20 15:11:14 2017 +0100
@@ -40,7 +40,7 @@
 // - station A uses default aggregation parameter values (A-MSDU disabled, A-MPDU enabled with maximum size of 65 kB);
 // - station B doesn't use aggregation (both A-MPDU and A-MSDU are disabled);
 // - station C enables A-MSDU (with maximum size of 8 kB) but disables A-MPDU;
-// - station C uses two-level aggregation (A-MPDU with maximum size of 32 kB and A-MSDU with maximum size of 4 kB).
+// - station D uses two-level aggregation (A-MPDU with maximum size of 32 kB and A-MSDU with maximum size of 4 kB).
 //
 // Packets in this simulation aren't marked with a QosTag so they
 // are considered belonging to BestEffort Access Class (AC_BE).
@@ -49,7 +49,7 @@
 // Example: ./waf --run "wifi-aggregation --distance=10 --enableRts=0 --simulationTime=20"
 //
 // The output prints the throughput measured for the 4 cases/networks decribed above. When default aggregation parameters are enabled, the
-// maximum A-MPDU size is 65 kB and the throughput is maximal. When aggregation is disabled, the thoughput is about the half of the
+// maximum A-MPDU size is 65 kB and the throughput is maximal. When aggregation is disabled, the throughput is about the half of the
 // physical bitrate as in legacy wifi networks. When only A-MSDU is enabled, the throughput is increased but is not maximal, since the maximum
 // A-MSDU size is limited to 7935 bytes (whereas the maximum A-MPDU size is limited to 65535 bytes). When A-MSDU and A-MPDU are both enabled
 // (= two-level aggregation), the throughput is slightly smaller than the first scenario since we set a smaller maximum A-MPDU size.