Index: includes/ajax.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/ajax.inc,v
retrieving revision 1.41
diff -u -p -r1.41 ajax.inc
--- includes/ajax.inc	23 Dec 2010 04:26:31 -0000	1.41
+++ includes/ajax.inc	31 Dec 2010 22:46:37 -0000
@@ -9,6 +9,8 @@
 /**
  * @defgroup ajax AJAX framework
  * @{
+ * Functions for Drupal's AJAX framework.
+ *
  * Drupal's AJAX framework is used to dynamically update parts of a page's HTML
  * based on data from the server. Upon a specified event, such as a button
  * click, a callback function is triggered which performs server-side logic and
@@ -696,6 +698,10 @@ function ajax_pre_render_element($elemen
 /**
  * @defgroup ajax_commands AJAX framework commands
  * @{
+ * Functions to create various AJAX commands.
+ *
+ * These functions can be used to create arrays for use with the
+ * ajax_render() function.
  */
 
 /**
Index: includes/image.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/image.inc,v
retrieving revision 1.41
diff -u -p -r1.41 image.inc
--- includes/image.inc	8 Dec 2010 07:11:39 -0000	1.41
+++ includes/image.inc	31 Dec 2010 22:46:38 -0000
@@ -9,6 +9,8 @@
 /**
  * @defgroup image Image toolkits
  * @{
+ * Functions for image file manipulations.
+ *
  * Drupal's image toolkits provide an abstraction layer for common image file
  * manipulations like scaling, cropping, and rotating. The abstraction frees
  * module authors from the need to support multiple image libraries, and it
Index: includes/locale.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/locale.inc,v
retrieving revision 1.264
diff -u -p -r1.264 locale.inc
--- includes/locale.inc	21 Nov 2010 09:01:30 -0000	1.264
+++ includes/locale.inc	31 Dec 2010 22:46:40 -0000
@@ -70,6 +70,10 @@ define('LOCALE_LANGUAGE_NEGOTIATION_URL_
 /**
  * @defgroup locale-languages-negotiation Language negotiation options
  * @{
+ * Functions for language negotiation.
+ *
+ * There are functions that provide the ability to identify the
+ * language. This behavior can be controlled by various options.
  */
 
 /**
@@ -422,6 +426,9 @@ function locale_string_is_safe($string) 
 /**
  * @defgroup locale-api-add Language addition API.
  * @{
+ * Add a language.
+ *
+ * The language addition API is used to create languages and store them.
  */
 
 /**
@@ -498,8 +505,12 @@ function locale_add_language($langcode, 
  */
 
 /**
- * @defgroup locale-api-import Translation import API.
+ * @defgroup locale-api-import-export Translation import/export API.
  * @{
+ * Functions to import and export translations.
+ *
+ * These functions provide the ability to import translations from
+ * external files and to export translations and translation templates.
  */
 
 /**
@@ -1274,7 +1285,7 @@ function _locale_import_parse_quoted($st
   }
 }
 /**
- * @} End of "locale-api-import"
+ * @} End of "locale-api-import-export"
  */
 
 /**
@@ -1347,7 +1358,7 @@ function _locale_parse_js_file($filepath
 }
 
 /**
- * @defgroup locale-api-export Translation (template) export API.
+ * @addtogroup locale-api-import-export
  * @{
  */
 
