diff --git a/aws-fs-lambda-webserver/LambdaWebServer/Setup.fs b/aws-fs-lambda-webserver/LambdaWebServer/Setup.fs
index 1d14780a9..22a1c5a72 100644
--- a/aws-fs-lambda-webserver/LambdaWebServer/Setup.fs
+++ b/aws-fs-lambda-webserver/LambdaWebServer/Setup.fs
@@ -45,7 +45,7 @@ let configureAppConfiguration (ctx:WebHostBuilderContext) (builder : IConfigurat
         .AddEnvironmentVariables() |> ignore
 
 // ---------------------------------
-// This type is the entry point when running in Lambda. It has similar responsiblities
+// This type is the entry point when running in Lambda. It has similar responsibilities
 // to the main entry point function that can be used for local development.
 // ---------------------------------
 type LambdaEntryPoint() =
diff --git a/aws-ts-eks-hello-world/README.md b/aws-ts-eks-hello-world/README.md
index d947733d0..d25939caa 100755
--- a/aws-ts-eks-hello-world/README.md
+++ b/aws-ts-eks-hello-world/README.md
@@ -236,7 +236,7 @@ After cloning this repo, from this working directory, run these commands:
 
     To access your new Kubernetes cluster using `kubectl`, we need to set up the
     `kubeconfig` file and download `kubectl`. We can leverage the Pulumi
-    stack output in the CLI, as Pulumi faciliates exporting these objects for us.
+    stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
     ```bash
     $ pulumi stack output kubeconfig > kubeconfig
diff --git a/aws-ts-pulumi-miniflux/README.md b/aws-ts-pulumi-miniflux/README.md
index 36b06ac16..319d36f4f 100644
--- a/aws-ts-pulumi-miniflux/README.md
+++ b/aws-ts-pulumi-miniflux/README.md
@@ -18,7 +18,7 @@
     pulumi stack init
     ```
 
-1. Apply the required configuration properties, making adjustments as you like, and taking care to choose strong passwords for the database user and service adminstrator (which will be stored as encrypted [Pulumi secrets](https://www.pulumi.com/docs/intro/concepts/config/):
+1. Apply the required configuration properties, making adjustments as you like, and taking care to choose strong passwords for the database user and service administrator (which will be stored as encrypted [Pulumi secrets](https://www.pulumi.com/docs/intro/concepts/config/):
 
     ```bash
     pulumi config set aws:region us-west-2
diff --git a/aws-ts-static-website/README.md b/aws-ts-static-website/README.md
index 3a5c35045..96cea4120 100644
--- a/aws-ts-static-website/README.md
+++ b/aws-ts-static-website/README.md
@@ -99,7 +99,7 @@ This is caused by CloudFront confirming the ETag of the resource before applying
 ETag is essentially a "version", and AWS is rejecting any requests that are trying to update
 any version but the "latest".
 
-This error will occurr when the state of the ETag get out of sync between the Pulumi Service
+This error will occur when the state of the ETag get out of sync between the Pulumi Service
 and AWS. (Which can happen when inspecting the CloudFront distribution in the AWS console.)
 
 You can fix this by running `pulumi refresh` to pickup the newer ETag values.
diff --git a/aws-ts-static-website/index.ts b/aws-ts-static-website/index.ts
index 506171237..54c3efdc2 100644
--- a/aws-ts-static-website/index.ts
+++ b/aws-ts-static-website/index.ts
@@ -179,7 +179,7 @@ const distributionArgs: aws.cloudfront.DistributionArgs = {
     // "100" is the least broad, and also the least expensive.
     priceClass: "PriceClass_100",
 
-    // You can customize error responses. When CloudFront recieves an error from the origin (e.g. S3 or some other
+    // You can customize error responses. When CloudFront receives an error from the origin (e.g. S3 or some other
     // web service) it can return a different error code, and return the response for a different resource.
     customErrorResponses: [
         { errorCode: 404, responseCode: 404, responsePagePath: "/404.html" },
diff --git a/azure-cs-msi-keyvault-rbac/README.md b/azure-cs-msi-keyvault-rbac/README.md
index 9a19e9a2c..61d66a57e 100644
--- a/azure-cs-msi-keyvault-rbac/README.md
+++ b/azure-cs-msi-keyvault-rbac/README.md
@@ -4,7 +4,7 @@
 
 [Managed identities](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/) for Azure resources provides Azure services with an automatically managed identity in Azure Active Directory (Azure AD).
 
-This example demostrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
+This example demonstrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
 
 The application consists of several parts:
 
diff --git a/azure-py-msi-keyvault-rbac/README.md b/azure-py-msi-keyvault-rbac/README.md
index 70aac29c1..180e8b84b 100644
--- a/azure-py-msi-keyvault-rbac/README.md
+++ b/azure-py-msi-keyvault-rbac/README.md
@@ -4,7 +4,7 @@
 
 [Managed identities](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/) for Azure resources provides Azure services with an automatically managed identity in Azure Active Directory (Azure AD).
 
-This example demostrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
+This example demonstrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
 
 The application consists of several parts:
 
diff --git a/azure-ts-cosmosapp-component/README.md b/azure-ts-cosmosapp-component/README.md
index d8fe2ce45..583b2f282 100644
--- a/azure-ts-cosmosapp-component/README.md
+++ b/azure-ts-cosmosapp-component/README.md
@@ -17,7 +17,7 @@ The [`CosmosApp`](cosmosApp.ts) defines a skeleton for the application. While no
 The application has three example of using this component with the following compute services:
 
 - Azure Functions
-- Azure Container Intances
+- Azure Container Instances
 - Azure VM Scale Sets + Azure Load Balancer
 
 ## Prerequisites
diff --git a/azure-ts-functions-raw/index.ts b/azure-ts-functions-raw/index.ts
index d5f127325..c409f799c 100644
--- a/azure-ts-functions-raw/index.ts
+++ b/azure-ts-functions-raw/index.ts
@@ -35,7 +35,7 @@ const javaApp = new azure.appservice.ArchiveFunctionApp("http-java", {
     },
 });
 
-// Create a dedicated resoure group for Linux App Service Plan - require for Python
+// Create a dedicated resource group for Linux App Service Plan - require for Python
 const linuxResourceGroup = new azure.core.ResourceGroup("linuxrg");
 
 // Python Function App won't run on Windows Consumption Plan, so we create a Linux Consumption Plan instead
diff --git a/azure-ts-msi-keyvault-rbac/README.md b/azure-ts-msi-keyvault-rbac/README.md
index 82d9ea0e4..46f354d5f 100644
--- a/azure-ts-msi-keyvault-rbac/README.md
+++ b/azure-ts-msi-keyvault-rbac/README.md
@@ -4,7 +4,7 @@
 
 [Managed identities](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/) for Azure resources provides Azure services with an automatically managed identity in Azure Active Directory (Azure AD).
 
-This example demostrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
+This example demonstrates using a managed identity with Azure App Service to access Azure KeyVault, Azure Storage, and Azure SQL Database without passwords or secrets.
 
 The application consists of several parts:
 
diff --git a/azure-ts-static-website/staticWebsite.ts b/azure-ts-static-website/staticWebsite.ts
index ca9b589e6..67f0c8597 100644
--- a/azure-ts-static-website/staticWebsite.ts
+++ b/azure-ts-static-website/staticWebsite.ts
@@ -39,7 +39,7 @@ class StorageStaticWebsiteProvider implements pulumi.dynamic.ResourceProvider {
         const url = require("url");
         const accountName = inputs[accountNameProp];
 
-        // Helper function to execute a command, supress the warnings from polluting the output, and parse the result as JSON
+        // Helper function to execute a command, suppress the warnings from polluting the output, and parse the result as JSON
         const executeToJson = (command: string) => JSON.parse(execSync(command, { stdio: ["pipe", "pipe", "ignore"] }).toString());
 
         // Install Azure CLI extension for storage (currently, only the preview version has the one we need)
diff --git a/gcp-cs-gke/README.md b/gcp-cs-gke/README.md
index b8bf7708f..c450cd31e 100644
--- a/gcp-cs-gke/README.md
+++ b/gcp-cs-gke/README.md
@@ -98,7 +98,7 @@ After cloning this repo, from this working directory, run these commands:
 
     To access your new Kubernetes cluster using `kubectl`, we need to setup the
     `kubeconfig` file and download `kubectl`. We can leverage the Pulumi
-    stack output in the CLI, as Pulumi faciliates exporting these objects for us.
+    stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
     ```bash
     $ pulumi stack output KubeConfig > kubeconfig
diff --git a/gcp-go-functions-raw/main.go b/gcp-go-functions-raw/main.go
index 37daa9cb8..fdc3a522f 100644
--- a/gcp-go-functions-raw/main.go
+++ b/gcp-go-functions-raw/main.go
@@ -51,7 +51,7 @@ func main() {
 			return err
 		}
 
-		// Export the tigger URL.
+		// Export the trigger URL.
 		ctx.Export("function", function.HttpsTriggerUrl)
 		return nil
 	})
diff --git a/gcp-go-functions/main.go b/gcp-go-functions/main.go
index 26ad41fcf..f94d04cd2 100644
--- a/gcp-go-functions/main.go
+++ b/gcp-go-functions/main.go
@@ -51,7 +51,7 @@ func main() {
 			return err
 		}
 
-		// Export the tigger URL.
+		// Export the trigger URL.
 		ctx.Export("function", function.HttpsTriggerUrl)
 		return nil
 	})
diff --git a/gcp-go-gke/README.md b/gcp-go-gke/README.md
index 8bc1cfbd2..5e56a7263 100644
--- a/gcp-go-gke/README.md
+++ b/gcp-go-gke/README.md
@@ -99,7 +99,7 @@ After cloning this repo, from this working directory, run these commands:
 
     To access your new Kubernetes cluster using `kubectl`, we need to setup the
     `kubeconfig` file and download `kubectl`. We can leverage the Pulumi
-    stack output in the CLI, as Pulumi faciliates exporting these objects for us.
+    stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
     ```bash
     $ pulumi stack output kubeconfig > kubeconfig
diff --git a/gcp-ts-gke-hello-world/README.md b/gcp-ts-gke-hello-world/README.md
index e3ea5df75..39213f3ca 100644
--- a/gcp-ts-gke-hello-world/README.md
+++ b/gcp-ts-gke-hello-world/README.md
@@ -143,7 +143,7 @@ After cloning this repo, from this working directory, run these commands:
 
     To access your new Kubernetes cluster using `kubectl`, we need to setup the
     `kubeconfig` file and download `kubectl`. We can leverage the Pulumi
-    stack output in the CLI, as Pulumi faciliates exporting these objects for us.
+    stack output in the CLI, as Pulumi facilitates exporting these objects for us.
 
     ```bash
     $ pulumi stack output kubeconfig > kubeconfig
diff --git a/kubernetes-ts-staged-rollout-with-prometheus/README.md b/kubernetes-ts-staged-rollout-with-prometheus/README.md
index 6d49ce2cd..908dc8cd5 100644
--- a/kubernetes-ts-staged-rollout-with-prometheus/README.md
+++ b/kubernetes-ts-staged-rollout-with-prometheus/README.md
@@ -63,7 +63,7 @@ can see `canary-example-app` and `canary-staging-app` created.
 
 1. **IMPORTANT NOTE:** The code in `index.ts` is meant to be run out-of-cluster (_e.g._, on your
    local machine). It will thus call `kubectl port-forward` on your behalf so that the Prometheus
-   service is fowarded to your local machine, which allows this program to poll for metrics. **If
+   service is forwarded to your local machine, which allows this program to poll for metrics. **If
    you are running Pulumi in-cluster, you can comment out this part of the example.**
 
 1. Perform the deployment:
diff --git a/twilio-ts-component/Pulumi.yaml b/twilio-ts-component/Pulumi.yaml
index 10eb53d2d..c3026b86f 100644
--- a/twilio-ts-component/Pulumi.yaml
+++ b/twilio-ts-component/Pulumi.yaml
@@ -1,5 +1,5 @@
 name: twilio-ts-component
-description: A small example that builds a Pulumi component for Twilio Programable SMS
+description: A small example that builds a Pulumi component for Twilio Programmable SMS
 runtime: nodejs
 template:
   config:
diff --git a/twilio-ts-component/README.md b/twilio-ts-component/README.md
index 2aade1ee2..828f863d4 100644
--- a/twilio-ts-component/README.md
+++ b/twilio-ts-component/README.md
@@ -58,7 +58,7 @@ A sample for interacting with Twilio SMS. This sample includes a custom Componen
     Update duration: 27.155440706s
     ```
 
-1. Send an SMS message to the phone number you have registered with Twilio, or make a request by hand with cURL (you may wish to pass aditional data with your request, see https://www.twilio.com/docs/sms/twiml#request-parameters for the complete set of data that Twilio sends).
+1. Send an SMS message to the phone number you have registered with Twilio, or make a request by hand with cURL (you may wish to pass additional data with your request, see https://www.twilio.com/docs/sms/twiml#request-parameters for the complete set of data that Twilio sends).
 
     ```
     $ curl -X POST -d "From=+12065555555" -d "Body=Hello!" $(pulumi stack output smsUrl)