remove comma after i.e.

P5/Source/Defunct/IN-RulesForInterchange.xml

@@ -279,7 +279,7 @@ guaranteed to succeed, and negotiation of interchange formats is
 therefore <emph>required</emph>, if any of the following apply:
 <list type="simple">
 <item>The communications link between the interchange partners garbles
-or corrupts any characters of ISO 646 (IRV), (i.e., ISO 646 (IRV) is
+or corrupts any characters of ISO 646 (IRV), (i.e. ISO 646 (IRV) is
 not a subset of the transmission character set).</item>
 <item>The communications link maps characters not in the repertoire of
 ISO 646 (IRV) onto characters in that repertoire.

P5/Source/Defunct/data.language.xml

@@ -53,7 +53,7 @@ $Id$
       2.2.5 --></item><label>extension</label><item>An extension has the format of a single letter followed by a hyphen followed by
           additional subtags. These exist to allow for future extension to BCP 47, but as of this
           writing no such extensions are in use.</item><label>private use</label><item>An extension that uses the initial subtag of the single letter
-          <mentioned>x</mentioned> (i.e., starts with <code>x-</code>) has no meaning except as
+          <mentioned>x</mentioned> (i.e. starts with <code>x-</code>) has no meaning except as
           negotiated among the parties involved. These should be used with great care, since they
           interfere with the interoperability that use of RFC 4646 is intended to promote. In order
           for a document that makes use of these subtags to be TEI-conformant, a corresponding
@@ -128,7 +128,7 @@ $Id$
           existantes</quote>.<!-- RFC 4646, sect
                 2.2.5 --></item><label>extension</label><item>Une extension a la forme d'une lettre unique, suivie d'un trait d'union, lui-même suivi de sous-étiquettes additionnelles. Ces dernières existent pour tenir compte d'une future extension
           de la norme BCP 47, mais à l'heure actuelle de telles extensions ne sont pas utilisées.</item><label>usage privé</label><item>Une extension utilisant la sous-étiquette initiale de la lettre
-          <mentioned>x</mentioned> (i.e., commençant par <code>x-</code>) n'a pas d'autre signification
+          <mentioned>x</mentioned> (i.e. commençant par <code>x-</code>) n'a pas d'autre signification
           que celle négociée entre les parties impliquées. Ces sous-étiquettes doivent être utilisées avec
           beaucoup de prudence, car elles interfèrent avec l'interopérabilité que l'utilisation de
           la norme RFC 4646 vise à promouvoir. Pour qu'un document qui utilise ces sous-étiquettes soit

P5/Source/Guidelines/en/CO-CoreElements.xml

@@ -4655,7 +4655,7 @@ value <val>a</val> implies the analytic level; the values
 <val>m</val>, <val>j</val>, and <val>u</val> imply the monographic level; the value <val>s</val> implies the series level.  Note, however, that the
 semantic error occurs only if the nested title is directly enclosed by
 the <gi>analytic</gi>, <gi>monogr</gi>, or <gi>series</gi> element; if
-it is enclosed only indirectly (i.e., nested more deeply), no semantic error need be present.  For
+it is enclosed only indirectly (i.e. nested more deeply), no semantic error need be present.  For
 example, the analytic title may contain a monographic title, as in the
 following example:
   <egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="COBICOR-egXML-lp" source="#NONE"><biblStruct>

P5/Source/Guidelines/en/DI-PrintDictionaries.xml

@@ -340,7 +340,7 @@ structures defined in this module. The content model for
 nest within entries, and that senses nest within entries, homographs,
 or senses, and may be nested to any depth to reflect the embedding of
 sub-senses. Any of the top-level constituents (<gi>def</gi>,
-<gi>usg</gi>, <gi>form</gi>, etc.) can appear at any level (i.e.,
+<gi>usg</gi>, <gi>form</gi>, etc.) can appear at any level (i.e.
 within entries, homographs, or senses).<specGrp xml:id="DDIEN" n="Dictionary entries and their structure">
 
 
@@ -2373,7 +2373,7 @@ plausibly be included in either a strictly typographic or an editorial view. In
 lexical view, the only information preserved concerning domain would be some standard
 symbol or string representing the nautical domain (e.g. <q>naut.</q>) regardless of the
 form in which it appears in the printed dictionary. </p>
-<p>In practice, publishers begin with the lexical view—i.e., lexical data as it might
+<p>In practice, publishers begin with the lexical view—i.e. lexical data as it might
 appear in a database—and generate first the editorial view, which reflects editorial
 choices for a particular dictionary (such as the use of the abbreviation <q>Naut.</q>
 for <q>nautical</q>, the fonts in which different types of information are to be

P5/Source/Guidelines/en/DR-PerformanceTexts.xml

@@ -1316,7 +1316,7 @@ be divided into text divisions marked with <gi>div</gi> or
 <q>act</q> and <q>scene</q>, further subdivisions or sequences may be
 identified, composed of individual <q>shots</q>, each associated with
 a single camera angle and setting.  Shots and sequences should be
-encoded using an appropriate text-division element (i.e., a
+encoded using an appropriate text-division element (i.e. a
 <gi>div3</gi> element if numbered division elements are in use and the
 next largest unit is a <gi>div2</gi>, or a <gi>div</gi> element if
 un-numbered divisions are in use) specifying <val>sequence</val> or

P5/Source/Guidelines/en/FS-FeatureStructures.xml

@@ -1415,7 +1415,7 @@ specification (which declares what default value should be supplied
 when the named feature does not appear in an <gi>fs</gi>). 
 If, in a feature
 structure, a feature:
-<list rend="bulleted"><item> is not optional (i.e., is obligatory),</item>
+<list rend="bulleted"><item> is not optional (i.e. is obligatory),</item>
 <item> has no value provided, or the value <gi>default</gi> is
 provided (see <ref target="#FSBO">ISO 24610-1, Subclause 5.10, Default Values</ref>, and</item>
 <item> either has no default specified, or has conditional defaults,
@@ -1777,7 +1777,7 @@ also have an auxiliary and a finite verb form.  That is,
    </fs>
 </cond></egXML></p>
 <p>The second constraint says that if a construction has a BAR value of
-zero (i.e., it is a sentence), then it must have a value for the
+zero (i.e. it is a sentence), then it must have a value for the
 features N, V, and SUBCAT.  By the same token, because it is a
 biconditional, if it has values for N, V, and SUBCAT, it must have
 BAR='0'.  That is,
@@ -1792,7 +1792,7 @@ BAR='0'.  That is,
 </bicond></egXML></p>
 <!-- <binary> was <any>-->
 <p>The final constraint says that if a construction has a BAR value of 1
-(i.e., it is a phrase), then the SUBCAT feature should be absent (~).
+(i.e. it is a phrase), then the SUBCAT feature should be absent (~).
 This is not biconditional, since there are other instances under which
 the SUBCAT feature is inappropriate.  That is,
    <egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="FDFS-egXML-ri" xml:lang="und" source="#UND"><cond>

P5/Source/Guidelines/en/HD-Header.xml

@@ -48,7 +48,7 @@ text profile may however be of use in any form of automatic text
 processing.  The TEI elements used to encode the profile description
 are described in section <ptr target="#HD4"/> below.</item>
 <item>a container element, tagged <gi>xenoData</gi>, which allows easy
-inclusion of metadata from non-TEI schemes (i.e., other than
+inclusion of metadata from non-TEI schemes (i.e. other than
 elements in the TEI namespace). For example, the MARC record for the
 encoded document might be included using MARCXML or MODS. A simple set
 of metadata for harvesting might be included encoded in Dublin
@@ -2805,7 +2805,7 @@ and about the revision of the file.
          <stdVals>
             <p>The values of <att>when-iso</att> on the <gi>time</gi>
             element always end in the format <val>HH:MM</val> or
-            <val>HH</val>; i.e., seconds, fractions thereof, and time
+            <val>HH</val>; i.e. seconds, fractions thereof, and time
             zone designators are not present.</p>
          </stdVals>
          <interpretation>

P5/Source/Guidelines/en/SA-LinkingSegmentationAlignment.xml

@@ -1097,7 +1097,7 @@ specific steps to transform it into a URI reference:
           etc.) with the corresponding matched substrings</item>
         <item>the result is taken as if it were a relative or 
           absolute URI reference specified on the <att>target</att> 
-          attribute; i.e., it should be used as is or combined with
+          attribute; i.e. it should be used as is or combined with
           the current <att>xml:base</att> attribute value as usual</item>
         <item>no further processing of this value of the <att>cRef</att> 
           attribute against the <gi>refsDecl</gi> should take place</item>

P5/Source/Guidelines/en/USE.xml

@@ -1337,7 +1337,7 @@ that practice. -->
           <item>Some components may occur multiple times, but are neither grouped nor identifiable.
 	    Examples include the <gi>desc</gi>, <gi>exemplum</gi>, <gi>remarks</gi>, <gi>listRef</gi>,
 	    <gi>datatype</gi> and <gi>defaultVal</gi> elements, and the members of
-	    <ident type="class">model.identSynonyms</ident>, i.e., the <gi>equiv</gi>,
+	    <ident type="class">model.identSynonyms</ident>, i.e. the <gi>equiv</gi>,
 	    <gi>altIdent</gi>, and <gi>gloss</gi>, elements. These should be copied from both the TEI
 	    ODD specification and the ODD customization, and all occurrences included in the output.</item>
         </list>

P5/Source/Specs/att.datcat.xml

@@ -99,7 +99,7 @@
       header) is also an option.</p>
     <p>The example below presents an <gi>fvLib</gi> element that collects the relevant feature values
       (most of them omitted). At the same time, this example shows one way of encoding a 
-      <term>tagset</term>, i.e., an established inventory of values of (in the case at hand)
+      <term>tagset</term>, i.e. an established inventory of values of (in the case at hand)
       morphosyntactic categories.
       <egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="DATCAT-egXML-fo">
         <fvLib n="POS values">
@@ -307,7 +307,7 @@
     <p>The <ident type="class">att.datcat</ident> class provides means of addressing the containers
       and their values, while at the same time providing a way to interpret them in the context of
       external taxonomies or ontologies. Aligning e.g. both the <gi>pos</gi> element and the
-        <att>pos</att> attribute with the same value of an external reference point (i.e., an entry
+        <att>pos</att> attribute with the same value of an external reference point (i.e. an entry
       in an agreed taxonomy) affirms the identity of the concept serialised by both the element container
       and the attribute container, and optionally provides a definition of that concept (in the case at hand,
       the concept <term>part of speech</term>).</p>

P5/Source/Specs/att.global.xml

@@ -140,7 +140,7 @@
           a practical step-by-step guide, see 
           <ptr target="https://www.w3.org/International/questions/qa-choosing-language-tags.en.php"/>.</p>
         <p>The value used must conform with BCP 47. If the value is a
-          private use code (i.e., starts with <val>x-</val> or contains
+          private use code (i.e. starts with <val>x-</val> or contains
           <val>-x-</val>), a <gi>language</gi> element with a matching
           value for its <att>ident</att> attribute should be supplied in
           the TEI header to document this value. Such documentation may

P5/Source/Specs/graph.xml

@@ -126,7 +126,7 @@ instead of the <att>adj</att> attribute.</p>
       </remarks>
     </attDef>
     <attDef ident="order" usage="opt">
-      <desc versionDate="2005-01-14" xml:lang="en">states the order of the graph, i.e., the number of its nodes.</desc>
+      <desc versionDate="2005-01-14" xml:lang="en">states the order of the graph, i.e. the number of its nodes.</desc>
       <desc versionDate="2007-12-20" xml:lang="ko">그래프의 순서를 진술한다. 즉, 그래프 노드의 번호.</desc>
       <desc versionDate="2007-05-02" xml:lang="zh-TW">說明圖形次序，例如：節點數目。</desc>
       <desc versionDate="2008-04-05" xml:lang="ja">当該グラフのオーダー。グラフに含まれるノード数を示す。</desc>
@@ -136,7 +136,7 @@ instead of the <att>adj</att> attribute.</p>
       <datatype><dataRef key="teidata.count"/></datatype>
     </attDef>
     <attDef ident="size" usage="opt">
-      <desc versionDate="2005-01-14" xml:lang="en">states the size of the graph, i.e., the number of its arcs.</desc>
+      <desc versionDate="2005-01-14" xml:lang="en">states the size of the graph, i.e. the number of its arcs.</desc>
       <desc versionDate="2007-12-20" xml:lang="ko">그래프의 크기를 진술한다. 즉, 그래프 호의 수.</desc>
       <desc versionDate="2007-05-02" xml:lang="zh-TW">說明圖形大小，例如：連線數目。</desc>
       <desc versionDate="2008-04-05" xml:lang="ja">当該グラフのサイズ。グラフに含まれる辺数を示す。</desc>

P5/Source/Specs/langKnown.xml

@@ -8,7 +8,7 @@
   <gloss versionDate="2008-12-09" xml:lang="fr">compétence linguistique</gloss>
   <gloss versionDate="2007-05-04" xml:lang="es">competencia lingüística</gloss>
   <gloss versionDate="2007-01-21" xml:lang="it">competenza linguistica</gloss>
-  <desc versionDate="2007-07-04" xml:lang="en">summarizes the state of a person's linguistic competence, i.e., knowledge of a single language.</desc>
+  <desc versionDate="2007-07-04" xml:lang="en">summarizes the state of a person's linguistic competence, i.e. knowledge of a single language.</desc>
   <desc versionDate="2007-12-20" xml:lang="ko">개인의 언어 능력 상태를 요약한다. 즉, 한 언어에 대한 지식</desc>
   <desc versionDate="2007-05-02" xml:lang="zh-TW">個人對於某單一語言的認知狀態。</desc>
   <desc versionDate="2008-04-05" xml:lang="ja">個人の言語能力を示す。すなわち、単一言語の知識を示す。</desc>

P5/Source/Specs/root.xml

@@ -45,7 +45,7 @@ other analytic element.</desc>
       <desc versionDate="2007-01-21" xml:lang="it">fornisce una lista di identificatori degli elementi figli del nodo radice</desc>
       <datatype maxOccurs="unbounded"><dataRef key="teidata.pointer"/></datatype>
       <remarks versionDate="2013-12-06" xml:lang="en">
-        <p>If the root has no children (i.e., the tree is
+        <p>If the root has no children (i.e. the tree is
 <soCalled>trivial</soCalled>), then the <att>children</att>
 attribute should be omitted.  </p>
       </remarks>

P5/Source/Specs/teidata.language.xml

@@ -63,7 +63,7 @@
                attributes. It is described in the informational <ref target="https://www.rfc-editor.org/info/rfc6067">RFC 6067</ref>.</item>
             <label>private use</label>
             <item>An extension that uses the initial subtag of the single letter
-          <mentioned>x</mentioned> (i.e., starts with <code>x-</code>) has no meaning except as
+          <mentioned>x</mentioned> (i.e. starts with <code>x-</code>) has no meaning except as
           negotiated among the parties involved. These should be used with great care, since they
           interfere with the interoperability that use of RFC 4646 is intended to promote. In order
           for a document that makes use of these subtags to be TEI-conformant, a corresponding
@@ -223,7 +223,7 @@
           de la norme BCP 47, mais à l'heure actuelle de telles extensions ne sont pas utilisées.</item>
             <label>usage privé</label>
             <item>Une extension utilisant la sous-étiquette initiale de la lettre
-          <mentioned>x</mentioned> (i.e., commençant par <code>x-</code>) n'a pas d'autre signification
+          <mentioned>x</mentioned> (i.e. commençant par <code>x-</code>) n'a pas d'autre signification
           que celle négociée entre les parties impliquées. Ces sous-étiquettes doivent être utilisées avec
           beaucoup de prudence, car elles interfèrent avec l'interopérabilité que l'utilisation de
           la norme RFC 4646 vise à promouvoir. Pour qu'un document qui utilise ces sous-étiquettes soit

P5/Source/Specs/tree.xml

@@ -98,7 +98,7 @@ unordered.</desc>
       </valList>
     </attDef>
     <attDef ident="order" usage="opt">
-      <desc versionDate="2005-01-14" xml:lang="en">gives the order of the tree, i.e., the number of its nodes.</desc>
+      <desc versionDate="2005-01-14" xml:lang="en">gives the order of the tree, i.e. the number of its nodes.</desc>
       <desc versionDate="2007-12-20" xml:lang="ko">수형도의 순서를 제시한다. 즉, 그 노드의 수</desc>
       <desc versionDate="2007-05-02" xml:lang="zh-TW">提供樹狀結構的次序，例如節點數目。</desc>
       <desc versionDate="2008-04-05" xml:lang="ja">木構造の順番を示す。例えば、ノードの番号を示す。</desc>