(cherry picked from commit 4b2b8925c2c8f195f135ff262f7b45601b111b0d)
... | ... |
@@ -77,7 +77,7 @@ typedef struct _dstring_t { |
77 | 77 |
/** predefined buffer size */ |
78 | 78 |
int buff_size; |
79 | 79 |
|
80 |
- /** a operation on this string was unsuccesfull -> |
|
80 |
+ /** a operation on this string was unsuccessful -> |
|
81 | 81 |
* all other operations will produce error */ |
82 | 82 |
int error; |
83 | 83 |
} dstring_t; |
... | ... |
@@ -16,7 +16,7 @@ |
16 | 16 |
users identified by uid. Credentials can be used in digest authentication |
17 | 17 |
in SIP and/or authentication in SERWeb. In most situations credentials for |
18 | 18 |
digest authentication and SERWeb authentication are same. There are cases, |
19 |
- however, where seperate credentials for SERWeb and separate credentials |
|
19 |
+ however, where separate credentials for SERWeb and separate credentials |
|
20 | 20 |
for digest authentication may be needed. One such example are setups where |
21 | 21 |
subscribers get HW user agents with locked configuration and thay do not |
22 | 22 |
know the password and are not allowed to change it. If they should be able |
... | ... |
@@ -73,8 +73,8 @@ db_cmd_t* db_cmd(enum db_cmd_type type, db_ctx_t* ctx, char* table, |
73 | 73 |
} |
74 | 74 |
|
75 | 75 |
/* FIXME: This should be redesigned so that we do not need to connect |
76 |
- * connections in context before comands are created, this takes splitting |
|
77 |
- * the command initializatio sequence in two steps, one would be creating |
|
76 |
+ * connections in context before commands are created, this takes splitting |
|
77 |
+ * the command initialization sequence in two steps, one would be creating |
|
78 | 78 |
* all the data structures and the second would be checking corresponding |
79 | 79 |
* fields and tables on the server. |
80 | 80 |
*/ |
... | ... |
@@ -15,7 +15,7 @@ |
15 | 15 |
users identified by uid. Credentials can be used in digest authentication |
16 | 16 |
in SIP and/or authentication in SERWeb. In most situations credentials for |
17 | 17 |
digest authentication and SERWeb authentication are same. There are cases, |
18 |
- however, where seperate credentials for SERWeb and separate credentials |
|
18 |
+ however, where separate credentials for SERWeb and separate credentials |
|
19 | 19 |
for digest authentication may be needed. One such example are setups where |
20 | 20 |
subscribers get HW user agents with locked configuration and thay do not |
21 | 21 |
know the password and are not allowed to change it. If they should be able |