Merge pull request #238 from Adobe-Enterprise-Docs/kg-6-18-26

Keith Gluck · web-flow · commit 48f8b44b5e4a · 2026-06-18T11:15:57.000-07:00
fixed typo
diff --git a/help/marketo/product-docs/crm-sync/salesforce-sync/sfdc-sync-details/sfdc-sync-merging-a-lead-contact-person.md b/help/marketo/product-docs/crm-sync/salesforce-sync/sfdc-sync-details/sfdc-sync-merging-a-lead-contact-person.md
@@ -28,7 +28,7 @@ Sometimes it is best to just list the rules. Here we go:
 
 >[!NOTE]
 >
->The behavior of boolean fields in an API merge changed in the March '26 release. Now, a False value is treated correctly as having a value for that field. Only a null value is treated as "empty" when evaluating conflicting fields. See [this Community post](https://experienceleaguecommunities.adobe.com/adobe-marketo-engage-27/api-merge-functionality-for-boolean-fields-251219){target="_blank"} more details.
+>The behavior of boolean fields in an API merge changed in the March '26 release. Now, a False value is treated correctly as having a value for that field. Only a null value is treated as "empty" when evaluating conflicting fields. See [this Community post](https://experienceleaguecommunities.adobe.com/adobe-marketo-engage-27/api-merge-functionality-for-boolean-fields-251219){target="_blank"} for more details.
 
 >[!MORELIKETHIS]
 >

Original file line number	Diff line number	Diff line change
`@@ -28,7 +28,7 @@ Sometimes it is best to just list the rules. Here we go:`
`28`	`28`
`29`	`29`	`>[!NOTE]`
`30`	`30`	`>`
`31`		`->The behavior of boolean fields in an API merge changed in the March '26 release. Now, a False value is treated correctly as having a value for that field. Only a null value is treated as "empty" when evaluating conflicting fields. See [this Community post](https://experienceleaguecommunities.adobe.com/adobe-marketo-engage-27/api-merge-functionality-for-boolean-fields-251219){target="_blank"} more details.`
	`31`	`+>The behavior of boolean fields in an API merge changed in the March '26 release. Now, a False value is treated correctly as having a value for that field. Only a null value is treated as "empty" when evaluating conflicting fields. See [this Community post](https://experienceleaguecommunities.adobe.com/adobe-marketo-engage-27/api-merge-functionality-for-boolean-fields-251219){target="_blank"} for more details.`
`32`	`32`
`33`	`33`	`>[!MORELIKETHIS]`
`34`	`34`	`>`