./prepare-release pre-export

[apt.git] / README.progress-reporting

diff --git a/README.progress-reporting b/README.progress-reporting
index b575e7879d4c8960fb4a57c6fac5cfe5bf782370..5d9b581c5e41ba67a41d14674c840f90f8ae7c28 100644 (file)
--- a/README.progress-reporting
+++ b/README.progress-reporting
@@ -2,17 +2,17 @@ Install-progress reporting
 --------------------------
 
 If the apt options: "APT::Status-Fd" is set, apt will send status
-reports to that fd. The status information is seperated with a ':', 
+reports to that fd. The status information is separated with a ':',
 there are the following status conditions:
 
 status = {"pmstatus", "dlstatus", "conffile-prompt", "error", "media-change" } 
 
 The reason for using a fd instead of a OpProgress class is that many
-apt frontend fork a (vte) terminal for the actual installation.
+apt front-end fork a (vte) terminal for the actual installation.
 
 The reason to do the mapping and l10n of the dpkg states to human
 readable (and translatable) strings is that this way the translation
-needs to be done only once for all frontends.
+needs to be done only once for all front-ends.
 
 
 pmstatus