Remove outdated TOCs from /Community/ directory (#227)

* Remove outdated TOCs from /Codecs-and-Media/ directory

* Remove outdated TOCs from /Community/ directory

---------

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

Author: TechWriterP

docs/FreeSWITCH-Explained/Community/Book_13173295.mdx

@@ -1,13 +1,6 @@
 
 # Book 
 
- 
-
-Click here to expand Table of Contents
-
-* 1 [The FreeSWITCH Book, aka The Bridge Book](#the-freeswitch-book-aka-the-bridge-book)  
-   * 1.1 [Errata](#errata)
-
 ## The FreeSWITCH Book, aka The Bridge Book
 
 We did it! We actually got a book published! Check it out [here](https://www.packtpub.com/freeswitch-1-0-6-build-robust-high-performance-telephony-systems/book).

docs/FreeSWITCH-Explained/Community/Contributing-Code/Adopt-A-Module_3965071.mdx

@@ -7,17 +7,6 @@
 
 The idea behind Adopt-a-Module... **TO-DO**
 
-* [About](#adopted-modules)
-* [Responsibilities of Adopter](#responsibilities-of-adopter)
-* [Why You Should Adopt-a-Module](#why-you-should-adopt-a-module)
-* [Adopted Modules](#adopted-modules)
-* [Modules Waiting for Adoption](#modules-waiting-for-adoption)
-* [Modules Off Limits](#modules-off-limits)
-* [FAQ](#adopted-modules)  
-   * [Can a module be adopted by more than one person?](#can-a-module-be-adopted-by-more-than-one-person)  
-   * [What happens if I can no longer maintain a module?](#what-happens-if-i-can-no-longer-maintain-a-module)
-* [See Also](#adopted-modules)
-
 ## Responsibilities of Adopter
 
 * Keep the wiki updated.

docs/FreeSWITCH-Explained/Community/Contributing-Code/Commit-Message-Guidelines_6587655.mdx

@@ -7,14 +7,6 @@
 
 How to better format your commit messages to meet the standards of the FreeSWITCH project.
 
-Click here to expand Table of Contents
-
-* 1 [Guidelines for a Good Commit](#guidelines-for-a-good-commit)
-* 2 [Writing a Good Commit Message](#writing-a-good-commit-message)
-* 3 [Patches Related to JIRA Issues](#patches-related-to-jira-issues)
-* 4 [Avoid Merges](#avoid-merges)
-* 5 [Do As We Say...](#do-as-we-say)
-
 #### Guidelines for a Good Commit
 
 To the extent possible and appropriate, address only one issue per commit. When we review your commit, anything that doesn't need to be there will only create confusion.

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

@@ -21,15 +21,6 @@ Modules register with an abstraction interface. At the time of this writing ther
 * ASR - this is the automated speech recognition interface
 * Management - SNMP interfaces
 
-Click here to expand Table of Contents
-
-* 1 [Creating a new Abstraction Interface](#creating-a-new-abstraction-interface)  
-   * 1.1 [src/include/switch\_module\_interfaces.h](#srcincludeswitch_module_interfacesh)  
-   * 1.2 [src/include/switch\_types.h](#srcincludeswitch_typesh)  
-   * 1.3 [src/include/switch\_loadable\_module.h](#srcincludeswitch_loadable_moduleh)  
-   * 1.4 [src/switch\_loadable\_module.c](#srcswitch_loadable_modulec)  
-   * 1.5 [Finally](#finally)
-
 ## Creating a new Abstraction Interface
 
 The FreeSWITCH™ core is somewhat guarded. While code contributions won't be refused outright, they do receive extra scrutiny. The core is common to all instances of FreeSWITCH™ and you can not do anything that would jeopardize the stability or performance for other users. Generally you will never have to do this, however there are times when you may. But be warned that if you go down this road your contributions may be rejected for inclusion in the tree.

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

@@ -7,12 +7,6 @@
 
 There are lots of tidbits that don't easily fall into a specific category for developers, so here are some miscellaneous and somewhat random tips that have been gleaned from conversations with the FreeSWITCH™ authors.
 
-Click here to expand Table of Contents
-
-* 1 [Apache Portable Runtime](#apache-portable-runtime)
-* 2 [Channel Data](#channel-data)
-* 3 [Debug Printing](#debug-printing)
-
 ## Apache Portable Runtime
 
 [![Informational Tip](https://wiki.freeswitch.org/images/thumb/b/b3/Info.png/64px-Info.png)](https://wiki.freeswitch.org/wiki/File:Info.png "Informational Tip")

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

@@ -7,45 +7,6 @@
 
 This page outlines some of the structure available to build a new FreeSWITCH™ module.
 
-Click to expand Table of Contents
-
-* 1 [Before You Begin...](#before-you-begin)  
-   * 1.1 [Building Modules](#building-modules)  
-      * 1.1.1 [Within Git checkout](#within-git-checkout)  
-         * 1.1.2 [Using development headers (libfreeswitch-dev)](#using-development-headers-libfreeswitch-dev)  
-   * 1.2 [Module Interface](#module-interface)  
-      * 1.2.1 [SWITCH\_MODULE\_LOAD\_FUNCTION](#switch_module_load_function)  
-         * 1.2.2 [SWITCH\_MODULE\_RUNTIME\_FUNCTION](#switch_module_runtime_function)  
-         * 1.2.3 [SWITCH\_MODULE\_SHUTDOWN\_FUNCTION](#switch_module_shutdown_function)  
-   * 1.3 [Iterative Development](#iterative-development)  
-      * 1.3.1 [Building Your Module](#creating-your-module)  
-         * 1.3.2 [Installing Your Module](#reloading-your-module)  
-         * 1.3.3 [Reloading Your Module](#creating-your-module)  
-   * 1.4 [XML API](#creating-your-module)  
-      * 1.4.1 [Domains](#creating-your-module)  
-         * 1.4.2 [Users](#creating-your-module)  
-         * 1.4.3 [Module Configuration](#module-configuration)  
-         * 1.4.4 [Gathering data from XML objects](#gathering-data-from-xml-objects)  
-   * 1.5 [Reacting](#creating-your-module)  
-      * 1.5.1 [Subscribing to events](#subscribing-to-events)  
-         * 1.5.2 [Handling events](#handling-events)  
-   * 1.6 [Setting hooks](#setting-hooks)  
-      * 1.6.1 [Channel States](#channel-states)  
-         * 1.6.2 [State handlers](#channel-states)  
-   * 1.7 [Making calls](#making-calls)  
-      * 1.7.1 [Analysis of a FreeSWITCH call](#analysis-of-a-freeswitch-call)  
-         * 1.7.2 [Making calls from within your module](#making-calls-from-within-your-module)  
-         * 1.7.3 [Session Objects](#session-objects)  
-   * 1.8 [Memory Management](#memory-management)  
-   * 1.9 [Useful Macros](#useful-macros)  
-      * 1.9.1 [SWITCH\_DECLARE\_GLOBAL\_STRING\_FUNC](#switch_declare_global_string_func)  
-         * 1.9.2 [switch\_malloc](#switch_malloc)  
-         * 1.9.3 [switch\_zmalloc](#switch_zmalloc)  
-         * 1.9.4 [switch\_strdup](#switch_strdup)  
-         * 1.9.5 [switch\_safe\_free](#switch_safe_free)
-* 2 [New Module Checklist](#new-module-checklist)
-* 3 [See Also:](#creating-your-module)
-
 ## Before You Begin...
 
 * Ensure that the functionality you're looking for has not already been implemented [somewhere else](../../../Modules/index.mdx#about).  

docs/FreeSWITCH-Explained/Community/Contributing-Code/Creating-RPM-repository_7766200.mdx

@@ -1,15 +1,5 @@
 
-# Creating RPM repository 
-
- 
-
-* 1 [Pre Requirements](#pre-requirements)  
-   * 1.1 [Installing mock utility](#installing-mock-utility)  
-   * 1.2 [Creating distribution specific config files](#creating-distribution-specific-config-files)
-* 2 [Creating repo](#creating-repo)  
-   * 2.1 [Creating SRPM packages](#creating-srpm-packages)  
-   * 2.2 [Creating RPM packages](#creating-rpm-packages)
-* 3 [Literature](#creating-repo)
+# Creating RPM repository
 
 ## About
 

docs/FreeSWITCH-Explained/Community/Contributing-Code/Pull-Requests_3966501.mdx

@@ -7,16 +7,6 @@
 
 This page describes the process of submitting code to FreeSWITCH.
 
-Click here to expand Table of Contents
-
-* 1 [Forking FreeSWITCH with Github](#forking-freeswitch-with-github)
-* 2 [Clone your fork](#clone-your-fork)
-* 3 [Ensure Git is Setup](#ensure-git-is-setup)
-* 4 [Create your working branch](#create-your-working-branch)
-* 5 [Commit your changes](#commit-your-changes)
-* 6 [Create Pull Request](#create-pull-request)
-* 7 [Getting feedback](#getting-feedback)
-
 ## Forking FreeSWITCH with Github
 
 * Create a new account in [Github](https://github.com)

docs/FreeSWITCH-Explained/Community/Contributing-Code/Tips-For-Using-Git_1048694.mdx

@@ -9,30 +9,6 @@ This page is a collection of tips for how to begin as a Developer working on Fre
 
 FreeSWITCH source code is now hosted at GitHub.
 
-Click to expand Table of Contents
-
-* 1 [Sources](#git-resources)
-* 2 [XKCD](#xkcd)
-* 3 [Install Git](#install-git)
-* 4 [Initial Checkout](#initial-checkout)
-* 5 [Checkout setup](#checkout-setup)
-* 6 [Syncing with Trunk](#syncing-with-trunk)  
-   * 6.1 [Delete Pulled Branch](#delete-pulled-branch)  
-   * 6.2 [Push to Master](#push-to-master)
-* 7 [Github Workflow](#github-workflow)  
-   * 7.1 [Committing Changes](#committing-changes)
-* 8 [Git Bisect - Tracking Down Breaks and Bugs Extremely Rapidly With git](#git-bisect---tracking-down-breaks-and-bugs-extremely-rapidly-with-git)
-* 9 [If You Change Code You Must Branch with Git](#if-you-change-code-you-must-branch-with-git)
-* 10 [Checking Out Previous Revisions](#checking-out-previous-revisions)
-* 11 [Cleaning Out Previous Revisions](#cleaning-out-previous-revisions)
-* 12 [GUIs and Utilities](#guis-and-utilities)  
-   * 12.1 [git-gui](#git-gui)  
-   * 12.2 [gitk](#git-gui)
-* 13 [Other Cool Tools](#other-cool-tools)
-* 14 [Git Resources](#git-resources)
-* 15 [See Also](#see-also)
-
-  
 ## Sources
 
 Hosted at [SignalWire GitHub](https://github.com/signalwire/):

docs/FreeSWITCH-Explained/Community/Using-the-Mailing-List_9633804.mdx

@@ -7,21 +7,6 @@
 
 The mailing list is the primary source for help on FreeSWITCH related questions/problems. However many users are unable to get full mileage from the list as they are inexperienced in formulating their questions and in interacting with the list members. This page seeks to address this problem. Many members of the list, including core developers, take a lot of time and trouble to patiently answer questions asked, and we users should take as much trouble to ask properly formulated questions. Try to follow the steps outlined below to make for a more pleasant and rewarding experience on the list.
 
-Click here to expand Table of Contents
-
-* 1 [Reporting a bug?](#reporting-a-bug)
-* 2 [Do your homework!](#do-your-homework)
-* 3 [How to use Google](#how-to-use-google)
-* 4 [Tips and Tricks](#tips-and-tricks)
-* 5 [Preparing your question](#preparing-your-question)  
-   * 5.1 [Do's](#dos)  
-   * 5.2 [Dont's](#donts)  
-   * 5.3 [Language](#language)
-* 6 [Formatting your emails/replies](#formatting-your-emailsreplies)
-* 7 [Follow up](#follow-up)
-* 8 [5-for-1](#5-for-1)
-* 9 [Urgent requests](#urgent-requests)
-
 ### Reporting a bug?
 
 Read this first! [Reporting Issues to GitHub](../Troubleshooting-Debugging/Reporting-Issues-to-GitHub_5046304.mdx#about)