diff --git a/xep-0080.xml b/xep-0080.xml
index 05f24991..73370cea 100644
--- a/xep-0080.xml
+++ b/xep-0080.xml
@@ -26,10 +26,10 @@
   &hildjj;
   &stpeter;
   <revision>
-    <version>1.4pre2</version>
-    <date>in progress, last updated 2007-06-07</date>
+    <version>1.4pre3</version>
+    <date>in progress, last updated 2007-06-21</date>
     <initials>psa</initials>
-    <remark><p>Renamed to User Location; corrected pubsub examples; removed non-pubsub examples; added uri element.</p></remark>
+    <remark><p>Renamed to User Location; corrected pubsub examples; recommended pubsub/PEP as transport for location information about human users; added uri element.</p></remark>
   </revision>
   <revision>
     <version>1.3</version>
@@ -255,9 +255,9 @@
   </table>
   <p>NOTE: The datatypes specified above are defined in &w3xmlschema2;.</p>
 </section1>
-<section1 topic='Transport' anchor='transport'>
-  <p>Location information SHOULD be communicated and transported by means of &xep0060; or the subset thereof specified in &xep0163; (the examples below assume that the user's XMPP server supports PEP, thus the publish request lacks a 'to' address and the notification message has a 'from' address of the user's bare JID).</p>
-  <p>Because location information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to &PRESENCE;.</p>
+<section1 topic='Recommended Transport' anchor='transport'>
+  <p>Location information about human users SHOULD be communicated and transported by means of &xep0060; or the subset thereof specified in &xep0163; (the examples below assume that the user's XMPP server supports PEP, thus the publish request lacks a 'to' address and the notification message has a 'from' address of the user's bare JID).</p>
+  <p>Although the XMPP publish-subscribe extension is the preferred means for transporting location information about human users, applications that do not involve human users (e.g., device tracking) MAY use other transport methods; however, because location information is not pure presence information and can change independently of network availability, it SHOULD NOT be provided as an extension to &PRESENCE;.</p>
   <section2 topic='Entity publishes location via PEP' anchor='usecases-pubsub'>
     <example caption='Entity publishes location'><![CDATA[
 <iq type='set' from='portia@merchantofvenice.lit/pda' id='publish1'>