Merge branch 'main' into gwh-fix-broken-link

Author: hey-august

docs/Channel-Variables-Catalog/hangup_after_bridge_16352708.mdx

@@ -3,7 +3,7 @@
 
  Created by  Ryan Harris, last modified by  Attila Gulyas on 2020.08.04
 
-boolean Controls what happens to a calling (A) party when in a [bridge state](../FreeSWITCH-Explained/Introduction/Life-Cycle-of-a-Call.mdx#0-about), and the called (B) party hangs up. If `true` the [dialplan](../FreeSWITCH-Explained/Dialplan/index.mdx#0-about) will stop processing, and the A leg will be terminated when the B leg terminates. If `false` (default) the dialplan continues to be processed after the B leg terminates. This is checked after [park\_after\_bridge](../FreeSWITCH-Explained/Dialplan/Variables-Master-List_16352570.mdx#park_after_bridge) and [transfer\_after\_bridge](../FreeSWITCH-Explained/Dialplan/Variables-Master-List_16352570.mdx#transfer_after_bridge).
+boolean Controls what happens to a calling (A) party when in a [bridge state](../FreeSWITCH-Explained/Introduction/Life-Cycle-of-a-Call.mdx#0-about), and the called (B) party hangs up. If `true` the [dialplan](../FreeSWITCH-Explained/Dialplan/index.mdx#about) will stop processing, and the A leg will be terminated when the B leg terminates. If `false` (default) the dialplan continues to be processed after the B leg terminates. This is checked after [park\_after\_bridge](../FreeSWITCH-Explained/Dialplan/Variables-Master-List_16352570.mdx#park_after_bridge) and [transfer\_after\_bridge](../FreeSWITCH-Explained/Dialplan/Variables-Master-List_16352570.mdx#transfer_after_bridge).
 
 The default value is `false` 
 

docs/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/13173942.mdx

@@ -3,7 +3,7 @@
 
 
 
-## About
+## About  
 
 This is how to Generate TLS certificates in win32\. A temporary solution for Windows users until an automatic script is available.
 

docs/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/Multi-home-tutorial/Multiple-Companies_13173524.mdx

@@ -7,7 +7,7 @@
 
 **Note**: _There is also some useful information on the [Multi-tenant](../../Examples/Multi-tenant_13173521.mdx#about) page, which needs merging._
 
-This is HOWTO to make one FreeSWITCH server act as a multi-tenant system for two or more companies, each with its own domain/users and independent [dialplans](../../Dialplan/index.mdx#0-about).
+This is HOWTO to make one FreeSWITCH server act as a multi-tenant system for two or more companies, each with its own domain/users and independent [dialplans](../../Dialplan/index.mdx#about).
 
 Basically, we want to have one FS server provide phone services to several separate companies, as if we are a VoIP provider. Let's start with two companies and give both companies the same two users (1000 for company-a and 1000 for company-b). These companies should be completely independent of each other, their identically-numbered extensions should not overlap or have anything to do with each other, and each company (and all of it's users/extensions) should have independent dialplans.
 

docs/FreeSWITCH-Explained/Client-and-Developer-Interfaces/Embedding-FreeSWITCH/index.mdx

@@ -55,7 +55,7 @@ Note some of the functions mentioned here may be a little bit different dependin
 
 Now the switch\_core\_init call is not needed unless you want to tie into the initial loading. The most likely reason to be involved in the initial loading is for tying into the xml\_search binding to be able to return custom XML during load from code. Why must the call pattern follow that? Technically switch\_core\_init calls switch\_core\_set\_globals, however switch\_core\_set\_globals must be called independently as switch\_core\_set\_globals is not called high enough in the function for it to work properly.
 
-#### Interacting with freeswitch
+#### Interacting with FreeSWITCH®
 
 Now you could tie your own app into also handling sessions (much like traditional dialplan calls) from your app. Depending on the application however it may be better to do as a traditional module/script just for code cleanness / separation. You of course do want to have some interaction with the core directly from your application most likely. The event module you can still use and then communicate over the event socket like external applications. You can also rely on the swig calls and interact with freeswitch through the native functions themselves. Swig allows you to call just about any native code, code with callbacks can be a bit more complex but in general you can call most native methods without issue. A best practice may be to instead use the API interface for dealing with freeswitch. Using the API most tasks can be accomplished and has the added safety of making it much harder to decrease the stability of freeswitch itself. There is also a large amount of documentation for the public API for freeswitch vs all the internal functions themselves. There are a few situations however where direct swig calls can be useful, most of the time it has to do with complex callbacks or function ties. There are two examples that frequently come up. The first is the switch\_xml\_bind\_search function, this allows you to return XML configuration during loading. There is a .net binding that the managed dll has to make it easier to add a callback (other bindings may or may not provide this). This allows you to return the config for any module directly. The second example is for events. Now you can tie into events several ways, for example through the event socket, but you can also tie into the main event loop (switch\_event\_bind) . Now doing this is risky, as its part of the main event loops events are not fully processed until you are done with them, so its suggested you duplicate events if you aren't handling them very quickly. The managed dll binding for this has a parameter for that.
 

docs/FreeSWITCH-Explained/Client-and-Developer-Interfaces/JavaScript/Javascript-Examples/JavaScript-Example---Session-in-Hangup-Hook_7766254.mdx

@@ -5,7 +5,7 @@
 
 ## About
 
-A simple example for accessing the session object after hangup when invoking the JS from the XML [dialplan](../../../Dialplan/index.mdx#0-about). More specifically, we're capturing the duration of the call and are saving it in a mySQL database with [ODBC](../../../Databases/ODBC-DSN/Using-ODBC-in-the-core_6586653.mdx).
+A simple example for accessing the session object after hangup when invoking the JS from the XML [dialplan](../../../Dialplan/index.mdx#about). More specifically, we're capturing the duration of the call and are saving it in a mySQL database with [ODBC](../../../Databases/ODBC-DSN/Using-ODBC-in-the-core_6586653.mdx).
 
 ## Dialplan
 

docs/FreeSWITCH-Explained/Client-and-Developer-Interfaces/JavaScript/index.mdx

@@ -22,7 +22,7 @@ If for some reason it's not, do the following:
 * Uncomment languages/mod\_v8 in modules.conf in your src directory (make it always build and install v8)
 * Run 'make mod\_v8-install' to make and install just the v8 module
 * Edit conf/autoload\_configs/modules.conf.xml in your FreeSWITCH™ install directory to load mod\_v8
-* Restart freeswitch
+* Restart FreeSWITCH
 
 ## Execution of a script