From ac43159f18c668547c1148f15fcccb8c908c3347 Mon Sep 17 00:00:00 2001
From: Mendon Kissling <59585235+mendonk@users.noreply.github.com>
Date: Tue, 28 Oct 2025 13:43:34 -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 | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/docs/get-started/what-is-openrag.mdx b/docs/docs/get-started/what-is-openrag.mdx
index 19f89ba3..aec21cdb 100644
--- a/docs/docs/get-started/what-is-openrag.mdx
+++ b/docs/docs/get-started/what-is-openrag.mdx
@@ -87,7 +87,11 @@ The **OpenRAG Frontend** provides the user interface for interacting with the sy
 
 ## Performance expectations
 
-On a local VM with 7 vCPUs and 8 GiB RAM, OpenRAG ingested ~5.03 GB across 1,083 files in ~42 minutes, or ~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.
+On a local VM with 7 vCPUs and 8 GiB RAM, OpenRAG ingested approximately 5.03 GB across 1,083 files in about 42 minutes.
+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.