fix links

fast/stages/3-gcve-dev/README.md

@@ -1,11 +1,8 @@
 # GCVE Private Cloud Minimal
 
-This blueprint presents an opinionated architecture to handle different Google VMware Engine deployment scenarios: from a simple single region private cloud to multi-region private clouds spread across different locations. The general idea behind this blueprint is to deploy a single project hosting one or more GCVE private clouds connected to a shared VMware Engine Network (VEN).
-Optionally this blueprint can deploy the VMWare Engine Network peerings to pre-existing VPCs.
+This stage implements a simple architecture that integrates Google VMware Engine in a FAST organization.
 
-Multiple deployments of this blueprint allow the user to achieve more complex design solutions as for example GCVE private clouds deployed on different projects or connected to independent VMWare Engine Networks.
-
-This blueprint is used as part of the [FAST GCVE stage](../../../fast/stages/3-gcve/) but it can also be used independently if desired.
+The setup configured here is for a single environment in a single region, and is provided as a starting point for the more complex patterns [described below in this document](#architectural-patterns) which can be easily implemented by extending this stage, and/or duplicating it across environments.
 
 <!-- BEGIN TOC -->
 - [Stage configuration](#stage-configuration)
@@ -91,7 +88,7 @@ Before running this stage, you need to make sure you have the correct credential
 
 ### Provider and Terraform variables
 
-As all other FAST stages, the [mechanism used to pass variable values and pre-built provider files from one stage to the next](../../0-bootstrap/README.md#output-files-and-cross-stage-variables) is also leveraged here.
+As all other FAST stages, the [mechanism used to pass variable values and pre-built provider files from one stage to the next](../0-bootstrap/README.md#output-files-and-cross-stage-variables) is also leveraged here.
 
 The commands to link or copy the provider and terraform variable files can be easily derived from the `stage-links.sh` script in the FAST root folder, passing it a single argument with the local output files folder (if configured) or the GCS output bucket in the automation project (derived from stage 0 outputs). The following examples demonstrate both cases, and the resulting commands that then need to be copy/pasted and run.
 

fast/stages/README.md

@@ -50,4 +50,4 @@ Implemented as an [add-on stage 1](./1-tenant-factory/), with optional FAST comp
 - [Networking Security](./3-network-security/) Manages NGFW Enterprise deployment for the production and development environments.
 - [Data Platform](3-data-platform/dev/)
 - [GKE Multitenant](3-gke-multitenant/dev/)
-- [Google Cloud VMware Engine](3-gcve/)
+- [Google Cloud VMware Engine](3-gcve-dev/)