From bd276c3e6375ef17ea82334807f780486c420452 Mon Sep 17 00:00:00 2001 From: Aaron Harper Date: Fri, 1 Jan 2021 23:04:04 -0500 Subject: [PATCH] Fixed typo in index.mdx --- website/pages/docs/nomad-vs-kubernetes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/docs/nomad-vs-kubernetes/index.mdx b/website/pages/docs/nomad-vs-kubernetes/index.mdx index ef44f1162..4a5410c6b 100644 --- a/website/pages/docs/nomad-vs-kubernetes/index.mdx +++ b/website/pages/docs/nomad-vs-kubernetes/index.mdx @@ -25,7 +25,7 @@ While Kubernetes is specifically focused on Docker, Nomad is more general purpos A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production. -In contrast to Kuberentes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments. +In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments. ## Scalability