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

---
 source/docs/v3/console-commands.blade.md                 | 2 +-
 source/docs/v3/event-system.blade.md                     | 4 ++--
 source/docs/v3/synced-resources-between-tenants.blade.md | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/source/docs/v3/console-commands.blade.md b/source/docs/v3/console-commands.blade.md
index c67ce74..ee1e76e 100644
--- a/source/docs/v3/console-commands.blade.md
+++ b/source/docs/v3/console-commands.blade.md
@@ -59,7 +59,7 @@ Listing all tenants.
 [Tenant] id: 49670df0-1a87-11e9-b7ba-cf5353777957 @ dev.localhost
 ```
 
-## **Selectively clearing tenant cache** {#selectively clearing tenant cache}
+## **Selectively clearing tenant cache** {#selectively-clearing-tenant-cache}
 
 You can delete specific tenants' cache by using the `--tags` option on `cache:clear`:
 
diff --git a/source/docs/v3/event-system.blade.md b/source/docs/v3/event-system.blade.md
index 31000c6..d11522f 100644
--- a/source/docs/v3/event-system.blade.md
+++ b/source/docs/v3/event-system.blade.md
@@ -28,7 +28,7 @@ $this->tenancy->initialize($tenant);
 
 Again, all of the above is configurable. You might even disable all tenancy bootstrappers, and just use tenant identification and scope your app manually around the tenant stored in `Stancl\Tenancy\Tenancy`. The choice is yours.
 
-# TenancyServiceProvider {#tenancyservice}
+# TenancyServiceProvider {#tenancyserviceprovider}
 
 This package comes with a very convenient service provider that's added to your application when you install the package. This service provider is used for mapping listeners to events specific to the package and is the place where you should put any tenancy-specific service container calls — to not pollute your AppServiceProvider.
 
@@ -52,7 +52,7 @@ The `JobPipeline` is a simple, yet **extremely powerful** class that lets you **
 
 You may use a job pipeline like any other listener, so you can register it in the `TenancyServiceProvider`, `EventServiceProvider` using the `$listen` array, or in any other place using `Event::listen()` — up to you.
 
-## Creating job pipelines
+## Creating job pipelines {creating-job-pipelines}
 
 To create a job pipeline, start by specifying the jobs you want to use:
 
diff --git a/source/docs/v3/synced-resources-between-tenants.blade.md b/source/docs/v3/synced-resources-between-tenants.blade.md
index 2f046c3..c547011 100644
--- a/source/docs/v3/synced-resources-between-tenants.blade.md
+++ b/source/docs/v3/synced-resources-between-tenants.blade.md
@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Synced resources between tenants {synced-resources-between-tenants}
+# Synced resources between tenants {#synced-resources-between-tenants}
 
 If you'd like to share certain resources, usually users, between tenant databases, you can use our resource syncing feature. This will let you **sync specific columns between specific tenant databases and the central database.**
 
@@ -30,7 +30,7 @@ An important requirement of the `Syncable` interface is the `getSyncedAttributeN
 
 The resource needs to have the same global ID in the central database and in tenant databases.
 
-## How it works [#how-it-works]
+## How it works {#how-it-works}
 
 Let's write an example implementation: