From 16b7541277f8c6464ba89df615d5f76f8aa01536 Mon Sep 17 00:00:00 2001 From: James Bardin Date: Wed, 1 Jul 2020 16:10:02 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Alisdair McDiarmid --- docs/destroying.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/destroying.md b/docs/destroying.md index 41babe974..8b6ede5ee 100644 --- a/docs/destroying.md +++ b/docs/destroying.md @@ -259,7 +259,7 @@ In order to resolve these cycles, and all resources that precede a resource with `create_before_destroy` must in turn be handled in the same manner. Reversing the incoming edged to `A destroy` resolves the problem: -![Correct create_before_destroy replacement](./images/replace_cbd_all.png) +![Correct create_before_destroy replacement](./images/replace_all_cbd.png) -This also demonstrates why `create_before_destry` cannot be overridden when +This also demonstrates why `create_before_destroy` cannot be overridden when it is inherited; changing the behaviour here isn't possible without removing the initial reason for `create_before_destroy`; otherwise cycles are always introduced into the graph.