remove table of contents

supercharge · Jan 30, 2022 · 91263eb · 91263eb
1 parent e9e4312
commit 91263eb
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 17 deletions.
diff --git a/about-supercharge.md b/about-supercharge.md
@@ -1,5 +1,6 @@
 # Introduction to Supercharge
 
+
 ## Philosophy
 Supercharge is a full-stack Node.js framework. It differs from a typical Node.js “web” framework in ways that it provides much more structure on how to build solid applications. Supercharge comes with a well-conceived application architecture to build scalable, testable, and maintainable apps.
 

diff --git a/service-container.md b/service-container.md
@@ -1,15 +1,6 @@
 # Service Container (IoC Container)
 
 
-- [Introduction](#introduction)
-- [Resolving Dependencies](#resolving-dependencies)
-- [When to Use The Container](#when-to-use-the-container)
-- [Binding](#binding)
-  - [Singleton Bindings](#singleton-bindings)
-- [Resolving](#resolving)
-
-
-
 ## Introduction
 Supercharge uses a service container to manage dependencies. The container allows you to register dependencies and retrieve them when needed. This setup supports dependency injection in your application. Well, dependency injection is a funky term that basically describes “injecting” dependencies into a class (or function).
 

diff --git a/service-providers.md b/service-providers.md
@@ -1,14 +1,6 @@
 # Service Providers
 
 
-- [Introduction](#introduction)
-- [Creating Service Providers](#creating-service-providers)
-  - [The Register method](#the-register-method)
-  - [The Boot method](#the-boot-method)
-- [Registering Providers](#registering-providers)
-
-
-
 ## Introduction
 Service providers are essential when bootstrapping your application. The Supercharge framework uses service providers to load core functionalities and your application should use them as well.