added package links and links to package releases

docs/landing-zone-v2/README.md

@@ -83,7 +83,7 @@ A deployed Landing Zone contains two sections the Core Landing Zone and the Clie
 
 ### Core Landing Zone
 
-This is made up of two packages `core-landing-zone` and `gatekeeper-policies`. This section provides the core of the landing zone functionality with Logging, Org Policies, and Shared Infrastructure like DNS and a Shared VPC (coming soon) as well as compliance enforcement in Config Controller.
+This is made up of two packages [core-landing-zone](../../solutions/core-landing-zone/) and [gatekeeper-policies](../../solutions/gatekeeper-policies/). This section provides the core of the landing zone functionality with Logging, Org Policies, and Shared Infrastructure like DNS and a Shared VPC (coming soon) as well as compliance enforcement in Config Controller.
 
 This can be deployed once or multiple times per organization as highlighted in the diagrams below.
 
@@ -96,7 +96,7 @@ This can be deployed once or multiple times per organization as highlighted in t
 
 ### Client Landing Zone
 
-This section is made up of two packages `client-setup` and `client-landing-zone`. The client setup package prepares the Config Controller instances for the new client and creates the required service accounts and namespaces for the client to use.
+This section is made up of two packages [client-setup](../../solutions/client-setup/) and [client-landing-zone](../../solutions/client-landing-zone/). The client setup package prepares the Config Controller instances for the new client and creates the required service accounts and namespaces for the client to use.
 
 The `client-landing-zone` package deploys the clients Google Cloud resources, including folder structure, firewalls, and Shared Infrastructure (VPC). The deployment of these packages are repeated for each onboarded client. A client in these examples would be an a department or working group that needs isolation from other groups.
 
@@ -400,6 +400,8 @@ cd pbmm-landingzone
     kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/[email protected]
     ```
 
+    All Gatekeeper Policy Package releases can be found [here](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=gatekeeper&expanded=true)
+
 1. Get the landing zone package
 
     - Experimentation
@@ -408,12 +410,16 @@ cd pbmm-landingzone
       kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/experimentation/[email protected]
       ```
 
+      [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=experimentation&expanded=true)
+
     - DEV, PREPROD, PROD
 
       ```shell
       kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/[email protected]
       ```
 
+      [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=core-landing-zone&expanded=true)
+
 1. Customize Packages
 
     Review and customize all packages' `setters.yaml` with the unique configuration of your landing zone.  

docs/landing-zone-v2/onboarding-client.md

@@ -54,6 +54,8 @@ You will execute this procedure to provision the foundational resources in GCP f
   kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/[email protected] ./clients/<client name>
   ```
 
+  [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=%22solutions%2Fclient-setup%22&expanded=true)
+
 1. Customize the `clients/<client name>/client-setup/setters.yaml` file
 
   > **!!! There is a folder in that package called `root-sync-git`. This folder can be deleted if your are not using a `Gitops - Git` deployment solution. But, if you are, you should now create a new repository for this client and add the client-landing-zone package to that repo**
@@ -79,21 +81,25 @@ You will execute this procedure to provision the foundational resources in GCP f
   kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/experimentation/[email protected] ./clients/<client name>
   ```
 
+  [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=experimentation%2Fclient-landing-zone&expanded=true)
+
 - DEV, PREPROD, PROD
 
   ```shell
   kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/[email protected] ./clients/<client name>
   ```
 
+  [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=solutions%2Fclient-landing-zone&expanded=true)
+
 1. Customize the `clients/<client name>/client-landing-zone/setters.yaml` file
 
-1. Render the Configs
+2. Render the Configs
 
     ```shell
     kpt fn render clients/<client name>/client-landing-zone
     ```
 
-1. Deploy the infrastructure using either kpt or gitops-git or gitops-oci
+3. Deploy the infrastructure using either kpt or gitops-git or gitops-oci
 
 ## <a name='NextStep'></a>Next Step
 

docs/landing-zone-v2/onboarding-project.md

@@ -52,12 +52,16 @@ You will execute this procedure to provision the service project in GCP for appl
   kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/experimentation/[email protected] ./projects/<project-id>
   ```
 
+  [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=%22experimentation%2Fclient-project%22&expanded=true)
+
 - DEV, PREPROD, PROD
 
   ```shell
   kpt pkg get https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit.git/solutions/[email protected] ./projects/<project-id>
   ```
 
+  [Releases List](https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/releases?q=%22solutions%2Fclient-project-setup%22&expanded=true)
+
 1. Customize the `setters.yaml` file
 
 - Experimentation