Update configuration-management.md (#1867)

Author: danepowell

readme/configuration-management.md

@@ -61,8 +61,8 @@ The best way to handle this is to always follow these steps when updating contri
 1. Start from a clean `local:setup` or `local:refresh`. If you are using Features, ensure that there are no overridden configuration. The `cm.features.no-overrides` flag in [project.yml](https://github.com/acquia/blt/blob/8.x/template/blt/project.yml#L62) can assist with this by halting builds with overridden features.
 2. Use `composer update drupal/modulename --with-dependencies` to download the new module version(s).
 3. Run `drush updb` to apply any pending updates locally.
-4. If any updates were applied, check if they modified any stored configuration. If using Features, check for overridden features. If using core CM, export all configuration and check for any changes on disk using `git status`.
-5. Export any changed Features (if using Features) and commit the changed configuration, along with the updated `composer.json` and `composer.lock`.
+4. Check for any modified configuration. If using Features, check for overridden features and export them. If using core CM, export all configuration (`drush config-export`) and check for any changes on disk using `git status`.
+5. Commit any changed configuration, along with the updated `composer.json` and `composer.lock`.
 
 We need to find a better way of preventing this than manually monitoring module updates. Find more information in these issues:
 * [Features and contributed module updates](https://www.drupal.org/node/2745685)