fixup! doc: edit import.meta.resolve documentation

Author: aduh95

doc/api/esm.md

@@ -366,16 +366,20 @@ import.meta.resolve('./dep');
 All features of the Node.js module resolution are supported. Dependency
 resolutions are subject to the permitted exports resolutions within the package.
 
-> **Caveat** This can result in synchronous file-system operations, which
-> can impact performance similarly to `require.resolve`. This feature is not
-> available within custom loaders (it would create a deadlock).
+**Caveats**:
 
-Previously, Node.js implemented an asynchronous resolver which also permitted
-a second contextual argument. The implementation has since been updated to be
-synchronous, with the second contextual `parent` argument still accessible
-behind the `--experimental-import-meta-resolve` flag:
+* This can result in synchronous file-system operations, which
+  can impact performance similarly to `require.resolve`.
+* This feature is not available within custom loaders (it would
+  create a deadlock).
+
+**Non-standard API**:
+
+When using the `--experimental-import-meta-resolve` flag, that function accepts
+a second argument:
 
 * `parent` {string|URL} An optional absolute parent module URL to resolve from.
+  **Default:** `import.meta.url`
 
 ## Interoperability with CommonJS