Remove contractions.

Approved by:	brueffer (mentor)
This commit is contained in:
Joel Dahl 2005-09-04 22:03:59 +00:00
parent 911480de43
commit 1f0ad5eded
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=25557

View file

@ -61,7 +61,7 @@
It has climbed to the fourth position and to an 8% market share
during the last two years thanks to superior quality of service.</para>
<para>In Argentina and Latin America in general people who don't
<para>In Argentina and Latin America in general people who do not
have computers at home go to so called <quote>Locutorios</quote>
(Internet Centers), where for a few pesos they can use a computer
connected to the Internet and usually read and write emails
@ -80,7 +80,7 @@
<para>The main challenge for Argentina.Com is to achieve a dialup
uptime of at least 99.95%, or less than 5 hours yearly
downtime. Due to the high rotation and volatility in this
business, things have to work correctly so the user doesn't switch
business, things have to work correctly so the user does not switch
-voluntarily or not- the dialup provider or the number he calls to
connect. The dialup business involves a support structure to deal
with the Telcos about telephony problems and quality of service,
@ -115,12 +115,12 @@
existence of spam (dictionary attacks, spams with high degree of
obfuscation and refinement, phishing, trojans, mail-bombs, etc.)
it becomes very difficult to achieve an excellent uptime while
repelling attacks. One must also be careful that the user doesn't
repelling attacks. One must also be careful that the user does not
lose mails because of false positives in the classification
strategy, that he doesn't become flooded with spam or spam
notifications, and dangerous mails don't make it through to his
strategy, that he does not become flooded with spam or spam
notifications, and dangerous mails do not make it through to his
mailbox. In addition, the technical infrastructure for spam
classification shouldn't introduce noticeable delays in the
classification should not introduce noticeable delays in the
delivery of mails. Finally, the mail system has to be protected
from spammers who might misuse it to send spam.</para>
@ -240,7 +240,7 @@
with a score below the one associated with the selected spam
tolerance goes to the user's Inbox. Emails between this level
and the cutoff level go to a user's folder named Spam, and those
above the cutoff level get discarded because it's a very obvious
above the cutoff level get discarded because it is a very obvious
spam. For the sake of simplicity, we transparently associated
the use of the Address Book with the antispam system, so that
every personal contact gets automatically whitelisted.</para>
@ -252,7 +252,7 @@
these mirrors that cost us between 1 and 2Mbps in traffic, we
were able to dramatically cut down Spamassassin latency.</para>
<para>At the 3rd level there's the delivery to the maildrops. As
<para>At the 3rd level there is the delivery to the maildrops. As
soon as we started building a new Cyrus-Imap back-end with MySQL
authentication, we needed to multiplex incoming mail to users in
both old and new maildrop formats. Finally, we managed to
@ -278,8 +278,8 @@
<para>As webmail software, we chose a commercial product named
Atmail, which is available with perl sources and utilizes
mod_perl. Under FreeBSD it's extremely easy to deal with perl
modules, you don't even need to use the CPAN shell, you just
mod_perl. Under FreeBSD it is extremely easy to deal with perl
modules, you do not even need to use the CPAN shell, you just
have to choose the right port and run "make install". After
several months of integration work, we integrated the
Client-only version of Atmail that talks IMAP with our