diff --git a/README.md b/README.md
index f92878b2c756f068cf8d1be67253c1a7a5377c71..8e7d5c919cd24e6631a930cbe3acc428b8ae27be 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ With both encoders, I can now plot my dubious encoder data against a known sourc
 
 If you look at the top (normalzied) and bottom (plotted against time) data you can see the importance of our reference encoder to really understand the accuracy of the system. The bottom plot is just the encoder readout plotted against time, and so there's a stretch at the beginning where I wasn't rotating the shaft + visible changes in pitch from my inadvertent speeding up or slowing down rotation. This is not at all going to be a sin-cos encoder, and instead looks much more like a piecewise triangle wave. I think this is a good thing, considering that more linear the data results in a more constant (and overall higher magnitude) encoder response for a given rotation angle. The caveat is that I won't be able to use the straightforward arctan trick to linearize my two signals, and instead will likely need to go straight to a lookup table off of a calibration.
 
-[<img src="images/dataCollectionVideo.png" width="800">](https://gitlab.cba.mit.edu/davepreiss/ldcoder/-/blob/master/images/rotorTarget%20.mp4)
+[<img src="images/dataCollectionVideo.png" width="800">](https://gitlab.cba.mit.edu/davepreiss/ldcoder/-/blob/master/images/dataCollectionVideo.mp4)
 
 ## HTMSTMAA Week 9 - 5/5/21