[ja_JP] Architecture Reference / Read-Write set semantics

[shimos]

Original HTML: https://hyperledger-fabric.readthedocs.io/en/release-2.5/readwrite.html
Original Source: https://github.com/hyperledger/fabric/blob/e1e8e2e52aa4fc543360d245fe6554a0eaf81183/docs/source/readwrite.rst

diff --git a/docs/source/readwrite.rst b/docs/source/readwrite.rst
index 829a213a0..32d0d23bb 100644
--- a/docs/source/readwrite.rst
+++ b/docs/source/readwrite.rst
@@ -117,14 +117,14 @@ shows the snapshot of the world state against which the transactions are
 simulated and the sequence of read and write activities performed by
 each of these transactions.
 
-::
+.. code-block:: none
 
     World state: (k1,1,v1), (k2,1,v2), (k3,1,v3), (k4,1,v4), (k5,1,v5)
     T1 -> Write(k1, v1'), Write(k2, v2')
-    T2 -> Read(k1), Write(k3, v3')
+    T2 -> Read(k1,1), Write(k3, v3')
     T3 -> Write(k2, v2'')
-    T4 -> Write(k2, v2'''), read(k2)
-    T5 -> Write(k6, v6'), read(k5)
+    T4 -> Write(k2, v2'''), read(k2,1)
+    T5 -> Write(k6, v6'), read(k5,1)
 
 Now, assume that these transactions are ordered in the sequence of
 T1,..,T5 (could be contained in a single block or different blocks)
@@ -133,18 +133,18 @@ T1,..,T5 (could be contained in a single block or different blocks)
    Further, the tuple of keys ``k1`` and ``k2`` in the world state are
    updated to ``(k1,2,v1'), (k2,2,v2')``
 
-2. ``T2`` fails validation because it reads a key, ``k1``, which was
-   modified by a preceding transaction - ``T1``
+2. ``T2`` fails validation because it reads key ``k1`` of version 1 but ``k1``
+   in the world state has progressed to version 2
 
-3. ``T3`` passes the validation because it does not perform a read.
-   Further the tuple of the key, ``k2``, in the world state is updated
-   to ``(k2,3,v2'')``
+3. ``T3`` passes the validation because it does not perform a read.  Further 
+   the tuple of the key, ``k2``, in the world state is updated to 
+   ``(k2,3,v2'')``
 
-4. ``T4`` fails the validation because it reads a key, ``k2``, which was
-   modified by a preceding transaction ``T1``
+4. ``T4`` fails the validation because it reads key ``k2`` of version 1 but
+   ``k2`` in the world state has progressed to version 3
 
-5. ``T5`` passes validation because it reads a key, ``k5,`` which was
-   not modified by any of the preceding transactions
+5. ``T5`` passes validation because it reads a key, ``k5``, which is still on
+   version 1
 
 **Note**: Transactions with multiple read-write sets are not yet supported.