GEM5 is not failed action

README.md

@@ -48,11 +48,11 @@ See the [getting started section](getting-started.md) for further details.
     1.  [modprobe](modprobe.md)
     1.  [X11](x11.md)
     1.  [Count boot instructions](count-boot-instructions.md)
+    1.  [GEM5](gem5.md)
     1.  [ftrace](ftrace.md)
     1.  [Device tree](device-tree.md)
 1.  Failed action
     1.  [Record and replay](record-and-replay.md)
-    1.  [GEM5](gem5.md)
 1.  Insane action
     1.  [Run on host](run-on-host.md)
     1.  [Hello host](hello_host/)

gem5.md

@@ -6,7 +6,7 @@ GEM5 is a system simulator, much like QEMU: <http://gem5.org/>
 
 Vs QEMU:
 
--   advantage: simulates a generic more realistic CPU pipelined and optionally out of order CPU cycle by cycle, including a realistic DRAM memory access model with latencies, caches and page table manipulations. This allows us to:
+-   advantage: simulates a generic more realistic pipelined and optionally out of order CPU cycle by cycle, including a realistic DRAM memory access model with latencies, caches and page table manipulations. This allows us to:
 
     - do much more realistic performance benchmarking with it, which makes absolutely no sense in QEMU, which is purely functional
     - make functional cache observations, e.g. to use Linux kernel APIs that flush memory like DMA, which are crucial for driver development. In QEMU, the driver would still work even if we forget to flush caches.