Is, I would say, almost never the right thino g to do. And the behaviour got even more undefined when we got shortcode support in markdownify in Hugo 0.100.0 (if you start think about it, you end up in a rabbit hole pretty fast).
If you need som inner content to be rendered as Markdown, I would look into the {{% delimiter or, if really needed, apply markdownify/RenderString to smaller text snippets and not the entire .Inner block. I’m not totally sure what exactly happens in your situation (I don’t see the source).
Ok, so let’s say I remove that markdownify tag. It doesn’t really fix anything. Here is straight copy and pastes from my site and a screenshot of what is rendered.
She thought about how to word it and ended up settling on a pithy and non-specific language.
{{<lang es "I want to buy">}}Quiero comprar.</a>
The response came back soon enough.
^ Notice “The response came back soon enough.” is in the code block. And the HTML source:
<p>She thought about how to word it and ended up settling on a pithy and non-specific language.</p>
<pre><code><span class="foreign-lang" lang="es" title="I want to buy">Quiero comprar.</a>
The response came back soon enough.
So not paragraph tags around the problem statement and it never closes the