diff --git a/index.html b/index.html
index 6439910..c6e2890 100644
--- a/index.html
+++ b/index.html
@@ -958,11 +958,6 @@ <h2>DID Resolution Algorithm</h2>
 			</li>
 		</ol>
 
-		<p class="issue">Should we define functionality that enables discovery of the list of <a>DID methods</a> or other
-		capabilities that are supported by a <a>DID resolver</a>? Or is this implementation-specific and out-of-scope
-		for this spec? For example, see <a href="https://github.com/w3c/did-resolution/issues/26">here</a> and
-		<a href="https://github.com/w3c/did-resolution/issues/25">here</a>.</p>
-
 	</section>
 
 </section>
@@ -1716,9 +1711,6 @@ <h2>Metadata Structure</h2>
 
 <section id="architectures">
 	<h1>DID Resolution Architectures</h1>
-	<p class="issue">TODO: Describe how <a>DID resolvers</a> are implemented and used, describe the relevance
-	of <a>DID methods</a>.
-	Explain the difference between "method architectures" and "resolver architectures".</p>
 
 	<section id="method-architectures">
 		<h2>Method Architectures</h2>
@@ -2120,16 +2112,6 @@ <h2>Example</h2>
 }
 </pre>
 
-	<p class="issue">Need to define how this data structure works exactly, and whether it always contains
-	a <a>DID document</a> or can also contain other results.</p>
-
-	</section>
-
-	<p class="issue">For certain data, it may be debatable whether it should be part of the DID document
-	(i.e., data that describes the DID Subject), or whether it is metadata (i.e., data about the DID document or about
-	the DID resolution process). For example the URL of the "Continuation DID document" in the BTCR method.
-	</p>
-
 </section>
 
 	<section id="did-url-dereferencing-result">
@@ -2744,8 +2726,6 @@ <h2>Caching</h2>
 			Resolvers that deny resolution without caching MUST respond with a <a href="#FEATURE_NOT_SUPPORTED">FEATURE_NOT_SUPPORTED</a> error that makes it clear that bypassing the cache was not permitted
 			so the client can attempt to resolve without using <code>noCache</code>.</p>
 
-			<p class="issue" data-number="10">See corresponding open issue.</p>
-		<p class="issue">Perhaps we can re-use caching mechanisms of other protocols such as HTTP.</p>
 	</section>
 	<section id="json-ld-integrity">
 		<h2>JSON-LD Context Integrity</h2>
@@ -2781,14 +2761,6 @@ <h2>VDR Network Forks</h2>
 			the specification of a <a>DID method</a> that uses a distributed system as a VDR SHOULD specify a means by which
 			the VDR they are using can be disambiguated from such forks.</p>
 	</section>
-	<section id="non-did-identifiers">
-		<h2>Non-DID Identifiers</h2>
-		<p class="issue" data-number="8">There is discussion on the relationship between <a>DID resolution</a> and
-		resolution of non-DID identifiers such as domain names, HTTP URIs, or e-mail addresses. This includes the
-		questions how DIDs can be discovered from non-DID identifiers, and how links between identifiers can
-		be verifiable.</p>
-
-	</section>
 
 	<section id="security-cycles-resolution">
 		<h2>Resolution Cycles</h2>
@@ -2829,8 +2801,6 @@ <h2>Resolution Cycles</h2>
 <section id="privacy-considerations">
 	<h1>Privacy Considerations</h1>
 
-	<p class="issue">TODO: Define privacy considerations for DID resolution</p>
-
 	<section id="profiling-requesters">
 		<h2>Profiling of DID Resolution and Dereferencing Requesters</h2>
 		<p><a>DID resolvers</a> and <a>DID URL dereferencers</a> will be able to log requests