moving functions to separate file, adding configuration files

[squirrelmail.git] / help / en_US / addresses.hlp

diff --git a/help/en_US/addresses.hlp b/help/en_US/addresses.hlp
index 964e6c111ac14315162375bfa002f5baa5dd50cd..99d10cf52d219f760e9348bf3f89e32fa4066eca 100644 (file)
--- a/help/en_US/addresses.hlp
+++ b/help/en_US/addresses.hlp
@@ -43,7 +43,7 @@
    </title>
    <description>
       <p>
    </title>
    <description>
       <p>

-      This must be the persons' fully qualified email address.  Guessing here 
+      This must be the person's fully qualified email address.  Guessing here 

       just won't cut it.  There are three parts to an email address.  First is 
       the recipients identifier, such as "johnq". Next is the domain name 
       section, which could take the form "tayloru".  Last comes the top level 
       just won't cut it.  There are three parts to an email address.  First is 
       the recipients identifier, such as "johnq". Next is the domain name 
       section, which could take the form "tayloru".  Last comes the top level 


@@ -107,7 +107,7 @@
       stored and made available.  If configured to use the universities 
       LDAP server, SquirrelMail would then be able to list all campus email 
       address (along with the other address book fields if available).  
       stored and made available.  If configured to use the universities 
       LDAP server, SquirrelMail would then be able to list all campus email 
       address (along with the other address book fields if available).  

-      SquirrelMail's LDAP use is truly powerful in that it <I>combines</I> 
+      SquirrelMail's LDAP use is truly powerful in that it <i>combines</i> 

       your local address book and the LDAP address server information to 
       present all of the information as if it was a single address book.
       </p><p>
       your local address book and the LDAP address server information to 
       present all of the information as if it was a single address book.
       </p><p>