[jira] [Updated] (FLUME-1624) Docs could be more consistent when giving examples of types

["Israel Ekpo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Israel Ekpo updated FLUME-1624:
-------------------------------

    Issue Type: Documentation  (was: Bug)
    
> Docs could be more consistent when giving examples of types
> -----------------------------------------------------------
>
>                 Key: FLUME-1624
>                 URL: https://issues.apache.org/jira/browse/FLUME-1624
>             Project: Flume
>          Issue Type: Documentation
>          Components: Docs
>    Affects Versions: v1.3.0
>            Reporter: Will McQueen
>            Assignee: Will McQueen
>            Priority: Minor
>             Fix For: v1.4.0
>
>
> Flume User Guide in flume.apache.org shows type names sometimes in uppercase and sometimes in lowercase. Although type name are case-insensitive (unless listing a FQCN), I recommend being consistent about using all-uppercase or all-lowercase. I recommend all-uppercase because this makes the type name stand-out more when quickly scanning a config file for type names, and it reinforces the fact that the value is an enum.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira