"Much like <command>apt</command> itself, its manpage is intended as an end "
"user interface and as such only mentions the most used commands and options "
"partly to not duplicate information in multiple places and partly to avoid "
-"overwelming readers with a cornucopia of options and details."
+"overwhelming readers with a cornucopia of options and details."
msgstr ""
#. type: Content of: <refentry><refsect1><variablelist><varlistentry><term>
msgid ""
"Removing a package removes all packaged data, but leaves usually small "
"(modified) user configuration files behind, in case the remove was an "
-"accident. Just issuing an installtion request for the accidently removed "
+"accident. Just issuing an installtion request for the accidentally removed "
"package will restore it funcation as before in that case. On the other hand "
"you can get right of these leftovers via calling <command>purge</command> "
"even on already removed packages. Note that this does not effect any data "
#. type: Content of: <refentry><refsect1><para>
#: apt-mark.8.xml
msgid ""
-"<command>apt-mark</command> can be used as a unified frontend to set various "
+"<command>apt-mark</command> can be used as a unified front-end to set various "
"settings for a package like marking a package as being automatically/"
"manually installed or changing <command>dpkg</command> selections such as "
"hold, install, deinstall and purge which are respected e.g. by <command>apt-"
msgid ""
"When you request that a package is installed, and as a result other packages "
"are installed to satisfy its dependencies, the dependencies are marked as "
-"being automatically installed, while package you installed explicitely is "
+"being automatically installed, while package you installed explicitly is "
"marked as manually installed. Once a automatically installed package is no "
"longer depended on by any manually installed package it is considered no "
"longer needed and e.g. <command>apt-get</command> or <command>aptitude</"
#. type: Content of: <refentry><refsect1><para>
#: apt-mark.8.xml
msgid ""
-"Some frontends like <command>apt-get dselect-upgrade</command> can be used "
+"Some front-ends like <command>apt-get dselect-upgrade</command> can be used "
"to apply previously sheduled changes to the install state of packages. Such "
"changes can be sheduled with the <option>install</option>, <option>remove</"
"option> (also known as <option>deinstall</option>) and <option>purge</"
msgid ""
"If an archive doesn't have a signed Release file or no Release file at all "
"current APT versions will raise a warning in <command>update</command> "
-"operations and frontends like <command>apt-get</command> will require "
+"operations and front-ends like <command>apt-get</command> will require "
"explicit confirmation if an installation request includes a package from "
"such an unauthenticated archive."
msgstr ""
#: apt-secure.8.xml
#, fuzzy
#| msgid ""
-#| "The package frontends &apt-get;, &aptitude; and &synaptic; support this "
+#| "The package front-ends &apt-get;, &aptitude; and &synaptic; support this "
#| "new authentication feature."
msgid ""
-"Note: All APT-based package management frontends like &apt-get;, &aptitude; "
+"Note: All APT-based package management front-ends like &apt-get;, &aptitude; "
"and &synaptic; support this authentication feature, so this manpage uses "
"<literal>APT</literal> to refer to them all for simplicity only."
msgstr ""
#. type: Content of: <refentry><refsect1><para>
#: apt-secure.8.xml
msgid ""
-"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."
#: apt-secure.8.xml
msgid ""
"<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 "
+"emphasis>. 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 "