updating "freeswitch" to "FreeSWITCH" where appropriate

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

@@ -61,7 +61,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/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
 

docs/FreeSWITCH-Explained/Databases/ODBC_13173465.mdx

@@ -5,7 +5,7 @@
 
 ## About
 
-Basic documentation about using ODBC with freeswitch
+Basic documentation about using ODBC with FreeSWITCH
 
 ## ODBC
 

docs/FreeSWITCH-Explained/Interoperability/Phones/Nokia-N95/Nokia_N95_Settings_13174184.mdx

@@ -64,7 +64,7 @@ Highligh _MyApp_ and select **Options/Connect to service**
 
 After a few seconds the _Not Connected_ at the top of the screen should change to _Connected_ and a couple of new icons should appear at the top right of the screen
 
-Check that the handset is registered on freeswitch
+Check that the handset is registered on FreeSWITCH
 
 Now try calling another extension by dialing **[[email protected]](mailto:[email protected])** (you need to switch alpha mode on) or try routing a call to extension 1000.
 

docs/FreeSWITCH-Explained/Interoperability/Softphones/FSComm_7143564.mdx

@@ -72,7 +72,7 @@ Note: an old (Feb 2010) pre-built binary for Windows maintained by tusc is avail
 
 The Windows support is very experimental at this time. Only tested with 32 bit builds (don't know if x64 is supported yet)
 
-1. Download and build freeswitch
+1. Download and build FreeSWITCH
 2. Manually install [http://get.qt.nokia.com/qt/source/qt-win-opensource-4.6.0-vs2008.exe](http://get.qt.nokia.com/qt/source/qt-win-opensource-4.6.0-vs2008.exe) (180mb, needs 950mb hdd space)
 3. Set the environment variable QTDIR in the environment variables. (This can be set from the Computer/Properties/Advanced system settings/Environment Variables/User Variables settings screen.)  
 QTDIR=c:\\qt\\4.6.0 (or wherever you installed it.)
@@ -126,7 +126,7 @@ chmod 644 ~/.fscomm/conf/freeswitch.xml
 
 ##  Trouble shooting and debugging 
 
-You can use fs\_cli as in normal freeswitch
+You can use fs\_cli as in normal FreeSWITCH
 
 /usr/local/freeswitch/bin/fs_cli
 

docs/FreeSWITCH-Explained/Modules/mod_com_amd_4653131.mdx

@@ -113,7 +113,7 @@ Copy key to /etc/freeswitch (do not put the zip file in there)
 cp 0abd19753bf28fbb88a5d74.conf /etc/freeswitch
 ```
 
-Shutdown freeswitch
+Shutdown FreeSWITCH
 
 ```xml
 systemctl stop freeswitch