md preview did show troubleshooting images but mkdocs did not, adapting link...

docs/aims2/troubleshooting.md

@@ -77,13 +77,13 @@ This section serves as a log of strange things we saw AIMS2 doing, for the recor
 
 ### Too little memory
 
-![too_little_memory](/docs/assets/images/too_little_memory.jpg)
+![too_little_memory](../assets/images/too_little_memory.jpg)
 
 Due somehow to an RPM update going wrong. Solved by removing and reinstalling the very same `aims2-loaders` RPM, and restarting `aims2sync` daemon with `service aims2sync restart`.
 
 ### You need to load the kernel first; alloc magic is broken
 
-![load_kernel_first_alloc_magic](/docs/assets/images/load_kernel_first_alloc_magic.jpg)
+![load_kernel_first_alloc_magic](../assets/images/load_kernel_first_alloc_magic.jpg)
 
 AIMS2 recently uploaded image is not yet available on disk, so the client will not find the missing TFTP file on `/tftpboot/aims/boot/IMAGENAME`; actually the path will not even exist