From 4f0a01355e13a83c4765a7b89d74425ad88171a3 Mon Sep 17 00:00:00 2001 From: David Nuzik Date: Thu, 31 Oct 2019 10:58:14 -0700 Subject: [PATCH] Remove "respectively" --- content/k3s/latest/en/installation/node-requirements/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/installation/node-requirements/_index.md b/content/k3s/latest/en/installation/node-requirements/_index.md index 3e3be073c62..565f6af8ba3 100644 --- a/content/k3s/latest/en/installation/node-requirements/_index.md +++ b/content/k3s/latest/en/installation/node-requirements/_index.md @@ -8,7 +8,7 @@ k3s is very lightweight, but has some minimum requirements as outlined below. Whether you're configuring a k3s cluster to run in a single-node or high-availability (HA) setup, each node running k3s should meet the following minimum requirements. You may need more resources to fit your needs. ## Pre-requisites -* Two nodes cannot have the same hostname. If all your nodes have the same hostname, pass `--node-name` or `$K3S_NODE_NAME` respectively with a unique name for each node you add to the cluster. +* Two nodes cannot have the same hostname. If all your nodes have the same hostname, pass `--node-name` or `$K3S_NODE_NAME` with a unique name for each node you add to the cluster. ## Operating Systems