Fixed heading in markdown doc

[marcusoftnet]

Hi,

Read the documentation and saw that the configuration part of the first doc string is not rendered correctly.

There's a missing newline/empty line before the heading Configuration.

[coveralls]

Coverage remained the same at 79.747% when pulling d1df117 on marcusoftnet:patch-1 into ccf54d0 on code-corps:master.

[coveralls]

Coverage remained the same at 79.747% when pulling d1df117 on marcusoftnet:patch-1 into ccf54d0 on code-corps:master.

[coveralls]

Coverage remained the same at 79.747% when pulling c036c06 on marcusoftnet:patch-1 into ccf54d0 on code-corps:master.

[begedin]

This replaces an <h3> in the generated output with a <strong> tag.

Ideally, it should be enough of a fix to simply keep the ### Configuring and and a new line before AND after it.

Did you try that and it did not work?

[marcusoftnet]

Hi,

yes, I tried that and for some reason, that formatting doesn't work in the moduledoc attribute but does work in a doc section.

I'm not happy with this but it's at least better than the output today that contains the ### or, if you add blank lines, drops the configuration-documentation altogether.

If you want to drop this PR I totally understand. Just saw it in the docs and thought I'd try to fix it.

[begedin]

@marcusoftnet Seems you're right. I even tried updating ex_doc but it didn't help.

Oh well, it might not be an actual header, but it looks like one, compared to what it previously looked like, so I'd say this is good to go.

[begedin]

Thank you @marcusoftnet 👍

[marcusoftnet]

Awesome! That's how i thought about it too!

Thanks a lot

[mjadczak]

Should we perhaps try to find when the issue happens exactly and submit an issue to ex_doc?

[marcusoftnet]

Oh, lovely - I think I could do that. Is that a separate repo?

[begedin]

ex_doc is the package providing the mix doc command

How I would go about this

1. Create a tracking issue here
2. Create an issue on https://github.com/elixir-lang/ex_doc explaining as much as possible about what the problem is.
3. Link the external issue to our tracking issue