Skip to content

Handle acronyms #39

Description

@nickynicolson

https://github.com/OA-WCVP/paper/blob/3a2ec92a4daa674457889ec44608ca00d00bb6df/01-summary.md

usually the Abstract is not the place to introduce acronyms and their meaning. For the sake of clarity and to help the reader find the meaning of acronyms used in this paper, it might be better to write down the full list of all acronyms used and in alphabetical order immediately after the Keywords. In addition, the Authors should evaluate the need for acronyms if used only once in the paper. Clarity is an important matter here, because the paper is of interest to a much wider audience, not a little circle of specialists.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions