> Deploying fleet on CoreOS is even simpler: just run `systemctl start etcd fleet`. The default configuration assumes each of your hosts is serving an etcd endpoint at the default location (http://127.0.0.1:4001). If your etcd cluster differs, you must make the corresponding [configuration changes](config).
>
> For those running CoreOS on EC2, things are even easier! Use of the bootstrapping features built-in to CoreOS and etcd will result in fleet being started automatically.

how about flipping the order of those two thoughts, since most people (we hope) are using discovery tokens:

If you provided a discovery token to CoreOS via instance user-data, fleet will automatically start and connect to the etcd cluster.

Fleet can also be started with `systemctl start etcd fleet`. The default configuration assumes each of your hosts is serving an etcd endpoint at the default location (http://127.0.0.1:4001). If your etcd cluster differs, you must make the corresponding [configuration changes](config).