magento · jeff-matthews · Jan 30, 2020 · Jan 22, 2020 · Jan 23, 2020 · Jan 24, 2020
diff --git a/src/guides/v2.3/performance-best-practices/deployment-flow.md b/src/guides/v2.3/performance-best-practices/deployment-flow.md
@@ -9,24 +9,14 @@ functional_areas:
 
 The Magento production deployment flow helps a store reach maximum performance.
 
-## Deploy static content
+## Install dependencies
 
-Deploying static content causes Magento 2 to perform the following actions:
+The `composer.json` and `composer.lock` files manage Magento dependencies and install the appropriate version for each package. You must install dependencies before [preprocessing dependency injection instructions](#preprocess-dependency-injection-instructions) if you plan to update the [autoloader](#update-the-autoloader).
 
-*  Analyze all static resources
-*  Perform merge, minimization, and bundling of content
-*  Read and process theme data
-*  Analyze theme fallback
-*  Store all processed and materialized content to specific folder for further usage
-
-If your static content is not deployed, Magento performs all listed operation on the fly, leading to a significant increase in response time.
-
-You can use a variety of options to customize deployment operations based on store size and fulfillment needs. The most common is the compact deploy strategy. See [Static files deployment strategies]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-static-deploy-strategies.html)
-
-Run the following command to deploy static content:
+To install Magento dependencies:
 
 ```bash
-bin/magento setup:static-content:deploy
+composer install
 ```
 
 ## Preprocess dependency injection instructions
@@ -38,22 +28,70 @@ When you preprocess and compile dependency injection (DI) instructions, Magento:
 *  Creates autogenerated files (including proxies, factories, etc.)
 *  Stores compiled data and configuration in a cache that saves up to 25% of time on requests processing
 
-Run the following command to preprocess and compile DI:
+To preprocess and compile DI instructions:
 
 ```bash
 bin/magento setup:di:compile
 ```
 
-After compilation completes, confirm that [APCu is enabled]({{ page.baseurl }}/performance-best-practices/software.html#php-settings), then run the following command:
+## Update the autoloader
+
+After compilation completes, confirm that [APCu is enabled]({{ page.baseurl }}/performance-best-practices/software.html#php-settings) and update the autoloader:
+
+To update the autoloader:
+
+{:.bs-callout-info}
+The `-o` option converts PSR-0/4 autoloading to classmap to get a faster autoloader. The `--apcu` option uses APCu to cache found/not-found classes.
 
 ```bash
 composer dump-autoload -o --apcu
 ```
 
+If you plan on updating the autoloader, you must run the following commands in order:
+
+```bash
+composer install
+```
+
+```bash
+bin/magento setup:di:compile
+```
+
+```bash
+composer dump-autoload -o
+```
+
+```bash
+bin/magento setup:static-content:deploy
+```
+
+## Deploy static content
+
+Deploying static content causes Magento 2 to perform the following actions:
+
+*  Analyze all static resources
+*  Perform merge, minimization, and bundling of content
+*  Read and process theme data
+*  Analyze theme fallback
+*  Store all processed and materialized content to specific folder for further usage
+
+If your static content is not deployed, Magento performs all listed operation on the fly, leading to a significant increase in response time.
+
+You can use a variety of options to customize deployment operations based on store size and fulfillment needs. The most common is the compact deploy strategy. See [Static files deployment strategies]({{ page.baseurl }}/config-guide/cli/config-cli-subcommands-static-deploy-strategies.html)
+
+To deploy static content:
+
+```bash
+bin/magento setup:static-content:deploy
+```
+
 This command allows Composer to rebuild the mapping to project files so that they load faster.
 
 ## Set production mode
 
+{:.bs-callout-info}
+Setting the mode to production automatically runs `setup:di:compile` and `setup:static-content:deploy`.
+
 Finally, you need to place your store in Production mode. Production mode is specifically optimized for maximum performance of your store. It also de-activates all developer-specific features. This can be done in your `.htaccess` or `nginx.conf` file:
 
 `SetEnv MAGE_MODE production`