aidan Sun Feb 13 22:37:35 2005 EDT
Modified files:
/phpdoc/en/reference/mail/functions mail.xml
Log:
Fix minor spelling/punctuation mistakes.
http://cvs.php.net/diff.php/phpdoc/en/reference/mail/functions/mail.xml?r1=1.30&r2=1.31&ty=u
Index: phpdoc/en/reference/mail/functions/mail.xml
diff -u phpdoc/en/reference/mail/functions/mail.xml:1.30
phpdoc/en/reference/mail/functions/mail.xml:1.31
--- phpdoc/en/reference/mail/functions/mail.xml:1.30 Sun Feb 13 21:45:46 2005
+++ phpdoc/en/reference/mail/functions/mail.xml Sun Feb 13 22:37:34 2005
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.30 $ -->
+<!-- $Revision: 1.31 $ -->
<refentry id="function.mail">
<refnamediv>
<refname>mail</refname>
@@ -71,7 +71,7 @@
<para>
(Windows only) When PHP is talking to a SMTP server directly, if a full
stop is found on the start of a line, it is removed. To counter-act
this,
- replace these occurences with a double dot.
+ replace these occurrences with a double dot.
<programlisting role="php">
<![CDATA[
<?php
@@ -95,8 +95,8 @@
<note>
<para>
If messages are not received, try using a LF (\n) only.
- Some poor quality Unix mail transfer agents replace \n by \r\n
- automatically (which leads to doubling \r if \r\n is used).
+ Some poor quality Unix mail transfer agents replace LF by CRLF
+ automatically (which leads to doubling CR if CRLF is used).
This should be a last resort, as it does not comply with
<ulink url="&url.rfc;2822">RFC 2822</ulink>.
</para>
@@ -118,7 +118,7 @@
<para>
The user that the webserver runs as should be added as a trusted user
to the
sendmail configuration to prevent a 'X-Warning' header from being added
- to the message when you set the envelope sender (-f) using this method.
+ to the message when the envelope sender (-f) is set using this method.
For sendmail users, this file is
<filename>/etc/mail/trusted-users</filename>.
</para>
</listitem>
@@ -359,7 +359,7 @@
<note>
<para>
- The following RFC's may be useful:
+ The following RFCs may be useful:
<ulink url="&url.rfc;1896">RFC 1896</ulink>,
<ulink url="&url.rfc;2045">RFC 2045</ulink>,
<ulink url="&url.rfc;2046">RFC 2046</ulink>,