From 75800a971773e6cb8bfd56f76a33b0e9bad2dffb Mon Sep 17 00:00:00 2001
From: Peter Koen <94012519+PeterKoen-MSFT@users.noreply.github.com>
Date: Thu, 16 Jan 2025 14:41:12 +0100
Subject: [PATCH] Update verifiable.presentation.protocol.md

fixed broken auth.flow.png URL
---
 specifications/verifiable.presentation.protocol.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/specifications/verifiable.presentation.protocol.md b/specifications/verifiable.presentation.protocol.md
index 672db3e..2f71f4d 100644
--- a/specifications/verifiable.presentation.protocol.md
+++ b/specifications/verifiable.presentation.protocol.md
@@ -19,7 +19,7 @@ resolve credential-related resources. The protocol also provides a mechanism for
 The following sequence diagram depicts a non-normative flow where a client interacts with a [=Verifier=] to present a
 [=Verifiable Credential=]:
 
-![alt text 2](specifications/auth.flow.png "Presentation Flow")
+![alt text 2](./specifications/auth.flow.png "Presentation Flow")
 
 1. The client sends a request to its [=Secure Token Service=] for a [=Self-Issued ID Token=]. The API used to make this
    request is implementation specific. The client may include a set of scopes that define the [=Verifiable Credentials=]
@@ -185,4 +185,4 @@ The following are non-normative examples of the JSON response body:
 #### Presentation Submissions
 
 Implementations that support the `presentationDefinition` parameter MUST include the `presentationSubmission` parameter in the [[[#presentation-response-message]]] with a valid [Presentation Submission](https://identity.foundation/presentation-exchange/spec/v2.0.0/#presentation-submission) when a `presentationDefinition` 
-is provided in the [[[#presentation-query-message]]].
\ No newline at end of file
+is provided in the [[[#presentation-query-message]]].