[Asterisk-code-review] Fix 'statement' typo throughout code. (asterisk[13])

[Richard Mudgett]

Richard Mudgett has uploaded this change for review. ( https://gerrit.asterisk.org/10506


Change subject: Fix 'statement' typo throughout code.
......................................................................

Fix 'statement' typo throughout code.

Most were in comments.  A couple were in warning messages.

Pointed out by Jonathan H on the Asterisk users mailing list.

Change-Id: I6286939dff5d0a27a2758140570106f1cb351855
---
M addons/ooh323c/src/ooasn1.h
M main/db.c
M res/res_config_ldap.c
M utils/astdb2sqlite3.c
4 files changed, 11 insertions(+), 11 deletions(-)



  git pull ssh://gerrit.asterisk.org:29418/asterisk refs/changes/06/10506/1

diff --git a/addons/ooh323c/src/ooasn1.h b/addons/ooh323c/src/ooasn1.h
index 8355c54..4fee621 100644
--- a/addons/ooh323c/src/ooasn1.h
+++ b/addons/ooh323c/src/ooasn1.h
@@ -664,7 +664,7 @@
 /**
  * This function adds an integer parameter to an error information structure.
  * Parameter substitution is done in much the same way as it is done in C
- * printf statments. The base error message specification that goes along with
+ * printf statements. The base error message specification that goes along with
  * a particular status code may have variable fields built in using '%'
  * modifiers. These would be replaced with actual parameter data.
  *
@@ -680,7 +680,7 @@
 /**
  * This function adds an string parameter to an error information structure.
  * Parameter substitution is done in much the same way as it is done in C
- * printf statments. The base error message specification that goes along with
+ * printf statements. The base error message specification that goes along with
  * a particular status code may have variable fields built in using '%'
  * modifiers. These would be replaced with actual parameter data.
  *
@@ -697,7 +697,7 @@
 /**
  * This function adds an unsigned integer parameter to an error information
  * structure. Parameter substitution is done in much the same way as it is done
- * in C printf statments. The base error message specification that goes along
+ * in C printf statements. The base error message specification that goes along
  * with a particular status code may have variable fields built in using '%'
  * modifiers. These would be replaced with actual parameter data.
  *
diff --git a/main/db.c b/main/db.c
index bf73020..4d1b372 100644
--- a/main/db.c
+++ b/main/db.c
@@ -191,8 +191,8 @@
 
 static int init_statements(void)
 {
-	/* Don't initialize create_astdb_statment here as the astdb table needs to exist
-	 * brefore these statments can be initialized */
+	/* Don't initialize create_astdb_statement here as the astdb table needs to exist
+	 * brefore these statements can be initialized */
 	return init_stmt(&get_stmt, get_stmt_sql, sizeof(get_stmt_sql))
 	|| init_stmt(&del_stmt, del_stmt_sql, sizeof(del_stmt_sql))
 	|| init_stmt(&deltree_stmt, deltree_stmt_sql, sizeof(deltree_stmt_sql))
@@ -347,7 +347,7 @@
 		ast_log(LOG_WARNING, "Couldn't bind value to stmt: %s\n", sqlite3_errmsg(astdb));
 		res = -1;
 	} else if (sqlite3_step(put_stmt) != SQLITE_DONE) {
-		ast_log(LOG_WARNING, "Couldn't execute statment: %s\n", sqlite3_errmsg(astdb));
+		ast_log(LOG_WARNING, "Couldn't execute statement: %s\n", sqlite3_errmsg(astdb));
 		res = -1;
 	}
 
diff --git a/res/res_config_ldap.c b/res/res_config_ldap.c
index 6137236..91be91a 100644
--- a/res/res_config_ldap.c
+++ b/res/res_config_ldap.c
@@ -89,7 +89,7 @@
 	int metric;
 	const char *variable_name;
 	const char *variable_value;
-	int var_metric; /*!< For organizing variables (particularly includes and switch statments) within a context */
+	int var_metric; /*!< For organizing variables (particularly includes and switch statements) within a context */
 };
 
 /*! \brief Table configuration
@@ -1032,7 +1032,7 @@
 
 /*! \brief See Asterisk doc
  *
- * this function will be called for the switch statment if no match is found with the realtime_ldap function(i.e. it is a failover);
+ * this function will be called for the switch statement if no match is found with the realtime_ldap function(i.e. it is a failover);
  * however, the ast_load_realtime wil match on wildcharacters also depending on what the mode is set to
  * this is an area of asterisk that could do with a lot of modification
  * I think this function returns Realtime dynamic objects
diff --git a/utils/astdb2sqlite3.c b/utils/astdb2sqlite3.c
index ba35f93..fa00bc9 100644
--- a/utils/astdb2sqlite3.c
+++ b/utils/astdb2sqlite3.c
@@ -95,7 +95,7 @@
 		fprintf(stderr, "Couldn't bind value to stmt: %s\n", sqlite3_errmsg(astdb));
 		res = -1;
 	} else if (sqlite3_step(put_stmt) != SQLITE_DONE) {
-		fprintf(stderr, "Couldn't execute statment: %s\n", sqlite3_errmsg(astdb));
+		fprintf(stderr, "Couldn't execute statement: %s\n", sqlite3_errmsg(astdb));
 		res = -1;
 	}
 	sqlite3_reset(put_stmt);
@@ -168,8 +168,8 @@
 
 static int init_statements(void)
 {
-	/* Don't initialize create_astdb_statment here as the astdb table needs to exist
-	 * brefore these statments can be initialized */
+	/* Don't initialize create_astdb_statement here as the astdb table needs to exist
+	 * brefore these statements can be initialized */
 	return init_stmt(&put_stmt, put_stmt_sql, sizeof(put_stmt_sql));
 }
 

-- 
To view, visit https://gerrit.asterisk.org/10506
To unsubscribe, or for help writing mail filters, visit https://gerrit.asterisk.org/settings

Gerrit-Project: asterisk
Gerrit-Branch: 13
Gerrit-MessageType: newchange
Gerrit-Change-Id: I6286939dff5d0a27a2758140570106f1cb351855
Gerrit-Change-Number: 10506
Gerrit-PatchSet: 1
Gerrit-Owner: Richard Mudgett <rmudgett at digium.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-code-review/attachments/20181018/41688b89/attachment.html>