chore: update docs

Author: pi0

README.md

@@ -9,19 +9,18 @@
 
 > Module resolution utilities for Node.js (based on previous work in [unjs/mlly](https://github.com/unjs/mlly), [wooorm/import-meta-resolve](https://github.com/wooorm/import-meta-resolve), and the upstream [Node.js](https://github.com/nodejs/node) implementation).
 
-This library exposes an API similar to [`import.meta.resolve`](https://nodejs.org/api/esm.html#importmetaresolvespecifier) based on Node.js upstream implementation and [resolution algorithm](https://nodejs.org/api/esm.html#esm_resolution_algorithm). It supports all built-in functionalities—`package.json`, import maps, export maps, CJS, and ESM—with some additions:
+This library exposes an API similar to [`import.meta.resolve`](https://nodejs.org/api/esm.html#importmetaresolvespecifier) based on Node.js's upstream implementation and [resolution algorithm](https://nodejs.org/api/esm.html#esm_resolution_algorithm). It supports all built-in functionalities—import maps, export maps, CJS, and ESM—with some additions:
 
 - Pure JS with no native dependencies (only Node.js is required).
-- Stable and versioned behavior.
 - Throws an error if the resolved path does not exist in the filesystem.
 - Can override the default [conditions](#conditions).
 - Can resolve [from](#from) one or more parent URLs.
-- Can resolve with implicit `/index` [suffix](#suffixes) as fallback.
-- Can resolve with implicit [extensions](#extensions) if not provided.
+- Can resolve with implicit `/index` [suffixes](#suffixes) as a fallback.
+- Can resolve with implicit [extensions](#extensions) if as fallback.
 
 ## Usage
 
-Install package:
+Install the package:
 
 ```sh
 # ✨ Auto-detect (npm, yarn, pnpm, bun, deno)
@@ -52,59 +51,55 @@ Differences between `resolveModuleURL` and `resolveModulePath`:
 
 - `resolveModuleURL` returns a URL string like `file:///app/dep.mjs`.
 - `resolveModulePath` returns an absolute path like `/app/dep.mjs`.
-  - If the resolved URL does not use the `file://` scheme (for example, `data:` or `node:`), it will throw an error.
-
-## Performance tips
-
-Resolution can be an expensive operation with various fallbacks and filesystem checks. By making stricter assumptions, we can reduce this.
-
-### Disable [`suffixes`](#suffixes) and [`extensions`](#extensions)
-
-Use `{ suffixes: [], extensions: [] }` and make sure resolve is always called with `./utils/index.ts` instead of `./utils`.
-
-### Use explicit module extensions `.mjs` or `.cjs` instead of `.js`
-
-This allows resolution fast-path to skip reading the closest `package.json` for the [`type`](https://nodejs.org/api/packages.html#type).
-
-### Make sure [`from`](#from) are explicit file URLs
-
-The paths set for [`from`](#from) should be absolute paths to the file that is requesting resolve.
-If it is set to an absolute path, resolver needs to first stat it to see if it is a file or directory.
-If input is `file://`, a URL or ends with `/`, resolver can skip this check.
+  - If the resolved URL does not use the `file://` scheme (e.g., `data:` or `node:`), it will throw an error.
 
 ## Resolve options
 
 ### `from`
 
-- Default: (current working directory)
+A URL, path, or array of URLs/paths to resolve the module from.
 
-A URL, path or array of URLs/paths to resolve module against them.
+If not provided, the resolution will start from the current working directory, but setting it is highly recommended.
 
-You can use `import.meta.url` for `from` to make behavior like `import.meta.resolve()`.
+You can use `import.meta.url` for `from` to mimic the behavior of `import.meta.resolve()`.
 
-### `conditions`
+> [!TIP]
+> For better performance, ensure the value is a `file://` URL.
+>
+> If it is set to an absolute path, the resolver first checks the filesystem to determine if it is a file or directory.
+> If the input is a `file://` URL or ends with `/`, the resolver can skip this check.
 
-- Default: `["node", "import"]`
+### `conditions`
 
-Conditions to apply when resolving package exports.
+Conditions to apply when resolving package exports (default: `["node", "import"]`).
 
 ### `suffixes`
 
-- Default: `["/index"]`
+Suffixes to check as fallbacks (default: `["/index"]`).
 
-Suffixes to check as fallback.
-
-> [!NOTE]
-> For performance, suffix fallbacks are skipped if input itself ends with the same suffix.
+> [!TIP]
+> Suffix fallbacks are skipped if the input ends with the same suffix.
+>
+> For better performance, always use explicit `/index` when needed.
+>
+> You can disable suffix fallbacks by setting `suffixes: []`.
 
 ### `extensions`
 
-- Default `[".mjs", ".cjs", ".js", ".mts", ".cts", ".ts", ".json"]`
+Additional file extensions to check as fallbacks (default: `[".mjs", ".cjs", ".js", ".mts", ".cts", ".ts", ".json"]`).
+
+> [!TIP]
+> Extension fallbacks are only checked if the input does not have an explicit extension.
+>
+> For better performance, ensure the input ends with an explicit extension.
+>
+> You can disable extension fallbacks by setting `extensions: []`.
+
+## Other Performance Tips
 
-Additional file extensions to consider when resolving modules.
+**Use explicit module extensions `.mjs` or `.cjs` instead of `.js`:**
 
-> [!NOTE]
-> For performance, extension fallbacks are only checked if input does not have an explicit extension.
+This allows the resolution fast path to skip reading the closest `package.json` for the [`type`](https://nodejs.org/api/packages.html#type).
 
 ## Development
 
@@ -113,7 +108,7 @@ Additional file extensions to consider when resolving modules.
 <summary>local development</summary>
 
 - Clone this repository
-- Install latest LTS version of [Node.js](https://nodejs.org/en/)
+- Install the latest LTS version of [Node.js](https://nodejs.org/en/)
 - Enable [Corepack](https://github.com/nodejs/corepack) using `corepack enable`
 - Install dependencies using `pnpm install`
 - Run interactive tests using `pnpm dev`