From 87577eb14ccc14f87d5e9eebf07be4e5ce70181c Mon Sep 17 00:00:00 2001
From: laurenfitzzz <63063106+laurenfitzzz@users.noreply.github.com>
Date: Thu, 2 Apr 2020 10:54:50 -0500
Subject: [PATCH] The documentation incorrectly has "localized: true" instead
 of "localizable: true"

---
 content/collections/docs/localization.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/collections/docs/localization.md b/content/collections/docs/localization.md
index eba9f6e3..843d70cc 100644
--- a/content/collections/docs/localization.md
+++ b/content/collections/docs/localization.md
@@ -240,7 +240,7 @@ J'adore le bacon
 There are 3 things to notice:
 
 1. The URL for the French site would use the localized slug
-2. We'll assume the `image` field didn't have `localized: true` in the fieldset.   That means it wouldn't have appeared in the publish form for the French locale. Also, since it's not defined in the French file, it falls back to the default locale's value.
+2. We'll assume the `image` field didn't have `localizable: true` in the fieldset.   That means it wouldn't have appeared in the publish form for the French locale. Also, since it's not defined in the French file, it falls back to the default locale's value.
 3. Assuming `{{ color }}` simply was left blank, or it had the same value as the default locale, it will fall back to the default locale's value.
 
 ## Subdomains {#subdomains}