a few more minor grammatical edits

docs/eml-faq.md

@@ -420,12 +420,12 @@ v2.1.0.
 
 **Q:** What does ‘dereferenced’ mean?  (context: a URI in an annotation)
 
-**A:** Within the context of semantic annotation, "dereferencing" refers to the process of interpreting a URI, and providing "useful information" back about the Resource of interest. The phrase "resolving a URI" is often used synonymously with "dereferencing", but technically "resolution" refers to the process of determining HOW and WHAT to do with the URI, whereas "dereferencing" is explicitly about the action taken and its result, which is typically retrieving a representation of the Resource of interest. The formal specification for these terms and what they mean is found in the IETF's (Internet Engineering Task Force) RFC (Request for Comment) 3986 (<https://tools.ietf.org/html/rfc3986>). 
+**A:** Within the context of semantic annotation, "dereferencing" refers to the process of interpreting a URI, and providing "useful information" back about the Resource of interest. The phrase "resolving a URI" is often used synonymously with "dereferencing", but technically "resolution" refers to the process of determining HOW and WHAT to do with the URI, whereas "dereferencing" is explicitly about the action taken and its result, which is typically retrieving a representation of the Resource of interest. The formal specification for these terms and what they mean is found in the IETF's (Internet Engineering Task Force) RFC (Request for Comments) 3986 (<https://tools.ietf.org/html/rfc3986>). 
 
 
 **Q:** Explain the difference between an URI and a URL. (context: sample URIs look a lot like a URL.  What makes it a URI?)
 
-**A:** The distinctions among URIs (Uniform Resource Identifiers), URLs (Uniform Resource Locators), and URNs (Uniform Resource Names), relate to differentiating the functionalities of *identifying* a Resource, as opposed to *locating* a Resource, or doing both. URLs are all URIs (with some edge case exceptions subject to argument), and URNs are also URIs.  In many cases, URIs serve both to name and locate a Resource.  Within the vision of the Semantic Web, URIs are ideally unique, persistent URNs identifying some Web Resource, that can also serve to locate (URL) and retrieve (dereference) a representation of that Resource. The formal specification for these terms and what they mean is found in the Internet Engineering Task Force's (IETF's) *Request for Comments* RFC 3986, section 1.1.3 (<https://tools.ietf.org/html/rfc3986#section-1.1.3>). Another acronym one may encounter with increasing frequency is IRI (Internationalized Resource Identifier) that simply extends the concept of a URI to include full Unicode character set, rather than just ASCII in its construction (<https://tools.ietf.org/html/rfc3987>)
+**A:** The distinctions among URIs (Uniform Resource Identifiers), URLs (Uniform Resource Locators), and URNs (Uniform Resource Names), relate to differentiating the functionalities of *identifying* a Resource, as opposed to *locating* a Resource, or doing both. URLs are all URIs (with some edge case exceptions subject to argument), and URNs are also URIs.  In many cases, URIs serve both to name and locate a Resource.  Within the vision of the Semantic Web, URIs are ideally unique, persistent URNs identifying some Web Resource, that can also serve to locate (URL) and retrieve (dereference) a representation of that Resource. The formal specification for these terms and what they mean is found in the IETF's RFC 3986, section 1.1.3 (<https://tools.ietf.org/html/rfc3986#section-1.1.3>). Another acronym one may encounter with increasing frequency is IRI (Internationalized Resource Identifier) that simply extends the concept of a URI to include full Unicode character set, rather than just ASCII in its construction (<https://tools.ietf.org/html/rfc3987>)
 
 
 **Q:** oveeview (“When are ID’s required in the EML”) - context: annotations
@@ -435,12 +435,12 @@ v2.1.0.
 
 **Q:** What is SKOS?
 
-**A:** SKOS (Simple Knowledge Management System) is a W3C recommendation for organizing a vocabulary in thesauri, taxonomies, and other classification schemes. SKOS provides a set of concepts and properties, that, when expressed in a formal RDF-compatible syntax, can assist with interpreting the relationship of terms with one another, such as defining some category as *broader than* another. For example, one could state in SKOS syntax, that "animals" is a *broader concept than* "mammals". Definitive specification of SKOS can be found at <https://www.w3.org/TR/2009/REC-skos-reference-20090818/>. SKOS does not provide strong semantics (see RDFS example below), but SKOS concepts and properties can be used within more expressive knowledge organization frameworks, such as RDFS/OWL ontologies.
+**A:** SKOS (Simple Knowledge Management System) is a W3C recommendation for organizing a vocabulary in thesauri, taxonomies, and other classification schemes. SKOS provides a set of concepts and properties, that, when expressed in a formal RDF-compatible syntax, can assist with interpreting the relationship of terms with one another, such as defining some category as *broader than* another. For example, one could state in SKOS syntax, that "animals" is a *broader concept than* "mammals". Definitive specification of SKOS can be found at <https://www.w3.org/TR/2009/REC-skos-reference-20090818/>. SKOS does not provide strong semantics (see RDFS example below), but SKOS concepts and properties can be used to describe looser, more lexically-oriented variations in term usage (as opposed to more formally defined logical assertions, such as *owl:sameAs* or *owl:equivalentClass*),within more expressive knowledge organization frameworks, such as RDFS/OWL ontologies.
 
 
 **Q:** What is RDFS?
 
-**A:** RDFS (Resource Description Framework Schema; <https://www.w3.org/TR/rdf-schema/>) is a W3C recommendation that extends the formal vocabulary for describing Resources expressed in an RDF data model (i.e., in a *graph*). "Base" RDF <https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/> provides a set of concepts for creating a *graph* model of data-- consisting of one or more *triples* relating a *subject*, *predicate*, and *object*.  RDFS adds to the base RDF model by specifying a number of well-defined concepts and properties, such as *rdfs:Class* and *rdfs:subClassOf*. These and other RDFS classes and properties, enable data and knowledge modellers to express many relationships between the Subject and Object of a *Triple*. In the context of the Semantic Web, the RDF model relies extensively on dereferenceable URIs in the subject and predicate positions, and URIs or literals in the object position (there are small formal exceptions to this not immediately relevant here). RDF triples can be expressed in several syntaxes, including XML, JSON-LD, and Turtle, among others. RDFS then can be used to enrich the precision and expressivity of the components of a triple, as well as clarify the relationships among these.
+**A:** RDFS (Resource Description Framework Schema; <https://www.w3.org/TR/rdf-schema/>) is a W3C recommendation that extends the formal vocabulary for describing Resources expressed in an RDF data model (i.e., in a *graph*). "Base" RDF <https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/> provides a set of concepts for creating a *graph* model of data-- consisting of one or more *triples* relating a *subject*, *predicate*, and *object*.  RDFS adds to the base RDF model by specifying a number of well-defined concepts and properties, such as *rdfs:Class* and *rdfs:subClassOf*. These and other RDFS classes and properties, enable data and knowledge modellers to express many relationships between the Subject and Object of a *Triple*. In the context of the Semantic Web and Linked Data, the RDF model relies extensively on dereferenceable URIs in the subject and predicate positions, and dereferenceable URIs *or literals* in the object position (there are small formal exceptions to this not immediately relevant here). RDF triples can be expressed in several syntaxes, including XML, JSON-LD, and Turtle, among others. RDFS concepts are used to enrich the precision and expressivity of the components of a triple, as well as clarify the relationships among these, as opposed to just RDF.
 
 
 **Q:** An example of a controlled vocabulary with a *rdfs label* or *skos label* would be helpful here in this text about labels.