diff options
| author | Ian Lewis <ianlewis@google.com> | 2020-03-12 18:14:31 -0400 |
|---|---|---|
| committer | Zach Koopmans <zkoopmans@google.com> | 2020-03-12 15:48:05 -0700 |
| commit | 14c1917b70a513ae71191c7fa7f24be62b1789a9 (patch) | |
| tree | ef7540d0e4132c637a6ab3a25b8437f3e6246910 /content/docs | |
| parent | 95535eca245cfa6de69c42a04a6f6b265f22e014 (diff) | |
Fix grammar mistake in Performance Guide
Fixes #147
Diffstat (limited to 'content/docs')
| -rw-r--r-- | content/docs/architecture_guide/performance.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/content/docs/architecture_guide/performance.md b/content/docs/architecture_guide/performance.md index 43ee5ada4..b33b512f0 100644 --- a/content/docs/architecture_guide/performance.md +++ b/content/docs/architecture_guide/performance.md @@ -25,9 +25,9 @@ Second, as gVisor is an independent implementation of the system call surface, many of the subsystems or specific calls are not as optimized as more mature implementations. A good example here is the network stack, which is continuing to evolve but does not support all the advanced recovery mechanisms offered by -other stacks and is less CPU efficient. This an **implementation cost** and is -distinct from **structural costs**. Improvements here are ongoing and driven by -the workloads that matter to gVisor users and contributors. +other stacks and is less CPU efficient. This is an **implementation cost** and +is distinct from **structural costs**. Improvements here are ongoing and driven +by the workloads that matter to gVisor users and contributors. This page provides a guide for understanding baseline performance, and calls out distint **structural costs** and **implementation costs**, highlighting where |