diff --git a/docs/distributions/c8.md b/docs/distributions/c8.md
index 7d6a5066bf6f252aaff789a26f8a2b225fe1c3e0..e0b5fbe09e7d8d9eca95efe86ba2d353aa1666b5 100644
--- a/docs/distributions/c8.md
+++ b/docs/distributions/c8.md
@@ -55,6 +55,27 @@ Once the new version of a release package is built and tagged as stable, you can
 delete the `.freeze.8all` file and rerun the Nomad job. This time, it will find
 your new RPM in the CERN repo and continue the process.
 
+### Seeing differences between snapshots
+
+You can see all the packages that changed between two dates using the `snapshotdiff`
+command, which is provided by [lxdist-build](https://gitlab.cern.ch/linuxsupport/lxdist-build/-/tree/master/bin):
+
+```bash
+[build@lxsoftadm01] snapshotdiff -d 8 -s 20200701 -e 20200709
+Calculating diff between 20200701 and 20200709...
+
+  apache-sshd                                        2.5.1-1.el8
+  apache-sshd-javadoc                                2.5.1-1.el8
+  bind                                               9.11.13-5.el8_2
+...
+  python-novaclient-doc                              15.1.1-1.el8
+  python-octaviaclient-doc                           1.10.1-1.el8
+  python3-bind                                       9.11.13-5.el8_2
+
+Changes listed: 75
+Total number of changes: 176
+```
+
 ### Manually updating symlinks
 
 You can also manually point symlinks to a more up-to-date snapshot. The symlink
@@ -67,6 +88,9 @@ continue pointing to that day even on Wednesday the 15th, where they should
 been moved to the 8th but won't be because they're never moved backwards in time.
 On Wednesday the 22nd they would be moved to Wednesday the 15th as usual.
 
+Before doint this, it is a good idea to check what packages have changed
+between the different snapshots using the `snapshotdiff` command.
+
 The recommended method of updating the links is to ssh into an lxsoftadm machine
 and run:
 
@@ -79,6 +103,7 @@ Once that file is created, rerun the snapshotting cron job in Nomad. It will see
 this file, set the production symlinks to that date, and then delete the `.forcemove.8`
 file. The job will also send the usual emails and update the web site.
 
+
 ## 'Minor' (8.x -> 8.x+1) version release process
 
 The daily update process will do most of the work when a new CentOS 8 minor release