diff --git a/.code-samples.meilisearch.yaml b/.code-samples.meilisearch.yaml
index b4e3d656f0..33e743ed07 100644
--- a/.code-samples.meilisearch.yaml
+++ b/.code-samples.meilisearch.yaml
@@ -238,13 +238,9 @@ field_properties_guide_searchable_1: |-
     -X POST 'http://localhost:7700/indexes/movies/settings' \
     --data '{
         "searchableAttributes": [
-            "uid",
-            "movie_id",
             "title",
             "description",
-            "poster",
-            "release_date",
-            "rank"
+            "genre"
         ]
     }'
 field_properties_guide_displayed_1: |-
diff --git a/guides/advanced_guides/field_properties.md b/guides/advanced_guides/field_properties.md
index b5be9227f1..85ceeecee5 100644
--- a/guides/advanced_guides/field_properties.md
+++ b/guides/advanced_guides/field_properties.md
@@ -14,7 +14,7 @@ Therefore, if a field attribute is not in the searchable-attributes list, the fi
 
 #### Example
 
-Suppose you manage a database that contains information about movies. By adding the following settings, the fields `uid`, `movie_id`, `title`, `description`, `poster`, `release_date` and `rank` will be searched.
+Suppose that you manage a database of movies with the following fields: `id`, `description`, `genre`, `title`, `release_date`. These fields all contain useful information; however, **some are more useful to search than others**. To make the `id` and `release_date` fields non-searchable and re-order the remaining fields by importance, you might update the searchable attributes list in the following way.
 
 <CodeSamples id="field_properties_guide_searchable_1" />