Fix #15704: Wrong description of writing custom_functions

mantisbt · Apr 2, 2013 · 6443c62 · 6443c62
1 parent 03b5f34
commit 6443c62
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docbook/administration_guide/en/customizing_mantis.sgml b/docbook/administration_guide/en/customizing_mantis.sgml
@@ -867,15 +867,15 @@ $g_status_enum_workflow[CLOSED]       ='20:feedback,50:assigned';
 		<para>User versions of these functions (overrides) are named like
 			<emphasis>custom_function_override_descriptive_name</emphasis>,
 			and placed in a file called
-			<filename>custom_constants_inc.php</filename> that must be saved in
+			<filename>custom_functions_inc.php</filename> that must be saved in
 			MantisBT's root directory (This is the same place where the
 			<filename>config_inc.php</filename> file resides).
 			In normal processing, the system will look for override functions
 			and execute them instead of the provided default functions.
 		</para>
 		<para>The simplest way to create a custom function is to copy the
 			default one from the api to your override file
-			(<filename>custom_constants_inc.php</filename>), and rename it
+			(<filename>custom_functions_inc.php</filename>), and rename it
 			(i.e. replacing 'default' by 'override').
 			The specific functionality you need can then be coded into the
 			override function.