Skip to content

'as-a-Service' entry contains an error #663

@daobrien

Description

@daobrien

The very last entry contains two issues:

Avoid use of an acronym if it could stand for more than one term in a single asset. for example, if you are writing content that discusses both Cloud-as-a-Service and Containers-as-a-Service.

  • IMO it would be better to write "Avoid using an acronym..."
  • The "for" in "for example" needs to be capped.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Can wait, but not too long.bugSomething is wrong and needs fixing.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions