@@ -1171,8 +1171,6 @@ export class Stack extends Construct implements ITaggable {
1171
1171
* remove the reference from the consuming stack. After that, you can remove
1172
1172
* the resource and the manual export.
1173
1173
*
1174
- * ## Example
1175
- *
1176
1174
* Here is how the process works. Let's say there are two stacks,
1177
1175
* `producerStack` and `consumerStack`, and `producerStack` has a bucket
1178
1176
* called `bucket`, which is referenced by `consumerStack` (perhaps because
@@ -1183,7 +1181,7 @@ export class Stack extends Construct implements ITaggable {
1183
1181
*
1184
1182
* Instead, the process takes two deployments:
1185
1183
*
1186
- * ### Deployment 1: break the relationship
1184
+ * ** Deployment 1: break the relationship**:
1187
1185
*
1188
1186
* - Make sure `consumerStack` no longer references `bucket.bucketName` (maybe the consumer
1189
1187
* stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just
@@ -1193,7 +1191,7 @@ export class Stack extends Construct implements ITaggable {
1193
1191
* between the two stacks is being broken.
1194
1192
* - Deploy (this will effectively only change the `consumerStack`, but it's safe to deploy both).
1195
1193
*
1196
- * ### Deployment 2: remove the bucket resource
1194
+ * ** Deployment 2: remove the bucket resource**:
1197
1195
*
1198
1196
* - You are now free to remove the `bucket` resource from `producerStack`.
1199
1197
* - Don't forget to remove the `exportValue()` call as well.
0 commit comments