diff --git a/DOCUMENTATION.md b/DOCUMENTATION.md
index e10d822..dfc9508 100644
--- a/DOCUMENTATION.md
+++ b/DOCUMENTATION.md
@@ -32,7 +32,7 @@ Before importing, you will need to do some preparation:
 3. You can then map fields from your blueprint to fields/columns in your file.
     * Depending on the fieldtype, some fields may have additional options, like "Related Key" or "Create when missing". You can read more about these below.
     * Mapping is disabled for some fieldtypes, like the [Replicator fieldtype](https://statamic.dev/fieldtypes/replicator#content). If you wish to import these fields, you will need to build a [custom transformer](#transformers).
-    * When you're importing taxonomy terms into a non-default site (eg. not the first site) and the slugs differ between sites, you can use the "Default Slug" field to specify the slug of the term in the default site.
+    * When you're importing taxonomy terms into a non-default site (eg. not the _first_ site you created) and the slugs differ between sites, you can map the "Slug in Default Site" field to the slug of the term in the default site in order for the importer to match up the terms correctly.
 4. If you're importing entries, you will also need to specify a "Unique Field". This field will be used to determine if an entry already exists in Statamic.
 5. Then, run the import and watch the magic happen! ✨
 
diff --git a/src/Imports/Import.php b/src/Imports/Import.php
index 2b0b7fc..42c26f5 100644
--- a/src/Imports/Import.php
+++ b/src/Imports/Import.php
@@ -177,7 +177,7 @@ public function mappingFields(): Fields
             if ($this->get('destination.site') !== $taxonomy->sites()->first()) {
                 $blueprint->ensureField('default_slug', [
                     'type' => 'slug',
-                    'display' => __('Default Slug'),
+                    'display' => __('Slug in Default Site'),
                 ]);
             }
         }