diff --git a/docs/learn/1004-first-env.md b/docs/learn/1004-first-env.md
index c1307338..3385b8b4 100644
--- a/docs/learn/1004-first-env.md
+++ b/docs/learn/1004-first-env.md
@@ -95,12 +95,14 @@ Developing for Dagger takes place in a [Cue module](https://cuelang.org/docs/con
 If you are familiar with Go, Cue modules are directly inspired by Go modules.
 Otherwise, don't worry: a Cue module is simply a directory with one or more Cue packages in it. For example, a Cue module has a `cue.mod` directory at its root.
 
-This guide will use the same directory as the root of the Dagger workspace and the Cue module, but you can create your Cue module anywhere inside the Dagger workspace.
+This guide will use the same directory as the root of the Dagger workspace and the Cue module, but you can create your Cue module anywhere inside the Dagger workspace. In general, you won't have to worry about it at all. You will initialize a dagger workspace with the following command.
 
 ```shell
-cue mod init
+dagger init # Optional, already present in `todoapp`
 ```
 
+> In our case, `todoapp` already contains a workspace, so this step is optional.
+
 ### Create a Cue package
 
 Now we start developing our Cue package at the root of our Cue module.
diff --git a/docs/learn/1006-google-cloud-run.md b/docs/learn/1006-google-cloud-run.md
index 84c2d997..0b06548a 100644
--- a/docs/learn/1006-google-cloud-run.md
+++ b/docs/learn/1006-google-cloud-run.md
@@ -25,14 +25,6 @@ Make sure that all commands are being run from the todoapp directory:
 cd examples/todoapp
 ```
 
-### (optional) Initialize a Cue module
-
-This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can create your Cue module anywhere inside the Dagger workspace.
-
-```shell
-cue mod init
-```
-
 ### Organize your package
 
 Let's create a new directory for our Cue package:
diff --git a/docs/learn/1007-kubernetes.md b/docs/learn/1007-kubernetes.md
index 77460b9c..cc12e605 100644
--- a/docs/learn/1007-kubernetes.md
+++ b/docs/learn/1007-kubernetes.md
@@ -97,15 +97,6 @@ Make sure that all commands are run from the todoapp directory:
 cd examples/todoapp
 ```
 
-### (optional) Initialize a Cue module
-
-This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can
-create your Cue module anywhere inside the Dagger workspace.
-
-```shell
-cue mod init
-```
-
 ### Organize your package
 
 Let's create a new directory for our Cue package:
diff --git a/docs/learn/1008-aws-cloudformation.md b/docs/learn/1008-aws-cloudformation.md
index 7884bcb4..f35ea17b 100644
--- a/docs/learn/1008-aws-cloudformation.md
+++ b/docs/learn/1008-aws-cloudformation.md
@@ -36,14 +36,6 @@ Make sure to run all commands from the todoapp directory:
 cd examples/todoapp
 ```
 
-### (optional) Initialize a Cue module
-
-This guide will use the same directory as the root of the Dagger workspace and the root of the Cue module, but you can create your Cue module anywhere inside the Dagger workspace.
-
-```shell
-cue mod init
-```
-
 ### Organize your package
 
 Let's create a new directory for our Cue package: