Backstage Integrations Upgrade for Terraform with TOFU - Doc Updates (#…

…268)

Signed-off-by: Elamaran Shanmugam <[email protected]>

examples/terraform-integrations/README.md

@@ -2,7 +2,7 @@
 
 `idpBuilder` is now experimentally extensible to launch custom terraform patterns using package extensions. This is an experimental effort allowing the users of the `idpBuilder` to run terraform modules using the tooling in place.
 
-Please use the below command to deploy an IDP reference implementation with an Argo application for terraform integrations with few sample patterns we have built:
+Please use the below command to deploy an IDP reference implementation with an Argo application for preparing up the setup for terraform integrations:
 
 ```bash
 idpbuilder create \
@@ -14,5 +14,4 @@ idpbuilder create \
 As you see above, this add-on to `idpbuilder` has a dependency to the [reference implementation](../ref-implementation/). This command primarily does the following:
 
 1. Installs `fluxcd` source repository controller as an `argo` application.
-2. Installs `tofu-controller` for managing the lifecycle of terraform deployments from your Kubernetes cluster for operations such as create, delete and update.
-3. Finally, this stack add-on goes together with the work done under [backstage-terraform-integrations](https://github.com/cnoe-io/backstage-terraform-integrations/). Once the add-on is enabled, the user will need to follow the setup discussed in the [backstage-terraform-integrations](https://github.com/cnoe-io/backstage-terraform-integrations/) repo for the remainder of the configuration, and terraform integrations should work.
+2. Installs `tofu-controller` for managing the lifecycle of terraform deployments from your Kubernetes cluster for operations such as create, delete and update.