🛠️ Fix other conformance declarations (#248)

quotes shall be straight

Signed-off-by: Andrew Berezovskyi <andriib@kth.se>

specs/asset/asset-management-spec.html

@@ -370,11 +370,11 @@ <h2>Base Requirements</h2>
 <section id="baseCompliance">
 <h2>Base Compliance</h2>
 
-<p class=‘conformance’>This specification is based on [[!OSLCCore3]]. OSLC Asset Management servers
+<p class="conformance">This specification is based on [[!OSLCCore3]]. OSLC Asset Management servers
 MUST be compliant with both the core specification,  MUST follow all the mandatory requirements in the normative sections of this specification, and SHOULD follow all the guidelines and recommendations in both
 these specifications.</p>
 
-<p class=‘conformance’>An OSLC Asset Management server MUST implement the domain vocabulary defined in <a href="http://docs.oasis-open.org/oslc-domains/qm/v2.1/asset-v2.1-part2-asset-management-vocab.html">OSLC Asset Management Version 2.1. Part 2: Vocabulary</a>
+<p class="conformance">An OSLC Asset Management server MUST implement the domain vocabulary defined in <a href="http://docs.oasis-open.org/oslc-domains/qm/v2.1/asset-v2.1-part2-asset-management-vocab.html">OSLC Asset Management Version 2.1. Part 2: Vocabulary</a>
 
 <p>The following table summarizes the requirements from OSLC Core Specification
 as well as some additional requirements specific to the Asset domain. Note that
@@ -1006,4 +1006,4 @@ <h2>Change History</h2>
 
 </body>
 
-</html>
+</html>

specs/recon/recon-resource-def.txt

@@ -1,17 +1,17 @@
 <section id="Resource-Definitions">
     <h2>Resource Definitions</h2>
 
-    <p class=‘conformance’>Resources defined by this specification can have properties other than those described here, in any namespace. It
+    <p class="conformance">Resources defined by this specification can have properties other than those described here, in any namespace. It
       is RECOMMENDED that any additional properties exist in their own unique namespace and not use the
       namespaces defined in this specification.</p>
 
-    <p class=‘conformance’>A list of properties is defined for each type of resource. Most of these properties are identified in <a
+    <p class="conformance">A list of properties is defined for each type of resource. Most of these properties are identified in <a
         href="https://archive.open-services.net/bin/view/Main/OSLCCoreSpecAppendixA.html"> OSLC Core Appendix A: Common Properties</a> and in the
       <a href="https://archive.open-services.net/wiki/reconciliation/Common-IT-Resource-Type-Vocabulary-Version-2.0/index.html">Common IT Resource Type vocabulary</a>. Any
       exceptions are noted. Relationship properties refer to other resources. These resources may be in any OSLC domain
       (including the Reconciliation domain).</p>
 
-    <p class=‘conformance’>For all resource types defined in this specification, all <strong>required</strong> properties (those defined
+    <p class="conformance">For all resource types defined in this specification, all <strong>required</strong> properties (those defined
       with an occurrence of <strong>exactly-one</strong> or <strong>one-or-many</strong>) MUST exist
       for each resource and must be provided when requested. All other properties are optional, and might not exist on
       some or any resources; those that do not exist will not be present in the returned representation even if
@@ -20,14 +20,14 @@
       own namespaces for such properties, or use standard Dublin Core or RDF namespaces and properties where
       appropriate.</p>
 
-    <p class=‘conformance’>If no specific set of properties is requested, <strong>all</strong> properties MUST be returned
+    <p class="conformance">If no specific set of properties is requested, <strong>all</strong> properties MUST be returned
       - both those defined in this specification as well as any provider-specific ones. See <a
         href="https://archive.open-services.net/bin/view/Main/OslcCoreSpecification.html#Selective_Property_Values">Selective Property Values</a>
       in the OSLC Core Specification.</p>
 
-    <p class=‘conformance’>Consumers should note that some resources may have a very large number of related resources, and that some
+    <p class="conformance">Consumers should note that some resources may have a very large number of related resources, and that some
       resources may be very large and/or expensive to compute. For this reason, consumers are strongly
         RECOMMENDED to use the <code>oslc.properties</code> parameter to limit the properties returned from a
       request to the subset required. See <a
         href="https://archive.open-services.net/bin/view/Main/OslcCoreSpecification.html#Selective_Property_Values">Selective Property Values</a>
-      in the OSLC Core Specification.</p>
+      in the OSLC Core Specification.</p>