Fix headers, semantic line breaks, and other small edits. (#256)

* Fix headers, semantic line breaks, and other small edits.

* Fix links

---------

Co-authored-by: August <[email protected]>
Co-authored-by: hey-august <[email protected]>

Author: rydiaroads

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/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/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/Codecs-and-Media/Bypass-Media-Overview/Call-Forward-Example_6587445.mdx

@@ -64,7 +64,7 @@ For instance, you can call the is\_forward features before you bridge to your ph
 **See also:**
 
 * [Simple CF with IVR](../../Examples/Simple-Call-Forward-with-IVR_9634448.mdx)
-* [Dialplan](../../Dialplan/index.mdx#0-about)
+* [Dialplan](../../Dialplan/index.mdx#about)
 
 
 

docs/FreeSWITCH-Explained/Community/Contributing-Code/Creating-New-Modules/9634354.mdx

@@ -98,7 +98,7 @@ The internal sections of FreeSWITCH only use:
 
 * uuid
 * caller\_id\_name, caller\_id\_number, caller\_extension
-* [dialplan](../../../Dialplan/index.mdx#0-about)
+* [dialplan](../../../Dialplan/index.mdx#about)
 * destination\_number
 
 The **channel** flags hold extra state information above and beyond the basic 13 states that are held in the `state` variable. The interesting flags are:

docs/FreeSWITCH-Explained/Configuration/Configuring-FreeSWITCH/index.mdx

@@ -415,7 +415,7 @@ See [Config\_1000.xml](../Default-Configuration_6587388#configuration) for a sim
 
 The FreeSWITCH dialplan is a full-featured, XML-based call-routing mechanism. (There also exists support for Asterisk-like dialplans as well as really fancy real-time and/or back-end database-driven dialplans).
 
-The best place to get started in learning about the FreeSWITCH dialplan is the [Dialplan](../../Dialplan/index.mdx#0-about) page here on the wiki. It discusses the basics of the FreeSWITCH dialplan. If you need an XML primer, check out the information on the [Basic\_XML](../../Dialplan/XML-Dialplan/index.mdx#about) page which will get you pointed in the right direction. There are two other important resources for you to learn more about the dialplan:
+The best place to get started in learning about the FreeSWITCH dialplan is the [Dialplan](../../Dialplan/index.mdx#about) page here on the wiki. It discusses the basics of the FreeSWITCH dialplan. If you need an XML primer, check out the information on the [Basic\_XML](../../Dialplan/XML-Dialplan/index.mdx#about) page which will get you pointed in the right direction. There are two other important resources for you to learn more about the dialplan:
 
 * the small-but-growing [Dialplan\_Recipes](../../Dialplan/Dialplan-Recipes_9634252.mdx#about) page
 * the [default dialplan](../../Dialplan/Default-Dialplan-QRF_9634422.mdx#park) that comes with a standard FreeSWITCH installation.
@@ -695,7 +695,7 @@ This is the main configuration file, and the only one that has a fixed name. Whe
 freeswitch.xml is divided into multiple sections, and each section is used by a different component in FreeSWITCH™. The sections are as follows:
 
 * The "configuration" section has children for [switch.conf](../XML-Switch-Configuration_13173223.mdx) and [modules.conf](../../Modules/XML-Modules-Configuration_13173211.mdx) which are used by the core, as well as a child for each module in use.
-* The [dialplan](../../Dialplan/index.mdx#0-about) section defines which action to invoke when a call arrvies to the switch.
+* The [dialplan](../../Dialplan/index.mdx#about) section defines which action to invoke when a call arrvies to the switch.
 * The [directory](../../Directory/XML-User-Directory/index.mdx#about) defines the users that can connect to the switch (user agents).
 * The phrases section defines where freeswitch can find the sound files, and if it can use any TTS engines.
 
@@ -784,7 +784,7 @@ FreeSWITCH is a B2BUA (back-to-back user agent). This means that it actually par
 
 ## See Also
 
-* [Dialplan](../../Dialplan/index.mdx#0-about)
+* [Dialplan](../../Dialplan/index.mdx#about)
 * [Dialplan XML](../../Dialplan/XML-Dialplan/index.mdx#about)
 * [Dialplan Recipes](../../Dialplan/Dialplan-Recipes_9634252.mdx#about)
 * [Dialplan Basics](https://wiki.freeswitch.org/wiki/Dialplan%5FBasics)

docs/FreeSWITCH-Explained/Configuration/Default-Configuration_6587388.mdx

@@ -312,15 +312,15 @@ This is where the different SIP profiles (or endpoints) are defined. (See [Sofia
 
 Public Context for Security
 
-You'll notice that all the SIP profiles in the [default configuration](./Default-Configuration_6587388.mdx#mod_vp8) use the `public` context for their [dialplan](../Dialplan/index.mdx#0-about), **including the `internal` profile**:
+You'll notice that all the SIP profiles in the [default configuration](./Default-Configuration_6587388.mdx#mod_vp8) use the `public` context for their [dialplan](../Dialplan/index.mdx#about), **including the `internal` profile**:
 
 **conf/sip\_profiles/\*.xml**
 
 ```xml
 <param name="context" value="public"/>
 ```
 
-If you look in the directory config files, `conf/directory/default/*.xml` (see Introduction in [Dialplan](../Dialplan/index.mdx#0-about)), you'll notice that the SIP profile's context is overridden there like so:
+If you look in the directory config files, `conf/directory/default/*.xml` (see Introduction in [Dialplan](../Dialplan/index.mdx#about)), you'll notice that the SIP profile's context is overridden there like so:
 
 **conf/directory/default/\*.xml**
 

docs/FreeSWITCH-Explained/Configuration/Sofia-SIP-Stack/Sofia-Configuration-Files_7144453.mdx

@@ -34,7 +34,7 @@ Now I've got two UAs defined by my profiles, each of which can handle a call. Wh
 
 So, the task becomes rather straightforward. Dialplans use pattern matching and other tricks to determine how to handle a call. My dialplan examines what I've dialed and then determines what profile to use with that call. If I dial a telephone number, the dialplan selects the UA that connects up to the PSTN. If I dial a SIP address outside the firewall, the dialplan selects that same UA because it uses the STUN server. But if I dial a SIP address that's inside the firewall, the dialplan selects the "local" UA.
 
-To understand how to write dialplans, use pattern matching, etc., see [Dialplan](../../Dialplan/index.mdx#0-about)
+To understand how to write dialplans, use pattern matching, etc., see [Dialplan](../../Dialplan/index.mdx#about)
 
 #### The Relationship Between SIP Profiles and Domains
 

docs/FreeSWITCH-Explained/Dialplan/Dialplan-Recipes_9634252.mdx

@@ -69,7 +69,7 @@ It is also possible to have various legs of the bridge contain different timeout
 
 ## See Also
 
-* [Misc.\_Dialplan\_Tools\_bridge](index.mdx#0-about)
+* [Misc.\_Dialplan\_Tools\_bridge](index.mdx#about)
 * [Regular Expression](../Examples/Regular-Expression/index.mdx)
 
 

docs/FreeSWITCH-Explained/Dialplan/Inline-Dialplan_13173434.mdx

@@ -85,7 +85,7 @@ Note that you specify "inline:" at the beginning of the parameter and not at the
 
 ## See Also
 
-* [Dialplan](./index.mdx#0-about)
+* [Dialplan](./index.mdx#about)
 * [Configuration](../Configuration/index.mdx#about)
 * [mod\_dptools: Inline Dialplan](../Modules/mod-dptools/6586667.mdx#about)