diff --git a/blueprints/serverless/cloud-run-explore/README.md b/blueprints/serverless/cloud-run-explore/README.md
index 2df7fcdb9..417e9d2f8 100644
--- a/blueprints/serverless/cloud-run-explore/README.md
+++ b/blueprints/serverless/cloud-run-explore/README.md
@@ -44,11 +44,11 @@ You should see this README and some terraform files.
 
 3. To deploy a specific use case, you will need to create a file in this directory called `terraform.tfvars` and follow the corresponding instructions to set variables. Sometimes values that are meant to be substituted will be shown inside brackets but you need to omit these brackets. E.g.:
 ```tfvars
-project_id = [your-project_id]
+project_id = "[your-project_id]"
 ```
 may become
 ```tfvars
-project_id = spiritual-hour-331417
+project_id = "spiritual-hour-331417"
 ```
 
 Although each use case is somehow built around the previous one they are self-contained so you can deploy any of them at will.
@@ -71,11 +71,11 @@ This is the simplest case, the "Hello World" for Cloud Run. A Cloud Run service
 
 In this case the only variable that you need to set in `terraform.tfvars` is the project ID:
 ```tfvars
-project_id = [your-project-id]
+project_id = "[your-project-id]"
 ```
 Alternatively you can pass this value on the command line:
 ```bash
-terraform apply -var project_id=[your-project-id]
+terraform apply -var project_id="[your-project-id]"
 ```
 
 The default URL is automatically created and shown as a terraform output variable. It will be similar to the one shown in the picture above. Now use your browser to visit it, you should see the following:
@@ -89,7 +89,7 @@ If you want to use your own custom domain you need a GCLB in front of your Cloud
 
 The following values will need to be set in `terraform.tfvars`, replacing the custom_domain value with your own domain:
 ```tfvars
-project_id    = [your-project-id]
+project_id    = "[your-project-id]"
 custom_domain = "cloud-run-explore.example.org"
 ```
 Since it is an HTTPS connection a Google managed certificate is created, but for it to be provisioned correctly you will need to point to the load balancer IP address with an A DNS record at your registrar: [Use Google-managed SSL certificates | Load Balancing](https://cloud.google.com/load-balancing/docs/ssl-certificates/google-managed-certs#update-dns). The LB IP is shown as a terraform output.
@@ -103,7 +103,7 @@ To block access to the default URL, you can configure Ingress Settings so that I
 
 You only need to set one more value in the previous `terraform.tfvars` file:
 ```tfvars
-project_id       = [your-project-id]
+project_id       = "[your-project-id]"
 custom_domain    = "cloud-run-explore.example.org"
 ingress_settings = "internal-and-cloud-load-balancing"
 ```
@@ -117,7 +117,7 @@ To use Cloud Armor to protect the Cloud Run service, you need to create a securi
 
 The code allows to block a list of IPs and a specific URL path. For example, you may want to block access to a login page to external users. To test its behavior, by default all IPs and the path `"/login.html"` are blocked, but you can override any of these settings with your own values:
 ```tfvars
-project_id       = [your-project-id]
+project_id       = "[your-project-id]"
 custom_domain    = "cloud-run-explore.example.org"
 ingress_settings = "internal-and-cloud-load-balancing"
 security_policy = {
@@ -135,7 +135,7 @@ You can enable IAP at the load balancer to control access using identity and con
 Use your own email as identity to access the Cloud Run service:
 
 ```tfvars
-project_id       = [your-project-id]
+project_id       = "[your-project-id]"
 custom_domain    = "cloud-run-explore.example.org"
 ingress_settings = "internal-and-cloud-load-balancing"
 security_policy = {