r39 - /web/deps/dep5.mdwn

Thu Apr 2 00:11:42 UTC 2009

Author: plessy
Date: Thu Apr  2 00:11:42 2009
New Revision: 39

URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=39
Log:
Spellchecked.

Modified:
    web/deps/dep5.mdwn

Modified: web/deps/dep5.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?rev=39&op=diff
==============================================================================

--- web/deps/dep5.mdwn (original)
+++ web/deps/dep5.mdwn Thu Apr  2 00:11:42 2009
@@ -23,13 +23,13 @@
 This document proposes a simple format for summarising license terms and
 copyrights, in original upstream programs and in their packaged version. This
 tool will make the task easier for users to select a program according to their
-licensing preferences, and for the developpers of software distributions to
+licensing preferences, and for the developers of software distributions to
 ensure that only compatible works are combined.
 
 
 # Rationale
 
-The diversity of free software licenses means that developpers, users and
+The diversity of free software licenses means that developers, users and
 distributors needs to care not only about the freeness of a given work, but
 also its license's compatibility with the other works it uses.
 
@@ -51,7 +51,7 @@
 
 Lastly, a user might want to have a way to avoid software with certain licenses
 that do not fit their work procedures or their philosophy, even if the licenses
-are recoginsed by many as free. For example, the Affero GPL.
+are recognised by many as free. For example, the Affero GPL.
 
 
 # Compatibility and Human-Readability
@@ -101,7 +101,7 @@
 more stanzas.
 
  * **`Files`**
-   * Required. However, the first **`Files`** field can be ommited and its value will be assumed to be '*'.
+   * Required. However, the first **`Files`** field can be omitted and its value will be assumed to be '*'.
    * List of patterns indicating files having the same licence and sharing copyright holders. See "File patterns" below
 
  * **`Copyright`**
@@ -125,7 +125,7 @@
 	 [LICENSE TEXT]
 
 ### Standalone License Section
-Where a set of files are dual (tri, etc) licensed, or when the same licence occurs multiple times, you can use a single line **`License`** field and standlone **`License`** fields to expand the license short names.
+Where a set of files are dual (tri, etc) licensed, or when the same licence occurs multiple times, you can use a single line **`License`** field and standalone **`License`** fields to expand the license short names.
 
 Example 1 (tri-licensed files).
 
@@ -152,7 +152,7 @@
 	License: MPL-1.1
 
 	Files: src/js/fdlibm/*
-	Copyright: 1993, J-Random Comporation
+	Copyright: 1993, J-Random Corporation
 	License: MPL-1.1
 
 	License: MPL-1.1
@@ -194,7 +194,7 @@
 	find . -path "*/Makefile.am" -o -name "*.py"
 
 It is quite common for a work to have files with copyright held by
-different parties and received under different licenses. To accomodate
+different parties and received under different licenses. To accommodate
 this, **multiple stanzas are allowed with different `Files`
 declarations**.
 
@@ -413,7 +413,7 @@
 distribution license. In addition, it requires that copyrights must be
 extractable by mechanical means. This proposal for machine-readable copyright
 and license summary files has been crafted for Debian's use, but it is our hope
-that other software distributions, as well as upstream developpers will adopt
+that other software distributions, as well as upstream developers will adopt
 it, so that review efforts can be easily reproduced and shared. 
 
 The copyright of the Debian packaging and the history of package maintainers is


