stancl/tenancy-docs
1
0
Fork 0
mirror of https://github.com/stancl/tenancy-docs.git synced 2025-12-12 10:14:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix spelling errors and broken links (#79)

Browse source 
* Fix spelling errors and broken links

* Make changes as requested
This commit is contained in:
DarthShmev 2020-09-01 11:55:31 -04:00 • committed by GitHub
parent de0a9c40f6
commit 4d12707980
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/docs/v3/event-system.blade.md
View file

@ -138,7 +138,7 @@ Note: All events are located in the `Stancl\Tenancy\Events` namespace.
- `RevertingToCentralContext`
- `RevertedToCentralContext`
Note the difference between *initializing tenancy and bootstrapping* tenancy. Tenancy is initialized when a tenant is loaded into the `Tenancy` object. Whereas boostrapping happens **as a result of initialization** — if you're using automatic tenancy, the `BootstrapTenancy` class is listening to the `TenancyInitialized` event and after it's done executing bootstrappers, it fires an event saying that tenancy was bootstrapped. You want to use the bootstrapped event if you want to execute something **after the app has been transitioned to the tenant context.**
Note the difference between *initializing tenancy and bootstrapping* tenancy. Tenancy is initialized when a tenant is loaded into the `Tenancy` object. Whereas bootstrapping happens **as a result of initialization** — if you're using automatic tenancy, the `BootstrapTenancy` class is listening to the `TenancyInitialized` event and after it's done executing bootstrappers, it fires an event saying that tenancy was bootstrapped. You want to use the bootstrapped event if you want to execute something **after the app has been transitioned to the tenant context.**
### Tenant {#tenant}

2
source/docs/v3/integrating.blade.md
View file

@ -7,7 +7,7 @@ section: content
# Integrating with other packages {#integrating-with-other-packages}
If you're using the [automatic mode]({{ $page->link('features/automatic-mode') }}) & [multi-database tenancy]({{ $page->link('multi-database-tenancy') }}), you'll be able to integrate with other packages easily.
If you're using the [automatic mode]({{ $page->link('automatic-mode') }}) & [multi-database tenancy]({{ $page->link('multi-database-tenancy') }}), you'll be able to integrate with other packages easily.
- [Integration with Spatie packages]({{ $page->link('integrations/spatie') }})
- [Laravel Horizon]({{ $page->link('integrations/horizon') }})

2
source/docs/v3/integrations/telescope.blade.md
View file

@ -6,6 +6,6 @@ section: content
# Laravel Telescope {#laravel-telescope}
Enable the the *Telescope tags* feature to have all Telescope requests tagged with the current tenant's id.
Enable the *Telescope tags* feature to have all Telescope requests tagged with the current tenant's id.
Note that Telescope (& its migrations) will be part of the central app.

2
source/docs/v3/introduction.blade.md
View file

@ -33,4 +33,4 @@ In the current version, we're also making [manual tenancy]({{ $page->link('manua
## Tenant identification {#tenant-identification}
For your application to be tenant-aware, a [tenant has to be identified]({{ $page->link('tenant-identification') }}). This package ships with a large number of identification middlewares. You may identify tenants by domain, subdomain, domain OR subdomain at the same time, path or request data.
For your application to be tenant-aware, a [tenant has to be identified]({{ $page->link('tenant-identification') }}). This package ships with many identification middleware classes. You may identify tenants by domain, subdomain, domain OR subdomain at the same time, path or request data.