diff --git a/website/content/docs/v0.4/Getting Started/create-workload.md b/website/content/docs/v0.4/Getting Started/create-workload.md
index 14197945..93051ae2 100644
--- a/website/content/docs/v0.4/Getting Started/create-workload.md	
+++ b/website/content/docs/v0.4/Getting Started/create-workload.md	
@@ -40,7 +40,7 @@ export KUBERNETES_VERSION=v1.22.2
 export CONTROL_PLANE_PORT=6443
 export CONTROL_PLANE_ENDPOINT=1.2.3.4
 
-clusterctl config cluster cluster-0 -i sidero > cluster-0.yaml
+clusterctl generate cluster cluster-0 -i sidero > cluster-0.yaml
 ```
 
 Take a look at this new `cluster-0.yaml` manifest and make any changes as you
diff --git a/website/content/docs/v0.4/Guides/bootstrapping.md b/website/content/docs/v0.4/Guides/bootstrapping.md
index 9e227b3d..5c2f74e5 100644
--- a/website/content/docs/v0.4/Guides/bootstrapping.md
+++ b/website/content/docs/v0.4/Guides/bootstrapping.md
@@ -207,7 +207,7 @@ We are now ready to template out our management plane.
 Using clusterctl, we can create a cluster manifest with:
 
 ```bash
-clusterctl config cluster management-plane -i sidero > management-plane.yaml
+clusterctl generate cluster management-plane -i sidero > management-plane.yaml
 ```
 
 Note that there are several variables that should be set in order for the templating to work properly:
@@ -235,7 +235,7 @@ export TALOS_VERSION=v0.13
 export KUBERNETES_VERSION=v1.22.2
 export CONTROL_PLANE_PORT=6443
 export CONTROL_PLANE_ENDPOINT=1.2.3.4
-clusterctl config cluster management-plane -i sidero > management-plane.yaml
+clusterctl generate cluster management-plane -i sidero > management-plane.yaml
 ```
 
 In addition, you can specify the replicas for control-plane & worker nodes in management-plane.yaml manifest for TalosControlPlane and MachineDeployment objects.
diff --git a/website/content/docs/v0.4/Guides/first-cluster.md b/website/content/docs/v0.4/Guides/first-cluster.md
index bf1173ac..102c26a2 100644
--- a/website/content/docs/v0.4/Guides/first-cluster.md
+++ b/website/content/docs/v0.4/Guides/first-cluster.md
@@ -107,7 +107,7 @@ The cluster creation process should be identical to what was detailed in the pre
 Using clusterctl, we can create a cluster manifest with:
 
 ```bash
-clusterctl config cluster workload-cluster -i sidero > workload-cluster.yaml
+clusterctl generate cluster workload-cluster -i sidero > workload-cluster.yaml
 ```
 
 Note that there are several variables that should be set in order for the templating to work properly:
diff --git a/website/content/docs/v0.5/Getting Started/create-workload.md b/website/content/docs/v0.5/Getting Started/create-workload.md
index 14197945..93051ae2 100644
--- a/website/content/docs/v0.5/Getting Started/create-workload.md	
+++ b/website/content/docs/v0.5/Getting Started/create-workload.md	
@@ -40,7 +40,7 @@ export KUBERNETES_VERSION=v1.22.2
 export CONTROL_PLANE_PORT=6443
 export CONTROL_PLANE_ENDPOINT=1.2.3.4
 
-clusterctl config cluster cluster-0 -i sidero > cluster-0.yaml
+clusterctl generate cluster cluster-0 -i sidero > cluster-0.yaml
 ```
 
 Take a look at this new `cluster-0.yaml` manifest and make any changes as you
diff --git a/website/content/docs/v0.5/Guides/bootstrapping.md b/website/content/docs/v0.5/Guides/bootstrapping.md
index 9e227b3d..5c2f74e5 100644
--- a/website/content/docs/v0.5/Guides/bootstrapping.md
+++ b/website/content/docs/v0.5/Guides/bootstrapping.md
@@ -207,7 +207,7 @@ We are now ready to template out our management plane.
 Using clusterctl, we can create a cluster manifest with:
 
 ```bash
-clusterctl config cluster management-plane -i sidero > management-plane.yaml
+clusterctl generate cluster management-plane -i sidero > management-plane.yaml
 ```
 
 Note that there are several variables that should be set in order for the templating to work properly:
@@ -235,7 +235,7 @@ export TALOS_VERSION=v0.13
 export KUBERNETES_VERSION=v1.22.2
 export CONTROL_PLANE_PORT=6443
 export CONTROL_PLANE_ENDPOINT=1.2.3.4
-clusterctl config cluster management-plane -i sidero > management-plane.yaml
+clusterctl generate cluster management-plane -i sidero > management-plane.yaml
 ```
 
 In addition, you can specify the replicas for control-plane & worker nodes in management-plane.yaml manifest for TalosControlPlane and MachineDeployment objects.
diff --git a/website/content/docs/v0.5/Guides/first-cluster.md b/website/content/docs/v0.5/Guides/first-cluster.md
index 7a7e6a56..63ac9634 100644
--- a/website/content/docs/v0.5/Guides/first-cluster.md
+++ b/website/content/docs/v0.5/Guides/first-cluster.md
@@ -115,7 +115,7 @@ The cluster creation process should be identical to what was detailed in the pre
 Using clusterctl, we can create a cluster manifest with:
 
 ```bash
-clusterctl config cluster workload-cluster -i sidero > workload-cluster.yaml
+clusterctl generate cluster workload-cluster -i sidero > workload-cluster.yaml
 ```
 
 Note that there are several variables that should be set in order for the templating to work properly: