diff --git a/CHANGELOG.md b/CHANGELOG.md
index ffa1ef5e..ff6e5c9f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file
 automatically by Versionist. DO NOT EDIT THIS FILE MANUALLY!
 This project adheres to [Semantic Versioning](http://semver.org/).
 
+## v7.9.1 - 2018-05-29
+
+* Update update-locking documentation #667 [Cameron Diver]
+
 ## v7.9.0 - 2018-05-23
 
 * Add support for Balena deltas #632 [Akis Kesoglou]
diff --git a/docs/update-locking.md b/docs/update-locking.md
index 4c008f83..e9ecf4cb 100644
--- a/docs/update-locking.md
+++ b/docs/update-locking.md
@@ -9,6 +9,8 @@ Locking updates means that the resin.io device supervisor will not be able to ki
 
 In order to do this, users can create a lockfile called `resin-updates.lock` in a way that it has exclusive access, which will prevent the device supervisor from killing and restarting the app. As with any other lockfile, the supervisor itself will create such a file before killing the app, so you should only create it in exclusive mode. This means that the lockfile should only be created if it doesn't already exist. The exclusive access is achieved by opening the lockfile with the [O_EXCL and O_CREAT flags](https://linux.die.net/man/3/open), and several tools exist to simplify this process with examples given [below](#creating-the-lockfile).
 
+The presence of a lockfile will ensure that your application does not get killed, but updates will still be downloaded by the supervisor, ready to be applied once the lockfile no longer exists.
+
 ### Location of the lockfile
 
 In supervisor v4.0.0 and higher, the lock is located at `/tmp/resin/resin-updates.lock`. This lock is cleared automatically when the device reboots, so the user app must take it every time it starts up.
diff --git a/package.json b/package.json
index 01be063c..33d7e4c2 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "resin-supervisor",
   "description": "This is resin.io's Supervisor, a program that runs on IoT devices and has the task of running user Apps (which are Docker containers), and updating them as Resin's API informs it to.",
-  "version": "7.9.0",
+  "version": "7.9.1",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",