Fix formatting inconsistencies in README, Terraform scripts, and example variables

README.md

@@ -1,4 +1,4 @@
-# Gemini Enterprise Agent Platform — Terraform Scaffold
+# Gemini Enterprise Agent Platform - Terraform Scaffold
 
 Provisions the infrastructure needed to use the Gemini Enterprise Agent Platform (Vertex AI Agent Engine) on an existing GCP project: required APIs, service accounts, and IAM bindings.
 
@@ -14,7 +14,7 @@ Provisions the infrastructure needed to use the Gemini Enterprise Agent Platform
 
 ```bash
 cp terraform.tfvars.example terraform.tfvars
-# edit terraform.tfvars — set your project_id
+# edit terraform.tfvars - set your project_id
 
 terraform init
 terraform plan
@@ -25,7 +25,7 @@ terraform apply
 
 | Name | Required | Default | Description |
 |---|---|---|---|
-| `project_id` | yes | — | Existing GCP project ID |
+| `project_id` | yes | - | Existing GCP project ID |
 | `prefix` | no | `gemini` | Short prefix applied to all resource names |
 
 ## Outputs
@@ -39,7 +39,7 @@ terraform apply
 ## What gets created
 
 - **7 GCP APIs** enabled (`aiplatform`, `cloudaicompanion`, `discoveryengine`, `dialogflow`, `secretmanager`, `iam`, `cloudresourcemanager`)
-- **2 service accounts** — one for app runtime, one for IDE enterprise config
+- **2 service accounts** - one for app runtime, one for IDE enterprise config
 - **4 project IAM bindings**
 
 ## Setting up credentials
@@ -51,7 +51,7 @@ gcloud auth application-default login
 gcloud config set project <your-project-id>
 ```
 
-For workloads running on GCP (Cloud Run, GKE, Compute Engine), attach the service account to the resource — no credentials file needed.
+For workloads running on GCP (Cloud Run, GKE, Compute Engine), attach the service account to the resource - no credentials file needed.
 
 ## Granting developer access to Gemini Code Assist
 
@@ -113,5 +113,5 @@ gcloud billing accounts list
 
 ## License
 
-[MIT](LICENSE) © 2026 Slawomir Koszewski
+[MIT](LICENSE) (c) 2026 Slawomir Koszewski