docs: name cleanup

README.md

@@ -71,13 +71,13 @@ Use the [**Starter Deployment Template with GWLB**](examples/base_cc_gwlb) to de
 
 Use the [**Starter Deployment Template with GWLB**](examples/base_cc_gwlb_zpa) to deploy your Cloud Connectors in a new VPC and to load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. Route 53 endpoints redirect DNS resolver capability for ZPA.
 
-### **Starter Deployment Template with Auto Scaling groups (ASG) and Gateway Load Balancer (GWLB)**
+### **Starter Deployment Template with Auto Scaling and Gateway Load Balancer (GWLB)**
 
 Use the [**Starter Deployment Template with ASG and GWLB**](examples/base_cc_gwlb_asg) to deploy your Cloud Connectors in a new VPC and to load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. For added resiliency and elasticity, Cloud Connectors are deployed via a Launch Template configured Auto Scaling group.
 
-### **Starter Deployment Template with Auto Scaling groups (ASG), Gateway Load Balancer (GWLB) and ZPA**
+### **Starter Deployment Template with Auto Scaling, Gateway Load Balancer (GWLB) and ZPA**
 
-Use the [**Starter Deployment Template with ASG and GWLB**](examples/base_cc_gwlb_asg_zpa) to deploy your Cloud Connectors in a new VPC and to load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. For added resiliency and elasticity, Cloud Connectors are deployed via a Launch Template configured Auto Scaling group. Route 53 endpoints redirect DNS resolver capability for ZPA.
+Use the [**Starter Deployment Template with ASG, GWLB and ZPA**](examples/base_cc_gwlb_asg_zpa) to deploy your Cloud Connectors in a new VPC and to load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. For added resiliency and elasticity, Cloud Connectors are deployed via a Launch Template configured Auto Scaling group. Route 53 endpoints redirect DNS resolver capability for ZPA.
 
 ## **Brownfield Deployment**
 
