More FaQs

README.md

@@ -40,7 +40,7 @@ Lines starting with `@!` are treated as repliqate meta commands:
 
 Answers to a few possible questions:
 
-### What at the `inuse-*qcow2` and `vd.img` files 
+### What are the `inuse-*qcow2` and `vd.img` files 
 
 These are temporary disk images that are used while repliqate is running. By default, repliqate deletes these once the script has run, however adding the metacommand
 `@!preserve` anywhere in the build script will cause repliqate to skip the cleanup - these disk images can then be mounted and explored further (e.g. to debug an issue)
@@ -50,4 +50,9 @@ These are temporary disk images that are used while repliqate is running. By def
 We do use Docker as part of our continuous build processes. However, we have chosen to develop repliqate to meet two specific requirements:
 
 1. Standlone and Unprivileged - [Docker requires a whole host of permissions](https://docs.docker.com/engine/install/linux-postinstall/) to be granted, and privileged services to be setup, in order for containers to be run by non-root users. Our goal with repliqate was to provide a standalone way of reproducing builds.
-2. Redundancy - Having a tool that is entirely separate from our build containers (and the Docker infrastructure that supports them) allows us have both keep each other in check.
+2. Redundancy - Having a tool that is entirely separate from our build containers (and the Docker infrastructure that supports them) allows us have both keep each other in check.
+
+### Builds are slow. Can they be sped up?
+
+Virtualization is inherently slower than running on bare metal. We consider the speed overhead worth it for complete isolation of the build environment. However, if you are considering using repliqate for 
+something more speed-sensitive then you may want to consider enabling and using qemu with [kvm](https://wiki.qemu.org/Features/KVM) enabled.