From e6494c7a15cd20453040262b4b5410b7c1092fee Mon Sep 17 00:00:00 2001
From: Adebayo Ilerioluwa <46798106+adebayoileri@users.noreply.github.com>
Date: Tue, 21 Jul 2020 18:27:35 +0100
Subject: [PATCH] fix: checks for mispelled words

---
 source/docs/v3/cached-lookup.blade.md         | 2 +-
 source/docs/v3/configuration.blade.md         | 2 +-
 source/docs/v3/console-commands.blade.md      | 2 +-
 source/docs/v3/event-system.blade.md          | 2 +-
 source/docs/v3/tenancy-bootstrappers.blade.md | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/source/docs/v3/cached-lookup.blade.md b/source/docs/v3/cached-lookup.blade.md
index 2a4c6c6..babc411 100644
--- a/source/docs/v3/cached-lookup.blade.md
+++ b/source/docs/v3/cached-lookup.blade.md
@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Cached lookup {cached-lookup}
+# Cached lookup {#cached-lookup}
 
 If you're using multiple databases, you may want to avoid making a query to the central database on **each tenant request** — for tenant identification. Even though the queries are very simple, the app has to establish a connection with the central database which is expensive.
 
diff --git a/source/docs/v3/configuration.blade.md b/source/docs/v3/configuration.blade.md
index a610ad2..eb818de 100644
--- a/source/docs/v3/configuration.blade.md
+++ b/source/docs/v3/configuration.blade.md
@@ -37,7 +37,7 @@ If you wish to use autoincrement ids instead of uuids:
 1. set this config key to null, or create a custom tenant model that doesn't use this trait
 2. update the `tenants` table migration to use an incrementing column type instead of `string`
 
-### Domain model {3domain-model}
+### Domain model {#domain-model}
 
 `tenancy.domain_model`
 
diff --git a/source/docs/v3/console-commands.blade.md b/source/docs/v3/console-commands.blade.md
index cff134a..c67ce74 100644
--- a/source/docs/v3/console-commands.blade.md
+++ b/source/docs/v3/console-commands.blade.md
@@ -50,7 +50,7 @@ If your command's signature were `email:send {--queue} {--subject=} {body}`, yo
 php artisan tenants:run email:send --tenants=8075a580-1cb8-11e9-8822-49c5d8f8ff23 --option="queue=1" --option="subject=New Feature" --argument="body=We have launched a new feature. ..."
 ```
 
-## **Tenant list** {#teant-list}
+## **Tenant list** {#tenant-list}
 
 ```
 php artisan tenants:list
diff --git a/source/docs/v3/event-system.blade.md b/source/docs/v3/event-system.blade.md
index d37cc0d..31000c6 100644
--- a/source/docs/v3/event-system.blade.md
+++ b/source/docs/v3/event-system.blade.md
@@ -38,7 +38,7 @@ Note that you can register listeners to this package's events **anywhere you wan
 Event::listen(TenancyInitialized::class, BootstrapTenancy::class);
 ```
 
-# Bootstrapping tenancy [#bootstrapping-tenancy]
+# Bootstrapping tenancy {#bootstrapping-tenancy}
 
 By default, the `BootstrapTenancy` class is listening to the `TenancyInitialized` event (exactly as you can see in the example above). That listener will execute the configured tenancy bootstrappers to transition the application into the tenant's context. You can read more about this on the [tenancy bootstrappers]({{ $page->link('tenancy-bootstrappers') }}) page.
 
diff --git a/source/docs/v3/tenancy-bootstrappers.blade.md b/source/docs/v3/tenancy-bootstrappers.blade.md
index 429e576..d4e79b2 100644
--- a/source/docs/v3/tenancy-bootstrappers.blade.md
+++ b/source/docs/v3/tenancy-bootstrappers.blade.md
@@ -49,7 +49,7 @@ You can read more about this on the *Queues* page:
 
 [Queues]({{ $page->link('queues') }})
 
-## Redis tenancy bootstrapper {#resis-tenancy-bootstrapper}
+## Redis tenancy bootstrapper {#redis-tenancy-bootstrapper}
 
 If you're using `Redis` calls (not cache calls, **direct** Redis calls) inside the tenant app, you will want to scope Redis data too. To do this, use this bootstrapper. It changes the Redis prefix for each tenant.