summaryrefslogtreecommitdiff
path: root/doc/apt-secure.8.xml
diff options
context:
space:
mode:
authorJustin B Rye <justin.byam.rye@gmail.com>2015-11-21 17:50:06 +0100
committerDavid Kalnischkies <david@kalnischkies.de>2015-11-21 18:04:29 +0100
commitd04e44ac8177fc5b70ae0189bb5e437c2502f910 (patch)
tree6ba968bf2a80d788c506007a4c1c0b233f2013c6 /doc/apt-secure.8.xml
parentabd6af5a1ce2c20a5742c5c3182dfadce10367ca (diff)
review of new/changed translatable program strings
Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
Diffstat (limited to 'doc/apt-secure.8.xml')
-rw-r--r--doc/apt-secure.8.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/apt-secure.8.xml b/doc/apt-secure.8.xml
index 9b4b7378d..1aab0af8f 100644
--- a/doc/apt-secure.8.xml
+++ b/doc/apt-secure.8.xml
@@ -151,7 +151,7 @@
as list the trusted keys. Limiting which key(s) are able to sign which archive
is possible via the <option>Signed-By</option> in &sources-list;.
</para><para>
- Note that a default installation already contains all keys to securily
+ Note that a default installation already contains all keys to securely
acquire packages from the default repositories, so fiddling with
<command>apt-key</command> is only needed if third-party repositories are
added.
@@ -191,7 +191,7 @@
<listitem><para>
<emphasis>Provide instructions on how to add your archive and key</emphasis>.
- If your users can't acquire your key securily the chain of trust described above is broken.
+ If your users can't acquire your key securely the chain of trust described above is broken.
How you can help users add your key depends on your archive and target audience ranging
from having your keyring package included in another archive users already have configured
(like the default repositories of their distribution) to leverage the web of trust.