Merge pull request #1466 from michaelhkay/1464-spelling-of-implementor

1464 Standardize on "implementer" spelling

specifications/xpath-datamodel-40/src/xpath-datamodel.xml

@@ -314,13 +314,13 @@ explanatory purposes and are not normative.</p>
   <p><termdef id="dt-implementation-defined" term="implementation
     defined"><term>Implementation-defined</term> indicates an aspect that
     may differ between implementations, but must be specified by the
-    implementor for each particular implementation.</termdef></p>
+    implementer for each particular implementation.</termdef></p>
 
   <p><termdef id="dt-implementation-dependent" term="implementation
     dependent"><term>Implementation-dependent</term> indicates an aspect
     that may differ between implementations, is not specified by this or
     any W3C specification, and is not required to be specified by the
-    implementor for any particular implementation.</termdef></p>
+    implementer for any particular implementation.</termdef></p>
 
   <p>In all cases where this specification leaves the behavior
     implementation-defined or implementation-dependent, the implementation
@@ -814,7 +814,7 @@ appropriate.</p>
 defined to be a value of type <code>xs:anyURI</code>. In
 <bibref ref="xmlschema-2"/>, the type <code>xs:anyURI</code> imposes some
 restrictions on the value space, but there is latitude for
-implementors to decide exactly what these restrictions are. In
+implementers to decide exactly what these restrictions are. In
 <bibref ref="xmlschema11-2"/> there are no restrictions on the form of
 an <code>xs:anyURI</code> value, so any sequence of characters is
 acceptable within the value space. In this and related specifications,

specifications/xpath-functions-40/src/xpath-functions.xml

@@ -11891,7 +11891,7 @@ ISBN 0 521 77752 6.</bibl>
                   <code>http://www.w3.org/2005/xpath-functions</code>, namely <code role="example">fn:put</code>. This function can be used
                to write a document to external storage. It is thus unusual in that it has side-effects; the XQuery Update 1.0
                specification defines semantics for updating expressions including this function.</p>
-               <p>Although XQuery Update 1.0 is defined as an extension of XQuery 1.0, a number of implementors have adapted it,
+               <p>Although XQuery Update 1.0 is defined as an extension of XQuery 1.0, a number of implementers have adapted it,
                in a fairly intuitive way, to work with later versions of XQuery. At the time of this publication, later versions of the
                XQuery Update specification remain at Working Draft status.</p>
             </div3>

specifications/xquery-40/src/back-matter.xml

@@ -1720,7 +1720,7 @@ specification since the publication of XPath 3.1 Recommendation.</p>
       <code>le</code>, <code>gt</code>, and <code>ge</code>; these are now defined by reference to the
       rules for the operators <code>eq</code> and <code>lt</code>.</p></item>
       <item><p>Recommended rules for processing an <code>import schema</code> declaration with multiple
-      location hints are now provided, though they are not binding on implementors.</p></item>
+      location hints are now provided, though they are not binding on implementers.</p></item>
 
     </olist>
   </div3>

specifications/xquery-40/src/expressions.xml

@@ -52,7 +52,7 @@ of <bibref
 			<p>
 				<termdef id="dt-implementation-defined" term="implementation defined"
 						><term>Implementation-defined</term> indicates an aspect that may differ
-					between implementations, but must be specified by the implementor for each
+					between implementations, but must be specified by the implementer for each
 					particular implementation.</termdef>
 			</p>
 		</item>
@@ -62,7 +62,7 @@ of <bibref
 		dependent"
 						><term>Implementation-dependent</term> indicates an aspect that may differ
 					between implementations, is not specified by this or any W3C specification, and
-					is not required to be specified by the implementor for any particular
+					is not required to be specified by the implementer for any particular
 					implementation.</termdef>
 			</p>
 		</item>

specifications/xslt-xquery-serialization-40/src/xslt-xquery-serialization.xml

@@ -1912,7 +1912,7 @@ characters in the text node.</p>
 <rfc2119>MUST NOT</rfc2119> be used except where they
 have been explicitly requested by the user, either by using the
 <code>cdata-section-elements</code> parameter, or by using some other
-<termref def="impdef">implementation-defined</termref> mechanism.</p><note><p>This is phrased to permit an implementor to provide an option that
+<termref def="impdef">implementation-defined</termref> mechanism.</p><note><p>This is phrased to permit an implementer to provide an option that
 attempts to preserve CDATA sections present in the source
 document.</p></note><imp-def-feature>A <termref def="serializer">serializer</termref> <rfc2119>MAY</rfc2119> provide an <termref def="impdef">implementation-defined</termref> mechanism to place CDATA sections in the <termref def="result-tree">result tree</termref>.</imp-def-feature></div3>
 <div3 id="XML_OMIT-XML-DECLARATION"><head>XML Output Method: the <code>omit-xml-declaration</code> and <code>standalone</code> Parameters</head><p>The XML output method