From 5192ba4e2314c05e107adcc0a2a71a65ec35bfc3 Mon Sep 17 00:00:00 2001 From: Andrei Dobre Date: Mon, 4 Apr 2022 08:05:36 +0300 Subject: [PATCH] docs: fix a typo in QEMU VM setup guide Fix a typo in the QEMU VM docs. Signed-off-by: Andrei Dobre Signed-off-by: Andrey Smirnov --- website/content/v0.10/local-platforms/qemu.md | 2 +- website/content/v0.11/local-platforms/qemu.md | 2 +- website/content/v0.12/local-platforms/qemu.md | 2 +- website/content/v0.13/local-platforms/qemu.md | 2 +- website/content/v0.14/local-platforms/qemu.md | 2 +- website/content/v0.7/local-platforms/qemu.md | 2 +- website/content/v0.8/local-platforms/qemu.md | 2 +- website/content/v0.9/local-platforms/qemu.md | 2 +- website/content/v1.0/local-platforms/qemu.md | 2 +- website/content/v1.1/local-platforms/qemu.md | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/website/content/v0.10/local-platforms/qemu.md b/website/content/v0.10/local-platforms/qemu.md index d9d0ab978..69d0ff556 100644 --- a/website/content/v0.10/local-platforms/qemu.md +++ b/website/content/v0.10/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.11/local-platforms/qemu.md b/website/content/v0.11/local-platforms/qemu.md index 28de30ba0..1a5589b6d 100644 --- a/website/content/v0.11/local-platforms/qemu.md +++ b/website/content/v0.11/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.12/local-platforms/qemu.md b/website/content/v0.12/local-platforms/qemu.md index c78e9709e..8e7ecc32b 100644 --- a/website/content/v0.12/local-platforms/qemu.md +++ b/website/content/v0.12/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.13/local-platforms/qemu.md b/website/content/v0.13/local-platforms/qemu.md index 3b1c4d2d5..29988ab66 100644 --- a/website/content/v0.13/local-platforms/qemu.md +++ b/website/content/v0.13/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.14/local-platforms/qemu.md b/website/content/v0.14/local-platforms/qemu.md index e56f2d24a..c0f70ba4f 100644 --- a/website/content/v0.14/local-platforms/qemu.md +++ b/website/content/v0.14/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.7/local-platforms/qemu.md b/website/content/v0.7/local-platforms/qemu.md index 95e6adbf7..d4287ed9a 100644 --- a/website/content/v0.7/local-platforms/qemu.md +++ b/website/content/v0.7/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.8/local-platforms/qemu.md b/website/content/v0.8/local-platforms/qemu.md index f7e69dfa9..cd07040d9 100644 --- a/website/content/v0.8/local-platforms/qemu.md +++ b/website/content/v0.8/local-platforms/qemu.md @@ -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 diff --git a/website/content/v0.9/local-platforms/qemu.md b/website/content/v0.9/local-platforms/qemu.md index 1b9485746..b8139abee 100644 --- a/website/content/v0.9/local-platforms/qemu.md +++ b/website/content/v0.9/local-platforms/qemu.md @@ -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 diff --git a/website/content/v1.0/local-platforms/qemu.md b/website/content/v1.0/local-platforms/qemu.md index 1a0c14e71..d08a71835 100644 --- a/website/content/v1.0/local-platforms/qemu.md +++ b/website/content/v1.0/local-platforms/qemu.md @@ -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 diff --git a/website/content/v1.1/local-platforms/qemu.md b/website/content/v1.1/local-platforms/qemu.md index 1a0c14e71..d08a71835 100644 --- a/website/content/v1.1/local-platforms/qemu.md +++ b/website/content/v1.1/local-platforms/qemu.md @@ -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