diff --git a/website/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.md b/website/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.md
index d4065703387..62d4fa33665 100644
--- a/website/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.md
+++ b/website/docs/onboarding/containers/creating-a-lima-instance-with-podman-desktop.md
@@ -54,14 +54,30 @@ Consider creating a custom Lima instance to:
      $ limactl start --name=docker template://docker-rootful
      ```
 
-   - To select the number of CPUs, the memory, and the disk size, add the `--set` option to the `limactl start` command:
+   - To select the number of CPUs, the memory, and the disk size, add the options to the `limactl start` command:
 
      ```shell-session
-     --set='.cpus = 2 | .memory = "2GiB" | .disk = "50GiB"'
+     --cpus=2 --memory=2 --disk=50
      ```
 
 2. Wait for the instance to start, and restart the Lima extension.
 
+   - Go to **<icon icon="fa-solid fa-cog" size="lg" /> Settings > Preferences > Extension: Lima**, to change the instance name and type.
+
+     - Podman (default)
+
+       - Type: podman
+       - Name: podman
+         ![Lima preferences Podman](img/lima-preferences-podman.png)
+
+     - Docker
+
+       - Type: docker
+       - Name: docker
+         ![Lima preferences Docker](img/lima-preferences-docker.png)
+
+   - Go to **<icon icon="fa-solid fa-cog" size="lg" /> Settings > Extensions > Lima**, to disable and enable the extension after changes.
+
 #### Verification
 
 - To verify the connection to a running "podman" instance:
diff --git a/website/docs/onboarding/containers/img/lima-preferences-docker.png b/website/docs/onboarding/containers/img/lima-preferences-docker.png
new file mode 100644
index 00000000000..6ce9d06b2b0
Binary files /dev/null and b/website/docs/onboarding/containers/img/lima-preferences-docker.png differ
diff --git a/website/docs/onboarding/containers/img/lima-preferences-podman.png b/website/docs/onboarding/containers/img/lima-preferences-podman.png
new file mode 100644
index 00000000000..48895f14e2f
Binary files /dev/null and b/website/docs/onboarding/containers/img/lima-preferences-podman.png differ
diff --git a/website/docs/onboarding/kubernetes/creating-a-lima-instance-with-podman-desktop.md b/website/docs/onboarding/kubernetes/creating-a-lima-instance-with-podman-desktop.md
index 2491a06e28b..8c745809b97 100644
--- a/website/docs/onboarding/kubernetes/creating-a-lima-instance-with-podman-desktop.md
+++ b/website/docs/onboarding/kubernetes/creating-a-lima-instance-with-podman-desktop.md
@@ -15,6 +15,7 @@ In the future, Podman Desktop might be able to create Lima instances.
 Consider creating a custom Lima instance to:
 
 - Control the assigned resources: CPUs, memory, and disk size.
+- Control which Kubernetes distribution (`template`) to install.
 
 #### Prerequisites
 
@@ -41,12 +42,36 @@ Consider creating a custom Lima instance to:
      $ limactl start template://k8s
      ```
 
+   - To select the number of CPUs, the memory, and the disk size, add the options to the `limactl start` command:
+
+     ```shell-session
+     --cpus=4 --memory=4 --disk=100
+     ```
+
 2. Wait for the instance to start, and restart the Lima extension.
 
+   - Go to **<icon icon="fa-solid fa-cog" size="lg" /> Settings > Preferences > Extension: Lima**, to change the instance name and type.
+
+     - k3s
+
+       - Type: kubernetes
+       - Name: k3s
+         ![Lima preferences k3s](img/lima-preferences-k3s.png)
+
+     - k8s
+
+       - Type: kubernetes
+       - Name: k8s
+         ![Lima preferences k8s](img/lima-preferences-k8s.png)
+
+   - Go to **<icon icon="fa-solid fa-cog" size="lg" /> Settings > Extensions > Lima**, to disable and enable the extension after changes.
+
 #### Verification
 
 1. When the installation is done, the location of the KUBECONFIG file is printed. See [Configuring access to a Kubernetes cluster](/docs/kubernetes/configuring-access-to-a-kubernetes-cluster).
 
+   - Go to **<icon icon="fa-solid fa-cog" size="lg" /> Settings > Preferences > Path to the kubeconfig file**, to set the path of the file.
+
 1. Use the `kubectl.lima` wrapper script to connect to the cluster:
 
    ```shell-session
diff --git a/website/docs/onboarding/kubernetes/img/lima-preferences-k3s.png b/website/docs/onboarding/kubernetes/img/lima-preferences-k3s.png
new file mode 100644
index 00000000000..12da42e1caf
Binary files /dev/null and b/website/docs/onboarding/kubernetes/img/lima-preferences-k3s.png differ
diff --git a/website/docs/onboarding/kubernetes/img/lima-preferences-k8s.png b/website/docs/onboarding/kubernetes/img/lima-preferences-k8s.png
new file mode 100644
index 00000000000..330d4e15a21
Binary files /dev/null and b/website/docs/onboarding/kubernetes/img/lima-preferences-k8s.png differ