diff --git a/README.md b/README.md
index ce9fce45..edc7cf00 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,7 @@ sudo docker run \
 
 cAdvisor is now running (in the background) on `http://localhost:8080`. The setup includes directories with Docker state cAdvisor needs to observe.
 
-**Note**: If you're running on CentOS, RHEL, or are using LXC take a look at our [running instructions](docs/running.md).
+**Note**: If you're running on CentOS, Fedora, RHEL, or are using LXC take a look at our [running instructions](docs/running.md).
 
 We have detailed [instructions](docs/running.md#standalone) on running cAdvisor standalone outside of Docker. cAdvisor [running options](docs/runtime_options.md) may also be interesting for advanced usecases. If you want to build your own cAdvisor Docker image see our [deployment](docs/deploy.md) page.
 
diff --git a/docs/running.md b/docs/running.md
index 1780c50a..10901368 100644
--- a/docs/running.md
+++ b/docs/running.md
@@ -29,6 +29,8 @@ tcp://192.168.59.103:2376
 
 In this case, cAdvisor UI should be accessible on `http://192.168.59.103:8080`
 
+## Other Configurations
+
 ### CentOS and RHEL
 
 You may need to run the container with `--privileged=true` and `--volume=/cgroup:/cgroup:ro \` in order for cAdvisor to monitor Docker containers.
@@ -37,7 +39,7 @@ RHEL and CentOS lock down their containers a bit more. cAdvisor needs access to
 
 On some versions of RHEL and CentOS the cgroup hierarchies are mounted in `/cgroup` so run cAdvisor with an additional Docker option of `--volume=/cgroup:/cgroup:ro \`.
 
-## Debian
+### Debian
 
 By default, Debian disables the memory cgroup which does not allow cAdvisor to gather memory stats. To enable the memory cgroup take a look at [these instructions](https://github.com/google/cadvisor/issues/432).