[PATCH 1/2] admin: Refer to processing order as "limited" rather than none

[Peter Hilber <peter.hilber@opensynergy.com>]

The non-normative section says that administration virtqueue commands
"will be consumed with no order constraints". But actually, the
requirements stipulate a total order for all commands in the same
virtqueue:

	The device MUST process commands on a given administration virtqueue
	in the order in which they are queued.

	If multiple administration virtqueues have been configured,
	device MAY process commands on distinct virtqueues with
	no order constraints.

Rather than "no order constraints", refer to "limited order constraints"
to not mislead the reader.

Fixes: bf1d6b0d24ae8 ("admin: conformance clauses")
Signed-off-by: Peter Hilber <peter.hilber@opensynergy.com>
---
 admin.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/admin.tex b/admin.tex
index 0803c269e5c4..54f18c255fb0 100644
--- a/admin.tex
+++ b/admin.tex
@@ -458,7 +458,7 @@ \section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Devic
 virtqueue, and they are used by the device on that same
 virtqueue. It is the responsibility of the driver to ensure
 strict request ordering for commands, because they will be
-consumed with no order constraints.  For example, if consistency
+consumed with limited order constraints.  For example, if consistency
 is required then the driver can wait for the processing of a
 first command by the device to be completed before submitting
 another command depending on the first one.
-- 
2.40.1