From f21edef534ba931070842fbda91f363b9ff5f7ba Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Fri, 22 Nov 2024 15:43:52 -0800 Subject: [PATCH] Fix typo --- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- .../tuning-and-best-practices-for-rancher-at-scale.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 22642bbdf63..07dd8265986 100644 --- a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.10/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.10/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 22642bbdf63..07dd8265986 100644 --- a/versioned_docs/version-2.10/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.10/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index e2359b3762e..b3fa374cf06 100644 --- a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 22642bbdf63..07dd8265986 100644 --- a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 22642bbdf63..07dd8265986 100644 --- a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.9/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.9/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 22642bbdf63..07dd8265986 100644 --- a/versioned_docs/version-2.9/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.9/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -139,5 +139,5 @@ At high scale, Rancher transfers more data from the upstream cluster to UI compo For best performance, ensure that the host running the hardware meets these requirements: - 2020 i5 10th generation Intel (4 cores) or equivalent - 8 GB RAM - - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Total network bandwidth to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less