diff --git a/site/.vitepress/theme/index.ts b/site/.vitepress/theme/index.ts
index 82048fd..bbe19fd 100644
--- a/site/.vitepress/theme/index.ts
+++ b/site/.vitepress/theme/index.ts
@@ -13,7 +13,7 @@ export default {
       // https://vitepress.dev/guide/extending-default-theme#layout-slots
       "layout-top": () =>
         h("marquee", { class: "banner", scrollamount: "10" }, [
-          "🚧🚧🚧 sqlite-vec is still in beta, and this documentation is incomplete! Watch the repo for updates 🚧🚧🚧",
+          "🚧🚧🚧 This documentation is a work-in-progress! 🚧🚧🚧",
         ]),
       //"home-hero-image": () => h(HeroImg),
       "aside-ads-before": () => h(Sponsors),
diff --git a/site/using/wasm.md b/site/using/wasm.md
index 6c965c3..cb35ab3 100644
--- a/site/using/wasm.md
+++ b/site/using/wasm.md
@@ -24,7 +24,7 @@ It's not possibly to dynamically load a SQLite extension into a WASM build of SQ
 
 ## The `sqlite-vec-wasm-demo` NPM package
 
-A **demonstration** of `sqlite-vec` in WASM is provided with the `sqlite-vec-wasm-demo` NPM package. This package is a demonstration and may change at any time. It doesn't follow the [Semantic version of `sqlite-vec`](../versioning.md).
+A **demonstration** of `sqlite-vec` in WASM is provided with the `sqlite-vec-wasm-demo` NPM package. This package is a demonstration and may change at any time. It doesn't follow the [Semantic version of `sqlite-vec`](./versioning.md).
 
 
 See