From 46093c1c368c291cd3026b7ac29356915939ea9e Mon Sep 17 00:00:00 2001
From: David Ashpole <dashpole@google.com>
Date: Wed, 22 Feb 2023 14:58:27 +0000
Subject: [PATCH] wording

---
 specification/metrics/supplementary-guidelines.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/specification/metrics/supplementary-guidelines.md b/specification/metrics/supplementary-guidelines.md
index 10b435db0c1..d8f271f8854 100644
--- a/specification/metrics/supplementary-guidelines.md
+++ b/specification/metrics/supplementary-guidelines.md
@@ -500,8 +500,9 @@ receiver's understanding of these events.
 
 Consider whether the SDK maintains individual timestamps for the
 individual stream, or just one per process.  In this example, where a
-thread can die and restart start counting page faults from zero, the
-valid behaviors at T<sub>5</sub> and T<sub>6</sub> are:
+process can die and restart, it starts counting page faults from zero.
+In this case, the valid behaviors at T<sub>5</sub> and T<sub>6</sub>
+are:
 
 1. If all streams in the process share a start time, and the SDK is
    not required to remember all past streams: the thread restarts with