W3C home > Mailing lists > Public > public-dap-commits@w3.org > January 2012

dap commit: Few language corrections

From: Mercurial notifier <cvsmail@w3.org>
Date: Tue, 31 Jan 2012 17:40:37 +0000
Message-Id: <E1RsHh7-00014t-67@mcbain.w3.org>
To: public-dap-commits@w3.org
changeset:   47:8fdb8dffe5be
tag:         tip
user:        Mounir Lamouri <mounir.lamouri@gmail.com>
date:        Tue Jan 31 18:40:09 2012 +0100
files:       network-api/index.html
description:
Few language corrections


diff -r 84a2fb7b753b -r 8fdb8dffe5be network-api/index.html
--- a/network-api/index.html	Tue Jan 31 18:00:31 2012 +0100
+++ b/network-api/index.html	Tue Jan 31 18:40:09 2012 +0100
@@ -159,20 +159,21 @@
         <dd>
           <p>
             A connection is <dfn>metered</dfn> when the user's connection is subject to a limitation from his Internet Service Provider
-            strong enough to request web applications to be gentle with the bandwidth usage.
+            strong enough to request web applications to be careful with the bandwidth usage.
           </p>
           <div class="note">
-            What is a metered connection is voluntarily left to the <a>user agent</a>. It would not be possible to give an exhaustive
-            way of all limitations considered strong enough to flag the connection has metered and even if doable, some limitations can be
+            What is a metered connection is voluntarily left to the <a>user agent</a> to judge. It would not be possible to give an exhaustive
+            list of limitations considered strong enough to flag the connection as metered and even if doable, some limitations can be
             considered strong or weak depending on the context.<br>
-            Examples of metered connections are mobile connection with a small bandwidth quota or a connection with a pay-per use.
+            Examples of metered connections are mobile connections with a small bandwidth quota or connections with a pay-per use plan.
           </div>
           <p>
             The attribute SHOULD return true if the connection with the Document's subdomain is <a title='metered'>metered</a> and false otherwise.
             If the implementation is not able to know the status of the connection or if the user is offline, it MUST return false.
           </p>
           <div class="note">
-            If not able to know if a connection is metered, a <a>user agent</a> could ask the user about the status of his current connection. For example, a preference letting the user say if the mobile connection used on the device is metered.
+            If not able to know if a connection is metered, a <a>user agent</a> could ask the user about the status of his current connection.
+            For example, a preference could let the user define if the mobile connection used on the device is metered.
           </div>
         </dd>
         <dt>[TreatNonCallableAsNull] attribute Function? onchange</dt>
@@ -186,7 +187,7 @@
       </p>
 
       <p>
-        When the user goes online or offline, in addition of the <code>change</code> event fired on the <code>Connection</code>
+        When the user goes online or offline, in addition to the <code>change</code> event fired on the <code>Connection</code>
         object, the <a>user agent</a> has to <a>fire a simple event</a> named either <code>online</code> or <code>offline</code>
         depending on the applicable value, as defined in [[!HTML5]].
       </p>
Received on Tuesday, 31 January 2012 17:40:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 31 January 2012 17:40:39 GMT