From 3982830328a869f612c22259f6f681d329e8a70d Mon Sep 17 00:00:00 2001
From: Artur Laksberg <1875734+arturl@users.noreply.github.com>
Date: Sat, 4 Jan 2025 12:19:36 -0800
Subject: [PATCH] Update content/blog/codegen-learnings/index.md

Co-authored-by: Gavin <57272374+thtmnisamnstr@users.noreply.github.com>
---
 content/blog/codegen-learnings/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/codegen-learnings/index.md b/content/blog/codegen-learnings/index.md
index 9e2135dfe92f..5ad9cf58ccf9 100644
--- a/content/blog/codegen-learnings/index.md
+++ b/content/blog/codegen-learnings/index.md
@@ -191,7 +191,7 @@ We observed that many generated TypeScript programs that fail to typecheck conta
 
 Monitoring these typechecking errors in production can also provide valuable insight into the quality of the RAG and even suggest specific solutions. For example, failure to typecheck a member-access expression is a likely indicator of a missing type schema (a recall problem) or a "wrong" schema brought in by an irrelevant document (a precision problem).
 
-Self-debugging can also be extended to include the `pulumi preview` command, which is a "dry run" operation before the actual deployment and can detect many real or potential problems such as destructive actions, incorrect configurations that cannot be detected at compile time, dependency conflicts and policy violations.
+Self-debugging can also be extended to include the `pulumi preview` command, which is a "dry run" operation before the actual deployment and can detect many real or potential problems such as destructive actions, incorrect configurations that cannot be detected at compile time, dependency conflicts, and policy violations.
 
 ## Running Pulumi code generator in production