From cb27bf424fdec2ad98add8745da92e7a7b9346b5 Mon Sep 17 00:00:00 2001
From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com>
Date: Tue, 27 Jan 2026 00:05:10 +0000
Subject: [PATCH] Fix typos in "I Have No Mouth, and I Must Scream" blog post
---
fern/docs/technical/i-must-scream.mdx | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fern/docs/technical/i-must-scream.mdx b/fern/docs/technical/i-must-scream.mdx
index 122cdd7..4a32024 100644
--- a/fern/docs/technical/i-must-scream.mdx
+++ b/fern/docs/technical/i-must-scream.mdx
@@ -58,7 +58,7 @@ Our customers often configure Promptless themselves, and sometimes they'll make
-This often helps us deliver a delightful customer experience—allowing us to provide a white-glove support process with Promptless's proactive help. Promptless In this case we were able to intervene with them to fix their set up before they realized anything was wrong.
+This often helps us deliver a delightful customer experience—allowing us to provide a white-glove support process with Promptless's proactive help. In this case we were able to intervene with them to fix their set up before they realized anything was wrong.
### It found bugs with its tools
@@ -72,7 +72,7 @@ This one was particularly insidious—git was returning success exit codes while
### It helped us get ahead of customer frustration
-Sometimes the will escalate to us something when it's clear that it screwed up earlier. In this case, a customer asked in Slack why their PR had unexpected files. Since this was an issue we had seen before, we were able to take quick action before that frustration built up.
+Sometimes the agent will escalate to us something when it's clear that it screwed up earlier. In this case, a customer asked in Slack why their PR had unexpected files. Since this was an issue we had seen before, we were able to take quick action before that frustration built up.
@@ -90,7 +90,7 @@ This was the result of a software bug that we were able to easily fix, but our t
### Bonus: It caught a critical bugs in our code
-This one we didn't expect. Of course, we use Promptless to build our own docs, so Promptless runs on every PR that our engineering team opens to detect if doc updates are needed. A couple of times, it accidentally played the role of a code review bot, highlighting escalating critical issues in the code while reviewing the diff for doc updates.
+This one we didn't expect. Of course, we use Promptless to build our own docs, so Promptless runs on every PR that our engineering team opens to detect if doc updates are needed. A couple of times, it accidentally played the role of a code review bot, escalating critical issues in the code while reviewing the diff for doc updates.
