diff --git a/core/modules/action/action.module b/core/modules/action/action.module
old mode 100644
new mode 100755
index 58bb4a8..517a730
--- a/core/modules/action/action.module
+++ b/core/modules/action/action.module
@@ -11,16 +11,23 @@
 function action_help($path, $arg) {
   switch ($path) {
     case 'admin/help#action':
-      $output = '<p>' . t('Actions are individual tasks that the system can do, such as unpublishing a piece of content or banning a user. Other modules can fire these actions when certain system events happen; for example, when a new post is added or when a user logs in. Modules may also provide additional actions. Visit the <a href="@actions">Actions page</a> to configure actions.', array('@actions' => url('admin/config/system/actions'))) . '</p>';
+      $output = '';
+      $output .='<h3>' . t('About') . '</h3>';  
+      $output .= '<p>' . t('The Action module provides tasks that can be executed by the site such as unpublishing content, sending an e-mail, or blocking a user. Other modules can trigger these actions when specific system events happen; for example, when new content is posted or when a user logs in. Modules can also provide additional actions. <em>Simple actions</em> do not require configuration and are listed automatically as available on the <a href="@action">Actions page</a>. <em>Advanced actions</em> need to be created and configured individually. For more information, see the <a href="@documentation">online documentation for the Action module</a>.', array('@action' => url('admin/config/system/actions'), '@documentation' => 'https://drupal.org/documentation/modules/action')) . '</p>';
+      $output .= '<h3>' . t('Uses') . '</h3>';
+      $output .= '<dl>';
+      $output .= '<dt>' . t('Creating and configuring advanced actions') . '</dt>';
+      $output .= '<dd>' . t('An advanced action can be created on the <a href="@action">Actions page</a> by selecting an action type from the drop-down list. You can then configure your action, for example by specifing the e-mail address to which an automated e-mail should be sent.', array('@action' => url('admin/config/system/actions'))) . '</dd>';
+      $output .= '</dl>';
       return $output;
 
     case 'admin/config/system/actions':
     case 'admin/config/system/actions/manage':
-      $output = '<p>' . t('There are two types of actions: simple and advanced. Simple actions do not require any additional configuration and are listed here automatically. Advanced actions need to be created and configured before they can be used because they have options that need to be specified; for example, sending an e-mail to a specified address or unpublishing content containing certain words. To create an advanced action, select the action from the drop-down list in the advanced action section below and click the <em>Create</em> button.') . '</p>';
+      $output = '<p>' . t('<em>Simple actions</em> do not require configuration and are automatically listed below as available. <em>Advanced actions</em> have options that need to be specified, for example by providing an e-mail address to which an automated e-mail should be sent.  An <em>advanced action</em> can be created and then configuerd by selecting an action type from the drop-down list below.') . '</p>';
       return $output;
 
-    case 'admin/config/system/actions/configure':
-      return t('An advanced action offers additional configuration options which may be filled out below. Changing the <em>Description</em> field is recommended in order to better identify the precise action taking place.');
+   case 'admin/config/system/actions/configure':
+      return t('An advanced action has to be configured by filling in the fields below. It is recommended to change the <em>label<em> (and with it the <em>machine name</em>) in order to identify the precies action.');
   }
 }