diff --git a/docs/formats/README.md b/docs/formats/README.md
index 9d7957cf8d..fd33a5f272 100644
--- a/docs/formats/README.md
+++ b/docs/formats/README.md
@@ -274,7 +274,7 @@ values.
 embodies Zed's more general model for heterogeneous and self-describing schemas.
 * [Zed over JSON](zjson.md) defines a JSON format for encapsulating Zed data
 in JSON for easy decoding by JSON-based clients, e.g.,
-the [zed-js JavaScript library](https://github.com/brimdata/zealot/tree/main/packages/zed-js)
+the [zed-js JavaScript library](https://github.com/brimdata/zui/tree/main/packages/zed-js)
 and the [Zed Python library](../libraries/python.md).
 
 Because all of the formats conform to the same Zed data model, conversions between
diff --git a/docs/formats/zjson.md b/docs/formats/zjson.md
index 30b54a7853..af8ff2adf0 100644
--- a/docs/formats/zjson.md
+++ b/docs/formats/zjson.md
@@ -65,7 +65,7 @@ so appropriate for a [super-structured data model](./README.md#2-zed-a-super-str
 like Zed.  That said, JSON can be used as an encoding format for Zed by mapping Zed data
 onto a JSON-based protocol.  This allows clients like web apps or
 Electron apps to receive and understand Zed and, with the help of client
-libraries like [zed-js](https://github.com/brimdata/zealot/tree/main/packages/zed-js),
+libraries like [zed-js](https://github.com/brimdata/zui/tree/main/packages/zed-js),
 to manipulate the rich, structured Zed types that are implemented on top of
 the basic JavaScript types.
 
diff --git a/docs/libraries/javascript.md b/docs/libraries/javascript.md
index aadcc5b38b..2d11791c74 100644
--- a/docs/libraries/javascript.md
+++ b/docs/libraries/javascript.md
@@ -5,7 +5,7 @@ sidebar_label: JavaScript
 
 # JavaScript
 
-The [zed-js library](https://github.com/brimdata/zealot/tree/main/packages/zed-js)
+The [zed-js library](https://github.com/brimdata/zui/tree/main/packages/zed-js)
 provides support for the Zed data model from within
 JavaScript as well as methods for communicating with a Zed lake.