diff --git a/source/docs/v3/integrations/nova.blade.md b/source/docs/v3/integrations/nova.blade.md
index 68e85aa..431bd6d 100644
--- a/source/docs/v3/integrations/nova.blade.md
+++ b/source/docs/v3/integrations/nova.blade.md
@@ -10,7 +10,7 @@ section: content
 
 If you wish to use Laravel Nova in the central application (to manage tenants), you need to make a small change to the Nova migrations, they expect your model primary keys to always be unsigned big integers, but your tenants might be using `string` ids.
 
-You can find the full Nova setup for managing tenants in the [SaaS boilerplate](/saas-boilerplate):
+You can find the full Nova setup for managing tenants in the [SaaS boilerplate](/saas-boilerplate). It also implements Nova for **both the central and tenant parts of the app, with separate resources**.
 
 ## In the tenant app {#in-the-tenant-app}
 
@@ -24,7 +24,6 @@ To use Nova inside of the tenant part of your application, do the following:
 
 - Prevent Nova from adding its migrations to your central migrations by adding `Nova::ignoreMigrations()` to `NovaServiceProvider::boot()` (Don't do this if you want to use Nova **[both in the central & tenant parts]({{ $page->link('features/universal-routes') }})** of the app.)
 - Add the tenancy middleware to your `nova.middleware` config. Example:
-
     ```php
     'middleware' => [
         // You can make this simpler by creating a tenancy route group
@@ -37,7 +36,6 @@ To use Nova inside of the tenant part of your application, do the following:
         Authorize::class,
     ],
     ```
-
 - In your `NovaServiceProvider`'s `routes()` method, replace the following lines:
 
     ```php
@@ -60,4 +58,5 @@ To use Nova inside of the tenant part of your application, do the following:
         PreventAccessFromCentralDomains::class,
         'web',
     ])
-    ```
\ No newline at end of file
+    ```
+- Set the `domain` in Nova config to `null`