summaryrefslogtreecommitdiff
path: root/doc/examples
diff options
context:
space:
mode:
authorMichael Vogt <michael.vogt@ubuntu.com>2010-10-15 18:30:09 +0200
committerMichael Vogt <michael.vogt@ubuntu.com>2010-10-15 18:30:09 +0200
commitb71a4a8dcd8b1d0e82f8071e5e993cc6423c6a57 (patch)
tree88c3ff0df846f2af9e901872f67e21b051129e3f /doc/examples
parent58d0598ad6f1c514bf7d89fdea676a697f0d9388 (diff)
parent95fe33dc131bee1a0917ba647e44855c10083ab5 (diff)
merged from debian-sid
Diffstat (limited to 'doc/examples')
-rw-r--r--doc/examples/apt-https-method-example.conf10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/examples/apt-https-method-example.conf b/doc/examples/apt-https-method-example.conf
index cc7889044..a03766746 100644
--- a/doc/examples/apt-https-method-example.conf
+++ b/doc/examples/apt-https-method-example.conf
@@ -6,7 +6,7 @@
This example file starts with a common setup that voluntarily exhibits
all available configurations knobs with simple comments. Extended
comments on the behavior of the option is provided at the end for
- better readibility. As a matter of fact, a common configuration file
+ better readability. As a matter of fact, a common configuration file
will certainly contain far less elements and benefit of default values
for many parameters.
@@ -38,12 +38,12 @@
matches their respective DNS names.
- We have CRL available for both dom1.tld and dom2.tld PKI, and intend
to use them.
- - It somtimes happens that we had other more generic https available
+ - It sometimes happens that we had other more generic https available
repository to our list. We want the checks to be performed against
a common list of anchors (like the one provided by ca-certificates
package for instance)
- The sample configuration below basically covers those simpe needs.
+ The sample configuration below basically covers those simple needs.
*/
@@ -168,12 +168,12 @@ Acquire::https::secure.dom2.tld::SslKey "/etc/apt/certs/my-key.pem";
When the option is set to "SSLv3" to have apt propose SSLv3 (and
associated sets of ciphersuites) instead of TLSv1 (the default)
when performing the exchange. This prevents the server to select
- TLSv1 and use associated cipheruites. You should probably not use
+ TLSv1 and use associated ciphersuites. You should probably not use
this option except if you know exactly what you are doing.
Note that the default setting does not guarantee that the server
will not select SSLv3 (for ciphersuites and SSL/TLS version as
- selectio is always done by the server, in the end). It only means
+ selection is always done by the server, in the end). It only means
that apt will not advertise TLS support.
Debug::Acquire::https "true";