Index: openacs-4/packages/contacts/contacts.info
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/contacts/contacts.info,v
diff -u -r1.93 -r1.94
--- openacs-4/packages/contacts/contacts.info	30 Jun 2007 06:59:59 -0000	1.93
+++ openacs-4/packages/contacts/contacts.info	17 Apr 2018 14:47:02 -0000	1.94
@@ -63,7 +63,7 @@
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="DeleteHistoryPermission"  default="no" description="Default 'no'. Valid options are: 'no', 'yours' or 'all'. If set to 'yours' then you can only delete history that was created by you (i.e. the acs_objects tables created_user is your user_id). If set to 'all' you can delete any history item. This does not actually delete the object, its just hidden because an entry is made in the contact_deleted_history table. NOTE: people with admin rights on the package instance are automatically given 'all' permission."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="DisableCSV"  default="0" description="Default '0'. If set to '1' people will not be able to download a csv of the contacts attributes displayed on this contact instances front page."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="DisplayEmployersP"  default="0" description="1 for yes, 0 for no. Display organization name behind username?"/>
-            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="EditDataAfterRel"  description="Default blank. A space seperated list of rel_types for which to redirect a contact to the edit form. If a relationship is altered and the rel_type is in this list the user will be redirected to the attribute edit page for that contact. This is useful for things such as the 'contact_rels_employment', when a user changes employers they often change office phone numbers or email address, and the user should be reminded to update this information. If you specify '*' any rel_type change will redirect."/>
+            <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="EditDataAfterRel"  description="Default blank. A space separated list of rel_types for which to redirect a contact to the edit form. If a relationship is altered and the rel_type is in this list the user will be redirected to the attribute edit page for that contact. This is useful for things such as the 'contact_rels_employment', when a user changes employers they often change office phone numbers or email address, and the user should be reminded to update this information. If you specify '*' any rel_type change will redirect."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="EmailAttachmentsAllowed"  default="1" description="1 for yes, 0 for now. Are email attachments allowed when sending messages?"/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="ForceSearchBeforeAdd"  default="0" description="1 for yes, 0 for no. Should we force users to search all contacts before they are allowed to add a person or organization? This is not an actual software force but the &quot;add person&quot; and &quot;add organization&quot; buttons will only be displayed after a search on &quot;all contacts.&quot;"/>
             <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="History"  default="/packages/contacts/templates/history" description="The template src for history page" section_name="Portal Templates"/>