From b3beba965258f99ccbb1e8dea4858e27d6d9d22a Mon Sep 17 00:00:00 2001
From: marj <marj@e107.org>
Date: Wed, 28 Oct 2009 14:13:44 +0000
Subject: [PATCH] PHPdoc

---
 e107_handlers/e107_class.php | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/e107_handlers/e107_class.php b/e107_handlers/e107_class.php
index 38b4cfc90..8273609a1 100644
--- a/e107_handlers/e107_class.php
+++ b/e107_handlers/e107_class.php
@@ -9,9 +9,9 @@
  * e107 Main
  *
  * $Source: /cvs_backup/e107_0.8/e107_handlers/e107_class.php,v $
- * $Revision: 1.59 $
- * $Date: 2009-10-23 18:14:42 $
- * $Author: secretr $
+ * $Revision: 1.60 $
+ * $Date: 2009-10-28 14:13:44 $
+ * $Author: marj_nl_fr $
 */
 
 if (!defined('e107_INIT')) { exit; }
@@ -840,13 +840,13 @@ class e107
 	/**
 	 * Get core template. Use this method for templates, which are following the 
 	 * new template standards:
-	 * - template variables naming convetnions
+	 * - template variables naming conventions
 	 * - one array variable per template only
 	 * - theme override is made now by current_theme/templates/ folder
 	 * 
 	 * <br><br>Results are cached (depending on $id and $override so it's safe to use
 	 * this method e.g. in loop for retrieving a template string. If template (or template key) is not 
-	 * found, <b>null</b> is returned.<br><br>
+	 * found, <b>NULL</b> is returned.<br><br>
 	 * 
 	 * Example usage: <code>e107::getCoreTemplate('user', 'short_start');</code>
 	 * Will search for:
@@ -855,7 +855,7 @@ class e107
 	 * - $USER_TEMPLATE array which contains all user templates
 	 * - $USER_TEMPLATE['short_start'] (if key is null, $USER_TEMPLATE will be returned)
 	 * 
-	 * @param string $id
+	 * @param string $id - file prefix, e.g. user for user_template.php
 	 * @param string|null $key
 	 * @param boolean $override
 	 * 
@@ -874,13 +874,13 @@ class e107
 	/**
 	 * Get plugin template. Use this method for plugin templates, which are following the 
 	 * new template standards:
-	 * - template variables naming convetnions
+	 * - template variables naming conventions
 	 * - one array variable per template only
 	 * - theme override is made now by current_theme/templates/plugin_name/ folder
 	 * 
 	 * <br><br>Results are cached (depending on $id and $override so it's safe to use
 	 * this method e.g. in loop for retrieving a template string. If template (or template key) is not 
-	 * found, <b>null</b> is returned.<br><br>
+	 * found, <b>NULL</b> is returned.<br><br>
 	 * 
 	 * Example usage: <code>e107::getTemplate('user', 'short_start');</code>
 	 * Will search for:
@@ -890,7 +890,7 @@ class e107
 	 * - $USER_TEMPLATE['short_start'] (if key is null, $USER_TEMPLATE will be returned)
 	 * 
 	 * @param string $plug_name
-	 * @param string $id
+	 * @param string $id - file prefix, e.g. calendar for calendar_template.php
 	 * @param string|null $key
 	 * @param boolean $override
 	 *