Update additional UI references and implementation type descriptions

Co-authored-by: JohannesRudolph <[email protected]>

Author: Copilot

docs/meshstack.how-to.get-started-building-blocks.md

@@ -60,15 +60,15 @@ A Building Block is created to operate on one or several Platforms. This selecti
 
 How often can the same Building Block be allocated to a particular project? Choose "One" for a single assignment, or "Multiple" for more than one.
 
-#### Terraform vs manual
+#### OpenTofu vs manual
 
-The building block definition has two implementation types: Terraform and manual. Using Terraform, the building block can automatically provision the infrastructure resources. This gives engineers and DevOps the ability to use the full power of IaC (Infrastructure as Code) to create self-service products available in the Marketplace.
+The building block definition has two implementation types: OpenTofu and manual. Using OpenTofu, the building block can automatically provision the infrastructure resources. This gives engineers and DevOps the ability to use the full power of IaC (Infrastructure as Code) to create self-service products available in the Marketplace.
 
 Manual implementation is beneficial when the Building Block provider wants to gather end-user information (through inputs) and process it outside of meshStack.
 
 #### Git repository authentication
 
-When the implementation type is configured as Terraform, meshStack offers two methods for retrieving your code from a remote Git repository of your choice:
+When the implementation type is configured as OpenTofu, meshStack offers two methods for retrieving your code from a remote Git repository of your choice:
 
 - HTTPS
 - SSH using deploy keys
@@ -271,7 +271,7 @@ The diagram illustrates the lifecycle of a Building Block definition. It indicat
 
 ## Execution logs
 
-Building Blocks with "Terraform" as the implementation type produce logs when they are added to a project by an end-user. These logs provide details on the resources provisioned or any errors if the execution is unsuccessful. Both Admins and owners of the Building Block definitions can access these logs. As an Admin, you can view them by going to the Admin Area, proceeding to "Marketplace > Building Block overview," and choosing the desired Building Block from the list of executed instances. On the next screen, you will find one or more "Runs," depending on the number of times the user has executed this specific Building Block. By selecting a Run, you can inspect the associated Terraform logs.
+Building Blocks with "OpenTofu" as the implementation type produce logs when they are added to a project by an end-user. These logs provide details on the resources provisioned or any errors if the execution is unsuccessful. Both Admins and owners of the Building Block definitions can access these logs. As an Admin, you can view them by going to the Admin Area, proceeding to "Marketplace > Building Block overview," and choosing the desired Building Block from the list of executed instances. On the next screen, you will find one or more "Runs," depending on the number of times the user has executed this specific Building Block. By selecting a Run, you can inspect the associated OpenTofu logs.
 
 The owner of the Building Block definition can access the logs by switching to “Platform Builder” view and navigating to "Building Blocks > Overview".
 

docs/new-guide-how-to-provide-your-own-platform.md

@@ -6,14 +6,14 @@ title: How to Provide Your Own Platform
 :::note What is this guide about?
 This guide will show you how to offer your own platform to application teams using meshStack and terraform. This enables you to provide platforms in an easy fashion including cost management, lifecycle management, self-service provisioning and enforce a compliant level of security and governance.
 
-Please be aware that you can also integrate your own platforms using other types of building blocks e.g. GitHub action or GitLab CI. This guide focuses on the Terraform implementation as it is the most common way to integrate platforms into meshStack.
+Please be aware that you can also integrate your own platforms using other types of building blocks e.g. GitHub action or GitLab CI. This guide focuses on the OpenTofu implementation as it is the most common way to integrate platforms into meshStack.
 
 :::
 
 On a high level, you need the following and your platform integration is done:
 
 1. Create a platform with its own name and icon.
-2. Create a Building Block that does the automation in the background using Terraform
+2. Create a Building Block that does the automation in the background using OpenTofu
 3. Create a Landing Zone that does the roll out of the Building Block.
 
 ## Prerequisites
@@ -46,7 +46,7 @@ Make sure to configure the following details:
 
 - Supported Platform: select the platform type you created in the previous step.
 - How often assigned: Once
-- Implementation Type: Terraform
+- Implementation Type: OpenTofu
 - OpenTofu Version: enter what version you used to write the OpenTofu
 - Git Repository URL: point this to the Git repository where your Terraform is
 - Git Repository Path: if your Terraform files are under a directory in the repository, enter that path here