Rev 5079: (jelmer, for John Szakmeister) Fix some typos in authentication help. in file:///home/pqm/archives/thelove/bzr/%2Btrunk/

[Canonical.com Patch Queue Manager]

At file:///home/pqm/archives/thelove/bzr/%2Btrunk/

------------------------------------------------------------
revno: 5079 [merge]
revision-id: pqm at pqm.ubuntu.com-20100310011027-9hbbdjalglssr00a
parent: pqm at pqm.ubuntu.com-20100310003856-dbh3pcbqw8y415zj
parent: john at szakmeister.net-20100309224338-pt4nsa2mm9wg3iso
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: +trunk
timestamp: Wed 2010-03-10 01:10:27 +0000
message:
  (jelmer, for John Szakmeister) Fix some typos in authentication help.
modified:
  bzrlib/help_topics/en/authentication.txt authentication_conf.-20071104135035-glfv0ri355tyg1nf-1
=== modified file 'bzrlib/help_topics/en/authentication.txt'
--- a/bzrlib/help_topics/en/authentication.txt	2010-01-03 03:33:10 +0000
+++ b/bzrlib/help_topics/en/authentication.txt	2010-03-09 22:43:38 +0000
@@ -58,10 +58,10 @@
 against a host. But, by using ``.htaccess`` files, for example, it is possible
 to define several (``user, realm, password``) for a given ``host``. So what is
 really needed is (``user``, ``password``, ``host``, ``path``). The ``realm`` is
-not taken into account in the defitions, but will displayed if bzr prompts you
-for a password.
+not taken into account in the definitions, but will displayed if bzr prompts
+you for a password.
 
-``HTTP proxy`` can be handled as ``HTTP`` (or ``HTTPS``) by explicitely
+``HTTP proxy`` can be handled as ``HTTP`` (or ``HTTPS``) by explicitly
 specifying the appropriate port.
 
 To take all schemes into account, the password will be deduced from a set of
@@ -165,7 +165,7 @@
 Source hosting provider
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-In the shp.net (fictious) domain, each project has its own site::
+In the shp.net (fictitious) domain, each project has its own site::
 
         [shpnet domain]
         # we use sftp, but ssh is the scheme used for authentication