From ff72925c55e5753cde479effd19d85e59073e82a Mon Sep 17 00:00:00 2001
From: Anand <19315039+sriv1211@users.noreply.github.com>
Date: Sat, 18 May 2019 22:57:50 +0100
Subject: [PATCH] Corrected typo

---
 content/docs/architecture_guide/performance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/architecture_guide/performance.md b/content/docs/architecture_guide/performance.md
index 1d3a060da..960058a19 100644
--- a/content/docs/architecture_guide/performance.md
+++ b/content/docs/architecture_guide/performance.md
@@ -231,7 +231,7 @@ the cost of VFS operations.
 {{< graph id="httpd100k" metric="transfer_rate" url="/performance/httpd100k.csv" title="perf.py http.httpd --connections=1 --connections=5 --connections=10 --connections=25 --runtime=runc --runtime=runsc" >}}
 
 The high costs of VFS operations can manifest in benchmarks that execute many
-such operations in the hot path for serviing requests, for example. The above
+such operations in the hot path for serving requests, for example. The above
 figure shows the result of using gVisor to serve small pieces of static content
 with predictably poor results. This workload represents `apache` serving a
 single file sized 100k from the container image to a client running