diff --git a/site/content/docs/main/how-velero-works.md b/site/content/docs/main/how-velero-works.md
index 9428289f11..a72bcc9d27 100644
--- a/site/content/docs/main/how-velero-works.md
+++ b/site/content/docs/main/how-velero-works.md
@@ -81,7 +81,7 @@ Likewise, if a backup object exists in Kubernetes but not in object storage, it
 
 [10]: backup-hooks.md
 [11]: restore-hooks.md
-[19]: img/backup-process.png
+[19]: /docs/main/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.2.0/how-velero-works.md b/site/content/docs/v1.2.0/how-velero-works.md
index 44013c5b0c..087ef508b1 100644
--- a/site/content/docs/v1.2.0/how-velero-works.md
+++ b/site/content/docs/v1.2.0/how-velero-works.md
@@ -76,7 +76,7 @@ This allows restore functionality to work in a cluster migration scenario, where
 Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
 
 [10]: hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.2.0/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.3.0/how-velero-works.md b/site/content/docs/v1.3.0/how-velero-works.md
index 44013c5b0c..5c269ce9d2 100644
--- a/site/content/docs/v1.3.0/how-velero-works.md
+++ b/site/content/docs/v1.3.0/how-velero-works.md
@@ -76,7 +76,7 @@ This allows restore functionality to work in a cluster migration scenario, where
 Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
 
 [10]: hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.3.0/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.3.1/how-velero-works.md b/site/content/docs/v1.3.1/how-velero-works.md
index 44013c5b0c..6f26e8e710 100644
--- a/site/content/docs/v1.3.1/how-velero-works.md
+++ b/site/content/docs/v1.3.1/how-velero-works.md
@@ -76,7 +76,7 @@ This allows restore functionality to work in a cluster migration scenario, where
 Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
 
 [10]: hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.3.1/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.3.2/how-velero-works.md b/site/content/docs/v1.3.2/how-velero-works.md
index 45889caef4..b8626169ec 100644
--- a/site/content/docs/v1.3.2/how-velero-works.md
+++ b/site/content/docs/v1.3.2/how-velero-works.md
@@ -78,7 +78,7 @@ This allows restore functionality to work in a cluster migration scenario, where
 Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
 
 [10]: hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.3.2/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.4/how-velero-works.md b/site/content/docs/v1.4/how-velero-works.md
index 45889caef4..db0dc0f169 100644
--- a/site/content/docs/v1.4/how-velero-works.md
+++ b/site/content/docs/v1.4/how-velero-works.md
@@ -78,7 +78,7 @@ This allows restore functionality to work in a cluster migration scenario, where
 Likewise, if a backup object exists in Kubernetes but not in object storage, it will be deleted from Kubernetes since the backup tarball no longer exists.
 
 [10]: hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.4/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd
diff --git a/site/content/docs/v1.5/how-velero-works.md b/site/content/docs/v1.5/how-velero-works.md
index 9428289f11..900e760d87 100644
--- a/site/content/docs/v1.5/how-velero-works.md
+++ b/site/content/docs/v1.5/how-velero-works.md
@@ -81,7 +81,7 @@ Likewise, if a backup object exists in Kubernetes but not in object storage, it
 
 [10]: backup-hooks.md
 [11]: restore-hooks.md
-[19]: img/backup-process.png
+[19]: /docs/v1.5/img/backup-process.png
 [20]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#customresourcedefinitions
 [21]: https://kubernetes.io/docs/concepts/api-extension/custom-resources/#custom-controllers
 [22]: https://github.com/coreos/etcd