clarify how consistent snapshots are used for root rotation

Signed-off-by: Trishank K Kuppusamy <[email protected]>

Author: trishankatdatadog

tuf-spec.md

@@ -1009,7 +1009,8 @@ repo](https://github.com/theupdateframework/specification/issues).
   Since it may now be signed using entirely different keys, the client must
   somehow be able to establish a trusted line of continuity to the latest set
   of keys (see Section 6.1). To do so, the client MUST download intermediate
-  root metadata files, until the latest available one is reached.
+  root metadata files, until the latest available one is reached. Therefore, it
+  must temporarily turn on consistent snapshots.
 
   * **1.1**. Let N denote the version number of the trusted root metadata file.
 
@@ -1061,6 +1062,9 @@ repo](https://github.com/theupdateframework/specification/issues).
   paper](https://ssl.engineering.nyu.edu/papers/kuppusamy-mercury-usenix-2017.pdf)
   for more details.
 
+  * **1.10**. **Set whether consistent snapshots are used as per the trusted
+  root metadata file** (see Section 4.3).
+
 **2**. **Download the timestamp metadata file**, up to Y number of bytes
 (because the size is unknown.) The value for Y is set by the authors of the
 application using TUF. For example, Y may be tens of kilobytes. The filename