SAAS-23305: Updating README.md

Author: Noamstrauss

examples/dedicated-project/README.md

@@ -4,7 +4,7 @@
 
 ## Overview
 
-This example shows how to onboard a GCP project by creating a dedicated project to provision all of Aqua’s resources into and apply the required labels for Aqua Security integration.
+This example demonstrates how to onboard a GCP project by creating a dedicated project to provision all of Aqua’s resources into and apply the required labels for Aqua Security integration.
 
 ## Pre-requisites
 
@@ -16,15 +16,21 @@ Before running this example, ensure that you have the following:
 
 ## Usage
 
-1. Leverage the Aqua platform to generate the local variables required by the module.
+1. Obtain the Terraform configuration file generated by the Aqua Security UI.
 2. Important: Replace `<aqua_api_key>` and `<aqua_api_secret>` with your generated API credentials.
 3. Run `terraform init` to initialize the Terraform working directory.
 4. Run `terraform apply` to create the dedicated project.
 
 ## What's Happening
-1. The `aqua_gcp_dedicated_project` module is called to create a dedicated GCP project is created with the name `aqua-agentless-<tenant_id>-<org_hash>`, where `org_hash` is the first six characters of the SHA1 hash of your organization name.
+
+1. The `aqua_gcp_dedicated_project` module is called to create a dedicated GCP project with the name `aqua-agentless-<tenant_id>-<org_hash>`, where `org_hash` is the first six characters of the SHA1 hash of your organization name.
 2. The `aqua_gcp_onboarding` module is called to provision the necessary resources (service accounts, roles, networking, etc.) in the dedicated GCP project.
-3. The `aqua_gcp_project_attachment` module is called to create the required IAM resources in the onboarding project and trigger the Aqua API.
+3. The `aqua_gcp_project_attachment` module is called to create the required IAM resources in the existing project and trigger the Aqua API to onboard the project.
+
+
+## Outputs
+
+- `onboarding_status`: The output from the `aqua_gcp_project_attachment` module, displaying the result of the onboarding process.
 
 ## Cleanup
 

examples/same-project/README.md

@@ -4,7 +4,7 @@
 
 ## Overview
 
-This example shows how to onboard a Google Cloud Platform (GCP) project by provisioning all of Aqua’s resources into the existing project.
+This example demonstrates how to onboard an existing Google Cloud Platform (GCP) project to Aqua Security by provisioning all the necessary resources directly into the existing project, without creating a dedicated project.
 
 ## Prerequisites
 
@@ -16,15 +16,19 @@ Before running this example, ensure that you have the following:
 
 ## Usage
 
-1. Replace the placeholder values in the `locals` block with your actual values.
-2. Run `terraform init` to initialize the Terraform working directory.
-3. Run `terraform apply` to create the resources.
+1. Obtain the Terraform configuration file generated by the Aqua Security UI.
+2. Replace the placeholders `<aqua_api_key>` and `<aqua_api_secret>` with your actual Aqua Security API key and secret.
+3. Run `terraform init` to initialize the Terraform working directory.
+4. Run `terraform apply` to create the resources.
 
 ## What's Happening
 
-1. The `aqua_gcp_onboarding` module is called to provision the necessary resources (service accounts, roles, networking, etc.) in the existing GCP project.
-2. The `aqua_gcp_project_attachment` module is called to create the required IAM resources in the onboarding project and trigger the Aqua API.
+1. The `aqua_gcp_onboarding` module is called to provision the necessary resources (service accounts, roles, networking, etc.) directly in the existing GCP project.
+2. The `aqua_gcp_project_attachment` module is called to create the required IAM resources in the existing project and trigger the Aqua API to onboard the project.
 
+## Outputs
+
+- `onboarding_status`: The output from the `aqua_gcp_project_attachment` module, displaying the result of the onboarding process.
 
 ## Cleanup