Docs fixes for Bug 298827: builtin or built-in and Bug 298832: ie (sp)

docs/en/xml/customization.xml

@@ -153,7 +153,7 @@
         to properly HTML filter data that has been passed into the template.
         This means that if the data can possibly contain special HTML characters
         such as <, and the data was not intended to be HTML, they need to be
-        converted to entity form, ie <.  You use the 'html' filter in the
+        converted to entity form, i.e. <.  You use the 'html' filter in the
         Template Toolkit to do this.  If you forget, you may open up
         your installation to cross-site scripting attacks.
       </para>
@@ -162,7 +162,7 @@
         Also note that Bugzilla adds a few filters of its own, that are not
         in standard Template Toolkit.  In particular, the 'url_quote' filter
         can convert characters that are illegal or have special meaning in URLs,
-        such as &amp;, to the encoded form, ie %26.  This actually encodes most
+        such as &amp;, to the encoded form, i.e. %26.  This actually encodes most
         characters (but not the common ones such as letters and numbers and so
         on), including the HTML-special characters, so there's never a need to
         HTML filter afterwards.
@@ -665,7 +665,7 @@
       Certain marked sections should not be changed - these are
       the <quote>plumbing</quote> which makes the rest of the function work.
       In between those sections, you'll find snippets of code like:
-      <programlisting>    # Allow the owner to change anything.
+      <programlisting>    # Allow the assignee to change anything.
     if ($ownerid eq $whoid) {
         return 1;
     }</programlisting>