Index: views.module
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/views.module,v
retrieving revision 1.341.4.45
diff -u -p -r1.341.4.45 views.module
--- views.module	17 Dec 2010 21:52:44 -0000	1.341.4.45
+++ views.module	22 Dec 2010 22:25:17 -0000
@@ -184,7 +184,7 @@ function _views_find_module_templates($c
             'template' => $file,
             'path' => dirname($files[$match]->filename),
             'variables' => $info['arguments'],
-            'original hook' => $hook,
+            'base hook' => $hook,
             'include files' => $info['include files'],
           );
         }
Index: help/api-default-views.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/api-default-views.html,v
retrieving revision 1.3.6.3
diff -u -p -r1.3.6.3 api-default-views.html
--- help/api-default-views.html	4 Aug 2010 05:54:08 -0000	1.3.6.3
+++ help/api-default-views.html	22 Dec 2010 22:25:17 -0000
@@ -51,7 +51,7 @@ To do this, you need to implement <em>ho
     'views_view__viewname__displayid' => array (
       'arguments' => array('view' => NULL),
       'template' => 'views-view--viewname--displayid',
-      'original hook' => 'views_view',
+      'base hook' => 'views_view',
       'path' => drupal_get_path('module', 'mymodule'),
     ),
   );
@@ -74,14 +74,14 @@ Be sure to use the right arguments line 
 </li>
 <li>The 'template' line should never include the extension, so drop the .tpl.php from it.</li>
 
-<li>You need to make sure that the Views preprocess functions get registered. The 'original hook' line in the definition does that, but it can only do it if it comes after the Views registration, which actually happens very late in theme building. 99% of the time, your module will come before Views. You have two choices to deal with this:
+<li>You need to make sure that the Views preprocess functions get registered. The 'base hook' line in the definition does that, but it can only do it if it comes after the Views registration, which actually happens very late in theme building. 99% of the time, your module will come before Views. You have two choices to deal with this:
 <ol>
   <li>Set your module's weight to 11 or higher in the database. Views' weight is 10. You can make this happen automatically when the module is first installed by creating a mymodule.install file and using this code:
   <pre>function mymodule_install() {
   db_query("UPDATE {system} SET weight = 11 WHERE name = 'mymodule'");
 }
 </pre>
-  If you use this method, the <em>original hook</em> should be set to the name of the original template being used. i.e, if this is a variate of views-view-list.tpl.php, this should be 'views_view_list'.
+  If you use this method, the <em>base hook</em> should be set to the name of the original template being used. i.e, if this is a variate of views-view-list.tpl.php, this should be 'views_view_list'.
   </li>
   <li>You can also just force it to list the preprocessors without actually having to detect them. This doesn't require modifying your module's weight, which is not always possible, you can insert this code into the array:
   <pre>      'preprocess functions' => array(
@@ -93,7 +93,7 @@ Be sure to use the right arguments line 
 
   The first one is the global 'template_preprocess' function which all templates utilize. It does some basic things such as setting up $zebra and a few other items. See <a href="http://api.drupal.org/api/function/template_preprocess/6">api.drupal.org</a> for specifics.
 
-  The second one is the plugin specific preprocess. Like 'original hook' it should conform to the name used by the original template. i.e, if the original template was <em>views-view-list.tpl.php</em> then that preprocess function would be named <em>template_preprocess_views_view_list</em>.
+  The second one is the plugin specific preprocess. Like 'base hook' it should conform to the name used by the original template. i.e, if the original template was <em>views-view-list.tpl.php</em> then that preprocess function would be named <em>template_preprocess_views_view_list</em>.
 
   The third one is your module's preprocess function, if it needs one. In general, you probably will not need one, and you should only attempt to use one if you are reasonably familiar with the concept of preprocess functions and Drupal's theme system in general. See Drupal's theme documentation for more information.
   </li>