docs(using_deis/*): add scale example and clarify process == container

Author: mboersma

docs/using_deis/process-types.rst

@@ -88,4 +88,8 @@ For Deis to use your Procfile, add the Procfile to the root of your application,
 For Docker image deployments, a Procfile in the current directory or specified by
 ``deis push --procfile`` will define the default process types for the application.
 
+Use ``deis scale web=3`` to increase ``web`` processes to 3, for example. Scaling a
+process type directly changes the number of :ref:`Containers <container>`
+running that process.
+
 .. _`process model`: https://devcenter.heroku.com/articles/process-model

docs/using_deis/using-buildpacks.rst

@@ -94,6 +94,10 @@ Use ``git push deis master`` to deploy your application.
 
 Because a Heroku-style application is detected, the ``web`` process type is automatically scaled to 1 on first deploy.
 
+Use ``deis scale web=3`` to increase ``web`` processes to 3, for example. Scaling a
+process type directly changes the number of :ref:`Containers <container>`
+running that process.
+
 Included Buildpacks
 -------------------
 For convenience, a number of buildpacks come bundled with Deis:

docs/using_deis/using-docker-images.rst

@@ -68,6 +68,11 @@ a private registry.
 
 Because you are deploying a Docker image, the ``cmd`` process type is automatically scaled to 1 on first deploy.
 
+Use ``deis scale cmd=3`` to increase ``cmd`` processes to 3, for example. Scaling a
+process type directly changes the number of :ref:`Containers <container>`
+running that process.
+
+
 .. attention::
 
     Support for Docker registry authentication is coming soon

docs/using_deis/using-dockerfiles.rst

@@ -113,6 +113,10 @@ Use ``git push deis master`` to deploy your application.
 
 Because a Dockerfile application is detected, the ``cmd`` process type is automatically scaled to 1 on first deploy.
 
+Use ``deis scale cmd=3`` to increase ``cmd`` processes to 3, for example. Scaling a
+process type directly changes the number of :ref:`Containers <container>`
+running that process.
+
 
 .. _`Dockerfile`: https://docs.docker.com/reference/builder/
 .. _`Docker Image`: https://docs.docker.com/introduction/understanding-docker/