Rename existing one to Standard All-Measurements Report Definition.

Signed-off-by: Jiewen Yao <[email protected]>

Author: jyao1

doc/standard_measurement_report.md

@@ -13,9 +13,9 @@ SPDM Requester and consumed by a Verifier while all agents are operating in prod
 particular, a production Verifier may only support a measurement report of this type and can point
 to this document to advertise that restriction to other agents.
 
-## Standard Measurement Report Definition
+## Standard All-Measurements Report Definition
 
-The standard measurement report is a byte buffer that consists of the L1/L2 transcript along with
+The standard all-measurements report is a byte buffer that consists of the L1/L2 transcript along with
 the signature over the transcript if the Responder supports signing. It is comprised of a single
 `GET_MEASUREMENTS` request and a single `MEASUREMENTS` response.
 
@@ -31,28 +31,28 @@ request has the following properties:
 * For SPDM 1.3 and later, `NewMeasurementRequested` is not set.
     * This requests the current state of the Responder and not its future state.
 
-## Rationale
+### Rationale
 
-### Single Request and Response
+#### Single Request and Response
 
 Capturing all measurements in a single response provides an atomic snapshot of the state of the
 Responder at a specific point in time. As such, a Verifier need not have to reason about the state
 of the Responder through multiple measurement requests and responses with a possibly unknown amount
 of time between each message.
 
-### Byte Buffer
+#### Byte Buffer
 
 A raw byte buffer allows the Verifier to verify the signature, if supported by the Responder, over
 the rest of the measurement report without any transformation of data.
 
-### `RawBitStreamRequested`
+#### `RawBitStreamRequested`
 
 In the interest of message size, `RawBitStreamRequested` is not set, indicating preference, when
 given the opportunity, for hashed measurements instead of raw measurements. In particular, certain
 raw measurements may only be examined for the purpose of debugging, whereas the hashed measurements
 are evaluated by the Verifier while the Responder is in production.
 
-### `NewMeasurementRequested`
+#### `NewMeasurementRequested`
 
 Presumably the Verifier evaluates the current state of the Responder and not its future state. As
 such `NewMeasurementRequested` is not set.