Usage of "content author" vs. "author"

[rahimabdi]

Describe the change

I'm observing the following 6 spec instances of the term "content author":

Section	Text
Section 5.2.1 Abstract Roles	Content authors MUST NOT use abstract roles because they are not implemented in the API binding.
5.2.2 Required States and Properties	Content authors MUST provide a non-empty value for required states and properties. Content authors MUST NOT use the value undefined for required states and properties, unless undefined is an explicitly-supported value of that state or property.
5.2.3 Supported States and Properties	Content authors MAY provide values for supported states and properties, but need not in cases where default values are sufficient.
alertdialog	Content authors SHOULD make alert dialogs modal by ensuring that, while the alertdialog is shown, keyboard and mouse interactions only operate within the dialog.
6.1 Clarification of States vs. Properties	Because the distinction between states and properties is of little consequence to most web content authors, this specification refers to both "states" and "properties" simply as "attributes" whenever possible.

Is "content author" different than a "web author" or the predominant spec term "author"?

Link to the version of the specification or documentation you were looking at

Link to documentation: https://w3c.github.io/aria/

Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?

Yes.