fix: broken links to Terraform documentation (#313)

Co-authored-by: Christian Lechner <[email protected]>

Author: lechnerc77

released/dsag/betriebstag2024/exercises/EXERCISE2/README.md

@@ -231,7 +231,7 @@ After the application you will find a new file called `terraform.tfstate` in you
 <img width="200px" src="assets/ex2_5.png" alt="terraform state in the file system">
 
 > [!IMPORTANT]
-> In real life you would not store this file locally but use a [remote backend](https://developer.hashicorp.com/terraform/language/settings/backends/configuration) that is capable of storing the state in a secure and consistent way. For the purpose of this exercise we will use the local backend.
+> In real life you would not store this file locally but use a [remote backend](https://developer.hashicorp.com/terraform/language/backend) that is capable of storing the state in a secure and consistent way. For the purpose of this exercise we will use the local backend.
 
 > [!NOTE]
 > In case you are getting an error that the subdomain already exists, you need change the project name in the `variables.tf` file.
@@ -251,6 +251,6 @@ Here you find additional information on the used Terraform features and function
 
 ## Summary
 
-You've now successfully created a subaccount.  
+You've now successfully created a subaccount.
 
 Continue to - [Exercise 3 - Assignment of subaccount emergency administrators](../EXERCISE3/README.md).

released/terraform-be/README.md

@@ -1,6 +1,6 @@
 # Terraform Remote Backend Configuration
 
-In Terraform, a *backend* determines where the state data files are stored. This state data is crucial for tracking the resources managed by Terraform. There are different configuration options to define these backends. They are described in the [Terraform documentation](https://developer.hashicorp.com/terraform/language/settings/backends/configuration).
+In Terraform, a *backend* determines where the state data files are stored. This state data is crucial for tracking the resources managed by Terraform. There are different configuration options to define these backends. They are described in the [Terraform documentation](https://developer.hashicorp.com/terraform/language/backend).
 
 The default configuration is the [local backend](https://developer.hashicorp.com/terraform/language/settings/backends/local) namely the local file system. However, this is not recommended for productive usage due to the lack of options to collaborate and securely store the state. Hence, it is common to use a remote backend.
 
@@ -18,4 +18,4 @@ As mentioned the default backend stores state as a local file on disk. It is sui
 
 ### Kubernetes Backend
 
-The [Kubernetes backend](https://developer.hashicorp.com/terraform/language/settings/backends/kubernetes) stores state in a Kubernetes secret and supports state locking using a Lease resource. It allows for secure and collaborative state management in Kubernetes environments. You find a sample technical setup in the directory [k8sasbackend](./k8sasbackend/README.md)
+The [Kubernetes backend](https://developer.hashicorp.com/terraform/language/settings/backends/kubernetes) stores state in a Kubernetes secret and supports state locking using a Lease resource. It allows for secure and collaborative state management in Kubernetes environments. You find a sample technical setup in the directory [k8sasbackend](./k8sasbackend/README.md)