fix a few things

docs/localization/keyboard-multiple-layouts.md

@@ -1,15 +1,14 @@
 Using multiple keyboard layouts
 ===============================
 
-The [official Qubes OS docs](https://www.qubes-os.org/faq/#my-keyboard-layout-settings-are-not-behaving-correctly-what-should-i-do) only cover how to change the layout *globally* - ie. both for dom0 and VMs, with a *single* layout.
+The [official Qubes OS faq entry](https://www.qubes-os.org/faq/#my-keyboard-layout-settings-are-not-behaving-correctly-what-should-i-do) only covers how to change the layout *globally* - ie. both for dom0 and VMs, with a *single* layout.
 
-
+This document shows several ways of using *multiple* keyboard layouts and being able to *quickly* switch between them.
-This document depicts several ways of using *multiple* keyboard layouts and being able to *quickly* switch between them.
 
 Recommended setup
 -----------------
 
-Run `setxkbmap` in *each* VM (dom0 will be configured with only one layout, since running `setxkbmap...` in dom0 would probably interfere with the VMs).
+Run `setxkbmap` in *each* VM. Dom0 stays untouched (running `setxkbmap` in dom0 too will interfere with the VM's `setxkbmap` setup).
 
 For instance the following command would alternate between the US English and the Bulgarian phonetic layout when pressing both shift keys:
 
@@ -27,7 +26,7 @@ Terminal=false
 Type=Application
 ~~~
 
-If you prefer to have per-VM rather than per-template `setxkbmap` commands create a `/rw/config/setxkbmap.desktop` with the same content as above and add the following line to `/rw/config/rc.local`:
+If you prefer to have a per-vm setup rather than per-template, create a `/rw/config/setxkbmap.desktop` with the same content as above and add the following line to `/rw/config/rc.local`:
 
 ~~~
 cp /rw/config/setxkbmap.desktop /etc/xdg/autostart
@@ -41,10 +40,10 @@ Alternatively, you could add the `setxkbmap` command to your profile's `.bashrc`
 Alternative setups
 ------------------
 
-- Configuring a keyboard shortcut in dom0 that would issue `qvm-run vname 'setxkbmap...'` to the VM whose window is under the mouse pointer (using `xprop -id $(xdotool getactivewindow`) ). This is a bit convoluted and `qvm-run` is sometimes slow when the system is under heavy I/O usage, so the layout switch doesn't happen immediately which is annoying.
+- Configuring a keyboard shortcut in dom0 that would issue `qvm-run vname 'setxkbmap ...'` to the VM whose window is under the mouse pointer (using `xprop -id $(xdotool getactivewindow`) ). This is a bit convoluted and `qvm-run` is sometimes slow when the system is under heavy I/O usage, so the layout switch doesn't happen immediately which is annoying.
-- Change the layout in dom0 with `setxkbmap ...`. This isn't optimal because:
+- Change the layout in dom0 with `setxkbmap`. This isn't optimal because:
     - there's no way to know which layout is used when typing the screensaver's password
     - sometimes the keyboard layout would not be propagated to one of the VMs, requiring a reboot of the VM. 
-- Once Qubes OS gains support for keyboard layout propagation from dom0 to VMs (see [this official issue](https://github.com/QubesOS/qubes-issues/issues/1396)) one could use the desktop environment's keyboard layout switcher (eg. Xfce Keyboard Layout switcher). It is not clear however if this solution won't exhibit the issues as above when running `setxkbmap ...` in dom0.
+- Once Qubes OS gains support for keyboard layout propagation from dom0 to VMs (see [this official issue](https://github.com/QubesOS/qubes-issues/issues/1396)) the desktop environment's keyboard layout switcher (eg. Xfce Keyboard Layout switcher) could be used instead of `setxkbmap`.  It is not clear however if this solution won't have the same issues when running `setxkbmap` in dom0 as above.
-- Change the layout in dom0 with localectl: it's a no-go as it requires a reboot
+- Change the layout in dom0 with `localectl`: it's a no-go as it requires a reboot