From 036f62e99adb49720fd7f69b9f153ac87236004b Mon Sep 17 00:00:00 2001
From: Mendon Kissling <59585235+mendonk@users.noreply.github.com>
Date: Tue, 28 Oct 2025 13:43:45 -0400
Subject: [PATCH] Apply suggestion from @aimurphy

Co-authored-by: April I. Murphy <36110273+aimurphy@users.noreply.github.com>
---
 docs/docs/get-started/what-is-openrag.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/docs/get-started/what-is-openrag.mdx b/docs/docs/get-started/what-is-openrag.mdx
index aec21cdb..e84e9fef 100644
--- a/docs/docs/get-started/what-is-openrag.mdx
+++ b/docs/docs/get-started/what-is-openrag.mdx
@@ -93,7 +93,8 @@ This equates to approximately 2.4 documents per second.
 You can generally expect equal or better performance on developer laptops and significantly faster on servers.
 Throughput scales with CPU cores, memory, storage speed, and configuration choices such as embedding model, chunk size and overlap, and concurrency.
 
-The 12 errors (~1.1%) were file‑specific and did not stop the pipeline.
+This test returned 12 errors (approximately 1.1%).
+All errors were file‑specific, and they didn't stop the pipeline.
 
 Ingestion dataset: