Explicitly call out PSC NEG for deployment setup (#1307)

GCP has various types of NEG and the one we care
about is the PSC NEG that enables the customer to
connect to a service provider via the service
attachment.

Author: puneetsarna

content/nginxaas-google/getting-started/create-deployment/deploy-console.md

@@ -87,7 +87,9 @@ To set up connectivity to your NGINXaaS deployment, you will need to configure a
 
 1. Access the [Google Cloud Console](https://console.cloud.google.com/).
 1. Create a public IP address. See [Google's documentation on reserving a static address](https://cloud.google.com/load-balancing/docs/tcp/set-up-ext-reg-tcp-proxy-zonal#console_3) for a step-by-step guide.
-1. Create a Network Endpoint Group (NEG). See [Google's documentation on creating a NEG](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends#console) for a step-by-step guide.
+1. Create a Private Service Connect Network Endpoint Group (PSC NEG). See [Google's documentation on creating a NEG](https://cloud.google.com/vpc/docs/access-apis-managed-services-private-service-connect-backends#console) for a step-by-step guide.
+   - Set **Network endpoint group type** to **Private Service Connect NEG (Regional)**.
+   - Set **Taget** to **Published service**.
    - For **Target service**, enter your NGINXaaS deployment's Service Attachment, which is visible on the `Deployment Details` section for your deployment.
    - For **Producer port**, enter the port your NGINX server is listening on. If you're using the default NGINX config, enter port `80`.
    - For **Network** and **Subnetwork** select your consumer VPC network and subnet.
@@ -105,4 +107,4 @@ To set up connectivity to your NGINXaaS deployment, you will need to configure a
 
 ## What's next
 
-[Manage your NGINXaaS users]({{< ref "/nginxaas-google/getting-started/manage-users-accounts.md" >}})
+[Manage your NGINXaaS users]({{< ref "/nginxaas-google/getting-started/manage-users-accounts.md" >}})