X-Git-Url: https://vcs.fsf.org/?a=blobdiff_plain;f=ext%2Fafform%2Fdocs%2Fstyle.md;h=5b9fb38abd72bdcb2525d1d8bbe8cf7ad9f89a05;hb=7491380f1b3d0bd21e24438447943b094a600bf5;hp=30063d2f67407a5d239dd7338fbfe52ddfa260cf;hpb=797aca9341a4e8a34ea67308e0f02190f6fdf04c;p=civicrm-core.git

diff --git a/ext/afform/docs/style.md b/ext/afform/docs/style.md
index 30063d2f67..5b9fb38abd 100644
--- a/ext/afform/docs/style.md
+++ b/ext/afform/docs/style.md
@@ -4,10 +4,10 @@
 
 The following naming conventions apply to directives defined within `afform.git`:
 
-* Standalone directives (e.g. `afModelProp` or `afField`), including forms (e.g. `afHtmlEditor`)
+* Standalone directives (e.g. `afEntity` or `afField`), including forms (e.g. `afHtmlEditor`)
     * The directive name must begin with the `af` prefix.
     * Supplemental attributes SHOULD NOT begin with the `af` prefix.
-    * Example: `<af-model-prop type="Activity" name="myPhoneCall">`
+    * Example: `<af-entity type="Activity" name="myPhoneCall">`
 
 * Mix-in directives (e.g. `afMonaco` or `afApi4Action`)
     * The directive name must begin with the `af` prefix.
@@ -18,7 +18,7 @@ __Discussion__: These differ in two ways:
 
 * Namespacing
     * Standalone directives form an implicit namespace.
-      (*Anything passed to `<af-model-prop>` is implicitly about `af-model-prop`.)
+      (*Anything passed to `<af-entity>` is implicitly about `af-entity`.)
     * Mix-in directives must share a namespace with other potential mix-ins.
       (*The *)
 * Directive arguments