pulumi · cnunciato · Aug 27, 2026 · Aug 25, 2026 · Aug 25, 2026 · Aug 25, 2026
diff --git a/content/blog/ai-ml-on-kubernetes-google-cloud-llm-rag/index.md b/content/blog/ai-ml-on-kubernetes-google-cloud-llm-rag/index.md
@@ -69,13 +69,13 @@ Running AI/ML workloads on Kubernetes presents unique challenges, including:
 - **Complex data pipelines** that integrate various cloud services
 - **Infrastructure automation** for seamless deployment
 
-Google Cloud Kubernetes (GKE) provides a robust foundation for AI/ML workloads, but managing infrastructure manually can be cumbersome. This is where Pulumi comes in—enabling Infrastructure as Code (IaC) to automate and simplify AI/ML infrastructure on Kubernetes.
+Google Cloud Kubernetes (GKE) provides a robust foundation for AI/ML workloads, but managing infrastructure manually can be cumbersome. This is where Pulumi comes in—enabling infrastructure as code (IaC) to automate and simplify AI/ML infrastructure on Kubernetes.
 
 <!--more-->
 
 ## Pulumi: Automating AI/ML Infrastructure on Google Cloud
 
-Pulumi is a modern Infrastructure as Code (IaC) tool that allows teams to define and manage cloud infrastructure using general-purpose programming languages like Python, TypeScript, and Go. This approach is particularly beneficial for AI/ML teams, as Python is already the dominant language in data science and machine learning.
+Pulumi is a modern infrastructure as code (IaC) tool that allows teams to define and manage cloud infrastructure using general-purpose programming languages like Python, TypeScript, and Go. This approach is particularly beneficial for AI/ML teams, as Python is already the dominant language in data science and machine learning.
 
 With Pulumi, you can:
 

diff --git a/content/blog/announcing-pulumi-up-2022/index.md b/content/blog/announcing-pulumi-up-2022/index.md
@@ -46,7 +46,7 @@ Stay tuned as we will announce the full agenda and speakers soon on our website
 
 **Inaugural Community Summit**: Connect and engage with Pulumi practitioners from around the world---from the comfort of your home. We are hosting a Community Summit on May 5 featuring lightning talks and discussions.
 
-**Workshops**: Get hands-on with Pulumi and cloud engineering in 1-hour workshops that will cover the fundamentals of Infrastructure as Code as well as more advanced subjects for experienced Pulumi users.
+**Workshops**: Get hands-on with Pulumi and cloud engineering in 1-hour workshops that will cover the fundamentals of infrastructure as code as well as more advanced subjects for experienced Pulumi users.
 
 ## Join us on May 4 and 5
 

diff --git a/content/blog/announcing-speaker-lineup-pulumiup-2023/index.md b/content/blog/announcing-speaker-lineup-pulumiup-2023/index.md
@@ -12,7 +12,7 @@ tags:
 category: community
 ---
 
