diff --git a/docs/1214-migrate-from-dagger-0.1.md b/docs/guides/1214-migrate-from-dagger-0.1.md
similarity index 100%
rename from docs/1214-migrate-from-dagger-0.1.md
rename to docs/guides/1214-migrate-from-dagger-0.1.md
diff --git a/docs/guides/1216-docker-cli-load.md b/docs/guides/1216-docker-cli-load.md
index f8e16681..188a4e43 100644
--- a/docs/guides/1216-docker-cli-load.md
+++ b/docs/guides/1216-docker-cli-load.md
@@ -3,10 +3,15 @@ slug: /1216/docker-cli-load
 displayed_sidebar: '0.2'
 ---
 
-# Loading a dagger image into a docker daemon
+# Loading an image into a docker engine
 
-Using `cli.#Load`, you can save a dagger image (`docker.#Image`) into a local or remote engine.
+Dagger can build, run, push and pull docker images natively, without the need of a Docker engine.
+This feature is available in the package `universe.dagger.io/docker`.
 
+However, sometimes after building an image, you specifically want to load it into your Docker engine.
+This is possible with the *Docker CLI* package: `universe.dagger.io/docker/cli`.
+
+Using `cli.#Load`, you can load an image built by Dagger into a local or remote engine.
 It can be useful to debug or test a build locally before pushing.
 
 ## Local daemon
diff --git a/website/sidebars.js b/website/sidebars.js
index d9dffe93..764842af 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -53,8 +53,8 @@ module.exports = {
         "guides/custom-buildkit",
         "guides/self-signed-certificates",
         "guides/pushing-plan-dependencies",
-        "guides/coding-style",
 	"guides/handling-outputs",
+      	"guides/migrate-from-dagger-0.1",
       ],
     },
     {
@@ -81,10 +81,6 @@ module.exports = {
         "use-cases/go-docker-swarm",
       ],
     },
-    {
-      type: "doc",
-      id: "migrate-from-dagger-0.1",
-    },
     {
       type: "link",
       label: "⬅️ Dagger 0.1",