fix: Pull before recreating DB init scripts

We should always get the latest images before provisioning.

Also fix an unrelated typo.

Author: timmc-edx

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 retore 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.down.<database service name>`` and ``make dev.up.<database service name>``.
 
 Running micro-frontends outside of devstack
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

update-dbs-init-sql-scripts.sh

@@ -20,6 +20,7 @@ export DEVSTACK_SKIP_DEMO="true"
 # create a docker devstack with LMS and ecommerce
 make destroy
 make dev.clone.ssh
+make dev.pull.lms+ecommerce
 make dev.provision.services.lms+ecommerce
 
 # dump schema and data from mysql databases in the mysql docker container and copy them to current directory in docker host