mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-03 03:20:57 +00:00
docs: Fix various typos in main/
Found via `codespell -q 3 -S "./CREDITS" -L abd,asent,atleast,childrens,contentn,crypted,dne,durationm,exten,inout,leapyear,nd,oclock,offsetp,ot,parm,parms,requestor,ser,slanguage,slin,thirdparty,varn,varns,ues`
(cherry picked from commit 03ec0f2d17
)
This commit is contained in:
committed by
Asterisk Development Team
parent
7300a506d0
commit
a82e7c2f89
@@ -1022,7 +1022,7 @@ static void pbx_destroy(struct ast_pbx *p)
|
||||
* in a similar collating sequence as sorting alphabetic strings, from left to
|
||||
* right. Thus, "1XXXXX" comes before "X11111", and would be the "better" match,
|
||||
* because "1" is more specific than "X".
|
||||
* So, to accomodate this philosophy, I sort the tree branches along the alt_char
|
||||
* So, to accommodate this philosophy, I sort the tree branches along the alt_char
|
||||
* line so they are lowest to highest in specificity numbers. This way, as soon
|
||||
* as we encounter our first complete match, we automatically have the "best"
|
||||
* match and can stop the traversal immediately. Same for CANMATCH/MATCHMORE.
|
||||
@@ -4341,7 +4341,7 @@ static enum ast_pbx_result __ast_pbx_run(struct ast_channel *c,
|
||||
callid = ast_read_threadstorage_callid();
|
||||
/* If the thread isn't already associated with a callid, we should create that association. */
|
||||
if (!callid) {
|
||||
/* Associate new PBX thread with the channel call id if it is availble.
|
||||
/* Associate new PBX thread with the channel call id if it is available.
|
||||
* If not, create a new one instead.
|
||||
*/
|
||||
callid = ast_channel_callid(c);
|
||||
|
Reference in New Issue
Block a user