@@ -1584,12 +1595,16 @@ function _locale_export_remove_plural($e
   return preg_replace('/(@count)\[[0-9]\]/', '\\1', $entry);
 }
 /**
- * @} End of "locale-api-export"
+ * @} End of "locale-api-import-export"
  */
 
 /**
- * @defgroup locale-api-seek String search functions.
+ * @defgroup locale-api-seek Translation search API.
  * @{
+ * Functions to search in translation files.
+ *
+ * These functions provide the functionality to search for specific
+ * translations.
  */
 
 /**
@@ -1894,6 +1909,7 @@ function _locale_translate_language_list
 /**
  * @defgroup locale-api-predefined List of predefined languages
  * @{
+ * API to provide a list of predefined languages.
  */
 
 /**
@@ -1928,6 +1944,10 @@ function _locale_prepare_predefined_list
 /**
  * @defgroup locale-autoimport Automatic interface translation import
  * @{
+ * Functions to create batches for importing translations.
+ *
+ * These functions can be used to import translations for installed
+ * modules.
  */
 
 /**
Index: includes/lock.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/lock.inc,v
retrieving revision 1.5
diff -u -p -r1.5 lock.inc
--- includes/lock.inc	16 Jul 2010 11:19:38 -0000	1.5
+++ includes/lock.inc	31 Dec 2010 22:46:40 -0000
@@ -7,8 +7,10 @@
  */
 
 /**
- * @defgroup lock Functions to coordinate long-running operations across requests.
+ * @defgroup lock Locking mechanisms
  * @{
+ * Functions to coordinate long-running operations across requests.
+ *
  * In most environments, multiple Drupal page requests (a.k.a. threads or
  * processes) will execute in parallel. This leads to potential conflicts or
  * race conditions when two requests execute the same code at the same time. A
Index: includes/update.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/update.inc,v
retrieving revision 1.85
diff -u -p -r1.85 update.inc
--- includes/update.inc	29 Dec 2010 03:46:39 -0000	1.85
+++ includes/update.inc	31 Dec 2010 22:46:41 -0000
@@ -209,7 +209,7 @@ function update_prepare_d7_bootstrap() {
     db_create_table('registry_file', $schema['registry_file']);
   }
 
-  // Older versions of Drupal 6 do not include the semaphore table, which is 
+  // Older versions of Drupal 6 do not include the semaphore table, which is
   // required to bootstrap, so we add it now so that we can bootstrap and
   // provide a reasonable error message.
   if (!db_table_exists('semaphore')) {
Index: modules/block/block.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/block/block.install,v
retrieving revision 1.47
diff -u -p -r1.47 block.install
--- modules/block/block.install	20 Oct 2010 01:15:58 -0000	1.47
+++ modules/block/block.install	31 Dec 2010 22:46:43 -0000
@@ -206,7 +206,7 @@ function block_update_dependencies() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Block updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -462,6 +462,6 @@ function block_update_7007() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */
Index: modules/comment/comment.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/comment/comment.install,v
retrieving revision 1.75
diff -u -p -r1.75 comment.install
--- modules/comment/comment.install	18 Dec 2010 01:50:15 -0000	1.75
+++ modules/comment/comment.install	31 Dec 2010 22:46:43 -0000
@@ -99,7 +99,7 @@ function comment_update_dependencies() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Comment updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-node
  * @{
  */
 
@@ -338,7 +338,7 @@ function comment_update_7006(&$sandbox) 
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-node"
  * The next series of updates should start at 8000.
  */
 
Index: modules/contact/contact.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/contact/contact.install,v
retrieving revision 1.25
diff -u -p -r1.25 contact.install
--- modules/contact/contact.install	8 Jun 2010 03:48:14 -0000	1.25
+++ modules/contact/contact.install	31 Dec 2010 22:46:43 -0000
@@ -90,8 +90,9 @@ function contact_uninstall() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Contact updates from 6.x to 7.x
+ * @defgroup updates-6.x-to-7.x-misc Updates from 6.x to 7.x: miscellaneous
  * @{
+ * Miscellaneous update functions from 6.x to 7.x.
  */
 
 /**
Index: modules/dblog/dblog.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/dblog/dblog.install,v
retrieving revision 1.23
diff -u -p -r1.23 dblog.install
--- modules/dblog/dblog.install	5 Sep 2010 19:56:03 -0000	1.23
+++ modules/dblog/dblog.install	31 Dec 2010 22:46:43 -0000
@@ -93,7 +93,7 @@ function dblog_schema() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x database logging updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -132,6 +132,6 @@ function dblog_update_7001() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */
Index: modules/field/field.crud.inc
===================================================================
RCS file: /cvs/drupal/drupal/modules/field/field.crud.inc,v
retrieving revision 1.73
diff -u -p -r1.73 field.crud.inc
--- modules/field/field.crud.inc	15 Dec 2010 04:13:48 -0000	1.73
+++ modules/field/field.crud.inc	31 Dec 2010 22:46:44 -0000
@@ -7,201 +7,6 @@
  */
 
 /**
- * @defgroup field_structs Field API data structures
- * @{
- * Represent Field API fields and instances.
- *
- * The Field API defines two primary data structures, Field and
- * Instance, and the concept of a Bundle. A Field defines a
- * particular type of data that can be attached to entities. A Field
- * Instance is a Field attached to a single Bundle. A Bundle is a set
- * of fields that are treated as a group by the Field Attach API and
- * is related to a single fieldable entity type.
- *
- * For example, suppose a site administrator wants Article nodes to
- * have a subtitle and photo. Using the Field API or Field UI module,
- * the administrator creates a field named 'subtitle' of type 'text'
- * and a field named 'photo' of type 'image'. The administrator
- * (again, via a UI) creates two Field Instances, one attaching the
- * field 'subtitle' to the 'node' bundle 'article' and one attaching
- * the field 'photo' to the 'node' bundle 'article'. When the node
- * system uses the Field Attach API to load all fields for an Article
- * node, it passes the node's entity type (which is 'node') and
- * content type (which is 'article') as the node's bundle.
- * field_attach_load() then loads the 'subtitle' and 'photo' fields
- * because they are both attached to the 'node' bundle 'article'.
- *
- * Field definitions are represented as an array of key/value pairs.
- *
- * @param array $field:
- * - id (integer, read-only)
- *     The primary identifier of the field. It is assigned automatically
- *     by field_create_field().
- * - field_name (string)
- *     The name of the field. Each field name is unique within Field API.
- *     When a field is attached to an entity, the field's data is stored
- *     in $entity->$field_name. Maximum length is 32 characters.
- * - type (string)
- *     The type of the field, such as 'text' or 'image'. Field types
- *     are defined by modules that implement hook_field_info().
- * - entity_types (array)
- *     The array of entity types that can hold instances of this field. If
- *     empty or not specified, the field can have instances in any entity type.
- * - cardinality (integer)
- *     The number of values the field can hold. Legal values are any
- *     positive integer or FIELD_CARDINALITY_UNLIMITED.
- * - translatable (integer)
- *     Whether the field is translatable.
- * - locked (integer)
- *     Whether or not the field is available for editing. If TRUE, users can't
- *     change field settings or create new instances of the field in the UI.
- *     Defaults to FALSE.
- * - module (string, read-only)
- *     The name of the module that implements the field type.
- * - active (integer, read-only)
- *     TRUE if the module that implements the field type is currently
- *     enabled, FALSE otherwise.
- * - deleted (integer, read-only)
- *     TRUE if this field has been deleted, FALSE otherwise. Deleted
- *     fields are ignored by the Field Attach API. This property exists
- *     because fields can be marked for deletion but only actually
- *     destroyed by a separate garbage-collection process.
- * - columns (array, read-only).
- *     An array of the Field API columns used to store each value of
- *     this field. The column list may depend on field settings; it is
- *     not constant per field type. Field API column specifications are
- *     exactly like Schema API column specifications but, depending on
- *     the field storage module in use, the name of the column may not
- *     represent an actual column in an SQL database.
- * - indexes (array).
- *     An array of indexes on data columns, using the same definition format
- *     as Schema API index specifications. Only columns that appear in the
- *     'columns' setting are allowed. Note that field types can specify
- *     default indexes, which can be modified or added to when
- *     creating a field.
- * - foreign keys: (optional) An associative array of relations, using the same
- *   structure as the 'foreign keys' definition of hook_schema(). Note, however,
- *   that the field data is not necessarily stored in SQL. Also, the possible
- *   usage is limited, as you cannot specify another field as related, only
- *   existing SQL tables, such as filter formats.
- * - settings (array)
- *     A sub-array of key/value pairs of field-type-specific settings. Each
- *     field type module defines and documents its own field settings.
- * - storage (array)
- *     A sub-array of key/value pairs identifying the storage backend to use for
- *     the for the field.
- *     - type (string)
- *         The storage backend used by the field. Storage backends are defined
- *         by modules that implement hook_field_storage_info().
- *     - module (string, read-only)
- *         The name of the module that implements the storage backend.
- *     - active (integer, read-only)
- *         TRUE if the module that implements the storage backend is currently
- *         enabled, FALSE otherwise.
- *     - settings (array)
- *         A sub-array of key/value pairs of settings. Each storage backend
- *         defines and documents its own settings.
- *
- * Field instance definitions are represented as an array of key/value pairs.
- *
- * @param array $instance:
- * - id (integer, read-only)
- *     The primary identifier of this field instance. It is assigned
- *     automatically by field_create_instance().
- * - field_id (integer, read-only)
- *     The foreign key of the field attached to the bundle by this instance.
- *     It is populated automatically by field_create_instance().
- * - field_name (string)
- *     The name of the field attached to the bundle by this instance.
- * - entity_type (string)
- *     The name of the entity type the instance is attached to.
- * - bundle (string)
- *     The name of the bundle that the field is attached to.
- * - label (string)
- *     A human-readable label for the field when used with this
- *     bundle. For example, the label will be the title of Form API
- *     elements for this instance.
- * - description (string)
- *     A human-readable description for the field when used with this
- *     bundle. For example, the description will be the help text of
- *     Form API elements for this instance.
- * - required (integer)
- *     TRUE if a value for this field is required when used with this
- *     bundle, FALSE otherwise. Currently, required-ness is only enforced
- *     during Form API operations, not by field_attach_load(),
- *     field_attach_insert(), or field_attach_update().
- * - default_value_function (string)
- *     The name of the function, if any, that will provide a default value.
- * - default_value (array)
- *     If default_value_function is not set, then fixed values can be provided.
- * - deleted (integer, read-only)
- *     TRUE if this instance has been deleted, FALSE otherwise.
- *     Deleted instances are ignored by the Field Attach API.
- *     This property exists because instances can be marked for deletion but
- *     only actually destroyed by a separate garbage-collection process.
- * - settings (array)
- *     A sub-array of key/value pairs of field-type-specific instance
- *     settings. Each field type module defines and documents its own
- *     instance settings.
- * - widget (array)
- *     A sub-array of key/value pairs identifying the Form API input widget
- *     for the field when used by this bundle.
- *     - type (string)
- *         The type of the widget, such as text_textfield. Widget types
- *         are defined by modules that implement hook_field_widget_info().
- *     - settings (array)
- *         A sub-array of key/value pairs of widget-type-specific settings.
- *         Each field widget type module defines and documents its own
- *         widget settings.
- *     - weight (float)
- *         The weight of the widget relative to the other elements in entity
- *         edit forms.
- *     - module (string, read-only)
- *         The name of the module that implements the widget type.
- * - display (array)
- *     A sub-array of key/value pairs identifying the way field values should
- *     be displayed in each of the entity type's view modes, plus the 'default'
- *     mode. For each view mode, Field UI lets site administrators define
- *     whether they want to use a dedicated set of display options or the
- *     'default' options to reduce the number of displays to maintain as they
- *     add new fields. For nodes, on a fresh install, only the 'teaser' view
- *     mode is configured to use custom display options, all other view modes
- *     defined use the 'default' options by default. When programmatically
- *     adding field instances on nodes, it is therefore recommended to at least
- *     specify display options for 'default' and 'teaser'.
- *     - default (array)
- *         A sub-array of key/value pairs describing the display options to be
- *         used when the field is being displayed in view modes that are not
- *         configured to use dedicated display options.
- *         - label (string)
- *             Position of the label. 'inline', 'above' and 'hidden' are the
- *             values recognized by the default 'field' theme implementation.
- *         - type (string)
- *             The type of the display formatter, or 'hidden' for no display.
- *         - settings (array)
- *             A sub-array of key/value pairs of display options specific to
- *             the formatter.
- *        - weight (float)
- *            The weight of the field relative to the other entity components
- *            displayed in this view mode.
- *         - module (string, read-only)
- *             The name of the module which implements the display formatter.
- *     - some_mode
- *         A sub-array of key/value pairs describing the display options to be
- *         used when the field is being displayed in the 'some_mode' view mode.
- *         Those options will only be actually applied at run time if the view
- *         mode is not configured to use default settings for this bundle.
- *         - ...
- *     - other_mode
- *        - ...
- *
- * Bundles are represented by two strings, an entity type and a bundle name.
- */
-/**
- * @} End of "defgroup field_structs".
- */
-
-/**
  * @defgroup field_crud Field CRUD API
  * @{
  * Create, update, and delete Field API fields, bundles, and instances.
@@ -210,7 +15,7 @@
  * data structures. UI modules will use it to create a user interface.
  *
  * The Field CRUD API uses
- * @link field_structs Field API data structures @endlink.
+ * @link field Field API data structures @endlink.
  */
 
 /**
@@ -243,7 +48,7 @@
  * @throw
  *   FieldException
  *
- * See: @link field_structs Field API data structures @endlink.
+ * See: @link field Field API data structures @endlink.
  */
 function field_create_field($field) {
   // Field name is required.
@@ -642,7 +447,7 @@ function field_delete_field($field_name)
  * @throw
  *   FieldException
  *
- * See: @link field_structs Field API data structures @endlink.
+ * See: @link field Field API data structures @endlink.
  */
 function field_create_instance($instance) {
   $field = field_read_field($instance['field_name']);
Index: modules/field/field.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/field/field.install,v
retrieving revision 1.26
diff -u -p -r1.26 field.install
--- modules/field/field.install	21 Dec 2010 21:01:49 -0000	1.26
+++ modules/field/field.install	31 Dec 2010 22:46:45 -0000
@@ -379,7 +379,7 @@ function _update_7000_field_create_insta
 }
 
 /**
- * @defgroup field-updates-6.x-to-7.x Field updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-misc
  * @{
  */
 
@@ -427,5 +427,5 @@ function field_update_7001() {
 }
 
 /**
- * @} End of "defgroup field-updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-misc"
  */
Index: modules/field/field.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/field/field.module,v
retrieving revision 1.93
diff -u -p -r1.93 field.module
--- modules/field/field.module	15 Dec 2010 02:55:21 -0000	1.93
+++ modules/field/field.module	31 Dec 2010 22:46:48 -0000
@@ -38,7 +38,191 @@ require_once DRUPAL_ROOT . '/modules/fie
  * fields via a web browser as well as a wide and flexible variety of
  * data type, form element, and display format capabilities.
  *
- * - @link field_structs Data structures: Field, Instance, Bundle @endlink.
+ * The Field API defines two primary data structures, Field and
+ * Instance, and the concept of a Bundle. A Field defines a
+ * particular type of data that can be attached to entities. A Field
+ * Instance is a Field attached to a single Bundle. A Bundle is a set
+ * of fields that are treated as a group by the Field Attach API and
+ * is related to a single fieldable entity type.
+ *
+ * For example, suppose a site administrator wants Article nodes to
+ * have a subtitle and photo. Using the Field API or Field UI module,
+ * the administrator creates a field named 'subtitle' of type 'text'
+ * and a field named 'photo' of type 'image'. The administrator
+ * (again, via a UI) creates two Field Instances, one attaching the
+ * field 'subtitle' to the 'node' bundle 'article' and one attaching
+ * the field 'photo' to the 'node' bundle 'article'. When the node
+ * system uses the Field Attach API to load all fields for an Article
+ * node, it passes the node's entity type (which is 'node') and
+ * content type (which is 'article') as the node's bundle.
+ * field_attach_load() then loads the 'subtitle' and 'photo' fields
+ * because they are both attached to the 'node' bundle 'article'.
+ *
+ * Field definitions are represented as an array of key/value pairs.
+ *
+ * array $field:
+ * - id (integer, read-only)
+ *     The primary identifier of the field. It is assigned automatically
+ *     by field_create_field().
+ * - field_name (string)
+ *     The name of the field. Each field name is unique within Field API.
+ *     When a field is attached to an entity, the field's data is stored
+ *     in $entity->$field_name. Maximum length is 32 characters.
+ * - type (string)
+ *     The type of the field, such as 'text' or 'image'. Field types
+ *     are defined by modules that implement hook_field_info().
+ * - entity_types (array)
+ *     The array of entity types that can hold instances of this field. If
+ *     empty or not specified, the field can have instances in any entity type.
+ * - cardinality (integer)
+ *     The number of values the field can hold. Legal values are any
+ *     positive integer or FIELD_CARDINALITY_UNLIMITED.
+ * - translatable (integer)
+ *     Whether the field is translatable.
+ * - locked (integer)
+ *     Whether or not the field is available for editing. If TRUE, users can't
+ *     change field settings or create new instances of the field in the UI.
+ *     Defaults to FALSE.
+ * - module (string, read-only)
+ *     The name of the module that implements the field type.
+ * - active (integer, read-only)
+ *     TRUE if the module that implements the field type is currently
+ *     enabled, FALSE otherwise.
+ * - deleted (integer, read-only)
+ *     TRUE if this field has been deleted, FALSE otherwise. Deleted
+ *     fields are ignored by the Field Attach API. This property exists
+ *     because fields can be marked for deletion but only actually
+ *     destroyed by a separate garbage-collection process.
+ * - columns (array, read-only).
+ *     An array of the Field API columns used to store each value of
+ *     this field. The column list may depend on field settings; it is
+ *     not constant per field type. Field API column specifications are
+ *     exactly like Schema API column specifications but, depending on
+ *     the field storage module in use, the name of the column may not
+ *     represent an actual column in an SQL database.
+ * - indexes (array).
+ *     An array of indexes on data columns, using the same definition format
+ *     as Schema API index specifications. Only columns that appear in the
+ *     'columns' setting are allowed. Note that field types can specify
+ *     default indexes, which can be modified or added to when
+ *     creating a field.
+ * - foreign keys: (optional) An associative array of relations, using the same
+ *   structure as the 'foreign keys' definition of hook_schema(). Note, however,
+ *   that the field data is not necessarily stored in SQL. Also, the possible
+ *   usage is limited, as you cannot specify another field as related, only
+ *   existing SQL tables, such as filter formats.
+ * - settings (array)
+ *     A sub-array of key/value pairs of field-type-specific settings. Each
+ *     field type module defines and documents its own field settings.
+ * - storage (array)
+ *     A sub-array of key/value pairs identifying the storage backend to use for
+ *     the for the field.
+ *     - type (string)
+ *         The storage backend used by the field. Storage backends are defined
+ *         by modules that implement hook_field_storage_info().
+ *     - module (string, read-only)
+ *         The name of the module that implements the storage backend.
+ *     - active (integer, read-only)
+ *         TRUE if the module that implements the storage backend is currently
+ *         enabled, FALSE otherwise.
+ *     - settings (array)
+ *         A sub-array of key/value pairs of settings. Each storage backend
+ *         defines and documents its own settings.
+ *
+ * Field instance definitions are represented as an array of key/value pairs.
+ *
+ * array $instance:
+ * - id (integer, read-only)
+ *     The primary identifier of this field instance. It is assigned
+ *     automatically by field_create_instance().
+ * - field_id (integer, read-only)
+ *     The foreign key of the field attached to the bundle by this instance.
+ *     It is populated automatically by field_create_instance().
+ * - field_name (string)
+ *     The name of the field attached to the bundle by this instance.
+ * - entity_type (string)
+ *     The name of the entity type the instance is attached to.
+ * - bundle (string)
+ *     The name of the bundle that the field is attached to.
+ * - label (string)
+ *     A human-readable label for the field when used with this
+ *     bundle. For example, the label will be the title of Form API
+ *     elements for this instance.
+ * - description (string)
+ *     A human-readable description for the field when used with this
+ *     bundle. For example, the description will be the help text of
+ *     Form API elements for this instance.
+ * - required (integer)
+ *     TRUE if a value for this field is required when used with this
+ *     bundle, FALSE otherwise. Currently, required-ness is only enforced
+ *     during Form API operations, not by field_attach_load(),
+ *     field_attach_insert(), or field_attach_update().
+ * - default_value_function (string)
+ *     The name of the function, if any, that will provide a default value.
+ * - default_value (array)
+ *     If default_value_function is not set, then fixed values can be provided.
+ * - deleted (integer, read-only)
+ *     TRUE if this instance has been deleted, FALSE otherwise.
+ *     Deleted instances are ignored by the Field Attach API.
+ *     This property exists because instances can be marked for deletion but
+ *     only actually destroyed by a separate garbage-collection process.
+ * - settings (array)
+ *     A sub-array of key/value pairs of field-type-specific instance
+ *     settings. Each field type module defines and documents its own
+ *     instance settings.
+ * - widget (array)
+ *     A sub-array of key/value pairs identifying the Form API input widget
+ *     for the field when used by this bundle.
+ *     - type (string)
+ *         The type of the widget, such as text_textfield. Widget types
+ *         are defined by modules that implement hook_field_widget_info().
+ *     - settings (array)
+ *         A sub-array of key/value pairs of widget-type-specific settings.
+ *         Each field widget type module defines and documents its own
+ *         widget settings.
+ *     - weight (float)
+ *         The weight of the widget relative to the other elements in entity
+ *         edit forms.
+ *     - module (string, read-only)
+ *         The name of the module that implements the widget type.
+ * - display (array)
+ *     A sub-array of key/value pairs identifying the way field values should
+ *     be displayed in each of the entity type's view modes, plus the 'default'
+ *     mode. For each view mode, Field UI lets site administrators define
+ *     whether they want to use a dedicated set of display options or the
+ *     'default' options to reduce the number of displays to maintain as they
+ *     add new fields. For nodes, on a fresh install, only the 'teaser' view
+ *     mode is configured to use custom display options, all other view modes
+ *     defined use the 'default' options by default. When programmatically
+ *     adding field instances on nodes, it is therefore recommended to at least
+ *     specify display options for 'default' and 'teaser'.
+ *     - default (array)
+ *         A sub-array of key/value pairs describing the display options to be
+ *         used when the field is being displayed in view modes that are not
+ *         configured to use dedicated display options.
+ *         - label (string)
+ *             Position of the label. 'inline', 'above' and 'hidden' are the
+ *             values recognized by the default 'field' theme implementation.
+ *         - type (string)
+ *             The type of the display formatter, or 'hidden' for no display.
+ *         - settings (array)
+ *             A sub-array of key/value pairs of display options specific to
+ *             the formatter.
+ *        - weight (float)
+ *            The weight of the field relative to the other entity components
+ *            displayed in this view mode.
+ *         - module (string, read-only)
+ *             The name of the module which implements the display formatter.
+ *     - some_mode
+ *         A sub-array of key/value pairs describing the display options to be
+ *         used when the field is being displayed in the 'some_mode' view mode.
+ *         Those options will only be actually applied at run time if the view
+ *         mode is not configured to use default settings for this bundle.
+ *         - ...
+ *     - other_mode
+ *        - ...
+ *
+ * Bundles are represented by two strings, an entity type and a bundle name.
  *
  * - @link field_types Field Types API @endlink. Defines field types,
  *   widget types, and display formatters. Field modules use this API
Index: modules/field/modules/field_sql_storage/field_sql_storage.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/field/modules/field_sql_storage/field_sql_storage.install,v
retrieving revision 1.12
diff -u -p -r1.12 field_sql_storage.install
--- modules/field/modules/field_sql_storage/field_sql_storage.install	21 Dec 2010 04:11:12 -0000	1.12
+++ modules/field/modules/field_sql_storage/field_sql_storage.install	31 Dec 2010 22:46:48 -0000
@@ -83,7 +83,7 @@ function _update_7000_field_sql_storage_
 }
 
 /**
- * @defgroup field-sql-storage-updates-6.x-to-7.x Field SQL storage updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-misc
  * @{
  */
 
@@ -210,5 +210,5 @@ function field_sql_storage_update_7002()
 }
 
 /**
- * @} End of "defgroup field-updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-misc"
  */
Index: modules/filter/filter.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/filter/filter.install,v
retrieving revision 1.50
diff -u -p -r1.50 filter.install
--- modules/filter/filter.install	30 Dec 2010 03:44:38 -0000	1.50
+++ modules/filter/filter.install	31 Dec 2010 22:46:48 -0000
@@ -162,7 +162,7 @@ function filter_update_dependencies() {
   return $dependencies;
 }
 /**
- * @defgroup updates-6.x-to-7.x Filter updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -490,6 +490,6 @@ function filter_update_7010() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */
Index: modules/locale/locale.admin.inc
===================================================================
RCS file: /cvs/drupal/drupal/modules/locale/locale.admin.inc,v
retrieving revision 1.21
diff -u -p -r1.21 locale.admin.inc
--- modules/locale/locale.admin.inc	21 Nov 2010 09:53:05 -0000	1.21
+++ modules/locale/locale.admin.inc	31 Dec 2010 22:46:48 -0000
@@ -7,8 +7,12 @@
  */
 
 /**
- * @defgroup locale-language-overview Language overview functionality
+ * @defgroup locale-language-administration Language administration interface
  * @{
+ * Administration interface for languages.
+ *
+ * These functions provide the user interface to show, add, edit and
+ * delete languages as well as providing options for language negotiation.
  */
 
 /**
@@ -161,14 +165,6 @@ function locale_languages_overview_form_
   $form_state['redirect'] = 'admin/config/regional/language';
   return;
 }
-/**
- * @} End of "locale-language-overview"
- */
-
-/**
- * @defgroup locale-language-add-edit Language addition and editing functionality
- * @{
- */
 
 /**
  * User interface for the language addition screen.
@@ -421,14 +417,6 @@ function locale_languages_edit_form_subm
   $form_state['redirect'] = 'admin/config/regional/language';
   return;
 }
-/**
- * @} End of "locale-language-add-edit"
- */
-
-/**
- * @defgroup locale-language-delete Language deletion functionality
- * @{
- */
 
 /**
  * User interface for the language deletion confirmation screen.
@@ -492,14 +480,6 @@ function locale_languages_delete_form_su
   $form_state['redirect'] = 'admin/config/regional/language';
   return;
 }
-/**
- * @} End of "locale-language-add-edit"
- */
-
-/**
- * @defgroup locale-languages-negotiation Language negotiation options
- * @{
- */
 
 /**
  * Setting for language negotiation options
@@ -759,12 +739,16 @@ function locale_language_providers_sessi
 }
 
 /**
- * @} End of "locale-languages-negotiation"
+ * @} End of "locale-language-administration"
  */
 
 /**
- * @defgroup locale-translate-overview Translation overview screen.
+ * @defgroup locale-translate-administration-screens Translation administration screens.
  * @{
+ * Screens for translation administration.
+ *
+ * These functions provide various screens as administration interface
+ * to import, export and view translations.
  */
 
 /**
@@ -803,14 +787,6 @@ function locale_translate_overview_scree
 
   return theme('table', array('header' => $headers, 'rows' => $rows));
 }
-/**
- * @} End of "locale-translate-overview"
- */
-
-/**
- * @defgroup locale-translate-seek Translation search screen.
- * @{
- */
 
 /**
  * String search screen.
@@ -948,15 +924,6 @@ function locale_translation_filter_form_
 }
 
 /**
- * @} End of "locale-translate-seek"
- */
-
-/**
- * @defgroup locale-translate-import Translation import screen.
- * @{
- */
-
-/**
  * User interface for the translation import screen.
  */
 function locale_translate_import_form($form) {
@@ -1045,14 +1012,6 @@ function locale_translate_import_form_su
   $form_state['redirect'] = 'admin/config/regional/translate';
   return;
 }
-/**
- * @} End of "locale-translate-import"
- */
-
-/**
- * @defgroup locale-translate-export Translation export screen.
- * @{
- */
 
 /**
  * User interface for the translation export screen.
@@ -1132,12 +1091,16 @@ function locale_translate_export_po_form
   _locale_export_po($language, _locale_export_po_generate($language, _locale_export_get_strings($language, $form_state['values']['group'])));
 }
 /**
- * @} End of "locale-translate-export"
+ * @} End of "locale-translate-administration-screens"
  */
 
 /**
- * @defgroup locale-translate-edit Translation text editing
+ * @defgroup locale-translate-edit-delete Translation editing/deletion interface
  * @{
+ * Edit and delete translation strings.
+ *
+ * These functions provide the user interface to edit and delete
+ * translation strings.
  */
 
 /**
@@ -1272,14 +1235,6 @@ function locale_translate_edit_form_subm
   $form_state['redirect'] = 'admin/config/regional/translate/translate';
   return;
 }
-/**
- * @} End of "locale-translate-edit"
- */
-
-/**
- * @defgroup locale-translate-delete Translation delete interface.
- * @{
- */
 
 /**
  * String deletion confirmation page.
@@ -1318,7 +1273,7 @@ function locale_translate_delete_form_su
   $form_state['redirect'] = 'admin/config/regional/translate/translate';
 }
 /**
- * @} End of "locale-translate-delete"
+ * @} End of "locale-translate-edit-delete"
  */
 
 /**
Index: modules/locale/locale.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/locale/locale.install,v
retrieving revision 1.71
diff -u -p -r1.71 locale.install
--- modules/locale/locale.install	9 Nov 2010 17:46:34 -0000	1.71
+++ modules/locale/locale.install	31 Dec 2010 22:46:49 -0000
@@ -28,7 +28,7 @@ function locale_install() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Locale updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -127,7 +127,7 @@ function locale_update_7002() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  */
 
 /**
Index: modules/node/node.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/node/node.install,v
retrieving revision 1.61
diff -u -p -r1.61 node.install
--- modules/node/node.install	23 Nov 2010 06:03:38 -0000	1.61
+++ modules/node/node.install	31 Dec 2010 22:46:49 -0000
@@ -446,8 +446,9 @@ function _update_7000_node_get_types() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x System updates from 6.x to 7.x
+ * @defgroup updates-6.x-to-7.x-node Updates from 6.x to 7.x: node
  * @{
+ * Node update functions from 6.x to 7.x.
  */
 
 /**
@@ -804,6 +805,6 @@ function node_update_7010() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "defgroup updates-6.x-to-7.x-node"
  * The next series of updates should start at 8000.
  */
Index: modules/node/node.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/node/node.module,v
retrieving revision 1.1334
diff -u -p -r1.1334 node.module
--- modules/node/node.module	30 Dec 2010 03:47:36 -0000	1.1334
+++ modules/node/node.module	31 Dec 2010 22:46:55 -0000
@@ -3493,6 +3493,7 @@ function _node_access_rebuild_batch_fini
 /**
  * @defgroup node_content Hook implementations for user-created content types.
  * @{
+ * Functions that implement hooks for user-created content types.
  */
 
 /**
Index: modules/openid/openid.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/openid/openid.install,v
retrieving revision 1.12
diff -u -p -r1.12 openid.install
--- modules/openid/openid.install	22 Aug 2010 22:00:16 -0000	1.12
+++ modules/openid/openid.install	31 Dec 2010 22:46:55 -0000
@@ -112,7 +112,7 @@ function openid_requirements($phase) {
 }
 
 /**
- * @defgroup updates-6.x-extra Extra openid updates for 6.x
+ * @addtogroup updates-6.x-to-7.x-misc
  * @{
  */
 
@@ -150,6 +150,6 @@ function openid_update_6000() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-extra"
+ * @} End of "addtogroup updates-6.x-to-7.x-misc"
  * The next series of updates should start at 7000.
  */
