From 9c1092739673a1ea12b440557da5eb2f4ce98738 Mon Sep 17 00:00:00 2001
From: Erich <erichbschulz@gmail.com>
Date: Thu, 26 Jan 2017 12:30:46 +1000
Subject: [PATCH] edit in response to feedback from Eileen!

---
 docs/core/architecture.md | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/docs/core/architecture.md b/docs/core/architecture.md
index c4504672..8f8bf96f 100644
--- a/docs/core/architecture.md
+++ b/docs/core/architecture.md
@@ -107,11 +107,8 @@ activity is created, or create activities and populating custom fields when a
 pledge is created.
 
 !!! note
-    BAOs typically have both `add()` and `create()` methods. The `add()` method
-    just creates the database record with the DAO `save()` method whereas 'create()' calls
-    subsidiary functions such as creating activities & populating custom fields.
-    The APIs call 'Create' which then calls 'Add' as well as other associated
-    functions.
+    Historically some BAOs had both `add()` and `create()` methods. Current practice 
+    is to favour a single `create()` method.
 
 ### Form
 In general each form page in CiviCRM maps to a file in one of
-- 
GitLab