[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


 REJECT-FAQ.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/REJECT-FAQ.html b/REJECT-FAQ.html
index 9874112..4797b2f 100644
--- a/REJECT-FAQ.html
+++ b/REJECT-FAQ.html
@@ -4,7 +4,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-  <meta name="description" content="Reject FAQ for Debians NEW Queue" />
+  <meta name="description" content="Reject FAQ for Debian's NEW Queue" />
   <meta name="generator" content="GNU/Emacs" />
   <title>Reject FAQ for Debian's NEW-Queue</title>
@@ -216,7 +216,7 @@
       it doesn't make any sense to split a 50k arch:all package from a 250k
       arch:any one. Or splitting a package for only one file, depending on
       the main package. Yes, big dependency chains can be a reason. Or big
-      documentation splitted into one -doc package. The point there is
+      documentation split into one -doc package. The point there is
@@ -477,11 +477,11 @@
 	  <td>Package uses <tt>waf</tt> as build system</td>
-	  <td>That's a special case of <q>source code missing</q>. Normaly
+	  <td>That's a special case of <q>source code missing</q>. Normally
 	      packages using waf as build system contain a Python script
               with a compressed tarball embedded as a binary blob, where
               it is not obvious how to get the actual source. As that's not
-              considered to be the prefered form of modification, it fails
+              considered to be the preferred form of modification, it fails
               the DFSG.  See <a href="https://bugs.debian.org/645190";>#645190</a> and
               <a href="https://wiki.debian.org/UnpackWaf";>https://wiki.debian.org/UnpackWaf</a>
               for details.</td>

Reply to: