adjust-spec-pages: match closing TOC tags exactly

[chalin]

Contributes to #906

Site diff yields:

$ (cd public && git diff -- . ':(exclude)*.xml') 

diff --git a/docs/reference/specification/overview/index.html b/docs/reference/specification/overview/index.html
index 480f62a6..6592fb21 100644
--- a/docs/reference/specification/overview/index.html
+++ b/docs/reference/specification/overview/index.html
@@ -19,8 +19,7 @@
 <link rel="icon" type="image/png" href="/favicons/android-192x192.png" sizes="192x192">
 
 <title>Overview | OpenTelemetry</title>
-<meta name="description" content="
-This document provides an overview of the OpenTelemetry project and defines important fundamental terms.
+<meta name="description" content="This document provides an overview of the OpenTelemetry project and defines important fundamental terms.
 Additional term definitions can be found in …">
 <meta property="og:title" content="Overview" />
 <meta property="og:description" content="This document provides an overview of the OpenTelemetry project and defines important fundamental terms.
@@ -804,8 +803,7 @@ OpenTelemetry Client Architecture At the highest architectural level, OpenTeleme
                
                
        </header>    
-       </details>
-<p>This document provides an overview of the OpenTelemetry project and defines important fundamental terms.</p>
+       <p>This document provides an overview of the OpenTelemetry project and defines important fundamental terms.</p>
 <p>Additional term definitions can be found in the <a href="/docs/reference/specification/glossary/">glossary</a>.</p>
 <h2 id="opentelemetry-client-architecture">OpenTelemetry Client Architecture</h2>
 <p><img src="/img/architecture.png" alt="Cross cutting concerns"></p>
diff --git a/docs/reference/specification/trace/sdk/index.html b/docs/reference/specification/trace/sdk/index.html
index 07da9af8..f1734ab4 100644
--- a/docs/reference/specification/trace/sdk/index.html
+++ b/docs/reference/specification/trace/sdk/index.html
@@ -20,14 +20,13 @@
 
 <title>Tracing SDK | OpenTelemetry</title>
 <meta name="description" content="Status: Stable
-
 Tracer Provider
 Tracer Creation
 New Tracer instances are always created through a TracerProvider (see
 API). The name and version …">
 <meta property="og:title" content="Tracing SDK" />
 <meta property="og:description" content="Status: Stable
- Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
+Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
 Configuration (i.e., SpanProcessors, IdGenerator, SpanLimits and Sampler) MUST be managed solely by the TracerProvider and it MUST provide some way to configure all of them that are implemented in the SDK, at least when creating or initializing it." />
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://opentelemetry.io/docs/reference/specification/trace/sdk/" /><meta property="article:section" content="docs" />
@@ -36,14 +35,14 @@ Configuration (i.e., SpanProcessors, IdGenerator, SpanLimits and Sampler) MUST b
 
 <meta itemprop="name" content="Tracing SDK">
 <meta itemprop="description" content="Status: Stable
- Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
+Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
 Configuration (i.e., SpanProcessors, IdGenerator, SpanLimits and Sampler) MUST be managed solely by the TracerProvider and it MUST provide some way to configure all of them that are implemented in the SDK, at least when creating or initializing it.">
 
 <meta itemprop="wordCount" content="3930">
 <meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="Tracing SDK"/>
 <meta name="twitter:description" content="Status: Stable
- Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
+Tracer Provider Tracer Creation New Tracer instances are always created through a TracerProvider (see API). The name and version arguments supplied to the TracerProvider must be used to create an InstrumentationLibrary instance which is stored on the created Tracer.
 Configuration (i.e., SpanProcessors, IdGenerator, SpanLimits and Sampler) MUST be managed solely by the TracerProvider and it MUST provide some way to configure all of them that are implemented in the SDK, at least when creating or initializing it."/>
 
 
@@ -802,7 +801,6 @@ Configuration (i.e., SpanProcessors, IdGenerator, SpanLimits and Sampler) MUST b
                
        </header>    
        <p><strong>Status</strong>: <a href="/docs/reference/specification/document-status/">Stable</a></p>
-</details>
 <h2 id="tracer-provider">Tracer Provider</h2>
 <h3 id="tracer-creation">Tracer Creation</h3>
 <p>New <code>Tracer</code> instances are always created through a <code>TracerProvider</code> (see