Index: modules/statistics/statistics.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/statistics/statistics.install,v
retrieving revision 1.28
diff -u -p -r1.28 statistics.install
--- modules/statistics/statistics.install	8 Dec 2010 06:43:07 -0000	1.28
+++ modules/statistics/statistics.install	31 Dec 2010 22:46:55 -0000
@@ -137,7 +137,7 @@ function statistics_schema() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x statistics updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-misc
  * @{
  */
 
@@ -155,6 +155,6 @@ function statistics_update_7000() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-misc"
  * The next series of updates should start at 8000.
  */
Index: modules/system/system.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/system/system.install,v
retrieving revision 1.531
diff -u -p -r1.531 system.install
--- modules/system/system.install	29 Dec 2010 03:46:39 -0000	1.531
+++ modules/system/system.install	31 Dec 2010 22:46:57 -0000
@@ -1718,8 +1718,9 @@ function system_update_dependencies() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x System updates from 6.x to 7.x
+ * @defgroup updates-6.x-to-7.x-system Updates from 6.x to 7.x: system
  * @{
+ * System update functions from 6.x to 7.x.
  */
 
 /**
@@ -2972,6 +2973,6 @@ function system_update_7069() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "defgroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */
Index: modules/taxonomy/taxonomy.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/taxonomy/taxonomy.module,v
retrieving revision 1.623
diff -u -p -r1.623 taxonomy.module
--- modules/taxonomy/taxonomy.module	15 Dec 2010 03:39:42 -0000	1.623
+++ modules/taxonomy/taxonomy.module	31 Dec 2010 22:46:58 -0000
@@ -1622,6 +1622,8 @@ function taxonomy_rdf_mapping() {
 
 /**
  * @defgroup taxonomy indexing Taxonomy functions maintaining {taxonomy_index}.
+ * @{
+ * Functions to maintain taxonomy indexing.
  *
  * Taxonomy uses default field storage to store canonical relationships
  * between terms and fieldable entities. However its most common use case
@@ -1634,7 +1636,6 @@ function taxonomy_rdf_mapping() {
  * field storage engines or alternative methods of denormalizing this data
  * you should set the variable 'taxonomy_maintain_index_table' to FALSE
  * to avoid unnecessary writes in SQL.
- * @{
  */
 
 /**
Index: modules/tracker/tracker.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/tracker/tracker.install,v
retrieving revision 1.5
diff -u -p -r1.5 tracker.install
--- modules/tracker/tracker.install	22 Aug 2010 13:55:53 -0000	1.5
+++ modules/tracker/tracker.install	31 Dec 2010 22:46:59 -0000
@@ -114,7 +114,7 @@ function tracker_schema() {
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Tracker updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-node
  * @{
  */
 
@@ -217,6 +217,6 @@ function tracker_update_7000() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-node"
  * The next series of updates should start at 8000.
  */
Index: modules/update/update.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/update/update.install,v
retrieving revision 1.20
diff -u -p -r1.20 update.install
--- modules/update/update.install	3 Oct 2010 22:44:48 -0000	1.20
+++ modules/update/update.install	31 Dec 2010 22:46:59 -0000
@@ -160,7 +160,7 @@ function _update_requirement_check($proj
 }
 
 /**
- * @defgroup updates-6.x-to-7.x Filter updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -187,6 +187,6 @@ function update_update_7001() {
 }
 
 /**
- * @} End of "defgroup updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */
Index: modules/update/update.manager.inc
===================================================================
RCS file: /cvs/drupal/drupal/modules/update/update.manager.inc,v
retrieving revision 1.30
diff -u -p -r1.30 update.manager.inc
--- modules/update/update.manager.inc	15 Dec 2010 03:52:05 -0000	1.30
+++ modules/update/update.manager.inc	31 Dec 2010 22:47:00 -0000
@@ -37,8 +37,11 @@
  */
 
 /**
- * @defgroup update_manager_update Update manager for updating existing code.
+ * @defgroup update_manager_update Update manager: update
  * @{
+ * Update manager for updating existing code.
+ *
+ * Provides a user interface to update existing code.
  */
 
 /**
@@ -436,8 +439,11 @@ function update_manager_update_ready_for
  */
 
 /**
- * @defgroup update_manager_install Update manager for installing new code.
+ * @defgroup update_manager_install Update manager: install
  * @{
+ * Update manager for installing new code.
+ *
+ * Provides a user interface to install new code.
  */
 
 /**
@@ -617,8 +623,12 @@ function update_manager_install_form_sub
  */
 
 /**
- * @defgroup update_manager_file Update manager file management functions.
+ * @defgroup update_manager_file Update manager: file management
  * @{
+ * Update manager file management functions.
+ *
+ * These functions are used by the update manager to copy, extract
+ * and verify archive files.
  */
 
 /**
Index: modules/update/update.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/update/update.module,v
retrieving revision 1.72
diff -u -p -r1.72 update.module
--- modules/update/update.module	15 Dec 2010 03:52:05 -0000	1.72
+++ modules/update/update.module	31 Dec 2010 22:47:01 -0000
@@ -721,6 +721,7 @@ function update_verify_update_archive($p
 /**
  * @defgroup update_status_cache Private update status cache system
  * @{
+ * Functions to manage the update status cache.
  *
  * We specifically do NOT use the core cache API for saving the fetched data
  * about available updates. It is vitally important that this cache is only
Index: modules/user/user.install
===================================================================
RCS file: /cvs/drupal/drupal/modules/user/user.install,v
retrieving revision 1.68
diff -u -p -r1.68 user.install
--- modules/user/user.install	20 Oct 2010 01:15:58 -0000	1.68
+++ modules/user/user.install	31 Dec 2010 22:47:01 -0000
@@ -393,7 +393,7 @@ function _update_7000_user_role_grant_pe
 }
 
 /**
- * @defgroup user-updates-6.x-to-7.x User updates from 6.x to 7.x
+ * @addtogroup updates-6.x-to-7.x-system
  * @{
  */
 
@@ -855,6 +855,6 @@ function user_update_7015() {
 }
 
 /**
- * @} End of "defgroup user-updates-6.x-to-7.x"
+ * @} End of "addtogroup updates-6.x-to-7.x-system"
  * The next series of updates should start at 8000.
  */