Package: debian-handbook
Version: 6.0+20120509
Severity: minor
Tags: patch
The typo "apporpriately" appears twice in the text. The attached patch
fixes it.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
--- a/en-US/11_network-services.xml
+++ b/en-US/11_network-services.xml
@@ -102,7 +102,7 @@
reject messages coming straight from such an IP address. In this
case, the smarthost will usually be the ISP's SMTP server, which is
always configured to accept email coming from the ISP's customers and
- forward it apporpriately. This setup (with a smarthost) is also
+ forward it appropriately. This setup (with a smarthost) is also
relevant for servers that are not permanently connected to the
internet, since it avoids having to manage a queue of undeliverable
messages that need to be retried later.</para>
--- a/pot/11_network-services.pot
+++ b/pot/11_network-services.pot
@@ -139,7 +139,7 @@
#. Tag: para
#, no-c-format
-msgid "The first question deals with the type of setup. Only two of the proposed answers are relevant in case of an Internet-connected server, “Internet site” and “Internet with smarthost”. The former is appropriate for a server that receives incoming email and sends outgoing email directly to its recipients, and is therefore well-adapted to the Falcot Corp case. The latter is appropriate for a server receiving incoming email nomally, but that sends outgoing email through an intermediate SMTP server — the “smarthost” — rather than directly to the recipient's server. This is mostly useful for individuals with a dynamic IP address, since many email servers reject messages coming straight from such an IP address. In this case, the smarthost will usually be the ISP's SMTP server, which is always configured to accept email coming from the ISP's customers and forward it apporpriately. This setup (with a smarthost) is also relevant for servers that are not permanent
ly connected to the internet, since it avoids having to manage a queue of undeliverable messages that need to be retried later."
+msgid "The first question deals with the type of setup. Only two of the proposed answers are relevant in case of an Internet-connected server, “Internet site” and “Internet with smarthost”. The former is appropriate for a server that receives incoming email and sends outgoing email directly to its recipients, and is therefore well-adapted to the Falcot Corp case. The latter is appropriate for a server receiving incoming email nomally, but that sends outgoing email through an intermediate SMTP server — the “smarthost” — rather than directly to the recipient's server. This is mostly useful for individuals with a dynamic IP address, since many email servers reject messages coming straight from such an IP address. In this case, the smarthost will usually be the ISP's SMTP server, which is always configured to accept email coming from the ISP's customers and forward it appropriately. This setup (with a smarthost) is also relevant for servers that are not permanent
ly connected to the internet, since it avoids having to manage a queue of undeliverable messages that need to be retried later."
msgstr ""
#. Tag: title