@@ -88,6 +88,6 @@ deployment. They also do not include a bastion or workload hosts deployed. See [
 
 Use the [**Custom Deployment template with GWLB**](examples/cc_gwlb) to deploy your Cloud Connector in a new or existing VPC and load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. Optional ZPA/Route 53 add-on capabilities.
 
-### **Custom Deployment Template with Auto Scaling groups (ASG) and Gateway Load Balancer (GWLB)**
+### **Custom Deployment Template with Auto Scaling and Gateway Load Balancer (GWLB)**
 
 Use the [**Custom Deployment template with GWLB**](examples/cc_gwlb_asg) to deploy your Cloud Connector in a new or existing VPC and load balance traffic across multiple Cloud Connectors. Zscaler\'s recommended deployment method is Gateway Load Balancer (GWLB). GWLB distributes traffic across multiple Cloud Connectors and achieves high availability. For added resiliency and elasticity, Cloud Connectors are deployed via a Launch Template configured Auto Scaling group. Optional ZPA/Route 53 add-on capabilities.

examples/base_1cc/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_1cc" deployment type
+# Zscaler Starter Deployment Template (Base_1cc)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. Everything from "Base" deployment type (Creates 1 new VPC with 1 public subnet and 1 private/workload subnet; 1 IGW; 1 NAT Gateway; 1 Centos server workload in the private subnet routing to NAT Gateway; 1 Bastion Host in the public subnet assigned an Elastic IP and routing to the IGW; generates local key pair .pem file for ssh access)<br>
 

examples/base_1cc_zpa/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_1cc_zpa" greenfield deployment type
+# Zscaler Starter Deployment Template with ZPA (Base_1cc_zpa)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. Everything from "Base_1cc" deployment type (Creates 1 new VPC with 1 public subnet and 1 private/workload subnet; 1 IGW; 1 NAT Gateway; 1 Centos server workload in the private subnet routing to NAT Gateway; 1 Bastion Host in the public subnet assigned an Elastic IP and routing to the IGW; generates local key pair .pem file for ssh access; Creates 1 Cloud Connector private subnet; 1 Cloud Connector VM routing to NAT Gateway; workload private subnet route repointed to service ENI of Cloud Connector.)<br>
 

examples/base_2cc/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_2cc" deployment type (deprecated)
+# Zscaler Starter Deployment Template with HA (Base_2cc) (deprecated)
 
 - **Note** This is only available as reference for legacy users. Zscaler's recommended deployment method is Gateway Load Balancer (GWLB), which distributes traffic across multiple Cloud Connectors and achieves high availability. Please refer to [**Starter Deployment Template with GWLB**](../base_cc_gwlb).
 

examples/base_2cc_zpa/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_2cc_zpa" deployment type (deprecated)
+# Zscaler Starter Deployment Template with HA and ZPA (Base_2cc_zpa) (deprecated)
 
 - **Note** This is only available as reference for legacy users. Zscaler's recommended deployment method is Gateway Load Balancer (GWLB), which distributes traffic across multiple Cloud Connectors and achieves high availability. Please refer to [**Starter Deployment Template with GWLB and ZPA**](../base_cc_gwlb_zpa).
 

examples/base_cc_gwlb/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_cc_gwlb" deployment type
+# Zscaler Starter Deployment Template with Gateway Load Balancer (Base_cc_gwlb)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. Everything from "Base_1cc" deployment type (Creates 1 new VPC with 1 public subnet and 1 private/workload subnet; 1 IGW; 1 NAT Gateway; 1 Centos server workload in the private subnet routing to NAT Gateway; 1 Bastion Host in the public subnet assigned an Elastic IP and routing to the IGW; generates local key pair .pem file for ssh access)<br>
 

examples/base_cc_gwlb_asg/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_cc_gwlb_asg" deployment type
+# Zscaler Starter Deployment Template with Auto Scaling and Gateway Load Balancer (Base_cc_gwlb_asg)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. By default, it will create 1 new VPC with 2 public subnets and 2 Cloud Connector private subnets; 1 IGW; 2 NAT Gateways; Cloud Connector Autoscaling Group + Launch Template spanning all CC subnets routing to the NAT Gateway in their same AZ; generates local key pair .pem file for ssh access; Customizable minimum/maximum number of Cloud Connectors and subnets deployed; generates local key pair .pem file for ssh access; Gateway Load Balancer with Instance based target group and health checks; VPC Endpoint Service; 2 GWLB Endpoints (1 in each Cloud Connector subnet); workload private subnet routes pointing to the GWLB Endpoint in their same AZ.<br>
 

examples/base_cc_gwlb_asg_zpa/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_cc_gwlb_asg_zpa" deployment type
+# Zscaler Starter Deployment Template with Auto Scaling, Gateway Load Balancer and ZPA (Base_cc_gwlb_asg_zpa)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. By default, it will create 1 new VPC with 2 public subnets and 2 Cloud Connector private subnets; 1 IGW; 2 NAT Gateways; Cloud Connector Autoscaling Group + Launch Template spanning all CC subnets routing to the NAT Gateway in their same AZ; generates local key pair .pem file for ssh access; Customizable minimum/maximum number of Cloud Connectors and subnets deployed; generates local key pair .pem file for ssh access; Gateway Load Balancer with Instance based target group and health checks; VPC Endpoint Service; 2 GWLB Endpoints (1 in each Cloud Connector subnet); workload private subnet routes pointing to the GWLB Endpoint in their same AZ.<br>
 

examples/base_cc_gwlb_zpa/README.md

@@ -1,4 +1,4 @@
-# Zscaler "Base_cc_gwlb_zpa" deployment type
+# Zscaler Starter Deployment Template with Gateway Load Balancer and ZPA (Base_cc_gwlb_zpa)
 
 This deployment type is intended for greenfield/pov/lab purposes. It will deploy a fully functioning sandbox environment in a new VPC with test workload VMs. Full set of resources provisioned listed below, but this will effectively create all network infrastructure dependencies for an AWS environment. Everything from "Base_1cc" deployment type (Creates 1 new VPC with 1 public subnet and 1 private/workload subnet; 1 IGW; 1 NAT Gateway; 1 Centos server workload in the private subnet routing to NAT Gateway; 1 Bastion Host in the public subnet assigned an Elastic IP and routing to the IGW; generates local key pair .pem file for ssh access)<br>
 

examples/cc_gwlb/README.md

@@ -1,4 +1,4 @@
-# Zscaler "cc_gwlb" deployment type
+# Zscaler Custom Deployment Template with Gateway Load Balancer (cc_gwlb)
 
 This deployment type is intended for brownfield/production purposes. By default, it will create 1 new VPC with 2 public subnets and 2 Cloud Connector private subnets; 1 IGW; 2 NAT Gateways; 4 Cloud Connector VMs (2 per subnet/AZ) routing to the NAT Gateway in their same AZ; generates local key pair .pem file for ssh access; Number of Cloud Connectors and subnets deployed, ability to use existing resources (VPC, subnets, IGW, NAT Gateways), toggle ZPA/R53 resources; generates local key pair .pem file for ssh access; Gateway Load Balancer auto registers service IPs to target group with health checks; VPC Endpoint Service; 2 GWLB Endpoints (1 in each Cloud Connector subnet)
 

examples/cc_gwlb_asg/README.md

@@ -1,4 +1,4 @@
-# Zscaler "cc_gwlb_asg" deployment type
+# Zscaler Custom Deployment Template with Auto Scaling and Gateway Load Balancer (cc_gwlb_asg)
 
 This deployment type is intended for brownfield/production purposes. By default, it will create 1 new VPC with 2 public subnets and 2 Cloud Connector private subnets; 1 IGW; 2 NAT Gateways; Cloud Connector Autoscaling Group + Launch Template spanning all CC subnets routing to the NAT Gateway in their same AZ; generates local key pair .pem file for ssh access; Customizable minimum/maximum number of Cloud Connectors and subnets deployed, ability to use existing resources (VPC, subnets, IGW, NAT Gateways), toggle ZPA/R53 resources; generates local key pair .pem file for ssh access; Gateway Load Balancer with Instance based target group and health checks; VPC Endpoint Service; 2 GWLB Endpoints (1 in each Cloud Connector subnet)
 

examples/cc_ha/README.md

@@ -1,4 +1,4 @@
-# Zscaler "cc_ha" deployment type (deprecated)
+# Zscaler Custom Deployment Template with HA (cc_ha) (deprecated)
 
 - **Note** This is only available as reference for legacy users. Zscaler's recommended deployment method is Gateway Load Balancer (GWLB), which distributes traffic across multiple Cloud Connectors and achieves high availability. Please refer to [**Custom Deployment template with GWLB**](../cc_gwlb).