Spacing in Q&A

README.md

@@ -32,20 +32,31 @@ Also frzr ships with utilities that are meant to regenerate bootloader entries w
 ## Q&A
 
 __Q__ Are there limitations on what systems can be deployed?
+
 __A__ Yes, supported systems must support booting from a btrfs subvolume.
 
+
 __Q__ Is the distro limited in what it can do once installed?
+
 __A__ Not by default, every limitation is decided by maintainers of that distro.
 
+
 __Q__ Is it easy to create a proof-of-concept distro that is compatible with frzr?
+
 __A__ Absolutely: frzr wants to be hackable and easy to work with in every aspect: just create a btrfs subvolume and run your preferred command to write a rootfs (debootstrap, pacstrap or whatever). Then create a snapshot of it with btrfs send and that file can be deployed on real hardware!
 
+
 __Q__ Can a distro be shipped with its own kernel?
+
 __A__ Yes and this is the preferred method. The user can boot a deployment only if such deployment comes with its own kernel or the user has installed one
 already via the dedicated *frzr kernel* tool!
 
+
 __Q__ Are there rules to follow?
+
 __A__ There are conventions: for example a distro should __NOT__ assume it's the only distro installed, and *SHOULD NOT* cause harm to other deployments for example by writing to the efi partition.
 
+
 __Q__ Can data be shared among different distributions?
+
 __A__ This depends on the distro: the easiest way probably is using systemd-homed and mount in /home the home directory.