From 751cf4343ed41043823cedb6736ad18f2255a8ff Mon Sep 17 00:00:00 2001
From: Jennifer Starratt <42216769+jennifer-starratt@users.noreply.github.com>
Date: Thu, 19 Nov 2020 07:41:49 -0800
Subject: [PATCH] Updates to README pertaining to required merge fields. (#53)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c08d283..f11eab1 100644
--- a/README.md
+++ b/README.md
@@ -149,7 +149,7 @@ If autotagging is enabled, all created or updated contacts will be automatically
 Merge fields are key value pairs that can be set on each contact. They can be customized for each audience. Common examples of merge fields are first name, last name, and phone number.
 The value of a merge field can be set and updated from the SDK. Merge fields are keyed off of a capitalized string. The Key does not include vertical bars on either end (ex. FNAME and not |FNAME|).
 
-Note: Merge Fields can be marked as required on the audience settings. If you attempt to create a contact without setting the required merge fields, the request will silently fail.
+While Merge Fields can be marked as required on the audience settings, those requirements will not be enforced when using the Mailchimp SDK.
 
 #### String Merge Fields
 The majority of merge field types are represented as a String. This includes Text, Number, Radio Buttons, Drop Downs, Dates, Birthday, Phone Numbers, and Websites.