Index: modules/node/node.api.php
===================================================================
RCS file: /cvs/drupal/drupal/modules/node/node.api.php,v
retrieving revision 1.16
diff -u -r1.16 node.api.php
--- modules/node/node.api.php	3 May 2009 10:11:34 -0000	1.16
+++ modules/node/node.api.php	4 May 2009 13:29:43 -0000
@@ -397,9 +381,7 @@
  * @param $node
  *   The node the action is being performed on.
  * @param $teaser
- *   The $teaser parameter from node_view().
- * @return
- *   None.
+ *   The $teaser parameter from node_build().
  */
 function hook_node_view($node, $teaser) {
   $node->content['my_additional_field'] = array(
Index: includes/common.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/common.inc,v
retrieving revision 1.892
diff -u -r1.892 common.inc
--- includes/common.inc	4 May 2009 10:38:47 -0000	1.892
+++ includes/common.inc	4 May 2009 13:29:43 -0000
@@ -3306,28 +3306,31 @@
  * HTML generation is controlled by two properties containing theme functions,
  * #theme and #theme_wrapper.
  *
- * #theme is the theme function called first. If it is set and the element has any
- * children, they have to be rendered there. For elements that are not allowed
- * to have any children, e.g. buttons or textfields, it can be used to render
- * the element itself. If #theme is not present and the element has children,
- * they are rendered and concatenated into a string by drupal_render_children().
- *
- * The theme function in #theme_wrapper will be called after #theme has run. It
- * can be used to add further markup around the rendered children, e.g. fieldsets
- * add the required markup for a fieldset around their rendered child elements.
- * A wrapper theme function always has to include the element's #children property
- * in its output, as this contains the rendered children.
+ * #theme is the theme function called first. If it is set and the element has
+ * any children, they have to be rendered there. For elements that are not
+ * allowed to have any children, e.g. buttons or textfields, it can be used to
+ * render the element itself. If #theme is not present and the element has
+ * children, they are rendered and concatenated into a string by
+ * drupal_render_children().
+ *
+ * The theme function in #theme_wrapper will be called after #theme has run.
+ * It can be used to add further markup around the rendered children, e.g.
+ * fieldsets add the required markup for a fieldset around their rendered
+ * child elements.  A wrapper theme function always has to include the
+ * element's #children property in its output, as this contains the rendered
+ * children.
  *
  * For example, for the form element type, by default only the #theme_wrapper
- * property is set, which adds the form markup around the rendered child elements
- * of the form. This allows you to set the #theme property on a specific form to
- * a custom theme function, giving you complete control over the placement of the
- * form's children while not at all having to deal with the form markup itself.
+ * property is set, which adds the form markup around the rendered child
+ * elements of the form. This allows you to set the #theme property on a
+ * specific form to a custom theme function, giving you complete control over
+ * the placement of the form's children while not at all having to deal with
+ * the form markup itself.
  *
  * This function is usually called from within a another function, like
- * drupal_get_form() or node_view(). Elements are sorted internally using
- * uasort(). Since this is expensive, when passing already sorted elements to
- * drupal_render(), for example from a database query, set
+ * drupal_get_form() or a theme function. Elements are sorted internally
+ * using uasort(). Since this is expensive, when passing already sorted
+ * elements to drupal_render(), for example from a database query, set
  * $elements['#sorted'] = TRUE to avoid sorting them a second time.
  *
  * @param $elements