docs: fix typos

Author: lechnerc77

.wordlist.txt

@@ -1,23 +1,32 @@
-APIs
+API
+api
 autocompletion
 APIs
 backend
 Backend
 breakpoint
 BTP
 btp
+carte
 CLA
 CLI
 CLIs
+cloudfoundry
+Cloudfoundry
 CodeQL
 config
 Copilot
+costcenter
+Costcenter
 customizations
 DCO
 dependabot
+Dev
+dev
 devcontainer
 devcontainers
 dir
+EMEA
 faq
 Github
 github
@@ -32,8 +41,11 @@ JSON
 js
 JS
 jq
+Kyma
 macOS
 md
+namings
+Namings
 NextSteps
 OAuth
 OpenSSF
@@ -70,6 +82,12 @@ TOML
 toolchain
 UIs
 UI
+Unmanaged
+unmanaged
+URL
+url
+uuid
+UUID
 VS
 workspace
 workspaces

sample-setups/README.md

@@ -2,7 +2,7 @@
 
 ## Paradigms
 
-We follow the paradigms of a simpel and clear Terraform configuration as laid out in the [Simple, Clear, Maintainable](https://rosesecurity.dev/blog/2024/11/24/terraform-proverbs) blog post of the [Development Log](https://rosesecurity.dev/) especially:
+We follow the paradigms of a simple and clear Terraform configuration as laid out in the [Simple, Clear, Maintainable](https://rosesecurity.dev/blog/2024/11/24/terraform-proverbs) blog post of the [Development Log](https://rosesecurity.dev/) especially:
 
 - Clear is better than clever.
 - Modules should be reusable, not rigid.
@@ -15,9 +15,9 @@ We follow the paradigms of a simpel and clear Terraform configuration as laid ou
 
 ## Naming Conventions and Tagging
 
-Ensuring naming conventions is one import aspect when provisioing and managing your SAP BTP account. We will align our samples in accordance to the [Naming Conventions for SAP BTP Accounts](https://help.sap.com/docs/btp/btp-admin-guide/naming-conventions-for-sap-btp-accounts).
+Ensuring naming conventions is one import aspect when provisioning and managing your SAP BTP account. We will align our samples in accordance to the [Naming Conventions for SAP BTP Accounts](https://help.sap.com/docs/btp/btp-admin-guide/naming-conventions-for-sap-btp-accounts).
 
-To ensure consistent naming of your resources, we encapsulate the guidlines in dedicated module. Besides the naming we will also include the labels that can be attached to some resources on SAP BTP.
+To ensure consistent naming of your resources, we encapsulate the guidelines in dedicated module. Besides the naming we will also include the labels that can be attached to some resources on SAP BTP.
 
 We have created one module for the level of the [directory](./modules/sap-btp-naming-conventions-directory/README.md) and one for the level of the [subaccount](./modules/sap-btp-naming-conventions-subaccount/README.md).
 

sample-setups/basic-setup/directory-setup/README.md

@@ -2,12 +2,12 @@
 
 ## Assumptions
 
-- We assume that we use the directories as structuring element for the subaccounts i.e., un an unmanaged fashion.
+- We assume that we use the directories as structuring element for the subaccounts i.e., in an unmanaged fashion.
 - We assume that we do the directory setup in one run for all involved departments.
 
 ## Design Decisions
 
-We decouple the directory creation i.e., the setup of the basic structure from the creation of the operational units namely the subaccounts inside of the directories. The changes on directory level are probably a rare sceanrio compared to changes in the subaccounts additionally depending on their stage. We want to avoid side effects as well as lengthy state refreshes and keep the state of the directories seperate.
+We decouple the directory creation i.e., the setup of the basic structure from the creation of the operational units namely the subaccounts inside of the directories. The changes on directory level are probably a rare scenario compared to changes in the subaccounts additionally depending on their stage. We want to avoid side effects as well as lengthy state refreshes and keep the state of the directories separate.
 
 ## Directory Setup
 

sample-setups/basic-setup/subaccount-setup/README.md

@@ -2,29 +2,29 @@
 
 ## Assumptions
 
-- We assume a bsaic setup of a subaccount is executed by the platform team/ SAP BTP administrator team
-- We assume that the responsibility of the platform team is restricted to a basic setup of a subacount leaving out app subscriptions and service instance creation.
+- We assume a basic setup of a subaccount is executed by the platform team/ SAP BTP administrator team
+- We assume that the responsibility of the platform team is restricted to a basic setup of a subaccount leaving out app subscriptions and service instance creation.
 
-## Design Decsions
+## Design Decisions
 
-To keep the Terraform state files clearly seperated the setup is done per subaccount i.e. per stage.
+To keep the Terraform state files clearly separated the setup is done per subaccount i.e. per stage.
 
 ## Subaccount Setup
 
 The setup of the subaccount comprises:
 
-- The setup of a subaccount in accordance to the naming conventions and labeling startegy of the company
+- The setup of a subaccount in accordance to the naming conventions and labeling strategy of the company
 - The trust configuration to a custom IdP is configured by default.
 - Default entitlements are added depending on the stage. In addition the requesting team can add additional project specific entitlements ("à la carte entitlements")
 - Optionally a Cloud Foundry Environment is created
 
 ### Naming Conventions and Labels
 
-The naming conventions and labels are centralized in the module [sap-btp-naming-conventions-subaccount](../../modules/sap-btp-naming-conventions-subaccount/README.md). The names and labels are drived based on input variables defined in the [variables.tf](./variables.tf) file.
+The naming conventions and labels are centralized in the module [sap-btp-naming-conventions-subaccount](../../modules/sap-btp-naming-conventions-subaccount/README.md). The names and labels are derived based on input variables defined in the [variables.tf](./variables.tf) file.
 
 ### Validations for Geographies and BTP Regions
 
-According to the SAP BTP Administrators Guide one part of the naming is the geographical region. To ensure that this region fits to the subaccount region, a validation is implemented in the [variables.tf](./variables.tf) file. The validation checks if the region of the subaccount is part of the geographical region. The geographical regions are defined in a local variable sdefined in the [main.tf](main.tf) file.
+According to the SAP BTP Administrators Guide one part of the naming is the geographical region. To ensure that this region fits to the subaccount region, a validation is implemented in the [variables.tf](./variables.tf) file. The validation checks if the region of the subaccount is part of the geographical region. The geographical regions are defined in a local variables defined in the [main.tf](main.tf) file.
 
 ### Setup of Entitlements
 

sample-setups/modules/sap-btp-environment/CloudFoundry/README.md

@@ -1,6 +1,6 @@
 # SAP BTP - Environment Setup
 
-This module encapsulates the creation of a Cloud Foundry environment in a subaccounton SAP BTP.
+This module encapsulates the creation of a Cloud Foundry environment in a subaccount on SAP BTP.
 
 ## Requirements