Merge pull request #3 from w3c/SteveALee-patch-1

Clarified GPII reference

user-research/index.html

@@ -954,7 +954,7 @@ <h3>Grouping Techniques</h3>
 				<p>Once we have a comprehensive set of techniques,  we may want to group techniques  into “enhancements”. For example, we may make a group of techniques as “simple text” enhancements for easier reference. </p>
 				<p>We may also want to identify how different enhancements benefit people with different limitations of cognitive functions. </p>
 				<p>To achieve this, we may need to label groups of cognitive functions, so that we can simplify linking enhancements to cognitive functions. See <a href="http://accessibility.athena-ict.com/cognativefunction.shtml">an initial page of cognitive function</a>. </p>
-				<p>Once we have a set of enhancements, we can enable standards, such as <abbr title="Evaluation and Report Language">EARL</abbr>, to identify  which documents support which enhancements. Other supported systems include <abbr title="Global Public Inclusive Infrastructure">GPII</abbr>, <abbr title="International Organization for Standardization">ISO</abbr>, Cloud4all, and possibly FLUID.</p>
+				<p>Once we have a set of enhancements, we can enable standards, such as <abbr title="Evaluation and Report Language">EARL</abbr>, to identify  which documents support which enhancements. Other supported standards and systems include <abbr title="International Organization for Standardization">ISO</abbr>, <abbr title="Global Public Inclusive Infrastructure">GPII</abbr> including subprojects Prosperity4All and Cloud4all, and possibly FLUID.</p>
 				<p>Once we have a comprehensive set of techniques, we can also explore what is needed to make a website adaptable to different groups of users.  We may be able to identify semantics that enable adaptation for specific learning and cognitive disabilities; and to conflicting needs of different users. </p>
 				<p> This could include:</p>
 				<ul>