Skip to content

Commit

Permalink
docs: fix a typo in QEMU VM setup guide
Browse files Browse the repository at this point in the history
Fix a typo in the QEMU VM docs.

Signed-off-by: Andrei Dobre <[email protected]>
Signed-off-by: Andrey Smirnov <[email protected]>
  • Loading branch information
voltbit authored and smira committed Apr 4, 2022
1 parent 663e3e8 commit 5192ba4
Show file tree
Hide file tree
Showing 10 changed files with 10 additions and 10 deletions.
2 changes: 1 addition & 1 deletion website/content/v0.10/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.11/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.12/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.13/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.14/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.7/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.8/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.9/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v1.0/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down
2 changes: 1 addition & 1 deletion website/content/v1.1/local-platforms/qemu.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).

Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).

## Using the Cluster

Expand Down

0 comments on commit 5192ba4

Please sign in to comment.