1 files changed, 2 insertions, 2 deletions
diff --git a/doc/chapters/basicauthentication.inc b/doc/chapters/basicauthentication.inc
index bbdd3641..cfcc96ff 100644
--- a/doc/chapters/basicauthentication.inc
+++ b/doc/chapters/basicauthentication.inc
@@ -14,7 +14,7 @@ GET /picture.png?mypassword
 In the rare situation where the client is customized enough and the connection occurs
 through secured lines (e.g., a embedded device directly attached to another via wire)
-and where the ability to embedd a password in the URI or to pass on a URI with a
+and where the ability to embed a password in the URI or to pass on a URI with a
 password are desired, this can be a reasonable choice. 
 But when it is assumed that the user connecting does so with an ordinary Internet browser,
@@ -37,7 +37,7 @@ Initially, the pointer this parameter references is set by @emph{MHD} in the cal
 also be "remembered" on the next call (for the same connection).
 Thus, we will generate no response until the parameter is non-null---implying the callback was
 called before at least once. We do not need to share information between different calls of the callback,
-so we can set the parameter to any adress that is assured to be not null. The pointer to the 
+so we can set the parameter to any address that is assured to be not null. The pointer to the 
 @code{connection} structure will be pointing to a legal address, so we take this.
 The first time @code{answer_to_connection} is called, we will not even look at the headers.

diff --git a/doc/chapters/basicauthentication.inc b/doc/chapters/basicauthentication.inc index bbdd3641..cfcc96ff 100644 --- a/doc/chapters/basicauthentication.inc +++ b/doc/chapters/basicauthentication.inc
@@ -14,7 +14,7 @@ GET /picture.png?mypassword
14		14
15	In the rare situation where the client is customized enough and the connection occurs	15	In the rare situation where the client is customized enough and the connection occurs
16	through secured lines (e.g., a embedded device directly attached to another via wire)	16	through secured lines (e.g., a embedded device directly attached to another via wire)
17	and where the ability to embedd a password in the URI or to pass on a URI with a	17	and where the ability to embed a password in the URI or to pass on a URI with a
18	password are desired, this can be a reasonable choice.	18	password are desired, this can be a reasonable choice.
19		19
20	But when it is assumed that the user connecting does so with an ordinary Internet browser,	20	But when it is assumed that the user connecting does so with an ordinary Internet browser,
@@ -37,7 +37,7 @@ Initially, the pointer this parameter references is set by @emph{MHD} in the cal
37	also be "remembered" on the next call (for the same connection).	37	also be "remembered" on the next call (for the same connection).
38	Thus, we will generate no response until the parameter is non-null---implying the callback was	38	Thus, we will generate no response until the parameter is non-null---implying the callback was
39	called before at least once. We do not need to share information between different calls of the callback,	39	called before at least once. We do not need to share information between different calls of the callback,
40	so we can set the parameter to any adress that is assured to be not null. The pointer to the	40	so we can set the parameter to any address that is assured to be not null. The pointer to the
41	@code{connection} structure will be pointing to a legal address, so we take this.	41	@code{connection} structure will be pointing to a legal address, so we take this.
42		42
43	The first time @code{answer_to_connection} is called, we will not even look at the headers.	43	The first time @code{answer_to_connection} is called, we will not even look at the headers.