prime context

Co-authored-by: Andrew McKnight <[email protected]>

Author: BYK

develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx

@@ -301,7 +301,10 @@ named "lockstep sampling" where the profiling samples occur at the same frequenc
 application. Ideally, the samples should be much more frequent than any cycles in the application, or
 at random intervals, so that the chance it occurs in any particular operation is proportional to the
 amount of time that operation takes. But this is often not feasible, so the next best thing is to use
-a sampling rate that doesn't coincide with the likely frequency of program cycles.
+a sampling rate that doesn't coincide with the likely frequency of program cycles. 
+
+We also chose 101 for its primality, whereas 1 below 100–99–is evenly divisible by several 
+smaller numbers, which could lead to similar lockstep behavior.
 
 This explanation is an excerpt from [this awesome StackOverflow answer](https://stackoverflow.com/a/45471031/1181370)
 which has more details and a nice analogy for the issue.