Tip not rendered correctly

[colleenmcginnis]

Describe the bug

Tip rendered as a code block. This might be an isolated case (I'm not sure what could have made this break).

AsciiDoc	docs-builder
Link	Link

Expected behavior

Should be a note/tip containing all the content (see AsciiDoc screenshot).

Steps to reproduce

1. Build the elasticsearch.md doc set
2. Go to http://localhost:5000/rpm.html#rpm-running-systemd

Tooling

• docs-builder
• migration tooling
• I'm not sure

[reakaleek]

This looks like a migration tooling bug.

I was able to create this with

    :::{tip}
    
    **Startup timeouts with older `systemd` version**
    
    By default Elasticsearch sets the TimeoutStartSec parameter to systemd to 900s. If you are running at least version 238 of systemd then Elasticsearch can automatically extend the startup timeout, and will do so repeatedly until startup is complete even if it takes longer than 900s.
    
    Versions of systemd prior to 238 do not support the timeout extension mechanism and will terminate the Elasticsearch process if it has not fully started up within the configured timeout. If this happens, Elasticsearch will report in its logs that it was shut down normally a short time after it started:
    
    ```shell
    [2022-01-31T01:22:31,077][INFO ][o.e.n.Node               ] [instance-0000000123] starting ...
    ...
    [2022-01-31T01:37:15,077][INFO ][o.e.n.Node               ] [instance-0000000123] stopping ...
    ```
    
    However the systemd logs will report that the startup timed out:
    
    ```shell
    Jan 31 01:22:30 debian systemd[1]: Starting Elasticsearch...
    Jan 31 01:37:15 debian systemd[1]: elasticsearch.service: Start operation timed out. Terminating.
    Jan 31 01:37:15 debian systemd[1]: elasticsearch.service: Main process exited, code=killed, status=15/TERM
    Jan 31 01:37:15 debian systemd[1]: elasticsearch.service: Failed with result 'timeout'.
    Jan 31 01:37:15 debian systemd[1]: Failed to start Elasticsearch.
    ```
    
    :::

[bmorelli25]

Potentially also related to (and may be fixed by) #262.