Change docs reference

Author: rambleraptor

docs/rules/0131/request-path-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Get methods: Field behavior
 
 This rule enforces that all `Get` standard methods have
-`aep.api.field_behavior` set to `REQUIRED` on their `string path` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string path` field, as
 mandated in [AEP-131][].
 
 ## Details
 
 This rule looks at any message matching `Get*Request` and complains if the
 `path` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0132/request-parent-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # List methods: Field behavior
 
 This rule enforces that all `List` standard methods have
-`aep.api.field_behavior` set to `REQUIRED` on their `string parent` field,
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string parent` field,
 as mandated in [AEP-132][].
 
 ## Details
 
 This rule looks at any message matching `List*Request` and complains if the
 `parent` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0133/request-parent-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Create methods: Field behavior
 
 This rule enforces that all `Create` standard methods have
-`aep.api.field_behavior` set to `REQUIRED` on their `string parent` field,
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string parent` field,
 as mandated in [AEP-133][].
 
 ## Details
 
 This rule looks at any message matching `Create*Request` and complains if the
 `parent` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0133/request-resource-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Create methods: Field behavior
 
 This rule enforces that all `Create` standard methods have
-`aep.api.field_behavior` set to `REQUIRED` on the field representing the
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on the field representing the
 resource, as mandated in [AEP-133][].
 
 ## Details
 
 This rule looks at any message matching `Create*Request` and complains if the
 resource field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0135/request-path-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Delete methods: Field behavior
 
 This rule enforces that all `Delete` standard methods have
-`aep.api.field_behavior` set to `REQUIRED` on their `string path` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string path` field, as
 mandated in [AEP-135][].
 
 ## Details
 
 This rule looks at any message matching `Delete*Request` and complains if the
 `path` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0162/commit-request-name-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Commit requests: Name field behavior
 
 This rule enforces that all `Commit` requests have
-`aep.api.field_behavior` set to `REQUIRED` on their `string name` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string name` field, as
 mandated in [AEP-162][].
 
 ## Details
 
 This rule looks at any message matching `Commit*Request` and complains if the
 `name` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0162/delete-revision-request-name-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Delete Revision requests: Name field behavior
 
 This rule enforces that all Delete Revision requests have
-`aep.api.field_behavior` set to `REQUIRED` on their `string name` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string name` field, as
 mandated in [AEP-162][].
 
 ## Details
 
 This rule looks at any message matching `Delete*RevisionRequest` and complains if the
 `name` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0162/rollback-request-name-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Rollback requests: Name field behavior
 
 This rule enforces that all `Rollback` requests have
-`aep.api.field_behavior` set to `REQUIRED` on their `string name` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string name` field, as
 mandated in [AEP-162][].
 
 ## Details
 
 This rule looks at any message matching `Rollback*Request` and complains if the
 `name` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0162/rollback-request-revision-id-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Rollback requests: Revision ID field behavior
 
 This rule enforces that all `Rollback` requests have
-`aep.api.field_behavior` set to `REQUIRED` on their `string revision_id` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string revision_id` field, as
 mandated in [AEP-162][].
 
 ## Details
 
 This rule looks at any message matching `Rollback*Request` and complains if the
 `revision_id` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples
 

docs/rules/0162/tag-revision-request-name-behavior.md

@@ -12,14 +12,14 @@ redirect_from:
 # Tag Revision requests: Name field behavior
 
 This rule enforces that all Tag Revision requests have
-`aep.api.field_behavior` set to `REQUIRED` on their `string name` field, as
+`aep.api.field_behavior` set to `FIELD_BEHAVIOR_REQUIRED` on their `string name` field, as
 mandated in [AEP-162][].
 
 ## Details
 
 This rule looks at any message matching `Tag*RevisionRequest` and complains if the
 `name` field does not have a `aep.api.field_behavior` annotation with a
-value of `REQUIRED`.
+value of `FIELD_BEHAVIOR_REQUIRED`.
 
 ## Examples