change made as requested by rob's review

profilesont/index.html

@@ -53,7 +53,7 @@ <h2>Introduction</h2>
     This Profiles Vocabulary provides a standardized, structured and human- and machine-readable set of terms to describe profiles. Its development was triggered by the appearance of multiple profiles of the Dataset Catalog Vocabulary (DCAT) [[VOCAB-DCAT]] and examples of profile description and implementation guidance systems such as the Guidelines for Dublin Core Application Profiles [[DCAP]] and the OpenGeospatial Consortium's Standard for Modular specifications [[MODSPEC]].
   </p>
   <p>
-    Profiles aim to increase interoperability within a community of users by introducing constraints, extensions or combinations on the use of more general specifications. This Profiles Vocabulary is an RDF vocabulary to describe the resources that define and implement a <em>profile</em>. A profile, also known as a <em>data profile</em> or perhaps an <em>application profile</em>, is defined as "A data specification that constrains, extends, combines, or provides guidance or explanation about the usage of other data specifications". A <em>data specification</em> is "A specification, with human- and/or machine-processable representations, that defines the content and structure of data used in a given context". Profile resources may be human-readable documents (PDFs, textual documents), vocabularies or ontologies (XSD, RDF), constraint language resources used by specific validation tools (SHACL, ShEx, Schematron), or any other files or resources that support the profile. In this specification, each resource is defined as having a role that defines its function within the profile.
+    Profiles aim to increase interoperability within a community of users by introducing constraints, extensions or combinations on the use of more general specifications. This Profiles Vocabulary is an RDF vocabulary to describe the resources that define and implement a <em>profile</em>. A profile, such as a <em>data profile</em> or perhaps an <em>application profile</em>, is defined as "A data specification that constrains, extends, combines, or provides guidance or explanation about the usage of other data specifications". A <em>data specification</em> is "A specification, with human- and/or machine-processable representations, that defines the content and structure of data used in a given context". Profile resources may be human-readable documents (PDFs, textual documents), vocabularies or ontologies (XSD, RDF), constraint language resources used by specific validation tools (SHACL, ShEx, Schematron), or any other files or resources that support the profile. In this specification, each resource is defined as having a role that defines its function within the profile.
 	</p>
   <p>
     This vocabulary provides for descriptions of relationships between a <a>profile</a> and a <a>specification</a> or another <a>profile</a> upon which a profile is based. These descriptions are are both human- and machine-readable and use existing, standardized vocabularies as much as possible. The basis of these descriptions is a specialization of the <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-Standard">dct:Standard</a></code> class which is defined here as a <code><a href="#Class:Profile">prof:Profile</a></code>. A <code>prof:Profile</code> is related to either a <code>dct:Standard</code> or another <code>prof:Profile</code> by being a <em>profile of</em> it, formally, <a href="#Property:isProfileOf"><code>prof:isProfileOf</code></a>. Resources that conform to either a <code>dct:Standard</code> or a <code>prof:Profile</code> are formally described as doing so with the use of the <code><a href="http://www.dublincore.org/specifications/dublin-core/dcmi-terms/#terms-conformsTo">dct:conformsTo</a></code> predicate.