docs: fix typo

Fix sendi/receive.

Signed-off-by: Till Hoffmann <till@thetillhoff.de>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
This commit is contained in:
Till Hoffmann 2025-05-16 17:07:49 +02:00 committed by Andrey Smirnov
parent f35b213b2b
commit 7a817df1cc
No known key found for this signature in database
GPG Key ID: FE042E3D4085A811
5 changed files with 5 additions and 5 deletions

View File

@ -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

View File

@ -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

View File

@ -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

View File

@ -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

View File

@ -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