docs: update

Author: lechnerc77

assets/base-directory-output.png

@@ -5,7 +5,7 @@
 - We assume that we use the directories as structuring element for the subaccounts i.e., un an unmanaged fashion.
 - We assume that we do the directory setup in one run for all involved departments.
 
-## Design Decsions
+## 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.
 
@@ -22,4 +22,10 @@ This is input data is reflected by the variables defined in the [variables.tf](.
 
 The directories are provisioned via the [main.tf](./main.tf) file which delegates to the module [base-directory-setup](../../modules/base-directory-setup/README.md). This module combines the corresponding module containing the naming and labeling conventions for a directory and calls the Terraform resource [btp_directory](https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory).
 
-After provisioning the output summarizes the executed setup as given by the [outputs.tf](./outputs.tf) file.
+After provisioning the output summarizes the executed setup as given by the [outputs.tf](./outputs.tf) file. Here is an example how the output could look like:
+
+![Sample Output for a directory](../../../assets/base-directory-output.png)
+
+## SAP BTP Administrator's Guide - References
+
+- [Naming and Directory Templates](https://help.sap.com/docs/btp/btp-admin-guide/naming-directory-templates)

sample-setup/README.md renamed to sample-setups/README.md

@@ -35,6 +35,8 @@ The setup of entitlements is split into two parts:
 
 The configuration merges the two files and adds the entitlements to the subaccount.
 
+To ease the provisioning of entitlements we use the Terraform community module [SAP BTP Entitlements Management with Terraform Module: sap-btp-entitlements](https://registry.terraform.io/modules/aydin-ozcan/sap-btp-entitlements/btp/latest).
+
 ### Setup of Cloud Foundry Environment
 
 The setup of a Cloud Foundry environment is optional. The caller can decide if a Cloud Foundry environment is required or not e.g. when setting up a shared subaccount. The boolean variable is `provision_cf_environment` in the [variables.tf](./variables.tf) file.
@@ -47,3 +49,12 @@ The output defined in the [outputs.tf](./outputs.tf) file returns the main infor
 - a link to the subaccount
 - The ID of the Cloud Foundry org
 - The API endpoint of the Cloud Foundry environment
+
+
+
+## SAP BTP Administrator's Guide - References
+
+- [Setting Up Your Account Model](https://help.sap.com/docs/btp/btp-admin-guide/setting-up-your-account-model)
+- [Naming and Directory Templates](https://help.sap.com/docs/btp/btp-admin-guide/naming-directory-templates)
+- [Setting Up Authentication](https://help.sap.com/docs/btp/btp-admin-guide/setting-up-authentication)
+- [Cloud Foundry, Kyma, or Both?](https://help.sap.com/docs/btp/btp-admin-guide/cloudfoundry-kyma-or-both)