diff --git a/website/content/v1.2/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.2/talos-guides/install/cloud-platforms/aws.md
index 0884baef6..597a31aad 100644
--- a/website/content/v1.2/talos-guides/install/cloud-platforms/aws.md
+++ b/website/content/v1.2/talos-guides/install/cloud-platforms/aws.md
@@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
 talosctl --talosconfig talosconfig kubeconfig .
 ```
 
-The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
+The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
 You can now watch as your cluster bootstraps, by using
 
 ```bash
diff --git a/website/content/v1.3/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.3/talos-guides/install/cloud-platforms/aws.md
index 0884baef6..597a31aad 100644
--- a/website/content/v1.3/talos-guides/install/cloud-platforms/aws.md
+++ b/website/content/v1.3/talos-guides/install/cloud-platforms/aws.md
@@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
 talosctl --talosconfig talosconfig kubeconfig .
 ```
 
-The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
+The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
 You can now watch as your cluster bootstraps, by using
 
 ```bash
diff --git a/website/content/v1.4/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.4/talos-guides/install/cloud-platforms/aws.md
index 0884baef6..597a31aad 100644
--- a/website/content/v1.4/talos-guides/install/cloud-platforms/aws.md
+++ b/website/content/v1.4/talos-guides/install/cloud-platforms/aws.md
@@ -308,7 +308,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
 talosctl --talosconfig talosconfig kubeconfig .
 ```
 
-The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
+The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
 You can now watch as your cluster bootstraps, by using
 
 ```bash
diff --git a/website/content/v1.5/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.5/talos-guides/install/cloud-platforms/aws.md
index 113803d2e..41afae69a 100644
--- a/website/content/v1.5/talos-guides/install/cloud-platforms/aws.md
+++ b/website/content/v1.5/talos-guides/install/cloud-platforms/aws.md
@@ -317,7 +317,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
 talosctl --talosconfig talosconfig kubeconfig .
 ```
 
-The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
+The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
 You can now watch as your cluster bootstraps, by using
 
 ```bash
diff --git a/website/content/v1.6/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.6/talos-guides/install/cloud-platforms/aws.md
index 113803d2e..41afae69a 100644
--- a/website/content/v1.6/talos-guides/install/cloud-platforms/aws.md
+++ b/website/content/v1.6/talos-guides/install/cloud-platforms/aws.md
@@ -317,7 +317,7 @@ At this point we can retrieve the admin `kubeconfig` by running:
 talosctl --talosconfig talosconfig kubeconfig .
 ```
 
-The different control plane nodes should sendi/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
+The different control plane nodes should send/receive traffic via the load balancer, notice that one of the control plane has intiated the etcd cluster, and the others should join.
 You can now watch as your cluster bootstraps, by using
 
 ```bash