From 2907e60ef21aeb73396354f4c9627071430bad89 Mon Sep 17 00:00:00 2001
From: Kristina <52878547+Sakurann@users.noreply.github.com>
Date: Wed, 19 Jun 2024 11:55:38 +0200
Subject: [PATCH] Apply suggestions from Sam's code review

Co-authored-by: Sam Goto <samuelgoto@gmail.com>
---
 openid-4-verifiable-presentations-1_0.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md
index 3825d188..c7703163 100644
--- a/openid-4-verifiable-presentations-1_0.md
+++ b/openid-4-verifiable-presentations-1_0.md
@@ -1494,7 +1494,7 @@ issuers in Self-Sovereign Identity ecosystems using TRAIN</title>
         </front>
 </reference>
 
-<reference anchor="w3c.digital_credentials_api" target="https://wicg.github.io/digital-identities/">
+<reference anchor="w3c.digital_credentials_api" target="https://wicg.github.io/digital-credentials/">
         <front>
           <title>Digital Credentials API</title>
 		  <author fullname="Marcos Caceres">
@@ -1541,7 +1541,7 @@ if ('DigitalCredential' in window) {
 The following is a non-normative example of a response corresponding to a previous request:
 
 ```js
-const { data } = response;
+const { data } = credential;
 ```
 
 The Digital Credentials API offers several advantages for implementers of both Verifiers and Wallets.