Issue #45: clarifying figure

index.html

@@ -136,10 +136,10 @@
       of the core profile, however the interoperability guarantees of the core profile
       hold only for the <a>WoT Core Profile</a> subset.
 
-      <section class="ednote">
-        The name <a>WoT Core Profile</a> is still under discussion in the group and is used as a working title.
-        It is subject to change after the profile specification has reached a certain level of maturity.
-      </section>
+    <section class="ednote">
+      The name <a>WoT Core Profile</a> is still under discussion in the group and is used as a working title.
+      It is subject to change after the profile specification has reached a certain level of maturity.
+    </section>
 
     <section>
       <h3>Motivation for a Profile</h3>
@@ -554,6 +554,10 @@ <h3 id="profile-description-methodology">Methodology</h3>
         to multiple profiles. Profiles can build on top of each
         other or overlap, extended profiles can be built on top
         of the core profile.</p>
+      <p>
+        This specification does not put any requirements on the 
+        scope and contents of other profiles.
+      </p>
 
       <figure id="WoT Profiles">
         <img src="images/WoT Profiles.png" class="wot-profiles" alt="WoT Profiles" />
@@ -848,7 +852,7 @@ <h4 id="constraints-against-the-td-specification">Data
             lamp1_color_g and lamp1_color_b. A similar
             mapping can be done for arrays and hierarchical
             objects. This constraint leads to simpler Thing
-              Descriptions that can be handled by very
+            Descriptions that can be handled by very
             limited devices.
           </p>
         </section>