Author: tedp-guest Date: 2007-06-16 18:26:09 +0000 (Sat, 16 Jun 2007) New Revision: 6022
Modified: doc/narrative_introduction Log: Fix typos Modified: doc/narrative_introduction =================================================================== --- doc/narrative_introduction 2007-06-16 18:18:07 UTC (rev 6021) +++ doc/narrative_introduction 2007-06-16 18:26:09 UTC (rev 6022) @@ -12,7 +12,7 @@ just a subversion repository and some text files that we collaboratively edit and then some scripts to parse these files and generate useful reports available online. Everything is designed to be -very simple to use, transparant and easy to see what other people are +very simple to use, transparent and easy to see what other people are working on so you can work on other things. Why are these issues disclosed to the public? @@ -33,7 +33,7 @@ knows about already, in fact users have told us that they prefer to know not only when a package they have installed is vulnerable (so they can disable it or firewall it off, or patch it or whatever), but -to also know that Debian is working on a fix. Transparancy is what our +to also know that Debian is working on a fix. Transparency is what our users expect, and what they deserve. Tracking publically known issues openly (and the occasional unfortunate embargoed issue privately) is good for the project as a whole, especially the public's perception of @@ -309,7 +309,7 @@ - Generate a list of packages that are subject to security problems, but stuck in testing migration due to problems with the dependency chain and thus candidates for a DTSA -- Generate a list of TODO issues that need to be adressed +- Generate a list of TODO issues that need to be addressed - Generate a list of packages that will enter Debian soon and need to be checked for security problems - Generate a list of provisional IDs that need to be turned into proper _______________________________________________ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testing-commits
