From 5e059c820fb523e88bb0bf4ee9eb05ad28f4b8e9 Mon Sep 17 00:00:00 2001
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Wed, 28 Jun 2023 16:16:41 -0700
Subject: [PATCH] Cite Multibase normatively

One instance was missing the citation, and the other had a MUST combined with a non-normative citation.
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 6a44eb7e..e2ed7fd2 100644
--- a/index.html
+++ b/index.html
@@ -475,7 +475,7 @@ <h3>Proofs</h3>
           <dd>
 A string value that contains the data necessary to verify the digital proof
 using the `verificationMethod` specified. The contents of the value MUST be a
-multibase-encoded binary value. Alternative fields with different encodings MAY
+[[MULTIBASE]]-encoded binary value. Alternative fields with different encodings MAY
 be used to encode the data necessary to verify the digital proof instead of this
 value. The contents of this value are determined by a cryptosuite and set to the
 <em>proof value</em> generated by the
@@ -975,7 +975,7 @@ <h3>Verification Material</h3>
                 <p>
 The `publicKeyMultibase` property is OPTIONAL. This feature is
 non-normative. If present, the value MUST be a <a
-data-cite="INFRA#string">string</a> representation of a [[?MULTIBASE]] encoded
+data-cite="INFRA#string">string</a> representation of a [[MULTIBASE]] encoded
 public key.
                 </p>
                 <p class="advisement">