From 441c96ad8cb5c3a23de4ccabc94e4aa651d7712c Mon Sep 17 00:00:00 2001
From: p-suedo <41720709+p-suedo@users.noreply.github.com>
Date: Thu, 9 Aug 2018 14:17:14 +0000
Subject: [PATCH 1/2] Small add in installing and updating

Hello Qubes! I am pretty new to this, but was reading about StandaloneVM, and think the command is only for 3.x, not 4.x. I tried copying from other material, hope I did it right! Figure is better to try myself since its little thing. Thanks!
---
 common-tasks/software-update-vm.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/common-tasks/software-update-vm.md b/common-tasks/software-update-vm.md
index a34be8da..79223108 100644
--- a/common-tasks/software-update-vm.md
+++ b/common-tasks/software-update-vm.md
@@ -189,6 +189,12 @@ In order to create a standalone VM you can use a command line like this (from co
 qvm-create <vmname> --standalone --label <label>
 ~~~
 
+or in 4.0:
+
+```
+qvm-create --class StandaloneVM --label <label> --property virt_mode=hvm <vmname>
+```
+
 ... or click appropriate options in the Qubes Manager's Create VM window.
 
 Using more than one template

From 4e30201deedea040484f1bcbc48f513a9cf0698a Mon Sep 17 00:00:00 2001
From: p-suedo <41720709+p-suedo@users.noreply.github.com>
Date: Fri, 24 Aug 2018 09:10:27 +0000
Subject: [PATCH 2/2] correcting with docs

This is not exactly like docs, but I followed https://www.qubes-os.org/doc/dispvm/ (and is also like other 3-4 specific on this page) - hope this is good. If not, tell me and I will fix better!
---
 common-tasks/software-update-vm.md | 31 +++++++++++++++++++++++-------
 1 file changed, 24 insertions(+), 7 deletions(-)

diff --git a/common-tasks/software-update-vm.md b/common-tasks/software-update-vm.md
index 79223108..fb100538 100644
--- a/common-tasks/software-update-vm.md
+++ b/common-tasks/software-update-vm.md
@@ -168,7 +168,29 @@ However, a compromise of a template affects only a subset of all your AppVMs (in
 Also, if your AppVMs are network disconnected, even though their filesystems might get compromised due to the corresponding template compromise, it still would be difficult for the attacker to actually leak out the data stolen in an AppVM.
 Not impossible (due to existence of cover channels between VMs on x86 architecture), but difficult and slow.
 
-Standalone VMs
+Standalone VMs (R4.0 and later)
+--------------
+Standalone VMs have their own copy of the whole filesystem, and thus can be updated and managed on their own.
+But this means that they take a few GBs on disk, and also that centralized updates do not apply to them.
+
+Sometimes it might be convenient to have a VM that has its own filesystem, where you can directly introduce changes, without the need to start/stop the template VM.
+Such situations include e.g.:
+
+-   VMs used for development (devel environments require a lot of \*-devel packages and specific devel tools)
+
+-   VMs used for installing untrusted packages.
+    Normally you install digitally signed software from Red Hat/Fedora repositories, and it's reasonable that such software has non malicious *installation* scripts (rpm pre/post scripts).
+    However, when you would like to install some packages from less trusted sources, or unsigned, then using a dedicated (untrusted) standalone VM might be a better way.
+
+In order to create a standalone VM you can use a command line like this (from console in Dom0):
+
+```
+qvm-create --class StandaloneVM --label <label> --property virt_mode=hvm <vmname>
+```
+
+... or click appropriate options in the Qubes Manager's Create VM window.
+
+Standalone VMs (R3.2 and earlier)
 --------------
 
 Standalone VMs have their own copy of the whole filesystem, and thus can be updated and managed on their own.
@@ -189,14 +211,9 @@ In order to create a standalone VM you can use a command line like this (from co
 qvm-create <vmname> --standalone --label <label>
 ~~~
 
-or in 4.0:
-
-```
-qvm-create --class StandaloneVM --label <label> --property virt_mode=hvm <vmname>
-```
-
 ... or click appropriate options in the Qubes Manager's Create VM window.
 
+
 Using more than one template
 ----------------------------