diff --git a/core/modules/translation_entity/translation_entity.module b/core/modules/translation_entity/translation_entity.module
index 9ab9cab..a530c65 100644
--- a/core/modules/translation_entity/translation_entity.module
+++ b/core/modules/translation_entity/translation_entity.module
@@ -22,16 +22,21 @@ function translation_entity_help($path, $arg) {
       $output .= '<h3>' . t('Uses') . '</h3>';
       $output .= '<dl>';
       $output .= '<dt>' . t('Enabling translation') . '</dt>';
-      $output .= '<dd>' . '<p>' . t('Before you can translate content <a href="!url">add another language</a> so that at least two languages are enabled.', array('!url' => url('admin/config/regional/language'))) . '</p>';
-      $output .= '<p>' . t('After adding languages, enable translation for any content you wish to translate. To enable translation for a certain <a href="@content-type">Content type</a>, edit the content type and in the Language settings, uncheck <em>Hide language selector</em> and check <em>Enable translation</em>. To enable translation for Comments switch to the Comment settings in the content type edit page and check <em>Enable translation</em> You enable translation of Taxonomy terms in a <a href="@vocabulary">Vocabulary</a> by editing the Vocabulary and checking <em>Enable translation</em> in the Terms settings. Similarly translation for User accounts can be enabled from the <a href="@account">Account settings</a> page, in the Language settings.', array('@content-type' => url('admin/structure/types'), '@vocabulary' => url('admin/structure/taxonomy'), '@account' => url('admin/config/people/accounts'))) . '</p>';
-      $output .= '<p>' . t('If you need to specify more precisely what should be translated, you can configure it at the field level by editing each field and then enabling or disabling translation in each field\'s <em>Global settings</em>.') . '</p></dd>';
+      $output .= '<dd><p>' . t('Before you can translate content, there must be at least two non-system languages added on the <a href="!url">languages administration</a> page.', array('!url' => url('admin/config/regional/language'))) . '</p>';
+      $output .= '<p>' . t('After adding languages, enable translation for any content you wish to translate:') . '</p>';
+      $output .= '<ul><li>' . t('<strong>Content types</strong>: Enable translation of <a href="@content_types_url">content types</a>, by clicking edit next to the appropriate type, and under Language settings, uncheck <em>Hide language selector</em> and check <em>Enable translation</em>. This allows selecting the language as part of creating or editing the content.', array('@content_types_url' => url('admin/structure/types'))) . '</li>';
+      $output .= '<li>' . t('<strong>Comments</strong>: switch to the Comment settings in the content type edit page and check Enable translation.</li>');
+      $output .= '<li>' . t('<strong>Taxonomy terms</strong>: Enable translation of <a href="@vocabularies_url">taxonomy</a> terms by editing the Vocabulary and checking <em>Enable translation</em> under Terms language.', array('@vocabularies_url' => url('admin/structure/taxonomy'))) . '</li>';
+      $output .= '<li>' . t('<strong>User accounts</strong>: Enable translation of user accounts in the <a href="@account_url">account settings page</a>, by checking <em>Enable translation</em> under Language settings.', array('@account_url' => url('admin/config/people/accounts'))) . '</li></ul>';
+      $output .= '<p>' . t('Finally, under the <em>Manage fields</em> tab, <em>edit</em> each field you wish to be translatable, and enable or disable translation under <em>Global settings</em>.') . '</p></dd>';
       $output .= '<dt>' . t('Translating content') . '</dt>';
-      $output .= '<dd>' . t('After enabling translation you can create a new content of the configured type or edit existing content and assign it a language. Once this is done you will see a <em>Translations</em> tab or link that will give you access to an overview of the translation status for the current content. From there you can add translations and edit or delete existing translations. This process is similar for every translatable element on your site, such as taxonomy terms, comments or user accounts.') . '</p>';
-      $output .= '<p>' . t('The source language can be changed. If you enable more than two languages and you create at least one content translation, when creating subsequent translations you will be able to choose which language to translate from through the <em>Source language</em> selector. If you choose a different language from the default one, all the translation form elements will be repopulated with the values from the specified source.') . '</dd>';
+      $output .= '<dd>' . t('After enabling translation you can create a new piece of content, or edit existing content and assign it a language. Once this is done you will see a Translations tab or link that will give you access to an overview of the translation status for the current content. From there, you can add translations and edit or delete existing translations. This process is similar for every translatable element on your site, such as taxonomy terms, comments or user accounts.') . '</dd>';
+      $output .= '<dt>' . t('Changing source language') . '</dt>';
+      $output .= '<dd>' . t('When there are two or more possible source languages, selecting a <em>Source language</em> will repopulate the form using the specified source\'s values. For example,  French is much closer to Spanish than to Chinese, so changing the French translation\'s source language to Spanish can assist translators.') . '</dd>';
       $output .= '<dt>' . t('Maintaining translations') . '</dt>';
-      $output .= '<dd>' . t('If editing content in one language requires that translated versions also be updated to reflect the change, use the <em>Flag other translations as outdated</em> check box to mark the translations as outdated and in need of revision.') . '</dd>';
+      $output .= '<dd>' . t('If editing content in one language requires that translated versions also be updated to reflect the change, use the Flag other translations as outdated check box to mark the translations as outdated and in need of revision.') . '</dd>';
       $output .= '<dt>' . t('Translation permissions') . '</dt>';
-      $output .= '<dd>' . t('Enabling the Entity Translation module makes a basic set of permissions available. Additional <a href="@permissions">permissions</a> are made available after translation is enabled for each type of content.', array('@permissions' => url('admin/people/permissions#module-translation_entity'))) . '</dd>';
+      $output .= '<dd>' . t('The Entity Translation module makes a basic set of permissions available. Additional <a href="@permissions">permissions</a> are made available after translation is enabled for each translatable element.', array('@permissions' => url('admin/people/permissions#module-translation_entity'))) . '</dd>';
       $output .= '</dl>';
       return $output;
   }
