Switch [spec] authors to "editors" in the Purpose section.

[jyasskin]

This is meant to fix #141. Elsewhere we use "authors" to refer to website authors, but that doesn't fit between spec developers and (presumably) spec reviewers.

Another option might be to remove this list item entirely: editors are either meant to apply the decisions of their working groups without needing to check the EWP, or they're acting as spec developers.

cc/ @lianqi

[csarven]

I'd like to offer two suggestions.

I believe the EWP Statement should be intended for either:

• any member of the standards development community, or
• any member of the W3C community.

I prefer the broader scope of the first option.

I believe the broader perspective to applying the EWP to practice beyond direct contributions to charters, specifications, or similar documents is more inclusive. It should cover anyone working on a technical or community report within W3C [1]. It also indirectly supports cases where incubation occurs outside the W3C space, making the Statement available to everyone, and so fostering a shared vision for improving the web.

[1] I've created a #143 to clarify that the Statement applies to all W3C technical or community reports, updates to those reports, and new charters.

[csarven]

Suggested change

	Spec developers, editors, and reviewers can use it to guide their thinking.
	Any member of the standards development community can use it to guide their thinking.

[csarven]

Suggested change

	Spec developers, editors, and reviewers can use it to guide their thinking.
	Any member of the W3C community can use it to guide their thinking.

[jyasskin]

+1 to Sarven's comment in general, but I think that might take this beyond an editorial change, which means we couldn't fix it in the Statement without AC review. I'd like to make the translation-aiding editorial corrections first, and then start on the next version.