From 57a6fa46b204374a2519a302f9d09cc562071317 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Thu, 26 Oct 2023 13:03:53 +0200
Subject: [PATCH] docs: fix broken image references

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 docs/content/about/notifications.md | 2 +-
 docs/content/spec/auth/token.md     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/about/notifications.md b/docs/content/about/notifications.md
index 81292bd9d..d5b11d5d4 100644
--- a/docs/content/about/notifications.md
+++ b/docs/content/about/notifications.md
@@ -10,7 +10,7 @@ pushes and pulls and layer pushes and pulls. These actions are serialized into
 events. The events are queued into a registry-internal broadcast system which
 queues and dispatches events to [_Endpoints_](#endpoints).
 
-![Workflow of registry notifications](/images/notifications.png)
+![Workflow of registry notifications](../../images/notifications.png)
 
 ## Endpoints
 
diff --git a/docs/content/spec/auth/token.md b/docs/content/spec/auth/token.md
index 1696280de..cc9d940e8 100644
--- a/docs/content/spec/auth/token.md
+++ b/docs/content/spec/auth/token.md
@@ -8,7 +8,7 @@ keywords: registry, on-prem, images, tags, repository, distribution, Bearer auth
 
 This document outlines the v2 Distribution registry authentication scheme:
 
-![v2 registry auth](/images/v2-registry-auth.png)
+![v2 registry auth](../../../images/v2-registry-auth.png)
 
 1. Attempt to begin a push/pull operation with the registry.
 2. If the registry requires authorization it will return a `401 Unauthorized`