Minor readme fixes

README.adoc

@@ -1940,7 +1940,7 @@ rm -rf \
 
 ====== PARSEC benchmark hacking
 
-If you end up going inside link:parsec/parsec[] to hack up the benchmark (you will!), these tips will be helpful.
+If you end up going inside link:parsec-benchmark/parsec-benchmark[] to hack up the benchmark (you will!), these tips will be helpful.
 
 Buildroot was not designed to deal with large images, and currently cross rebuilds are a bit slow, due to some image generation and validation steps.
 
@@ -1959,12 +1959,12 @@ before going for the cross compile build.
 * patch Buildroot to work well, and keep cross compiling all the way. This should be totally viable, and we should do it.
 +
 Don't forget to explicitly rebuild PARSEC with:
++
 ....
 ./build -a arm -g -i buildroot_config_fragment_parsec parsec-benchmark-reconfigure
 ....
 +
 You may also want to test if your patches are still functionally correct inside of QEMU first, which is a faster emulator.
-+
 * sell your soul, and compile natively inside the guest. We won't do this, not only because it is evil, but also because Buildroot explicitly does not support it: https://buildroot.org/downloads/manual/manual.html#faq-no-compiler-on-target ARM employees have been known to do this: https://github.com/arm-university/arm-gem5-rsk/blob/aa3b51b175a0f3b6e75c9c856092ae0c8f2a7cdc/parsec_patches/qemu-patch.diff
 
 TODO Buildroot is slow because of the `pkg-generic` `GLOBAL_INSTRUMENTATION_HOOKS` sanitation which go over the entire tree doing complex operations... I no like, in particular `check_bin_arch` and `check_host_rpath`.