summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Kühl <chris@kinvolk.io>2016-02-09 13:52:25 +0100
committerChris Kühl <chris@kinvolk.io>2016-02-09 13:52:25 +0100
commit5eef9a7df826954fdbaf7c179fe0a05652d42206 (patch)
tree7ad38a65b54e6af21a5467d132191989f1c84a0d
parent7372a80b5e7d1e209f9c7a4390be108915c28c62 (diff)
docs: replace Rocket with rkt
-rw-r--r--mesos-style.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/mesos-style.md b/mesos-style.md
index c8d096be..c0510264 100644
--- a/mesos-style.md
+++ b/mesos-style.md
@@ -129,7 +129,7 @@ In contrast, in Mesos, API operations go to a particular framework. However, the
in the API server rather than in the controller. Of course you can choose to make these operations be no-ops for
your application-specific collection abstractions, and handle them in your controller.
* On the node level, Mesos allows application-specific executors, whereas Kubernetes only has
-executors for Docker and Rocket containers.
+executors for Docker and rkt containers.
The end-to-end flow is