Consider changing the name of the spec to better convey purpose, align with conventions

[othermaciej]

The spec is currently called "IsLoggedIn". This is odd for a couple of reasons:
(1) Web standards are not usually named after a single API entry point they provide.
(2) Web standard names are usually either an acronym or separate words, not words run together (with occasional exceptions for "Web" as a prefix)
(3) isLoggedIn isn't even the most relevant entry point. That would be the one where the page tells the browser that the user is logged in, not the one where it asks the browser whether the user is logged in. Pages don't need to ask, they already know. The primary purpose of the spec is for them to share that information.

I'd propose a name like "Login State API" or "Login Status API" to align with web standard naming conventions and better convey the overall purpose of this spec.

[johnwilander]

Thanks, Maciej! I prefer Login Status API to not confuse it with login state as in cookies carrying actual credentials.