docs generation

port-labs · Jan 22, 2024 · 5b3f283 · 5b3f283
1 parent d69e61e
commit 5b3f283
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/resources/port_blueprint.md b/docs/resources/port_blueprint.md
@@ -98,9 +98,9 @@ description: |-
   }
   ```
   Force Deleting a Blueprint
-  There could be cases where a blueprint will be managed by Terraform, but entities will get created from other sources such as the PORT UI or different integrations.
-  In this case, when trying to delete the blueprint, Terraform will fail because it will try to delete the entities that were created outside of Terraform.
-  To overcome this behavior, you can set the environment variable PORT_FORCE_DELETE_ENTITIES to true.
+  There could be cases where a blueprint will be managed by Terraform, but entities will get created from other sources (e.g. Port UI, API or other supported integrations).
+  In this case, when trying to delete the blueprint, Terraform will fail because it will try to delete the blueprint without deleting the entities first as they are not managed by Terraform.
+  To overcome this behavior, you can set the environment variable PORT_FORCE_DELETE_ENTITIES=true.
   This will trigger a migration that will delete all the entities in the blueprint and then delete the blueprint itself.
 ---
 
@@ -219,10 +219,10 @@ resource "port_blueprint" "microservice" {
 
 ## Force Deleting a Blueprint
 
-There could be cases where a blueprint will be managed by Terraform, but entities will get created from other sources such as the PORT UI or different integrations.
-In this case, when trying to delete the blueprint, Terraform will fail because it will try to delete the entities that were created outside of Terraform.
+There could be cases where a blueprint will be managed by Terraform, but entities will get created from other sources (e.g. Port UI, API or other supported integrations).
+In this case, when trying to delete the blueprint, Terraform will fail because it will try to delete the blueprint without deleting the entities first as they are not managed by Terraform.
 
-To overcome this behavior, you can set the environment variable `PORT_FORCE_DELETE_ENTITIES` to `true`. 
+To overcome this behavior, you can set the environment variable `PORT_FORCE_DELETE_ENTITIES=true`. 
 This will trigger a migration that will delete all the entities in the blueprint and then delete the blueprint itself.