APIv4 - Update contact type api comment

diff --git a/Civi/Api4/Household.php b/Civi/Api4/Household.php
index 3807d0c289408f623d9a77c321219ec6e00b69c7..260cc8852d208978a98dd8bf7c9542e9a0ca7664 100644 (file)
--- a/Civi/Api4/Household.php
+++ b/Civi/Api4/Household.php
@@ -14,7 +14,7 @@ namespace Civi\Api4;
  * Contacts of type Household.
  *
  * This api is a facade for the Contact entity.
- * In most ways it acts exactly like the Contact entity, but will inject [contact_type => Individual]
+ * In most ways it acts exactly like the Contact entity, plus it injects [contact_type => Household]
  * into get, create, and batch actions (however, when updating or deleting a single Contact by id,
  * this will transparently pass-through to the Contact entity, so don't rely on this facade to enforce
  * contact type for single-record-by-id write operations).

diff --git a/Civi/Api4/Individual.php b/Civi/Api4/Individual.php
index f72f8cde8702f62d4ad9a311050eac574e36d753..9b701ef93611fdf4d6afa8a8b7fa5cdecac221fc 100644 (file)
--- a/Civi/Api4/Individual.php
+++ b/Civi/Api4/Individual.php
@@ -14,7 +14,7 @@ namespace Civi\Api4;
  * Contacts of type Individual.
  *
  * This api is a facade for the Contact entity.
- * In most ways it acts exactly like the Contact entity, but will inject [contact_type => Individual]
+ * In most ways it acts exactly like the Contact entity, plus it injects [contact_type => Individual]
  * into get, create, and batch actions (however, when updating or deleting a single Contact by id,
  * this will transparently pass-through to the Contact entity, so don't rely on this facade to enforce
  * contact type for single-record-by-id write operations).

diff --git a/Civi/Api4/Organization.php b/Civi/Api4/Organization.php
index 6b1e9a06ce1de5ae9c16f5414bd552ae9799aa2b..76c664e73bdc3f01efa318e0fb61338a432f359b 100644 (file)
--- a/Civi/Api4/Organization.php
+++ b/Civi/Api4/Organization.php
@@ -14,7 +14,7 @@ namespace Civi\Api4;
  * Contacts of type Organization.
  *
  * This api is a facade for the Contact entity.
- * In most ways it acts exactly like the Contact entity, but will inject [contact_type => Organization]
+ * In most ways it acts exactly like the Contact entity, plus it injects [contact_type => Organization]
  * into get, create, and batch actions (however, when updating or deleting a single Contact by id,
  * this will transparently pass-through to the Contact entity, so don't rely on this facade to enforce
  * contact type for single-record-by-id write operations).