diff --git a/customization/i3.md b/customization/i3.md
index 02f9c819..9178fccf 100644
--- a/customization/i3.md
+++ b/customization/i3.md
@@ -82,33 +82,6 @@ After that you can just install the generated rpm like any other local package
 
 Log out, select i3, then log in again.
 
-### Configuration
-
-**Warning**: Be careful when writing configuration/scripts for the dom0. A script which communicates with the qubes VMs could potentially open a security hole.
-
-Things needed/recommended to be done:
-
-  1. Create [a script][xdg_autostart_script] to start all entries in the xdg
-     autostart directory. This is necessary to bring transient vm's up and
-restore state.
-  2. Change dmenu to i3-dmenu-desktop in the i3 configuration file. This
-     respects xdg desktop files and gives you a good way of starting programs in
-specific domains.
-  3. Install i3status or use a [different kind of script][i3bar_script] to drive
-     i3bar.
-  4. You could install and bind tools to change backlight and volume levels in
-     i3's config. You could also run kmix and xfce4-power-manager, which are
-part of a normal Qubes installation, and bind the keys for you.
-  5. Qubes does automatic screen locking and so should you. Install `xautolock`
-     and `i3lock` in dom0 and then add
-
-         exec --no-startup-id "xautolock -detectsleep -time 3 -locker 'i3lock -d -c 000000' -notify 30 -notifier \"notify-send -t 2000 'Locking screen in 30 seconds'\""
-
-     to your i3 config to enable it.
-  6. By default `$mod+Return` in i3 will open a new terminal in dom0. If you
-     prefer to start a new terminal in the domain of the currently active
-     window, use [a script like this][terminal_start_script].
-
 [xdg_autostart_script]:https://gist.github.com/SietsevanderMolen/7b4cc32ce7b4884513b0a639540e454f
 [i3bar_script]: https://gist.github.com/SietsevanderMolen/e7f594f209dfaa3596907e427b657e30
 [terminal_start_script]: https://gist.github.com/SietsevanderMolen/7c6f2b5773dbc0c08e1509e49abd1e96