From 3a7719016f0b081ac43203e9137796265f6a037b Mon Sep 17 00:00:00 2001
From: rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>
Date: Wed, 12 Feb 2014 03:15:33 +0000
Subject: Feedback #5: Applied.

As per minutes:
	https://lists.oasis-open.org/archives/virtio/201402/msg00121.html

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@236 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
---
 introduction.tex | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'introduction.tex')

diff --git a/introduction.tex b/introduction.tex
index 83b01f0..8e08d02 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -13,14 +13,15 @@ inter-guest communication) requires copying.
 }
 
   Efficient: Virtio devices consist of rings of descriptors
-  for input and output, which are neatly separated to avoid cache
+  for both input and output, which are neatly laid out to avoid cache
   effects from both driver and device writing to the same cache
   lines.
 
   Standard: Virtio makes no assumptions about the environment in which
-  it operates, beyond supporting the bus attaching the device.  Virtio
+  it operates, beyond supporting the bus to which device is attached.
+  In this specification, virtio
   devices are implemented over PCI and other buses, and earlier drafts
-  been implemented on other buses not included in this spec.
+  have been implemented on other buses not included here.
 \footnote{The Linux implementation further separates the PCI virtio code
 from the specific virtio drivers: these drivers are shared with
 the non-PCI implementations (currently lguest and S/390).
-- 
cgit v1.2.3

