reset and resetToDefault are doing the same thing

According to the documentation at http://wiremock.org/docs/stubbing/ reset and resetToDefault should do different things.

• reset: The WireMock server can be reset at any time, removing all stub mappings and deleting the request log
• resetToDefault: If you’ve created some file based stub mappings to be loaded at startup and you don’t want these to disappear when you do a reset you can call WireMock.resetToDefault() instead

However as far as I can tell both calls are doing the same thing.
I can even see it in the code in com.github.tomakehurst.wiremock.core.WireMockApp#resetAll:

    @Override
    public void resetAll() {
        resetToDefaultMappings();
    }

I noticed this behavior in WireMock 2.18.0.
Are there any plans for changing this behavior?

Start with the documented reset and resetToDefault behavior, then inspect com.github.tomakehurst.wiremock.core.WireMockApp#resetAll and the related resetToDefaultMappings path. Verify how file-based stub mappings and the request log are handled, and confirm that the two public operations produce the distinct outcomes described in the issue.