diff --git a/community/knowledge/data-modeling/transferfields-skip-type-mismatch-can-drop-data.md b/community/knowledge/data-modeling/transferfields-skip-type-mismatch-can-drop-data.md
index a2ebeb6..7d1ea77 100644
--- a/community/knowledge/data-modeling/transferfields-skip-type-mismatch-can-drop-data.md
+++ b/community/knowledge/data-modeling/transferfields-skip-type-mismatch-can-drop-data.md
@@ -17,10 +17,10 @@ application-area: [all]
 
 Use `TransferFields(Source)` only when every field the destination requires, including primary key fields, is guaranteed to share a matching field number and type with the source; this form defaults `InitPrimaryKeyFields` to `true`. Fields with no matching field number, and fields whose types differ across extensions, are skipped regardless of `SkipFieldsNotMatchingType` — that parameter only governs same-extension type mismatches. If the destination depends on a field that falls into either case, map and validate it explicitly in code rather than relying on `TransferFields` to catch the gap. Use `SkipFieldsNotMatchingType = true` only when skipping same-extension type mismatches is an intentional, documented part of the transfer contract.
 
+See sample: `transferfields-skip-type-mismatch-can-drop-data.good.al`.
+
 ## Anti Pattern
 
 Using `TransferFields(Source, InitPrimaryKeyFields, true)` as a generic way to make two evolving table schemas transfer without errors, when the destination depends on every required source field being copied. A type change on either table can turn a previously transferred field into a silently skipped one without making the transfer itself fail.
 
-See sample: `transferfields-skip-type-mismatch-can-drop-data.good.al`.
-
-See sample: `transferfields-skip-type-mismatch-can-drop-data.bad.al`.
+See sample: `transferfields-skip-type-mismatch-can-drop-data.bad.al`.
\ No newline at end of file