diff --git a/UpgradeToR2B1.md b/UpgradeToR2B1.md
index 4fb024c3..2d18d35d 100644
--- a/UpgradeToR2B1.md
+++ b/UpgradeToR2B1.md
@@ -9,15 +9,15 @@ Upgrading Qubes R1 to R2 (beta)
 
 **Note: Qubes R2 Beta has not been release yet, DO NOT follow those instructions before R2 Beta is released**
 
-Existing users of Qubes R1 (but not R1 betas!) can upgrade their systems to the latest R2 beta release by following the procedure below. As usual, tt is advisable to backup the system before proceeding with the upgrade
+Existing users of Qubes R1 (but not R1 betas!) can upgrade their systems to the latest R2 beta release by following the procedure below. As usual, it is advisable to backup the system before proceeding with the upgrade
 
 Upgrade all Template and Standalone VM(s)
 -----------------------------------------
 
 By default, in Qubes R1, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. More information on using multiple Template VMs, as well as Standalone VMs, can be found [SoftwareUpdateVM here]. The steps described in this section should be repeated in *all* user's Template and Standalone VMs.
 
-1.  Open terminal in the template VM (or standalone VM). E.g. use the Qubes Manager's right-click menu and choose Run Command in VM and type **gnome-terminal** there.
-2.  Install **qubes-upgrade-vm** package (this package brings in R2 repo definitions and R2 keys)
+1.  Open terminal in the template VM (or standalone VM). E.g. use the Qubes Manager's right-click menu and choose Run Command in VM and type `gnome-terminal` there.
+2.  Install `qubes-upgrade-vm` package (this package brings in R2 repo definitions and R2 keys)
 
     ``` {.wiki}
     sudo yum install qubes-upgrade-vm
@@ -40,9 +40,9 @@ Importing GPG key 0x0A40E458:
 Is this ok [y/N]:
 ```
 
-If you see (as is the case on the "screenshot" above) that the new is was imported from a local filesystem (**/etc/pki/rpm-gpg/...**) you can safely accept the key, without checking its fingerprint. This is because there were only ways for such key to make it to your Template VM's filesystem:
+If you see (as is the case on the "screenshot" above) that the new is was imported from a local filesystem (`/etc/pki/rpm-gpg/...`) you can safely accept the key, without checking its fingerprint. This is because there were only ways for such key to make it to your Template VM's filesystem:
 
--   via a legitimate RPM package previously installed (in our case it was the qubes-upgrade-vm RPM). Such an RPM must have been signed by one of the keys you decided to trust previously, by default this would be either via the Qubes R1 signing key, or Fedora 17 signing key.
+-   via a legitimate RPM package previously installed (in our case it was the `qubes-upgrade-vm` RPM). Such an RPM must have been signed by one of the keys you decided to trust previously, by default this would be either via the Qubes R1 signing key, or Fedora 17 signing key.
 -   via system compromise or via some illegal RPM package (e.g. Fedora released package pretending to bring new Firefox). In that case, however, your VM is already compromised, and it careful checking of the new R2 key would not change this situation to any better one. The game is lost for this VM anyway (and all VMs based on this template).
 
 1.  Shut down the VM.