--- a/battery/Overview.html	Mon Aug 11 11:16:04 2014 +0300
+++ b/battery/Overview.html	Mon Aug 11 11:38:21 2014 +0300
@@ -436,7 +436,7 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">Battery Status API</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-11T05:13:55.000Z" id="w3c-editor-s-draft-11-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-08-11">11 August 2014</time></h2>
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-11T05:34:46.000Z" id="w3c-editor-s-draft-11-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-08-11">11 August 2014</time></h2>
   <dl>
     
       <dt>This version:</dt>
@@ -611,7 +611,8 @@
         unable to make decisions based on the battery status. Given knowledge
         of the battery status, web developers are able to craft web content and
         applications which are power-efficient, thereby leading to improved
-        user experience.
+        user experience. Authors should be aware, however, that a naïve
+        implementation of this API can negatively affect the battery life.
      </p>
      <p>
         The Battery Status API can be used to defer or scale back work when

--- a/battery/Overview.src.html	Mon Aug 11 11:16:04 2014 +0300
+++ b/battery/Overview.src.html	Mon Aug 11 11:38:21 2014 +0300
@@ -80,7 +80,8 @@
         unable to make decisions based on the battery status. Given knowledge
         of the battery status, web developers are able to craft web content and
         applications which are power-efficient, thereby leading to improved
-        user experience.
+        user experience. Authors should be aware, however, that a naïve
+        implementation of this API can negatively affect the battery life.
      </p>
      <p>
         The Battery Status API can be used to defer or scale back work when