summaryrefslogtreecommitdiffstats
path: root/doc/narrative_introduction
diff options
context:
space:
mode:
authorNico Golde <nion@debian.org>2007-09-06 22:45:06 +0000
committerNico Golde <nion@debian.org>2007-09-06 22:45:06 +0000
commit025fea92ce5d3d73fdb127bbf783a47910aa339f (patch)
tree3d8487929ab53e9cd7512be5ec1917ecdda08e57 /doc/narrative_introduction
parenta003a6e6703ea73196a2639c44fba4b9def07ec8 (diff)
now spelling :)
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@6527 e39458fd-73e7-0310-bf30-c45bca0a0e42
Diffstat (limited to 'doc/narrative_introduction')
-rw-r--r--doc/narrative_introduction4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/narrative_introduction b/doc/narrative_introduction
index 6938b83529..58c0d761cd 100644
--- a/doc/narrative_introduction
+++ b/doc/narrative_introduction
@@ -4,7 +4,7 @@
About
-----
-Everything that Testing Security does is publically available, as in
+Everything that Testing Security does is publicly available, as in
"Debian doesn't hide problems" available.
The best thing about our tracking 'system' is that it is very basic.
@@ -34,7 +34,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. Transparency is what our
-users expect, and what they deserve. Tracking publically known issues
+users expect, and what they deserve. Tracking publicly known issues
openly (and the occasional unfortunate embargoed issue privately) is
good for the project as a whole, especially the public's perception of
the project.

© 2014-2024 Faster IT GmbH | imprint | privacy policy