diff --git a/src/documentation/user_guides/publishing/publishing.malloynb b/src/documentation/user_guides/publishing/publishing.malloynb
index e7120bec..100f0a99 100644
--- a/src/documentation/user_guides/publishing/publishing.malloynb
+++ b/src/documentation/user_guides/publishing/publishing.malloynb
@@ -19,14 +19,14 @@ Once published, your models can be accessed via:
 The fastest way is to let Publisher scaffold one:
 
 ```bash
-npm create malloy-package my-analytics
+npm create @malloy-publisher/malloy-package my-analytics
 ```
 
 That writes the package and a starter model, registers it in `publisher.config.json` so the server actually serves it, and sets up the workspace around it: a start script, an MCP config, agent instructions, and the Malloy agent skills as files an AI assistant can read. Seed the starter model from a local file with `--data` (CSV, Parquet, or Excel):
 
 ```bash
-npm create malloy-package my-analytics -- --data ./orders.csv   # npm create needs the --
-npx create-malloy-package my-analytics --data ./orders.csv      # npx does not, and rejects it
+npm create @malloy-publisher/malloy-package my-analytics -- --data ./orders.csv   # npm create needs the --
+npx @malloy-publisher/create-malloy-package my-analytics --data ./orders.csv      # npx does not, and rejects it
 ```
 
 The two entry points differ in one way that matters. `npm create` reads anything before the `--` as one of its own options, so the separator is required there. `npx` passes flags through untouched, and a `--` would reach the tool as an extra argument.