From abb4c7b27c7dbc4c62fdfa1b0509c965af4d7cb8 Mon Sep 17 00:00:00 2001
From: Michael <46441246+michael-ow@users.noreply.github.com>
Date: Fri, 22 May 2020 11:50:20 +0100
Subject: [PATCH] fix to link

---
 docs/installation/using-a-single-database.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/installation/using-a-single-database.md b/docs/installation/using-a-single-database.md
index a93d3ac..05acc12 100644
--- a/docs/installation/using-a-single-database.md
+++ b/docs/installation/using-a-single-database.md
@@ -24,4 +24,4 @@ This will create the `tenants` table which holds configuration per tenant.
 
 When using multiple tenants, you probably want to [isolate the cache](/laravel-multitenancy/v1/using-tasks-to-prepare-the-environment/cache/) or [use separate filesystems per tenant](/laravel-multitenancy/v1/using-tasks-to-prepare-the-environment/filesystems/), ... These things are perform by [task classes](/laravel-multitenancy/v1/using-tasks-to-prepare-the-environment/overview/) that will be executed when making a tenant the current one.
 
-The package can also has an option to [make the queue tenant aware](/laravel-multitenancy/v1/installation/making-queues-tenant-aware/).
+The package can also has an option to [make the queue tenant aware](/laravel-multitenancy/v1/basic-usage/making-queues-tenant-aware/).