From ed8aa7647ba25e30c06f8fff03178512f17c1af0 Mon Sep 17 00:00:00 2001 From: Evan Ibbott Date: Tue, 1 Sep 2020 11:35:51 -0400 Subject: [PATCH] Fix spelling errors and broken links --- navigation.php | 2 +- source/docs/v2/central-app.blade.md | 2 +- source/docs/v2/configuration.blade.md | 2 +- .../docs/v2/difference-between-this-package-and-others.blade.md | 2 +- source/docs/v2/upgrading.blade.md | 2 +- source/docs/v3/early-identification.blade.md | 2 +- source/docs/v3/event-system.blade.md | 2 +- source/docs/v3/integrating.blade.md | 2 +- source/docs/v3/integrations/telescope.blade.md | 2 +- source/docs/v3/introduction.blade.md | 2 +- source/donate.blade.md | 2 +- 11 files changed, 11 insertions(+), 11 deletions(-) diff --git a/navigation.php b/navigation.php index 4c7643a..5220d3f 100644 --- a/navigation.php +++ b/navigation.php @@ -104,7 +104,7 @@ return [ ], ], 'Integrations' => [ - 'url' => 'docs/integrations', + 'url' => 'integrations', 'children' => [ 'Spatie Packages' => 'spatie', 'Horizon' => 'horizon', diff --git a/source/docs/v2/central-app.blade.md b/source/docs/v2/central-app.blade.md index 9aeee9f..ee36bc6 100644 --- a/source/docs/v2/central-app.blade.md +++ b/source/docs/v2/central-app.blade.md @@ -11,7 +11,7 @@ This package uses routes to separate the tenant part of the application from the ## Central routes {#central-routes} -Routes in the `routes/web.php` file are the central routes. When they are visited, tenancy is *not* intialized and any model, cache call, controller, job dispatch, Redis call and anything else that is called in during this request will be central. +Routes in the `routes/web.php` file are the central routes. When they are visited, tenancy is *not* initialized and any model, cache call, controller, job dispatch, Redis call and anything else that is called in during this request will be central. ## Central domains {#central-domains} diff --git a/source/docs/v2/configuration.blade.md b/source/docs/v2/configuration.blade.md index e836f8a..13818fc 100644 --- a/source/docs/v2/configuration.blade.md +++ b/source/docs/v2/configuration.blade.md @@ -92,7 +92,7 @@ The aliases are used by the [event system]({{ $page->link('hooks') }}) ### `features` {#bootstrappers} -[Features]({{ $page->link('optional-features') }}) are similar to bootstrappers, but they are executed regardless of whether tenancy has been initialized or not. Their purpose is to provide additional functionality beyond what is necessary for the package to work. Things like easy redirects to tenant domains, tags in Telescope, etc. +[Features]({{ $page->link('features') }}) are similar to bootstrappers, but they are executed regardless of whether tenancy has been initialized or not. Their purpose is to provide additional functionality beyond what is necessary for the package to work. Things like easy redirects to tenant domains, tags in Telescope, etc. ### `home_url` {#home-url} diff --git a/source/docs/v2/difference-between-this-package-and-others.blade.md b/source/docs/v2/difference-between-this-package-and-others.blade.md index 32ca908..3cb6728 100644 --- a/source/docs/v2/difference-between-this-package-and-others.blade.md +++ b/source/docs/v2/difference-between-this-package-and-others.blade.md @@ -23,7 +23,7 @@ This package takes a completely new approach to multi-tenancy. It makes your application multi-tenant automatically and attempts to make you not have to change anything in your code. The philosophy behind this approach is that you should write your app, not tenancy boilerplate. -We belive that your code will be a lot cleaner if tenancy and the actual app don't mix. Why pollute your code with tons of tenancy implementations, when you can push all of tenancy one layer below your actual application? +We believe that your code will be a lot cleaner if tenancy and the actual app don't mix. Why pollute your code with tons of tenancy implementations, when you can push all of tenancy one layer below your actual application? Apart from saving you a ton of time, the benefit of going with the automatic approach 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') }}) diff --git a/source/docs/v2/upgrading.blade.md b/source/docs/v2/upgrading.blade.md index b504874..71d3225 100644 --- a/source/docs/v2/upgrading.blade.md +++ b/source/docs/v2/upgrading.blade.md @@ -7,7 +7,7 @@ section: content # Upgrading from 1.x {#upgrading} -The 2.0.0 release is essentialy a ~60% rewrite, with 3,187 additions and 1,896 deletions (lines of code). Version 2 introduces Laravel 6 support and drops Laravel 5.8 support. +The 2.0.0 release is essentially a ~60% rewrite, with 3,187 additions and 1,896 deletions (lines of code). Version 2 introduces Laravel 6 support and drops Laravel 5.8 support. This guide attempts to cover the main changes that were made to the package. The rewrite was mainly: - an internal thing: much better code quality means much better maintainability and much more features in the future :) diff --git a/source/docs/v3/early-identification.blade.md b/source/docs/v3/early-identification.blade.md index f47c90a..1355fc6 100644 --- a/source/docs/v3/early-identification.blade.md +++ b/source/docs/v3/early-identification.blade.md @@ -33,7 +33,7 @@ class PostController } ``` -If you don't like that because you access some dependency from many actions, consider creating a memoized method: +If you don't like that because you access some dependency from many actions, consider creating a memorized method: ```php class PostController diff --git a/source/docs/v3/event-system.blade.md b/source/docs/v3/event-system.blade.md index 763a1af..a479b9f 100644 --- a/source/docs/v3/event-system.blade.md +++ b/source/docs/v3/event-system.blade.md @@ -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} diff --git a/source/docs/v3/integrating.blade.md b/source/docs/v3/integrating.blade.md index c6ccbc6..38446a9 100644 --- a/source/docs/v3/integrating.blade.md +++ b/source/docs/v3/integrating.blade.md @@ -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') }}) diff --git a/source/docs/v3/integrations/telescope.blade.md b/source/docs/v3/integrations/telescope.blade.md index bde54f5..2892f52 100644 --- a/source/docs/v3/integrations/telescope.blade.md +++ b/source/docs/v3/integrations/telescope.blade.md @@ -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. diff --git a/source/docs/v3/introduction.blade.md b/source/docs/v3/introduction.blade.md index b413931..738e19a 100644 --- a/source/docs/v3/introduction.blade.md +++ b/source/docs/v3/introduction.blade.md @@ -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 a large number of identification middleware. You may identify tenants by domain, subdomain, domain OR subdomain at the same time, path or request data. diff --git a/source/donate.blade.md b/source/donate.blade.md index 7ddd581..f0a020b 100644 --- a/source/donate.blade.md +++ b/source/donate.blade.md @@ -27,7 +27,7 @@ If you would like to support me on a monthly basis in USD, you can use GitHub Sp If you'd like to donate using credit/debit card, select the amount below and click *Donate*. You will be redirected to Stripe. -This is the prefered method for one-time donations because it comes with **no fees at all** for either party. +This is the preferred method for one-time donations because it comes with **no fees at all** for either party.