update readme file

Author: uolter

README.md

@@ -5,7 +5,7 @@ Template useful to create a AWS infrastructures with terraform
 ## Howo to use this template
 
 1. Create your github repository starting form this template.
-2. Configure your aws cli and set the [credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html). Also refer the conflunece page to work with [AWS SSO](https://pagopa.atlassian.net/wiki/spaces/DEVOPS/pages/466846955/AWS+-+Users+groups+and+roles#SSO-with-GSuite).
+2. Configure your aws cli and set the [credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html). Also refer the confluence page to work with [AWS SSO](https://pagopa.atlassian.net/wiki/spaces/DEVOPS/pages/466846955/AWS+-+Users+groups+and+roles#SSO-with-GSuite).
 3. The __src/init__ directory contains the terraform code to setup the S3 backend, the Dynamodb lock table, github openid connection and the iam role to use in the github actions
 4. The __src/main__ directory cointains the terraform code to setup the core infrastructure.
 5. The __.github/workflows__ directory contains two yaml files to run a terraform plan and apply actions. They need a github environment secret to be created: IAM_ROLE (see below.)
@@ -47,19 +47,22 @@ cd src/main
 
 In the repository two github actions are already provided:
 
-* **terraform-plan**: it runs every time a new Pull request(PR) is created and every time a push is made within the PR branch. It runs terraform plan through all the environments.
+* **terraform-plan**: it runs every time new code is pushed in every branch excluded main and master. It runs terraform plan through all the environments in parallel.
+
+* **terraform-apply**: it run terraform apply in all the environments once a PR is merged with main.
+  * The apply in PROD should require an approval: it depends on the Environment protection rules.
+  * It can also be triggerd manually in all the environment expect main.
 
-* **terraform-apply**: it runs terraform apply in one of the environment (uat by default) every time a PR is merged into main branch or it can be triggered manually and users have the facolty to choose on which environment to apply it.
 
 ### Configurations
 
-* Create [github environment](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment) every environments:dev, uat, prod, and prod_w.
+* Create [github environment](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment) for every environments:dev, uat, prod, and prod_w.
 * **prod_w** is like prod but it is meant to be used only in the apply action in production. 
 
 ![](docs/github-environments.png)
 
-* In each environmen create a secret named **IAM_ROLE** and set as a value the **arn** of the role created at the very beginnig when you set up the environment (init).
-* Within the **prod_w** set two **Environment protection rules* as shown in the screenshot above:
+* In each environment create a secret named **IAM_ROLE** and set its value with the **arn** of the role created at the very beginnig (init).
+* Within the **prod_w** set two **Environment protection rules* as shown in the screenshot below:
 ![](docs/protection-rules-and-secrets.png)