random: update docs

The documentation incorrectly stated that we fall back to crypto/rand,
while we actually used math/rand. In practice, the question of what
source of randomness we are using is actually quite subtle.

Just mention that this source of randomness integrates with the
platform and don't specify what we do exactly for the fallback.

Author: lmb

random/random.go

@@ -1,14 +1,13 @@
 //go:build !no_antithesis_sdk
 
-// Package random requests both structured and unstructured randomness from the Antithesis environment. is part of the [Antithesis Go SDK], which enables Go applications to integrate with the [Antithesis platform].
+// Package random is part of the [Antithesis Go SDK], which enables Go applications to integrate with the [Antithesis platform].
 //
-// These functions should not be used to seed a conventional PRNG, and should not have their return values stored and used to make a decision at a later time. Doing either of these things makes it much harder for the Antithesis platform to control the history of your program's execution, and also makes it harder for Antithesis to learn which inputs provided at which times are most fruitful. Instead, you should call a function from the random package every time your program or [workload] needs to make a decision, at the moment that you need to make the decision.
+// Use these functions to generate pseudo-random data using [math/rand.Rand] while providing feedback to the platform.
 //
-// These functions are also safe to call outside the Antithesis environment, where they will fall back on values from [crypto/rand].
+// Avoid storing random values to make a decision at a later time, as this makes it much harder for the Antithesis platform to control the history of your program's execution.
 //
 // [Antithesis Go SDK]: https://antithesis.com/docs/using_antithesis/sdk/go/
 // [Antithesis platform]: https://antithesis.com
-// [workload]: https://antithesis.com/docs/getting_started/first_test/
 package random
 
 import (