Improve spatie/laravel-permission section

source/docs/v3/integrations/spatie.blade.md

@@ -29,19 +29,23 @@ php artisan vendor:publish --provider="Spatie\Permission\PermissionServiceProvid
 mv database/migrations/*_create_permission_tables.php database/migrations/tenant
 ```
 
-Then add this to your `TenancyServiceProvider::boot()`:
+Next, add the following listeners to the `TenancyBootstrapped` and `TenancyEnded` events in `TenancyServiceProvider::events()`:
 
 ```php
-Event::listen(TenancyBootstrapped::class, function (TenancyBootstrapped $event) {
+Events\TenancyBootstrapped::class => [
+    function (TenancyBootstrapped $event) {
         \Spatie\Permission\PermissionRegistrar::$cacheKey = 'spatie.permission.cache.tenant.' . $event->tenancy->tenant->id;
-});
+    }
+],
 
-Event::listen(TenancyEnded::class, function (TenancyEnded $event) {
+Events\TenancyEnded::class => [
+    function (TenancyEnded $event) {
         \Spatie\Permission\PermissionRegistrar::$cacheKey = 'spatie.permission.cache';
-});
+    }
+],
 ```
 
-The reason for this is that spatie/laravel-permission caches permissions & roles to save DB queries, which means that we need to separate the permission cache by tenant.
+The reason for this is that spatie/laravel-permission caches permissions & roles to save DB queries, which means that we need to separate the permission cache by tenant. We also need to reset the cache key when tenancy ends so that the tenant's cache key isn't used in the central app.
 
 ## **laravel-medialibrary** {#laravel-medialibrary}