Markdown: coloring wrong after fenced code block

[bpasero]

Refs: #7945

The markdown content is:

# amdefine

A module that can be used to implement AMD's define() in Node. This allows you
to code to the AMD API and have the module work in node programs without
requiring those other programs to use AMD.

## Usage

**1)** Update your package.json to indicate amdefine as a dependency:

```javascript
    "dependencies": {
        "amdefine": ">=0.1.0"
    }

Then run npm install to get amdefine into your project.

2) At the top of each module that uses define(), place this code:

if (typeof define !== 'function') { var define = require('amdefine')(module) }

Only use these snippets when loading amdefine. If you preserve the basic structure,
with the braces, it will be stripped out when using the RequireJS optimizer.

You can add spaces, line breaks and even require amdefine with a local path, but
keep the rest of the structure to get the stripping behavior.

As you may know, because if statements in JavaScript don't have their own scope, the var
declaration in the above snippet is made whether the if expression is truthy or not. If
RequireJS is loaded then the declaration is superfluous because define is already already
declared in the same scope in RequireJS. Fortunately JavaScript handles multiple var
declarations of the same variable in the same scope gracefully.

[kieferrm]

I'm not yet sure what happens. But when I add a\n or ; in front of the last '}' the tokenization is correct.

It seems the minimal case causing the wrong tokenization is:

[mjbvz]

Most cases should be fixed by #14626 . I've tested the cases in this issue, and they work fine: