diff --git a/specs/config/config-resources.html b/specs/config/config-resources.html
index 9d37ebf..8e6dfa1 100644
--- a/specs/config/config-resources.html
+++ b/specs/config/config-resources.html
@@ -146,8 +146,7 @@
           CORS: {
             title: "Fetch standard",
             authors: ["WHATWG contributors"],
-            href:
-              "https://fetch.spec.whatwg.org/commit-snapshots/d070ea245c6eb66cf4196324f063dc6ab608d9e6/#http-cors-protocol",
+            href: "https://fetch.spec.whatwg.org/commit-snapshots/d070ea245c6eb66cf4196324f063dc6ab608d9e6/#http-cors-protocol",
             status: "Living Standard",
             publisher: "WHATWG",
           },
@@ -461,9 +460,7 @@ <h2>Supported Operations on Components</h2>
         A configuration server SHOULD support, and a global configuration server MUST support one or more component
         creation factories declared in one or more OSLC service providers.
       </p>
-      <p class="conformance">
-        A configuration server SHOULD support one or more query capabilities for components.
-      </p>
+      <p class="conformance">A configuration server SHOULD support one or more query capabilities for components.</p>
     </section>
     <section id="configoperations">
       <h2>Supported Operations on Configurations</h2>
@@ -586,9 +583,7 @@ <h2>Supported Operations on Change Set Delivery</h2>
       </p>
       <section id="creationfactorydelivery">
         <h2>Delivering change sets using a creation factory</h2>
-        <p>
-          There are several key aspects of change set delivery that OSLC Configuration Management should support:
-        </p>
+        <p>There are several key aspects of change set delivery that OSLC Configuration Management should support:</p>
         <ol>
           <li>Delivery is atomic. Either all the changed/new/removed resources are delivered, or none are.</li>
           <li>A delivery might be a long-running operation.</li>
@@ -659,9 +654,7 @@ <h2>Delivery Conflicts</h2>
       </section>
       <section id="deliveryhistory">
         <h2>Change Set Delivery History</h2>
-        <p>
-          There are several common uses cases for finding information about change set deliveries:
-        </p>
+        <p>There are several common uses cases for finding information about change set deliveries:</p>
         <ul>
           <li>When was a specified change set delivered to a specified stream, and by whom?</li>
           <li>Which streams has a specified change set been delivered to?</li>
diff --git a/specs/config/oslc-config-mgt.html b/specs/config/oslc-config-mgt.html
index 0eff530..691c8d2 100644
--- a/specs/config/oslc-config-mgt.html
+++ b/specs/config/oslc-config-mgt.html
@@ -494,7 +494,7 @@ <h2>Acknowledgements</h2>
         The following individuals have participated in the creation of this specification and are gratefully
         acknowledged:
       </p>
-      <p style="margin-left: 40px;">
+      <p style="margin-left: 40px">
         David Honey (Persistent)<br />
         Ian Green (Persistent)<br />
         Geoff Clemm (Persistent)<br />
diff --git a/specs/config/versioned-resources.html b/specs/config/versioned-resources.html
index 76b41a1..ba61c1a 100644
--- a/specs/config/versioned-resources.html
+++ b/specs/config/versioned-resources.html
@@ -229,9 +229,9 @@ <h2>Delegated UIs</h2>
     <section id="vcompact">
       <h2>Compact Rendering</h2>
       <p class="conformance">
-        A versioned resource server SHOULD implement compact rendering (resource preview), both for concept resources and version
-        resources. See <a href="config-resources.html#compact">Compact Rendering</a> for the handling of configuration
-        context in such rendering.
+        A versioned resource server SHOULD implement compact rendering (resource preview), both for concept resources
+        and version resources. See <a href="config-resources.html#compact">Compact Rendering</a> for the handling of
+        configuration context in such rendering.
       </p>
     </section>
     <section id="vtrs">