From 00d451584931299089f66e92fbaad4f89901841f Mon Sep 17 00:00:00 2001
From: daimond113 <72147841+daimond113@users.noreply.github.com>
Date: Wed, 20 Nov 2024 18:40:36 +0100
Subject: [PATCH] docs: link making binary packages

---
 docs/src/content/docs/guides/binary-packages.mdx | 2 ++
 docs/src/content/docs/guides/workspaces.mdx      | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/src/content/docs/guides/binary-packages.mdx b/docs/src/content/docs/guides/binary-packages.mdx
index 5c9babd..8e7f2b6 100644
--- a/docs/src/content/docs/guides/binary-packages.mdx
+++ b/docs/src/content/docs/guides/binary-packages.mdx
@@ -8,6 +8,8 @@ A **binary package** is a package that contains a binary export.
 Binary packages can be run like a normal program. There are several ways to use
 binary packages with pesde.
 
+To make your own binary package, see the [guide](/quickstart#adding-a-main-script).
+
 ## Using `pesde x`
 
 The `pesde x` command can be used to run a one-off binary package. This is
diff --git a/docs/src/content/docs/guides/workspaces.mdx b/docs/src/content/docs/guides/workspaces.mdx
index fd3017a..b57972c 100644
--- a/docs/src/content/docs/guides/workspaces.mdx
+++ b/docs/src/content/docs/guides/workspaces.mdx
@@ -29,7 +29,7 @@ Within the root `pesde.toml` file, we can define a workspace:
 ```toml title="pesde.toml"
 name = "acme/root"
 version = "0.0.0"
-private = "true"
+private = true
 
 workspace_members = ["pkgs/*"]