Update the description in the man page.

[email-validator.git] / doc / man1 / email-validator.1

diff --git a/doc/man1/email-validator.1 b/doc/man1/email-validator.1
index 95991872aca3da9da8fe1e1e6641a4bb81912525..232a5f422da13539aa4e1521d73514624b156f85 100644 (file)
--- a/doc/man1/email-validator.1
+++ b/doc/man1/email-validator.1
@@ -22,20 +22,22 @@ stdout), one per line.
 .SH DESCRIPTION
 
 .P
-We check the validity of an email address using three techniques:
+Validate an email address using three techniques:
 
 .IP \[bu] 2
-We ensure that the length of local and domain parts is within the
+Ensuring that the length of local and domain parts is within the
 RFC-specified limits.
 
 .IP \[bu]
-A regular expression is used to check for invalid characters and syntax.
+A syntax check using a regular expression, or the full RFC 5322
+grammar (see the \fB\-\-rfc5322\fR option).
 
 .IP \[bu]
-We confirm the existence of a MX record for the domain part of the
-address. This is not required; in fact many domains accept mail via
-an 'A' record for e.g. example.com which is used in lieu of an MX
-record. This behavior can be controlled via the \fR\-a\fR flag.
+Confirmation of the existence of an \fIMX\fR record for the domain
+part of the address. This is not required; in fact many domains accept
+mail via an \fIA\fR record for e.g. example.com which is used in lieu
+of an \fIMX\fR record. This behavior can be controlled via the
+\fR\-\-accept\-a\fR flag.
 
 .P
 These checks are performed in parallel using the number of available