Improved Documentation Search (#61)

* chore: (Improve documentation search for V3)

* fix: checks for mispelled words

* fix: mispelled words

* fix spaces and syntax

* Update multi-database-tenancy.blade.md

Co-authored-by: Samuel Stancl <samuel.stancl@gmail.com>

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

@@ -4,7 +4,7 @@ extends: _layouts.documentation
 section: content
 ---
 
-# Laravel Passport
+# Laravel Passport {#laravel-passport}
 
 > If you just want to write an SPA, but don't need an API for some other use (e.g. mobile app), you can avoid a lot of the complexity of writing SPAs by using [Inertia.js](https://inertiajs.com/).
 
@@ -29,7 +29,7 @@ If you want to use the same keypair for all tenants, do the following.
 
 - Don't use `passport:install`, use just `passport:keys`. The install command creates keys & two clients. Instead of creating clients centrally, create `Client`s manually in your [tenant database seeder]({{ $page->link('configuration#seeder-params') }}).
 
-## **Tenant-specific keys**
+## **Tenant-specific keys** {#tenant-specific-keys}
 
 If you want to use a unique keypair for each tenant, do the following. (Note: The security benefit of doing this isn't probably that big, since you're likely already using the same `APP_KEY` for all tenants.)
 
@@ -47,7 +47,7 @@ There are multiple ways you can store & load tenant keys, but the most straightf
 
 And again, you need to create clients in your tenant database seeding process.
 
-## Using Passport in both the central & tenant app
+## Using Passport in both the central & tenant app {#using-passport-in-both-the-central-and-tenant-app}
 
 ![Passport for both central & tenant app](/assets/images/passport_universal.png)