diff --git a/core/modules/config/config.module b/core/modules/config/config.module
index 84e0210..c15bded 100644
--- a/core/modules/config/config.module
+++ b/core/modules/config/config.module
@@ -15,15 +15,50 @@ function config_help($route_name, RouteMatchInterface $route_match) {
     case 'help.page.config':
       $output = '';
       $output .= '<h3>' . t('About') . '</h3>';
-      $output .= '<p>' . t('The Configuration manager module provides a user interface for importing and exporting configuration changes; i.e., for staging configuration data between multiple instances of this web site. For more information, see the online handbook entry for <a href="!url">Configuration manager module</a>', array(
-        '!url' => 'http://drupal.org/documentation/administer/config',
-      )) . '</p>';
+      $output .= '<p>' . t('The Configuration Manager module provides a user interface for importing and exporting configuration changes between a Drupal installation in different environments, such as Development, Staging and Production, so you can make and verify your changes with a comfortable distance from your live environment.') . '</p>';
+      $output .= '<p>' . t('This allows you to deploy a configuration from one environment to another, provided they are the same site. The site is identified using a Universally Unique Identifier (UUID). The site UUID must match the target site to allow any importing of configuration files on that site.') . '</p>';
+      $output .= '<p>' . t('For more information, see the online handbook entry for <a href="!url">Configuration manager module</a>', array(
+          '!url' => 'http://drupal.org/documentation/administer/config',
+        )) . '</p>';
+      $output .= '<h3>' . t('Uses') . '</h3>';
+      $output .= '<dl>';
+      $output .= '<dt>' . t('Synchronize') . '</dt>';
+      $output .= '<dd>' . t('Once you ran the import, you should synchronize your changes which will let you review all the changes between the active and staging directories. From this list you can view the differences between the configuration to ensure that the changes are as expected, before setting the changes active. The Synchronize page will also show new or removed config files. It is important to check that there are no removals of any core configuration (such as system.*, entity.*) as this will result in a site error.'). '</dd>';
+      $output .= '<dt>' . t('Full import') . '</dt>';
+      $output .= '<dd>' . t('The full import feature can be used to import a full site configuration on a development site (given the two sites are copies of each other). You can import, synchronize, make changes, package up again and import and synchronize back on the live site as well.') . '</dd>';
+      $output .= '<dt>' . t('Full export') . '</dt>';
+      $output .= '<dd>' . t('You can download an archive of all the active configuration files with this feature.') . '</dd>';
+      $output .= '<dt>' . t('Single import') . '</dt>';
+      $output .= '<dd>' . t('The single import option lets you specify the type of the configuration file and import it from your copy-pasted value.') . '</dd>';
+      $output .= '<dt>' . t('Single export') . '</dt>';
+      $output .= '<dd>' . t('The single export option lets you retrieve the configuration that you can use to copy-paste into a the single import form.') . '</dd>';
+      $output .= '</dl>';
       return $output;
 
     case 'config.sync':
       $output = '';
       $output .= '<p>' . t('Import configuration that is placed in your staging directory. All changes, deletions, renames, and additions are listed below.') . '</p>';
       return $output;
+
+    case 'config.export_full':
+      $output = '';
+      $output .= '<p>' . t('The full export page can be used to export all configurations of this site, and download them as a gzipped tar file.') . '</p>';
+      return $output;
+
+    case 'config.import_full':
+      $output = '';
+      $output .= '<p>' . t('The full import page can be used to import the full configuration of this site by uploading a gzipped tar file consisting of all configuration yml files.') . '</p>';
+      return $output;
+
+    case 'config.export_single':
+      $output = '';
+      $output .= '<p>' . t('The single export page can be used to retrieve a single configuration in a yml structure.') . '</p>';
+      return $output;
+
+    case 'config.import_single':
+      $output = '';
+      $output .= '<p>' . t('The single import page can be used to import a single configuration by pasting a yml structure in the textarea.') . '</p>';
+      return $output;
   }
 }