Casing of search result types should be consistent

[waldyrious]

Initially reported as part of #629. In the example there, a search for "markdown" (http://docs.julialang.org/en/latest/search/?q=markdown) produced the following results:

• Markdown syntax(section)
• Markdown(page)
• Markdown(section)
• Markdown Syntax Extensions(section)
• InteractiveUtils.varinfo(Function)
• Advanced Usage(section)
• Tables(section)
• Links(section)
• Documentation(section)
• Unicode Input(section)
• Language changes(section)
• Deprecated or removed(section)

It's unclear why "(Function)" is in uppercase, while "(section)" and "(page)" are in lowercase. I would expect this to be consistent (all in lowercase).

This seems an easy enough issue that even someone not familiar with the codebase could fix, but I'd need some pointers regarding which files / lines to look at. Perhaps somewhere around here? https://github.com/JuliaDocs/Documenter.jl/blob/master/src/Utilities/Utilities.jl#L280-L284

[KristofferC]

Maybe because Function is the Julia type Function which is spelled with capital F?

[waldyrious]

@KristofferC the search results doesn't seem to provide a hint in this direction, though. Perhaps rendering it as code would make this clearer? I'd go as far as making it a subtle (i.e. unstyled) link to https://docs.julialang.org/en/stable/manual/functions/, but that may be overkill :)

[fredrikekre]

I'm confused, it says Function because it is a link to the varinfo Function. Similar as there are sometimes methods that are documented, where it will instead say Method.

[mortenpi]

It comes from the doccat function and the capitalization seems to be an arbitrary choice (possibly due to how it the string was used in the Markdown builds). lowercase()-ing here, which is where the categories get written into the search index, should be easiest and least intrusive fix.

[waldyrious]

Thanks for the pointer @mortenpi; I'll see if I can take a stab at that in the next few days.