Fix spelling errors and broken links (#79)

* Fix spelling errors and broken links

* Make changes as requested

source/docs/v2/central-app.blade.md

@@ -11,7 +11,7 @@ This package uses routes to separate the tenant part of the application from the
 
 ## Central routes {#central-routes}
 
-Routes in the `routes/web.php` file are the central routes. When they are visited, tenancy is *not* intialized and any model, cache call, controller, job dispatch, Redis call and anything else that is called in during this request will be central.
+Routes in the `routes/web.php` file are the central routes. When they are visited, tenancy is *not* initialized and any model, cache call, controller, job dispatch, Redis call and anything else that is called in during this request will be central.
 
 ## Central domains {#central-domains}
 

source/docs/v2/configuration.blade.md

@@ -92,7 +92,7 @@ The aliases are used by the [event system]({{ $page->link('hooks') }})
 
 ### `features` {#bootstrappers}
 
-[Features]({{ $page->link('optional-features') }}) are similar to bootstrappers, but they are executed regardless of whether tenancy has been initialized or not. Their purpose is to provide additional functionality beyond what is necessary for the package to work. Things like easy redirects to tenant domains, tags in Telescope, etc.
+[Features]({{ $page->link('features') }}) are similar to bootstrappers, but they are executed regardless of whether tenancy has been initialized or not. Their purpose is to provide additional functionality beyond what is necessary for the package to work. Things like easy redirects to tenant domains, tags in Telescope, etc.
 
 ### `home_url` {#home-url}
 

source/docs/v2/difference-between-this-package-and-others.blade.md

@@ -23,7 +23,7 @@ This package takes a completely new approach to multi-tenancy.
 
 It makes your application multi-tenant automatically and attempts to make you not have to change anything in your code. The philosophy behind this approach is that you should write your app, not tenancy boilerplate.
 
-We belive that your code will be a lot cleaner if tenancy and the actual app don't mix. Why pollute your code with tons of tenancy implementations, when you can push all of tenancy one layer below your actual application?
+We believe that your code will be a lot cleaner if tenancy and the actual app don't mix. Why pollute your code with tons of tenancy implementations, when you can push all of tenancy one layer below your actual application?
 
 Apart from saving you a ton of time, the benefit of going with the automatic approach is that you can adapt easily, since you're not bound to a specific implementation of multi-tenancy. [You can always change how tenancy is bootstrapped.]({{ $page->link('tenancy-bootstrappers') }})
 

source/docs/v2/upgrading.blade.md

@@ -7,7 +7,7 @@ section: content
 
 # Upgrading from 1.x {#upgrading}
 
-The 2.0.0 release is essentialy a ~60% rewrite, with 3,187 additions and 1,896 deletions (lines of code). Version 2 introduces Laravel 6 support and drops Laravel 5.8 support.
+The 2.0.0 release is essentially a ~60% rewrite, with 3,187 additions and 1,896 deletions (lines of code). Version 2 introduces Laravel 6 support and drops Laravel 5.8 support.
 
 This guide attempts to cover the main changes that were made to the package. The rewrite was mainly:
 - an internal thing: much better code quality means much better maintainability and much more features in the future :)