docs: replaced dev.down with dev.remove-containers

Author: cintnguyen

docs/devstack_interface.rst

@@ -51,7 +51,7 @@ Useful Commands and Summary
 
   Especially if you are running devstack after a few days of break, you will likely want to use ``make dev.pull.<service>`` before this using this command.
 
-  Also see below at ``dev.stop`` and ``dev.down`` for opposite counterparts of this command
+  Also see below at ``dev.stop`` and ``dev.remove-containers`` for opposite counterparts of this command
 
   Variations:
 
@@ -70,15 +70,15 @@ Useful Commands and Summary
   Variation:
   + ``make dev.stop.<service>`` will only stop the specified container
 
-- ``dev.down``: stops and removes all running containers as well as any networks that were created. Next time you use dev.up.<service> to bring up containers, your containers have reverted back to the pulled image.
+- ``dev.remove-containers``: stops and removes all running containers as well as any networks that were created. Next time you use dev.up.<service> to bring up containers, your containers have reverted back to the pulled image.
 
   Note: This will not affect content of the databases.
 
-  When to use: use this command only if you are okay with removing any changes you might have made to your containers. You will likely want to use ``make dev.stop`` instead of ``make dev.down``.
+  When to use: use this command only if you are okay with removing any changes you might have made to your containers. You will likely want to use ``make dev.stop`` instead of ``make dev.remove-containers``.
 
   Variation:
 
-  + ``make dev.down.<service>`` will stop and remove only the specified container.
+  + ``make dev.remove-containers.<service>`` will stop and remove only the specified container.
 
     Note: This will only bring down <service>'s container and not its dependencies.
 

docs/getting_started.rst

@@ -120,7 +120,7 @@ The default devstack services can be run by following the steps below.
 
 To stop a service, use ``make dev.stop.<service>``, and to both stop it
 and remove the container (along with any changes you have made
-to the filesystem in the container) use ``make dev.down.<service>``.
+to the filesystem in the container) use ``make dev.remove-containers.<service>``.
 
 After the services have started, if you need shell access to one of the
 services, run ``make dev.shell.<service>``. For example to access the

docs/workflow.rst

@@ -52,7 +52,7 @@ If you want to pull down just the images for one service but not its dependencie
 Database backups
 ~~~~~~~~~~~~~~~~
 
-You can routinely create backups of your local databases. To create a backup, use ``make dev.backup``. When you want to restore you database to the backup, run ``make dev.restore``. Warning, this will restore all your databases. You might have to cycle the database containers off and on using ``make dev.down.<database service name>`` and ``make dev.up.<database service name>``.
+You can routinely create backups of your local databases. To create a backup, use ``make dev.backup``. When you want to restore you database to the backup, run ``make dev.restore``. Warning, this will restore all your databases. You might have to cycle the database containers off and on using ``make dev.remove-containers.<database service name>`` and ``make dev.up.<database service name>``.
 
 Comprehensive backup
 ~~~~~~~~~~~~~~~~~~~~