a minor changes to improve the readability

[iPazooki]

In this ReturnsExtensions.cs file, we are using if (!(minDelay < maxDelay)) which could be changed to if (minDelay >= maxDelay) which is more readable.

[stakx]

@iPazooki, it's a very small change, so probably doesn't warrant extended discussion, just a few points on this:

• I suspect the intention behind the form !(minDelay < maxDelay) might have been to state the expectation (minDelay < maxDelay must hold), and to then use negation (!) to hint at its violation.

• Some mathematically inclined people may also prefer the < operator when dealing with numeric intervals or ranges, so e.g. when translating the mathematical constraint a ≤ x < b to a language like C#, they might prefer a <= x && x < b over x >= a && x < b. (See e.g. Times.cs for examples of this.)

That being said, yes, the present condition is a little unwieldy. There's no reason why it absolutely has to stay that way.

[kzu]

Fixed in #1422