Răsfoiți Sursa

usrloc: typos

Дилян Палаузов 2 ani în urmă
părinte
comite
6c4f9b049e

+ 7 - 7
src/modules/usrloc/doc/usrloc_admin.xml

@@ -700,7 +700,7 @@ modparam("usrloc", "db_url", "&exampledb;")
 			4 - This uses database to load records at startup but uses only
 			memory during the runtime. Records are not written back at all,
 			not even at shutdown. Useful for scenarios when registrations are
-			replicated to a node that does the storage in database during
+			replicated to a node that does the storage in a database during
 			runtime.
 			</para>
 		</listitem>
@@ -730,8 +730,8 @@ modparam("usrloc", "db_mode", 2)
 	<section id="usrloc.p.db_load">
 		<title><varname>db_load</varname> (int)</title>
 		<para>
-		Determine if the usrloc module should load contacts from the database storage during module initialization
-		A value of 0 disable the loading from the database, this parameter is ignored if db_mode 4 is set
+		Determine if the usrloc module should load contacts from the database storage during module initialization.
+		A value of 0 disables the loading from the database, this parameter is ignored if db_mode 4 is set.
 		</para>
 		<para>
 		<emphasis>
@@ -1323,7 +1323,7 @@ modparam("usrloc", "version_table", 0)
 		</para>
 		<para>
 		Note: Keepalives will be sent to the IP and port using the transport
-		defined in the “received” column.  If not set, then keepalives will be sent
+		defined in the <quote>received</quote> column.  If not set, then keepalives will be sent
 		to the AOR using UDP as a default transport.  If available, the TCP
 		connection will be re-used for WS, TCP and TLS.
 		</para>
@@ -1755,7 +1755,7 @@ modparam("usrloc", "db_clean_tcp", 1)
 		<title>users</title>
 			<para>
 			Number of AOR existing in the USRLOC memory cache for that domain
-			- can not be reset; this statistic will be register for each
+			- can not be reset; this statistic will be registered for each
 			used domain (Ex: location).
 			</para>
 		</section>
@@ -1763,7 +1763,7 @@ modparam("usrloc", "db_clean_tcp", 1)
 		<title>contacts</title>
 			<para>
 			Number of contacts existing in the USRLOC memory cache for that
-			domain - can not be reset; this statistic will be register for
+			domain - can not be reset; this statistic will be registered for
 			each used domain (Ex: location).
 			</para>
 		</section>
@@ -1771,7 +1771,7 @@ modparam("usrloc", "db_clean_tcp", 1)
 		<title>expires</title>
 			<para>
 			Total number of expired contacts for that domain - can be reset;
-			 this statistic will be register for each used domain
+			 this statistic will be registered for each used domain
 			(Ex: location).
 			</para>
 		</section>

+ 1 - 1
src/modules/usrloc/doc/usrloc_devel.xml

@@ -440,7 +440,7 @@
 		</title>
 		<para>
 		The function register with USRLOC a callback function to be called
-		when some event occures inside USRLOC.
+		when some event occurs inside USRLOC.
 		</para>
 		<para>Meaning of the parameters is as follows:</para>
 		<itemizedlist>

+ 1 - 1
src/modules/usrloc/udomain.c

@@ -1295,7 +1295,7 @@ void mem_timer_udomain(udomain_t* _d, int istart, int istep)
 /*!
  * \brief Get lock for a domain
  * \param _d domain
- * \param _aor adress of record, used as hash source for the lock slot
+ * \param _aor address of record, used as hash source for the lock slot
  */
 void lock_udomain(udomain_t* _d, str* _aor)
 {

+ 1 - 1
src/modules/usrloc/urecord.c

@@ -548,7 +548,7 @@ int db_delete_urecord_by_ruid(str *_table, str *_ruid)
  * \warning Failing to calls this function after get_urecord will
  * result in a memory leak when the DB_ONLY mode is used. When
  * the records is later deleted, e.g. with delete_urecord, then
- * its not necessary, as this function already releases the record.
+ * it is not necessary, as this function already releases the record.
  * \param _r released record
  */
 void release_urecord(urecord_t* _r)

+ 1 - 1
src/modules/usrloc/urecord.h

@@ -135,7 +135,7 @@ int delete_urecord_by_ruid(udomain_t* _d, str *_ruid);
  * \warning Failing to calls this function after get_urecord will
  * result in a memory leak when the DB_ONLY mode is used. When
  * the records is later deleted, e.g. with delete_urecord, then
- * its not necessary, as this function already releases the record.
+ * it is not necessary, as this function already releases the record.
  * \param _r released record
  */
 void release_urecord(urecord_t* _r);