From 216318b171ca17e0ea410355f479e56221daeedf Mon Sep 17 00:00:00 2001 From: Aaron Yarborough Date: Wed, 13 Mar 2024 12:24:57 +0000 Subject: [PATCH] fix: typo in deployment article --- content/writing/static-site-on-google-cloud.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/writing/static-site-on-google-cloud.md b/content/writing/static-site-on-google-cloud.md index 19ca584..9216b4e 100644 --- a/content/writing/static-site-on-google-cloud.md +++ b/content/writing/static-site-on-google-cloud.md @@ -7,9 +7,9 @@ Google actually has [documentation](https://cloud.google.com/storage/docs/hostin ## Networking -This site is just a collection oh static assets (HTML, JS, CSS and images) that live inside a Google Cloud Storage bucket. When you load the site, the below route is taken once your request reaches GCP. +This site is just a collection of static assets (HTML, JS, CSS and images) that live inside a Google Cloud Storage bucket. When you load the site, the below route is taken once your request reaches GCP. -![Route diagram showing networking path from user to destination on GCP](/img/screenshot-2024-03-13-at-11.58.55.png "Route diagram showing networking path from yser to destination on GCP") +![Route diagram showing networking path from user to destination on GCP](/img/screenshot-2024-03-13-at-11.58.55.png "Route diagram showing networking path from year to destination on GCP") 1. As you can see, you: 2. Hit a load balancer, which then @@ -21,7 +21,7 @@ The setup is pretty simple, and doesn't really deviate from Google's suggested s ## Deploying -Setting up a seamless deployment stategy gets a little tricker, however. I opted to set up a manual deployment strategy, which involves calling `npm run deploy` to kick off the deployment. This in turn calls a bash script that handles the deployment. +Setting up a seamless deployment strategy gets a little tricker, however. I opted to set up a manual deployment strategy, which involves calling `npm run deploy` to kick off the deployment. This in turn calls a bash script that handles the deployment. The script consists of 4 deployment steps: