From 3f82b616831f5651fbb160fa8d9c45220e7b587e Mon Sep 17 00:00:00 2001
From: Samler <samler@foxmail.com>
Date: Sat, 28 Jun 2025 12:38:42 +0800
Subject: [PATCH] docs: correction CAP_CUSTOM_WASM_URL use case

Fixes #56
---
 docs/guide/standalone/options.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guide/standalone/options.md b/docs/guide/standalone/options.md
index d1b7920..70b3d1c 100644
--- a/docs/guide/standalone/options.md
+++ b/docs/guide/standalone/options.md
@@ -29,10 +29,10 @@ For the floating mode, use:
 <script src="https://<server url>/assets/floating.js"></script>
 ```
 
-And by setting `window.CAP_CUSTOM_WASM_URL` to the path of the `cap_wasm_bg.wasm` file, like this:
+And by setting `window.CAP_CUSTOM_WASM_URL` to the path of the `cap_wasm.js` file, like this:
 
 ```js
-window.CAP_CUSTOM_WASM_URL = "https://<server url>/assets/cap_wasm_bg.wasm";
+window.CAP_CUSTOM_WASM_URL = "https://<server url>/assets/cap_wasm.js";
 ```
 
 By default, these fetch from `process.env.CACHE_HOST` (which defaults to `https://cdn.jsdelivr.net`). You can change this by setting the `CACHE_HOST` env variable when running the server.