--- a/schema.org/drafts/changes.html	Tue Apr 10 16:55:37 2012 +0200
+++ b/schema.org/drafts/changes.html	Tue Apr 10 17:10:19 2012 +0200
@@ -23,8 +23,8 @@
 <ul>
 	<li>add new properties per <a href="http://www.w3.org/wiki/WebSchemas/Singularity">Singularity</a proposal>: 23 changes: actor, album, attendee, award, blogPost, colleague, contactPoint,
 		employee, encoding, episode, event, founder, map, member, parent, performer, photo, review, season, sibling, significantLink, subEvent, track.</li>
-    <li>How do we express the aliasing/replacement nature? For now, we simply add these. Future updates may indicate the earlier forms as archaic (in HTML and in a machine schema). 
-    OR SHOULD WE DO THIS FOR NOW? ... append: "(legacy spelling; see singular form, xxxx)" for each of the definitions of the plural spelling?</li>
+    <li>How do we express the aliasing/replacement nature? For now, we simply add these and express the aliasing in promse. 
+	Future updates may indicate the earlier forms as archaic in both HTML and in a machine schema. For now append: "(legacy spelling; see singular form, xxxx)" for each of the definitions of the plural spelling, substituting preferred i.e. singular form for 'xxx'.</li>
     <li>album(s): "A collection of music albums."; new text: "A music album."</li>
     <li>attendee(s): "A person attending the event."; new text: "A person or organization attending the event."</li>
     <li>award(s): "Awards won by this person or for this creative work."; new text: "An award won by this person or for this creative work."</li>