From c552ca0fbd5c90d393f7568e26de82c4c3fe328b Mon Sep 17 00:00:00 2001 From: Chris Carty Date: Mon, 28 Aug 2023 14:05:16 -0400 Subject: [PATCH] fixed typos --- docs/landing-zone-v2/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/landing-zone-v2/README.md b/docs/landing-zone-v2/README.md index 342db6f40..a4a315e2c 100644 --- a/docs/landing-zone-v2/README.md +++ b/docs/landing-zone-v2/README.md @@ -60,7 +60,7 @@ This Landing Zone v2 assumes that the different required environments known as E ## Single GCP organization -This pattern will be ideal for most use-cases and isolation between enviornments is achieved through folder structures. +This pattern will be ideal for most use-cases and isolation between environments is achieved through folder structures. In this example a Landing Zone is deployed per environment. @@ -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 pacakges `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` 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 can be deployed once or multiple times per organization as highlighted in the diagrams below.