summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhornet <hornet@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-07-23 11:57:56 +0000
committerhornet <hornet@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-07-23 11:57:56 +0000
commit8a3d1521930d9dacca4972d591ff720d614e37e8 (patch)
tree5ec13194d5217dfb74da4c68a1837bc03b44367e
parent3766328a09ef9085ce209f63bc142639f868ce71 (diff)
VIRTIO-111: Fix minor typos
Fix minor typos as reported in ARM's feedback. Signed-off-by: Pawel Moll <pawel.moll@arm.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@406 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--content.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/content.tex b/content.tex
index f2a9e79..0f7326e 100644
--- a/content.tex
+++ b/content.tex
@@ -168,7 +168,7 @@ space.
\drivernormative{\subsection}{Device Configuration Space}{Basic Facilities of a Virtio Device / Device Configuration Space}
Drivers MUST NOT assume reads from
-fields greater than 32 bits wide are atomic, nor reads from
+fields greater than 32 bits wide are atomic, nor are reads from
multiple fields: drivers SHOULD read device configuration space fields like so:
\begin{lstlisting}
@@ -216,7 +216,7 @@ The correct endian-ness is documented for each device.
Legacy devices did not have a configuration generation field, thus are
susceptible to race conditions if configuration is updated. This
-effects the block \field{capacity} (see \ref{sec:Device Types /
+affects the block \field{capacity} (see \ref{sec:Device Types /
Block Device / Feature bits / Device configuration layout}) and
network \field{mac} (see \ref{sec:Device Types / Network Device /
Device configuration layout}) fields;
@@ -684,7 +684,7 @@ Device Initialization / Read feature bits} Read device feature bits, and write t
understood by the OS and driver to the device. During this step the
driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device before accepting it.
-\item\label{itm:General Initialization And Device Operation / Device Initialization / Set FEATURES-OK} Set the FEATURES_OK status bit. The driver MUST not accept
+\item\label{itm:General Initialization And Device Operation / Device Initialization / Set FEATURES-OK} Set the FEATURES_OK status bit. The driver MUST NOT accept
new feature bits after this step.
\item\label{itm:General Initialization And Device Operation / Device Initialization / Re-read FEATURES-OK} Re-read \field{device status} to ensure the FEATURES_OK bit is still
@@ -3632,7 +3632,7 @@ compartibility.
\drivernormative{\subparagraph}{Setting Offloads State}{Device Types / Network Device / Device Operation / Control Virtqueue / Offloads State Configuration / Setting Offloads State}
-A driver MUST NOT enable a offload for which the appropriate feature
+A driver MUST NOT enable an offload for which the appropriate feature
has not been negotiated.
\subparagraph{Legacy Interface: Setting Offloads State}\label{sec:Device Types / Network Device / Device Operation / Control Virtqueue / Offloads State Configuration / Setting Offloads State / Legacy Interface: Setting Offloads State}