@@ -2411,17 +2411,23 @@ <h2>
24112411 Installable web applications
24122412 </ h2 >
24132413 < p >
2414- A common use case of a manifest is for a user agent to
2415- < dfn data-local-lt ="installing|installation " data-lt =
2416- "installed "> install</ dfn > a web application; whereby the user agent
2417- provides the end-user with a means of instantiating a new < a > top-level
2418- browsing context</ a > that has the manifest's members < a > applied</ a > to
2419- it. A web application that is installed is known as a < dfn data-export =
2420- ""> installed web application</ dfn > . That is, the manifest's members, or
2421- their defaults, are in effect on the < a > top-level browsing context</ a > .
2422- This distinguishes an installed web application from a traditional
2423- bookmark, as opening a web page from a traditional bookmark will not
2424- have the manifest's properties < a > applied</ a > to it.
2414+ Any website is an < strong > installable web application</ strong > .
2415+ </ p >
2416+ < p >
2417+ A user agent can provide a way for the end-user to < dfn data-local-lt =
2418+ "installing|installation " data-lt ="installed "> install</ dfn > a web
2419+ application on the end-user's device, allowing the user to instantiate
2420+ a new [=top-level browsing context=] with the manifest's members
2421+ [=applied=].
2422+ </ p >
2423+ < p >
2424+ Once a web application is [=installed=] it is known as a < dfn class =
2425+ "export "> installed web application</ dfn > : That is, the manifest's
2426+ members, or their defaults, are [=applied=] to the < a > top-level
2427+ browsing context</ a > of the web application. This distinguishes an
2428+ installed web application from a traditional bookmark, as opening a web
2429+ page from a traditional bookmark will not have the manifest's
2430+ properties < a > applied</ a > to it.
24252431 </ p >
24262432 < p class ="note ">
24272433 For example, on user agents that support installation, a web
0 commit comments