From 6bd848bd33aa23878ab56dd17280eb6b13c7834a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Mon, 23 Sep 2019 11:45:12 +0200 Subject: [PATCH] Change link --- .../v2/difference-between-this-package-and-others.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/v2/difference-between-this-package-and-others.blade.md b/docs/source/v2/difference-between-this-package-and-others.blade.md index 0c990ed..c51764e 100644 --- a/docs/source/v2/difference-between-this-package-and-others.blade.md +++ b/docs/source/v2/difference-between-this-package-and-others.blade.md @@ -13,7 +13,7 @@ Packages like tenancy/multi-tenant and tenancy/tenancy give you an API for makin This package (stancl/tenancy) makes your application multi-tenant automatically and attempts to make you not have to change any things in your code. The philosophy behind this approach is that you should write your app, not tenancy boilerplate. -Apart from saving you a ton of time, the benefit of going with the automatic approach (stancl/tenancy) 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('configuration#tenancy-bootstrappers') }}) +Apart from saving you a ton of time, the benefit of going with the automatic approach (stancl/tenancy) 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') }}) ## Which one should you use?