-[PulumiUP](https://www.pulumi.com/pulumi-up/) is our virtual user conference for the Pulumi community and anyone interested in Infrastructure as Code. Every year, we strive to build a program packed with technical talks, demos, and best practices with the goal of leaving you with new learnings and inspiration that will help you become a better cloud engineer. You'll hear from industry leaders and experts about IaC, software engineering, DevOps, Platform engineering, and AI.
+[PulumiUP](https://www.pulumi.com/pulumi-up/) is our virtual user conference for the Pulumi community and anyone interested in infrastructure as code. Every year, we strive to build a program packed with technical talks, demos, and best practices with the goal of leaving you with new learnings and inspiration that will help you become a better cloud engineer. You'll hear from industry leaders and experts about IaC, software engineering, DevOps, Platform engineering, and AI.
 
 We hope you'll [join us virtually](https://www.pulumi.com/pulumi-up/) and take this opportunity to grow your knowledge and become infrastructure as code stars.
 
@@ -34,7 +34,7 @@ You'll hear from innovators, leaders, and experts from multiple industries and l
 ### Sam Cogan - Solution Architect, WTW
 
 _Talk: Keeping your Infrastructure Code DRY (Don't Repeat Yourself)_  
-Sam is a Solution Architect with [WTW](https://www.wtwco.com/?utm_source=Pulumi.com&utm_medium=Website&utm_campaign=PulumiUP) and a Microsoft Azure MVP. Sam is focused on delivering applications into the cloud using IaaS, PaaS, Serverless, Containers, and Kubernetes. Sam is particularly focused on automation and DevOps, including Infrastructure as Code, Cloud automation tooling, PowerShell, and CI/CD tooling.
+Sam is a Solution Architect with [WTW](https://www.wtwco.com/?utm_source=Pulumi.com&utm_medium=Website&utm_campaign=PulumiUP) and a Microsoft Azure MVP. Sam is focused on delivering applications into the cloud using IaaS, PaaS, Serverless, Containers, and Kubernetes. Sam is particularly focused on automation and DevOps, including infrastructure as code, Cloud automation tooling, PowerShell, and CI/CD tooling.
 
 ### Dennis Sauvé - DevOps Engineer, Washington Trust Bank
 

diff --git a/content/blog/any-terraform-provider/index.md b/content/blog/any-terraform-provider/index.md
@@ -134,7 +134,7 @@ Planetscale is an exciting example, but it is just one of thousands of 3rd party
 
 Pulumi has a rich and expressive Native Provider model for building providers directly against the full capabilities of the Pulumi Infrastructure as Code resource model.  Many of the most important Pulumi providers are built directly on this foundation, including our [Azure Native](https://www.pulumi.com/registry/packages/azure-native/) and [Kubernetes](https://www.pulumi.com/registry/packages/kubernetes/) providers.  So why are we excited to support using Terraform and OpenTofu providers from Pulumi?
 
-In short, we believe in giving Pulumi users access to every ecosystem of great providers and components available across the industry and in meeting partners where they are.  If a partner or user has built something exciting for managing infrastructure in the cloud, we want Pulumi users to benefit from it. Similarly, we want the partner or user to easily extend the value of their provider to also be able to reach the Pulumi user base, and all of the benefits that Pulumi can offer for Infrastructure as Code management, with no extra effort on their part.
+In short, we believe in giving Pulumi users access to every ecosystem of great providers and components available across the industry and in meeting partners where they are.  If a partner or user has built something exciting for managing infrastructure in the cloud, we want Pulumi users to benefit from it. Similarly, we want the partner or user to easily extend the value of their provider to also be able to reach the Pulumi user base, and all of the benefits that Pulumi can offer for infrastructure as code management, with no extra effort on their part.
 
 We’ve embraced this approach in many other areas as well:
 

diff --git a/content/blog/automatically-enforcing-aws-resource-tagging-policies/index.md b/content/blog/automatically-enforcing-aws-resource-tagging-policies/index.md
@@ -8,15 +8,15 @@ meta_desc: "Learn how to automate AWS resource tagging using Infrastructure and
 
 ---
 
-AWS publishes best practices for how to tag your resources for cost tracking, automation, and organization. But how do you enforce that you're doing it correctly across all of your projects? And is it really necessary to manually track down all those places where you missed a tag and manually patch things up? In this article, we'll see how to use Policy as Code to enforce your team's tagging strategies in addition to some powerful [Infrastructure as Code](/what-is/what-is-infrastructure-as-code/) techniques to automate applying your tags in a consistent way across all of your projects and resources.
+AWS publishes best practices for how to tag your resources for cost tracking, automation, and organization. But how do you enforce that you're doing it correctly across all of your projects? And is it really necessary to manually track down all those places where you missed a tag and manually patch things up? In this article, we'll see how to use Policy as Code to enforce your team's tagging strategies in addition to some powerful [infrastructure as code](/what-is/what-is-infrastructure-as-code/) techniques to automate applying your tags in a consistent way across all of your projects and resources.
 
 ## Why Tag Your Resources?
 
 A tag is simply a key/value label that you can apply to your AWS infrastructure resources. Tags enable you to manage, search for, and filter resources. There aren't any predefined tags &mdash; you can use whatever makes sense for your scenario and business requirements.
 
 [Amazon recommends many tagging strategies](https://aws.amazon.com/answers/account-management/aws-tagging-strategies/), including technical tags like name and environment, automation tags like dates and security requirements, business tags like owner and cost center, and security tags for compliance. Each of these enables you to apply policies.
 
-Specifying a tag in your Infrastructure as Code is easy. Not all resources are taggable (although the most important ones are); to tag a resource, specify a map of key/values using the `tags` property. For example, this code declares an S3 Bucket that carries three tags that enable cost allocation reporting: `"user:Project"`, `"user:Stack"`, and `"user:Cost Center"`:
+Specifying a tag in your infrastructure as code is easy. Not all resources are taggable (although the most important ones are); to tag a resource, specify a map of key/values using the `tags` property. For example, this code declares an S3 Bucket that carries three tags that enable cost allocation reporting: `"user:Project"`, `"user:Stack"`, and `"user:Cost Center"`:
 
 {{< chooser language "javascript,typescript,python,go,csharp" >}}
 
@@ -370,7 +370,7 @@ In all cases, after manually fixing our bucket, and adding the correct tags, the
 
 ![Tag Policy Succeeded](/blog/automatically-enforcing-aws-resource-tagging-policies/tag-policy-succeed.png)
 
-This is great &mdash; we can now rest assured that all taggable AWS resources will be tagged before we provision them. But it sure is tedious to add these tags to every resource and then get policy violations errors anytime we forget. One of the advantages of using Infrastructure as Code is that we can automate the injection of these tags.
+This is great &mdash; we can now rest assured that all taggable AWS resources will be tagged before we provision them. But it sure is tedious to add these tags to every resource and then get policy violations errors anytime we forget. One of the advantages of using infrastructure as code is that we can automate the injection of these tags.
 
 To do that, let's write a function that detects taggable resources and merges in automatic tags:
 

diff --git a/content/blog/automation-api/index.md b/content/blog/automation-api/index.md
@@ -10,9 +10,9 @@ category: product
 canonical_url: "https://www.pulumi.com/docs/iac/using-pulumi/automation-api/"
 ---
 
-Today’s [Infrastructure as Code](/what-is/what-is-infrastructure-as-code/) platforms let organizations build rich, reliable, and complex cloud-based applications and architectures. But as teams move to modern cloud technologies,  they continue to search for ways to drive increased software-driven automation. Although modern Infrastructure as Code tools bring key software engineering benefits to cloud engineering, they remain focused on human-driven workflows. For example, a person running `pulumi up` at their terminal or wiring the Pulumi CLI into their CI/CD system.
+Today’s [infrastructure as code](/what-is/what-is-infrastructure-as-code/) platforms let organizations build rich, reliable, and complex cloud-based applications and architectures. But as teams move to modern cloud technologies,  they continue to search for ways to drive increased software-driven automation. Although modern infrastructure as code tools bring key software engineering benefits to cloud engineering, they remain focused on human-driven workflows. For example, a person running `pulumi up` at their terminal or wiring the Pulumi CLI into their CI/CD system.
 
-To scale up how we deploy and manage cloud infrastructure and ultimately unlock the cloud's value and agility, we believe it will be critical to build software systems around our Infrastructure as Code platforms - systems that scale with software, not just humans.
+To scale up how we deploy and manage cloud infrastructure and ultimately unlock the cloud's value and agility, we believe it will be critical to build software systems around our infrastructure as code platforms - systems that scale with software, not just humans.
 
 <!--more-->
 

diff --git a/content/blog/aws-proton-pulumi/index.md b/content/blog/aws-proton-pulumi/index.md
@@ -15,7 +15,7 @@ category: tutorials
 
 Self-service infrastructure is the holy grail of DevOps. When platform engineering teams can empower application teams to provision their own infrastructure without needing to understand the details of configuring networking, storage, and compute resources, IT organizations can drastically increase their ability to deliver on organizational goals.  The first step in this process is to codify infrastructure best practices using platforms like Pulumi and the next step is to make these best practices available in a workflow that fits into the application team’s software development tools and process.
 
-Today, AWS [announced support](https://aws.amazon.com/blogs/containers/announcing-aws-cdk-support-and-codebuild-provisioning-for-aws-proton/) for [AWS CodeBuild](https://aws.amazon.com/codebuild/) as a provisioner in [AWS Proton](https://aws.amazon.com/proton/). Using CodeBuild as a provisioner allows Proton to integrate with the most popular Infrastructure as Code platforms, including Pulumi. With Codebuild provisioning, Proton enables platform teams to define the steps to provision resources based on their own custom workflow and IaC tool of choice.
+Today, AWS [announced support](https://aws.amazon.com/blogs/containers/announcing-aws-cdk-support-and-codebuild-provisioning-for-aws-proton/) for [AWS CodeBuild](https://aws.amazon.com/codebuild/) as a provisioner in [AWS Proton](https://aws.amazon.com/proton/). Using CodeBuild as a provisioner allows Proton to integrate with the most popular infrastructure as code platforms, including Pulumi. With Codebuild provisioning, Proton enables platform teams to define the steps to provision resources based on their own custom workflow and IaC tool of choice.
 
 ## What are AWS Proton and AWS CodeBuild?
 

diff --git a/content/blog/celebrating-20k-stars/index.md b/content/blog/celebrating-20k-stars/index.md
@@ -19,7 +19,7 @@ Since its inception, Pulumi's vision has been rooted in enabling teams to build
 
 ## Fueled by Community Contributions
 
-Over the past 7 years, the Pulumi project has had 4,400+ contributors that made 75,000+ pull requests. Pulumi is depended upon by 6,600+ GitHub projects and supports over 160+ packages in the registry. It has been downloaded more than 100 million times by 170,000+ developers. In just the last month, Pulumi has been the most active Infrastructure as Code (IaC) open-source project compared to Terraform or OpenTofu. Pulumi has had 117 merged pull requests (67 TF, 83 OpenTofu), 82 closed issues (49 TF, 54 OpenTofu), and 53 new issues (27 TF, 29, OpenTofu).
+Over the past 7 years, the Pulumi project has had 4,400+ contributors that made 75,000+ pull requests. Pulumi is depended upon by 6,600+ GitHub projects and supports over 160+ packages in the registry. It has been downloaded more than 100 million times by 170,000+ developers. In just the last month, Pulumi has been the most active infrastructure as code (IaC) open-source project compared to Terraform or OpenTofu. Pulumi has had 117 merged pull requests (67 TF, 83 OpenTofu), 82 closed issues (49 TF, 54 OpenTofu), and 53 new issues (27 TF, 29, OpenTofu).
 
 ## Notable Features and Milestones
 

diff --git a/content/blog/cloud-engineering-fuels-startup-innovation/index.md b/content/blog/cloud-engineering-fuels-startup-innovation/index.md
@@ -50,7 +50,7 @@ Cloud engineering is a central character in the next chapter of how the modern c
 
 ## Panther Labs
 
-Panther Labs helps modern security teams build world-class detection and response pipelines using code and automation, developer-friendly workflows, and big data primitives. Its Platform Team is responsible for a large, complex serverless architecture on AWS. Because of the limitations of its legacy Infrastructure-as-Code (IaC) tool, the team was unable to manage and scale its cloud infrastructure with the speed and automation that the company needed to support its fast-growing business. After comparing different alternatives, Panther Labs decided to migrate to the Pulumi Cloud Engineering Platform. Pulumi increased the company’s deployment speeds by up to 10x, reduced the size of its infrastructure codebase by >50%, and enabled its developers to adopt cloud engineering best practices to deliver its cloud applications faster and more reliably.
+Panther Labs helps modern security teams build world-class detection and response pipelines using code and automation, developer-friendly workflows, and big data primitives. Its Platform Team is responsible for a large, complex serverless architecture on AWS. Because of the limitations of its legacy infrastructure-as-code (IaC) tool, the team was unable to manage and scale its cloud infrastructure with the speed and automation that the company needed to support its fast-growing business. After comparing different alternatives, Panther Labs decided to migrate to the Pulumi Cloud Engineering Platform. Pulumi increased the company’s deployment speeds by up to 10x, reduced the size of its infrastructure codebase by >50%, and enabled its developers to adopt cloud engineering best practices to deliver its cloud applications faster and more reliably.
 
 [![Pulumi vs. DSL](pulumi_v_cf.png)](/case-studies/panther-labs/)
 

diff --git a/content/blog/cloud-engineering-the-future-is-now/index.md b/content/blog/cloud-engineering-the-future-is-now/index.md
@@ -27,7 +27,7 @@ In the current cloud engineering landscape, we will continue to see movement tow
 
 The cloud engineering panel included Justin Fitzhugh, Dana Lawson, VP of Engineering at GitHub, Charity Majors, CTO at Honeycomb, and was moderated by Kat Cosgrove, Developer Advocate at JFrog. The session, titled "Your Peers," discussed the future of cloud engineering.
 
-When planning for the future of modern cloud applications, the panel agreed that the industry would continue to iterate and evolve away from domain specific languages, DSLs, and towards software engineering practices for infrastructure. They also agreed that while **Go** would be the most popular language for Infrastructure as Code, Ruby and JavaScript will also continue to be key languages.
+When planning for the future of modern cloud applications, the panel agreed that the industry would continue to iterate and evolve away from domain specific languages, DSLs, and towards software engineering practices for infrastructure. They also agreed that while **Go** would be the most popular language for infrastructure as code, Ruby and JavaScript will also continue to be key languages.
 
 Cloud engineering personas will change as new technologies such as the Internet of Things, availability of 5G, orchestration, edge computing, and future network APIs roll out. Cloud engineers should continue to focus on containers and what goes into applications. Knowing the entire lifecycle of their application from development to production is a must for cloud engineers. It underlies the concept of a single persona that can use services to compose development and services. Ultimately, the job of the cloud engineer is to reduce complexity and reduce friction in the pipeline by using patterns as needed and building platforms and tools consistently.
 

diff --git a/content/blog/cloud-systems-part-one/index.md b/content/blog/cloud-systems-part-one/index.md
@@ -40,7 +40,7 @@ The simplest website you can build is a static site. That means no web server, j
 
 - NodeJS (optional if you want to preview the site locally)
 
-There are a lot of ways to provision an S3 bucket and set its permissions, but for this I’m going to use Pulumi, an Infrastructure as Code tool that allows you to provision, configure, and deploy a variety of cloud services and tools programmatically, without learning a new language. That way, we can stay in our code, and the syntax will be more familiar for developers. It also saves us the headache of going through the AWS Console. All of the code for this, both the website and the infrastructure code, can be found in the [GitHub repository](https://github.com/katcosgrove/cloud-systems-101) for the series, although I'll be walking you through everything here too.
+There are a lot of ways to provision an S3 bucket and set its permissions, but for this I’m going to use Pulumi, an infrastructure as code tool that allows you to provision, configure, and deploy a variety of cloud services and tools programmatically, without learning a new language. That way, we can stay in our code, and the syntax will be more familiar for developers. It also saves us the headache of going through the AWS Console. All of the code for this, both the website and the infrastructure code, can be found in the [GitHub repository](https://github.com/katcosgrove/cloud-systems-101) for the series, although I'll be walking you through everything here too.
 
 ## Building a Static Site