- From: Anssi Kostiainen via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 24 Aug 2011 10:39:00 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/system-info
In directory hutz:/tmp/cvs-serv17342
Modified Files:
battery-status.html
Log Message:
editorial change: remove "Specification" from the title in line with Touch Events
Index: battery-status.html
===================================================================
RCS file: /sources/public/2009/dap/system-info/battery-status.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- battery-status.html 24 Aug 2011 08:07:42 -0000 1.36
+++ battery-status.html 24 Aug 2011 10:38:58 -0000 1.37
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>Battery Status Events Specification</title>
+ <title>Battery Status Events</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<script src='../ReSpec.js/js/respec.js' class='remove'></script>
<script class='remove'>
@@ -74,7 +74,7 @@
<section class="informative">
<h2>Introduction</h2>
<p>
- The Battery Status Events Specification defines a means for web
+ The Battery Status Events specification defines a means for web
developers to programmatically determine the battery status of the
hosting device and whether the device is plugged in or not. Without
knowing the battery status of a device, a web developer must design
@@ -632,7 +632,7 @@
<h2>Acknowledgements</h2>
<p>
Many thanks to the people behind the System Information API and Device
- Orientation Event Specification for inspiration. Also thanks to the
+ Orientation Event specification for inspiration. Also thanks to the
nice folks bringing us the Page Visibility specification, which
motivated the editor of this specification to write the introduction
chapter discussing some real-world high value use cases that apply
Received on Wednesday, 24 August 2011 10:39:02 UTC