Improved comment of parameter

intranet-timesheet2.info

@@ -33,7 +33,7 @@
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="LogHoursOnParentWithChildrenP"  default="1" description="Is it allowed to log hours on main projects, even though they have children? Set thçis parameter to 0 if you want to force employees to log their hours on the subprojects/tasks only."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="LogHoursOnSolitaryProjectsP"  default="1" description="Is it allowed to log hours on main projects without children? Some companies don't allow logging hours on these 'solitary' projects. Default is 1 to enable logging on solitary projects."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SyncHoursInterval"  default="61" description="Interval for the hours costs synchronizer to between checks if new im_hours items have been generated to be synchronized. This interval can be &quot;never&quot; (1000000) if timesheet hours are captured by the system itself. However, you should set this interval to something less for systems importing im_hours from an external source."/>
-            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SyncHoursP"  default="1" description="Should we bother to create im_cost cost items for every timesheet hour in general? If 1, then the parameter SyncHoursInterval will determine the interval for periodic syncronization and SyncHoursImmediatelyAfterEntryP will initiate synchronization directly after entering hours (may take about a second). The default value is '1', unless you don't use the profit &amp; loss functionality."/>
+            <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SyncHoursP"  default="1" description="Should we bother to create im_cost cost items for every timesheet hour in general? If 1, then the parameter SyncHoursInterval will determine the interval for periodic syncronization and SyncHoursImmediatelyAfterEntryP will initiate synchronization directly after entering hours (may take about a second). The default value is '1', unless you don't use the profit &amp; loss functionality. Using a value different form 0 or 1 means that this value should be used as the name of a custom function to sync."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SyncHoursImmediatelyAfterEntryP"  default="1" description="Should we create im_cost cost items for logged hours immediately after the user has entered them? The default is '1', which is valid for most installation. Set to '0' for very large installations with many people logging hours at the same time."/>
             <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="TimesheetAddHoursSortOrder"  default="order" description="Sort the timesheet tasks on the &quot;add hours&quot; page by &quot;order&quot; (gantt sort order), &quot;name&quot; (task name) or &quot;nr&quot; (task id). The default is the gantt sort order."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="TimesheetHoursPerAbsence"  default="8.0" description="Specifies the equivalent hours of a day of absences. 8.0 by default."/>