diff --git a/user/managing-os/reinstall-template.md b/user/managing-os/reinstall-template.md
index efd946bf..e300396e 100644
--- a/user/managing-os/reinstall-template.md
+++ b/user/managing-os/reinstall-template.md
@@ -13,8 +13,9 @@ If you suspect your [TemplateVM] is broken, misconfigured, or compromised, you c
 
 The procedure varies by Qubes version; see the appropriate section below.
 
-Automated Reinstallation Method (R3.1+)
-----------------------------
+
+Automatic Method
+----------------
 
 First, copy any files that you wish to keep from the TemplateVM's `/home` and `/rw` folders to a safe storage location.
 Then, in a dom0 terminal, run:
@@ -39,8 +40,8 @@ For example:
 **Note:** VMs that are using the reinstalled template will not be affected until they are restarted.
 
 
-Manual Reinstallation Method (R3.1+)
-----------------------------
+Manual Method
+-------------
 
 In what follows, the term "target TemplateVM" refers to whichever TemplateVM you want to reinstall.
 If you want to reinstall more than one TemplateVM, repeat these instructions for each one.
@@ -80,57 +81,7 @@ If you want to reinstall more than one TemplateVM, repeat these instructions for
 6. Delete the cloned template.
    You can do this in Qubes Manager by right-clicking on the VM and clicking **Remove VM**, or you can use the
    command `qvm-remove <vm-name>` in dom0.
-   
-   
-Manual Reinstallation Method (R3.0 or earlier)
-----------------------------
 
-If you're using Qubes 3.0 or older, you should use the manual reinstallation method. 
-You can also use this method on later Qubes versions if, for any reason, you want to reinstall a template manually.
-
-In what follows, the term "target TemplateVM" refers to whichever TemplateVM you want to reinstall. 
-If you want to reinstall more than one TemplateVM, repeat these instructions for each one.
-
-1. (Optional) Clone the existing target TemplateVM.
-
-   This can be a good idea if you've customized the existing template and want to keep your customizations. 
-   On the other hand, if you suspect that this template is broken, misconfigured, or compromised, you may want to remove it without cloning it.
-
-2. Create a temporary dummy template:
-
-        mkdir /var/lib/qubes/vm-templates/dummy
-        touch /var/lib/qubes/vm-templates/dummy/{root.img,private.img}
-        qvm-add-template dummy
-
-3. Temporarily change all VMs based on the target TemplateVM to the new dummy template, or remove them.
-
-   This can be a good idea if you have user data in these VMs that you want to keep. 
-   On the other hand, if you suspect that these VMs (or the templates on which they are based) are broken, misconfigured, or compromised, you may want to remove them instead.
-   You can do this in Qubes Manager by right-clicking on the VM and clicking **Remove VM**, or you can use the command `qvm-remove <vm-name>` in dom0.
-
-   Using a dummy template as a temporary template is preferable to using another real TemplateVM because you can't accidentally boot any VMs from the dummy template.
-   (There is no OS in the dummy template, so the boot will fail.)
-
-4. Uninstall the target TemplateVM from dom0:
-
-        $ sudo yum remove <template-package-name>
-
-   For example, to uninstall the `whonix-gw` template:
-
-        $ sudo yum remove qubes-template-whonix-gw
-
-5. Reinstall the target TemplateVM in dom0:
-
-        $ sudo qubes-dom0-update --enablerepo=<optional-additional-repo> \
-          <template-package-name>
-
-   For example, to install the `whonix-gw` template:
-
-        $ sudo qubes-dom0-update --enablerepo=qubes-templates-community \
-          qubes-template-whonix-gw
-
-6. If you temporarily changed all VMs based on the target TemplateVM to the dummy template in step 3, change them back to the new target TemplateVM now.
-   If you instead removed all VMs based on the old target TemplateVM, you can recreate your desired VMs from the newly reinstalled target TemplateVM now.
 
 [TemplateVM]: /doc/templates/