Skip to content

Commit 377ef26

Browse files
committed
docs: review comments
1 parent 17069a2 commit 377ef26

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

sample-setups/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ We follow the paradigms of a simple and clear Terraform configuration as laid ou
1313
- Name with underscores, not dashes.
1414
- Using locals makes code descriptive and maintainable.
1515

16-
Another important paradigm is avoiding a monolithic Terraform state (*"Terralith"*). Hence, there is no single Terraform configuration for a complete SAP BTP account. Instead, we split the setup in configurations that are provisioned and managed separately.
16+
It's important to avoid a monolithic Terraform state (*"Terralith"*). Because of that, we don't provide a single Terraform configuration for a complete SAP BTP account. Instead, we split the setup in configurations that are provisioned and managed separately.
1717

1818
## Overview
1919

@@ -31,7 +31,7 @@ The folder `basic-setup/subaccount-setup` contains the setup of subaccounts. For
3131

3232
## Modules
3333

34-
We have created a set of modules to encapsulate the reusable parts of the setup. The modules are located in the folder `modules`. Each module has its own README file that describes the module and its usage.
34+
We have created a set of modules to encapsulate the reusable parts of the setup. You find the modules in the folder modules. Learn about the modules and their usage in their respective `README` files
3535

3636
### Naming Conventions and Labeling
3737

0 commit comments

Comments
 (0)