[PATCH] format: replace "- i.e." with ", i.e.,"

["Michael S. Tsirkin" <mst@redhat.com>]

This seems to be preferred by native speakers, and
seems just as effective as a sentence device.

Fixes: https://issues.oasis-open.org/browse/VIRTIO-171
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 content.tex     | 12 ++++++------
 packed-ring.tex |  4 ++--
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/content.tex b/content.tex
index ede0ef6..4180296 100644
--- a/content.tex
+++ b/content.tex
@@ -277,15 +277,15 @@ virtqueues\footnote{For example, the simplest network device has one virtqueue f
 transmit and one for receive.}.
 
 Driver makes requests available to device by adding
-an available buffer to the queue - i.e. adding a buffer
+an available buffer to the queue, i.e., adding a buffer
 describing the request to a virtqueue, and optionally triggering
-a driver event - i.e. sending an available buffer notification
+a driver event, i.e., sending an available buffer notification
 to the device.
 
 Device executes the requests and - when complete - adds
-a used buffer to the queue - i.e. lets the driver
+a used buffer to the queue, i.e., lets the driver
 know by marking the buffer as used. Device can then trigger
-a device event - i.e. send a used buffer notification to the driver.
+a device event, i.e., send a used buffer notification to the driver.
 
 Device reports the number of bytes it has written to memory for
 each buffer it uses. This is referred to as ``used length''.
@@ -489,8 +489,8 @@ of a device are live once the device has been reset.
 
 \drivernormative{\subsection}{Device Cleanup}{General Initialization And Device Operation / Device Cleanup}
 
-A driver MUST NOT alter virtqueue entries for exposed buffers -
-i.e. buffers which have been
+A driver MUST NOT alter virtqueue entries for exposed buffers,
+i.e., buffers which have been
 made available to the device (and not been used by the device)
 of a live virtqueue.
 
diff --git a/packed-ring.tex b/packed-ring.tex
index e10d87f..caf47a5 100644
--- a/packed-ring.tex
+++ b/packed-ring.tex
@@ -65,12 +65,12 @@ in which their processing is complete.
 
 The Device Event Suppression data structure is write-only by the
 device. It includes information for reducing the number of
-device events - i.e. sending fewer available buffer notifications
+device events, i.e., sending fewer available buffer notifications
 to the device.
 
 The Driver Event Suppression data structure is read-only by the
 device. It includes information for reducing the number of
-driver events - i.e. sending fewer used buffer notifications 
+driver events, i.e., sending fewer used buffer notifications 
 to the driver.
 
 \subsection{Driver and Device Ring Wrap Counters}
-- 
MST