diff --git a/website/source/docs/internals/architecture.html.md b/website/source/docs/internals/architecture.html.md index 94311de24..69bf43f77 100644 --- a/website/source/docs/internals/architecture.html.md +++ b/website/source/docs/internals/architecture.html.md @@ -37,7 +37,7 @@ clarify what is being discussed: Example Drivers include Docker, Qemu, Java, and static binaries. * **Task** - A Task is the smallest unit of work in Nomad. Tasks are executed by drivers, - which allow Nomad to be flexible in the types of tasks it supports. Tasks + which allow Nomad to be flexible in the types of tasks it supports. Tasks specify their driver, configuration for the driver, constraints, and resources required. * **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the diff --git a/website/source/docs/internals/gossip.html.md b/website/source/docs/internals/gossip.html.md index 8f9efe486..65d3919eb 100644 --- a/website/source/docs/internals/gossip.html.md +++ b/website/source/docs/internals/gossip.html.md @@ -22,7 +22,7 @@ to learn about them without having to go spelunking through the source code. ## Gossip in Nomad -Named makes use of a single global WAN gossip pool that all servers participate in. +Nomad makes use of a single global WAN gossip pool that all servers participate in. Membership information provided by the gossip pool allows servers to perform cross region requests. The integrated failure detection allows Nomad to gracefully handle an entire region losing connectivity, or just a single server in a remote region. The gossip protocol diff --git a/website/source/intro/vs/kubernetes.html.md b/website/source/intro/vs/kubernetes.html.md index 96f64fa06..e226a1094 100644 --- a/website/source/intro/vs/kubernetes.html.md +++ b/website/source/intro/vs/kubernetes.html.md @@ -25,8 +25,8 @@ common drivers. Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers -which are consumed by other services that provide higher level APIs or features -like scheduling. Kubernetes supports running in a high available +which are consumed by other services that provide higher level APIs for features +like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup. Nomad is architecturally much simpler. Nomad is a single binary, both for clients diff --git a/website/source/intro/vs/mesos.html.md b/website/source/intro/vs/mesos.html.md index 1c548c3f6..4266a90f3 100644 --- a/website/source/intro/vs/mesos.html.md +++ b/website/source/intro/vs/mesos.html.md @@ -16,8 +16,8 @@ depends on ZooKeeper to provide both coordination and storage. There are many different frameworks that integrate with Mesos, popular general purpose ones include Aurora and Marathon. These frameworks allow users to submit jobs and implement scheduling -logic. These frameworks depend on Mesos for resource management, -and external systems like ZooKeeper to provide coordination and storage. +logic. They depend on Mesos for resource management, and external +systems like ZooKeeper to provide coordination and storage. Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage.