From 4b2b8925c2c8f195f135ff262f7b45601b111b0d Mon Sep 17 00:00:00 2001 From: Bastian Triller Date: Thu, 5 May 2022 18:22:00 +0200 Subject: [PATCH] lib: Fix typos --- src/lib/cds/dstring.h | 2 +- src/lib/srdb1/schema/uid_credentials.xml | 2 +- src/lib/srdb2/db_cmd.c | 4 ++-- src/lib/srdb2/schema/credentials.xml | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/lib/cds/dstring.h b/src/lib/cds/dstring.h index 039ed2b0998..5dc2de5c914 100644 --- a/src/lib/cds/dstring.h +++ b/src/lib/cds/dstring.h @@ -77,7 +77,7 @@ typedef struct _dstring_t { /** predefined buffer size */ int buff_size; - /** a operation on this string was unsuccesfull -> + /** a operation on this string was unsuccessful -> * all other operations will produce error */ int error; } dstring_t; diff --git a/src/lib/srdb1/schema/uid_credentials.xml b/src/lib/srdb1/schema/uid_credentials.xml index 8391e28e1c5..d0089693e02 100644 --- a/src/lib/srdb1/schema/uid_credentials.xml +++ b/src/lib/srdb1/schema/uid_credentials.xml @@ -16,7 +16,7 @@ users identified by uid. Credentials can be used in digest authentication in SIP and/or authentication in SERWeb. In most situations credentials for digest authentication and SERWeb authentication are same. There are cases, - however, where seperate credentials for SERWeb and separate credentials + however, where separate credentials for SERWeb and separate credentials for digest authentication may be needed. One such example are setups where subscribers get HW user agents with locked configuration and thay do not know the password and are not allowed to change it. If they should be able diff --git a/src/lib/srdb2/db_cmd.c b/src/lib/srdb2/db_cmd.c index 0adeca646a0..691b5f29991 100644 --- a/src/lib/srdb2/db_cmd.c +++ b/src/lib/srdb2/db_cmd.c @@ -73,8 +73,8 @@ db_cmd_t* db_cmd(enum db_cmd_type type, db_ctx_t* ctx, char* table, } /* FIXME: This should be redesigned so that we do not need to connect - * connections in context before comands are created, this takes splitting - * the command initializatio sequence in two steps, one would be creating + * connections in context before commands are created, this takes splitting + * the command initialization sequence in two steps, one would be creating * all the data structures and the second would be checking corresponding * fields and tables on the server. */ diff --git a/src/lib/srdb2/schema/credentials.xml b/src/lib/srdb2/schema/credentials.xml index 8bc7809fbfe..a6c3ccadfbc 100644 --- a/src/lib/srdb2/schema/credentials.xml +++ b/src/lib/srdb2/schema/credentials.xml @@ -15,7 +15,7 @@ users identified by uid. Credentials can be used in digest authentication in SIP and/or authentication in SERWeb. In most situations credentials for digest authentication and SERWeb authentication are same. There are cases, - however, where seperate credentials for SERWeb and separate credentials + however, where separate credentials for SERWeb and separate credentials for digest authentication may be needed. One such example are setups where subscribers get HW user agents with locked configuration and thay do not know the password and are not allowed to change it. If they should be able