diff --git a/content/config/containers/multi-service_container.md b/content/config/containers/multi-service_container.md
index a552742c7c..f805758a59 100644
--- a/content/config/containers/multi-service_container.md
+++ b/content/config/containers/multi-service_container.md
@@ -25,8 +25,8 @@ your process falls into this category, you can use the `--init` option when you
 run the container. The `--init` flag inserts a tiny init-process into the
 container as the main process, and handles reaping of all processes when the
 container exits. Handling such processes this way is superior to using a
-full-fledged init process such as `sysvinit`, `upstart`, or `systemd` to handle
-process lifecycle within your container.
+full-fledged init process such as `sysvinit` or `systemd` to handle process
+lifecycle within your container.
 
 If you need to run more than one service within a container, you can achieve
 this in a few different ways.
diff --git a/content/config/containers/start-containers-automatically.md b/content/config/containers/start-containers-automatically.md
index 71c5a12c66..08a05cd264 100644
--- a/content/config/containers/start-containers-automatically.md
+++ b/content/config/containers/start-containers-automatically.md
@@ -72,8 +72,7 @@ Keep the following in mind when using restart policies:
 
 If restart policies don't suit your needs, such as when processes outside
 Docker depend on Docker containers, you can use a process manager such as
-[upstart](http://upstart.ubuntu.com/),
-[systemd](https://freedesktop.org/wiki/Software/systemd/), or
+[systemd](https://freedesktop.org/wiki/Software/systemd/) or
 [supervisor](http://supervisord.org/) instead.
 
 > **Warning**