remove the reference to the SYSAPPS-RUNTIME in abstract
define 'application' in terminology; link to the definition in prose
ISSUE: 'Create a main document steps must be defined. The main document should be created based on the manifest presence.'
ISSUE: 'Need a mechanism for passing data to the main document from the application that launched it. Does Web Activities/Intents address the use case (in scope for Web Intents Task Force), or should we e.g. pass such data in LaunchEvent?'
ISSUE: 'Should remove features that do not have strong use cases [...]'
remove RFC2119 keywords from non-normative sections
add a missing <a>
typo
acknowledgments to F2F participants
Mozilla would like the Mozilla Push API to use  ...
typo
An implementation can allow a persistent event to wake up the system from sleeping.
fix wording in introduction
fix bracing in the example
ISSUE: 'Simplify the above example for better ergonomics [...]'
remove 'The IDL fragments in this specification must be interpreted'
Conformance: 'Implementations that use ECMAScript to implement the APIs [...]'
Add 'This section is non-normative.' to non-normative sections, move 'Application Events' and 'Persistent Events' sections to non-normative 'UCs and Reqs' section; fixes to non-normative language
use uppercase RFC 2119 terms for clarity
add a browser-driven UC for Persistent Events