@@ -60,7 +60,7 @@ public interface DatabaseClient {
6060 ReadContext singleUse ();
6161
6262 /**
63- * Returns a context in which a single read can be performed.
63+ * Returns a context in which a single read can be performed at the given timestamp bound .
6464 *
6565 * @param bound the timestamp bound at which to perform the read
6666 */
@@ -75,9 +75,9 @@ public interface DatabaseClient {
7575 ReadOnlyTransaction singleUseReadOnlyTransaction ();
7676
7777 /**
78- * Returns a read-only transaction context in which a single read or query can be performed. This
79- * method differs from {@link #singleUse(TimestampBound)} in that the read timestamp used may be
80- * inspected after the read has returned data or finished successfully.
78+ * Returns a read-only transaction context in which a single read or query can be performed at the
79+ * given timestamp bound. This method differs from {@link #singleUse(TimestampBound)} in that the
80+ * read timestamp used may be inspected after the read has returned data or finished successfully.
8181 *
8282 * @param bound the timestamp bound at which to perform the read
8383 */
@@ -93,8 +93,8 @@ public interface DatabaseClient {
9393
9494 /**
9595 * Returns a read-only transaction context in which a multiple reads and/or queries can be
96- * performed. All reads/queries will use the same timestamp, and the timestamp can be inspected
97- * after any read/query has returned data or finished successfully.
96+ * performed at the given timestamp bound . All reads/queries will use the same timestamp, and the
97+ * timestamp can be inspected after any read/query has returned data or finished successfully.
9898 *
9999 * <p>Note that the bounded staleness modes, {@link TimestampBound.Mode#MIN_READ_TIMESTAMP} and
100100 * {@link TimestampBound.Mode#MAX_STALENESS}, are not supported for multi-use read-only
0 commit comments