ednote. people getting all bunchy over the term 'at-risk' in an edito…

…rial note, so changing ednote to remove that term and reference PFWG-ISSUE-690 instead.

aria/aria.html

@@ -7804,7 +7804,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 				<p>Authors MUST ensure the URI value of <pref>aria-describedat</pref> be a valid reference to a separate document, or a content fragment identifier in a separate document, or a content fragment identifier within the same document.</p>
 				<p>Authors SHOULD should use native markup features and self-describing content where possible (e.g., accessible SVG charts, audio-described video, EPUB footnotes), and only link to external content for descriptions when no other mechanism is available in the host language.</p>
 				<p>User agents SHOULD provide a device-independent mechanism to allow a user to navigate the user agent to content referenced by the <aref>aria-describedat</aref> attribute. User agents SHOULD also provide a device-independent mechanism to return the user's focus from the descriptive content view to the original content view. For example, a user agent MAY provide access to the document or document fragment referenced by the <aref>aria-describedat</aref> attribute in a contextual menu associated with the object.</p>
-				<p class="ednote">JC 2014-12-05. The previous paragraph may be at-risk. Implementors have <a href="http://lists.w3.org/Archives/Public/wai-xtech/2014Dec/0004.html">expressed concern</a> over the RFC-2119 "SHOULD" requirement above. If the statement remains as-is, <aref>aria-describedat</aref> would change the established ARIA pattern to not affect mainstream UI.</p>
+				<p class="ednote">Editorial Note: JC 2014-12-10 (updated from 2014-12-05 and 2014-06-03). <a href="https://www.w3.org/WAI/PF/Group/track/issues/690">PFWG-ISSUE-690</a> The RFC-2119 statements in the previous paragraph are subject to change. Several implementors have <a href="http://lists.w3.org/Archives/Public/wai-xtech/2014Dec/0004.html">expressed concern</a> that if the requirements remain as-is, <aref>aria-describedat</aref> would change the established ARIA pattern to not affect mainstream UI.</p>
 				<p>In order to provide input- and device-independent access to the associated descriptive content, authors SHOULD use the <code>tabindex</code> attribute to ensure the object is included in the default tab order.</p>
 			</div>
 			<table class="property-features">