wip

Author: kmoe

docs/design/plan-modification.md

@@ -37,7 +37,7 @@ The `PlanResourceChange` RPC response also contains a list of attribute paths: `
 
 In allowing providers to control the `PlanResourceChange` response, i.e. "modify the plan", the plugin framework therefore enables providers not only to modify the diff that will be displayed to the user (and ultimately applied), but also to branch into a destroy-and-create lifecycle phase, triggering other RPCs.
 
-Plan modification has two distinct use cases for providers:
+Plan modification currently has two distinct use cases for providers:
   - Modifying plan values, and
   - Forcing resource replacement.
 
@@ -338,6 +338,8 @@ type ModifyAttributePlanResponse struct {
 }
 ```
 
+This approach directly offers documentation hooks, so that plan modification behaviours can be documented alongside their definition and included in generated schema docs.
+
 In this case, `RequiresReplace` and `RequiresReplaceIf` can be implemented as `AttributePlanModifier`s, e.g.: