Index: modules/field_ui/field_ui.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/field_ui/field_ui.module,v
retrieving revision 1.19
diff -u -p -r1.19 field_ui.module
--- modules/field_ui/field_ui.module	12 Dec 2009 23:04:57 -0000	1.19
+++ modules/field_ui/field_ui.module	15 Dec 2009 15:32:23 -0000
@@ -14,13 +14,22 @@ function field_ui_help($path, $arg) {
     case 'admin/help#field_ui':
       $output = '';
       $output .= '<h3>' . t('About') . '</h3>';
-      $output .= '<p>' . t('The Field UI module provides an administrative user interface (UI) for adding custom fields to content types, users, comments, and other types of data. The field types are defined by other modules, and collected and managed by the <a href="@field">Field module</a>. For more information, see the online handbook entry for <a href="@field-ui">Field UI module</a>.', array('@field-ui' => 'http://drupal.org/handbook/modules/field-ui', '@field' => url('admin/help/field'))) . '</p>';
+      $output .= '<p>' . t('The Field UI module provides an administrative user interface (UI) for adding custom fields to content types, users, comments, and other types of data (generically called bundles). The field types are defined by other modules, and collected and managed by the <a href="@field">Field module</a>. For more information, see the online handbook entry for <a href="@field-ui">Field UI module</a>.', array('@field-ui' => 'http://drupal.org/handbook/modules/field-ui', '@field' => url('admin/help/field'))) . '</p>';
       $output .= '<h3>' . t('Uses') . '</h3>';
       $output .= '<dl>';
-      $output .= '<dt>' . t('Defining custom fields') . '</dt>';
-      $output .= '<dd>' . t('When adding a custom field, you need to determine whether the field type will contain text, numbers, lists, etc., as well as how it will be input (as a text field, text area, select box, checkboxes, radio buttons, etc.). A field may have a single value or multiple values. For example, an employee field might have a single employee identification number, whereas a phone number field might have multiple phone numbers.') . '</dd>';
+      $output .= '<dt>' . t('Planning and adding custom fields') . '</dt>';
+      $output .= '<dd>';
+      $output .= '<p>' . t('When adding a custom field, you need to determine whether the field type will contain (text, numbers, lists, etc. — this is the field itself), how it will be input (text field, select box, radio buttons, etc. — this is called the Widget), and how it will be shown when viewed (this is called the Display).') . '</p>';
+      $output .= '<p>' . t('The name of a field that is displayed to administrators and users (its Label) may be changed after creating the field, but the machine-readable name that Drupal stores in the database cannot be changed after a field is created.') . '</p>';
+      $output .= '<p>' . t('A field may have a single value or multiple values. For example, an employee field might have a single employee identification number, whereas a phone number field might have multiple phone numbers.  This setting may be changed after you\'ve created the field, but note that if you reduce the number of values stored, any values beyond the number you\'ve set will be lost.') . '</p>';
+      $output .= '</dd>';
       $output .= '<dt>' . t('Adding fields to content types') . '</dt>';
-      $output .= '<dd>' . t("Some fields are provided by default when you create a content type, such as the Title and Body fields. The Field UI module lets administrators edit or delete the default fields attached to content, as well as create new fields for storing any additional information. Field configuration is accessible through tabs on each specific content type's configuration page, listed on the <a href='@content-types'>Content types administration page</a>. See the <a href='@node-help'>Node module help page</a> for more information about content types.", array('@content-types' => url('admin/structure/types'), '@node-help' => url('admin/help/node'))) . '</dd>';
+      $output .= '<dd>';
+      $output .= '<p>' . t('Some fields are provided by default when you create a content type, such as the Title and Body fields. The Field UI module lets administrators edit or delete these default fields, as well as create new fields for storing any additional information.') . '</p>';
+      $output .= '<p>' . t("To add or edit fields on a content type, go to the <a href='@content-types'>Content types administration page</a> and choose \"manage fields\". See the <a href='@node-help'>Node module help page</a> for more information about content types.", array('@content-types' => url('admin/structure/types'), '@node-help' => url('admin/help/node'))) . '</p>';
+      $output .= '<p>' . t('A single field may be added to more than one content type or other bundle.  A specific example is sharing the same image field between two content types so all the images are stored in the same place, and share the same image styles, without doing any extra work.  The default fields Title and Body are shared in the default content types Article and Page.') . '</p>';
+      $output .= '<p>' . t('When adding an existing field to a content type, its settings become unique to that content type.  The machine-readable name is still the same (and not editable), but all other settings will apply only to that content type.  For example, changing the number of default text format of the Body field for the Page content type does not change this setting for the Article content type, or anywhere else the Body field is used.') . '</p>';
+      $output .= '</dd>';
       $output .= '</dl>';
       return $output;