diff --git a/docs/deployment/process-management.md b/docs/deployment/process-management.md
index dbd956fec..bd924e4e4 100644
--- a/docs/deployment/process-management.md
+++ b/docs/deployment/process-management.md
@@ -15,7 +15,7 @@ ps:restart-policy <app>                        # Shows the restart-policy for an
 ps:set-restart-policy <app> <policy>           # Sets app restart-policy
 ```
 
-By default, Dokku will only start a single `web` process - if defined - though process scaling can be managed by the `ps` plugin or via a custom `DOKKU_SCALE` file.
+By default, Dokku will only start a single `web` process - if defined - though process scaling can be managed by the `ps` plugin or [via a custom `DOKKU_SCALE` file](/dokku/deployment/process-management/#manually-managing-process-scaling).
 
 > The `web` proctype is the only proctype that will invoke custom checks as defined by a CHECKS file. It is also the only process type that will be launched in a container that is either proxied via nginx or bound to an external port.
 
@@ -178,7 +178,7 @@ Restart policies have no bearing on server reboot, and Dokku will always attempt
 
 ## Manually managing process scaling
 
-You can optionally create a `DOKKU_SCALE` file in the root of your repository. Dokku expects this file to contain one line for every process defined in your Procfile.
+You can optionally _commit_ a `DOKKU_SCALE` file to the root of your repository - *not* to the /home/dokku/APP directory. Dokku expects this file to contain one line for every process defined in your Procfile.
 
 Example:
 
@@ -187,4 +187,6 @@ web=1
 worker=2
 ```
 
+If it is not committed to the repository, the `DOKKU_SCALE` file will otherwise be automatically generated based on your `ps:scale` settings.
+
 > *NOTE*: Dokku will always use the DOKKU_SCALE file that ships with the repo to override any local settings.