diff --git a/README.md b/README.md
index 4e633c5c..d7459e22 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ Although LOOT uses a cross-platform build system and cross-platform libraries, i
 
 Installer and zip archive releases for the main LOOT application can be handled by running the scripts `installer.nsi` and `archive.py` in the `src` folder respectively. The installer script requires [NSIS 3](http://nsis.sourceforge.net/), while the archive script requires [Python](http://www.python.org/) (2 or 3). The installer and archive files are created in the `build/` folder, relative to the repository root.
 
-If you have [Git for Windows (msysGit)](https://msysgit.github.io/) or [GitHub for Windows](https://windows.github.com/) installed and you're building from a clone of this repository, the archive script will give archives descriptive names using the output of `git describe --tags --long`. If you have [7-zip](www.7-zip.org) installed, `.7z` archives will be created. Otherwise, archives will be named `LOOT Archive` and created as deflate-compressed zip files.
+If you have [Git for Windows (msysGit)](https://msysgit.github.io/) or [GitHub for Windows](https://windows.github.com/) installed and you're building from a clone of this repository, the archive script will give archives descriptive names using the output of `git describe --tags --long`. If you have [7-Zip](www.7-zip.org) installed, `.7z` archives will be created. Otherwise, archives will be named `LOOT Archive` and created as deflate-compressed zip files.
 
 ## Snapshot Builds
 
diff --git a/docs/LOOT Readme.html b/docs/LOOT Readme.html
index 8ae58278..b1f0ef30 100644
--- a/docs/LOOT Readme.html	
+++ b/docs/LOOT Readme.html	
@@ -289,7 +289,7 @@ h3{
 
 <p>If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install, then use the <a href="#copyMetadataAsText">Copy Metadata As Text</a> feature to easily get it in a form that you can then edit into a masterlist on GitHub or post in the official forum threads.
 
-<p>Information on dirty plugins is very welcome, but for such information to be useful we require at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or 7-zip, with other sources being unverified as correct. In the case of 7-zip, the <q><em>CRC checksum for data</em></q> is the one required. In addition to the CRC, the number of records removed (the ITM count) and/or undeleted (the UDR count) are also welcome.
+<p>Information on dirty plugins is very welcome, but for such information to be useful we require at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or 7-Zip, with other sources being unverified as correct. In the case of 7-Zip, the <q><em>CRC checksum for data</em></q> is the one required. In addition to the CRC, the number of records removed (the ITM count) and/or undeleted (the UDR count) are also welcome.
 
 
 <h2 id="credits">Credits</h2>
diff --git a/src/archive.py b/src/archive.py
index b77f2711..02c2269f 100644
--- a/src/archive.py
+++ b/src/archive.py
@@ -40,14 +40,14 @@ archive_name = 'LOOT Archive.zip'
 # There are two compression methods available:
 #
 #  * Zip (Deflate)
-#  * 7-zip (LZMA)
+#  * 7-Zip (LZMA)
 #
 # Python 3.3+ can also do BZIP2 and LZMA zip archives, but they don't have good
 # Windows OS support, so people think they should be able to open them without
 # an archiving utility, find they can't, and think the archive is broken. So
 # they won't be used.
 #
-# Look for 7-zip in its default install location, and use it if it is found.
+# Look for 7-Zip in its default install location, and use it if it is found.
 # Fall back to zip if not.
 #
 # Archives are named using the output of `git describe --tags --long`, if Git