address running script; see #95

storage.bs

@@ -477,22 +477,24 @@ evaluating quotas.
 
 
 
-<h2 id=ui-guidelines>User Interface Guidelines</h2>
+<h2 id=ui-guidelines>User interface guidelines</h2>
 
 <p>User agents should not distinguish between network state and storage in their user interface.
-Instead user agents should offer users the ability to remove all storage for each group of
+Instead user agents should offer users the ability to clear all storage for each group of
 <a>schemelessly same site</a> <a for=/>origins</a>. This ensures to some extent that network state
 cannot be used to revive storage. This also reduces the amount users need to know about the
 different ways in which websites can store data.
 <!-- To some extent, since HTTP ETag... And also, permissions/credentials, maybe? -->
 
+<p>User agents should not clear storage while script that is able to access the storage is running.
+
 <p>Credentials should be separated as they contain data the user might not be able to revive, such
 as an autogenerated password. Permissions are best separated too to avoid inconveniencing the user.
 Credentials and permissions are also somewhat easier to understand and differentiate for users from
 network state and storage.
 
 
-<h3 id=storage-pressure>Storage Pressure</h3>
+<h3 id=storage-pressure>Storage pressure</h3>
 
 <p>When the user agent notices it comes under storage pressure and it cannot free up sufficient
 space by clearing network state, <a>session storage buckets</a>, and <a>local storage buckets</a>