Skip to content

Commit 418e5d2

Browse files
iHiDBethanyG
andauthored
[meltdown-mitigation] Be super explicit (#3501)
* [meltdown-mitigation] Be super explicit It seems a few people get stuck on this (maybe because the sentence is quite long and for non-native speakers it's tough to parse - e.g. "plus or minus 10%" could feel confusing maybe?) so I thought maybe we become SUPER explicit. * Update exercises/concept/meltdown-mitigation/.docs/instructions.md --------- Co-authored-by: BethanyG <[email protected]>
1 parent 49cc1ec commit 418e5d2

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

exercises/concept/meltdown-mitigation/.docs/instructions.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,9 +61,7 @@ Implement the function called `fail_safe()`, which takes 3 parameters: `temperat
6161
- If `temperature * neutrons_produced_per_second` < 90% of `threshold`, output a status code of 'LOW'
6262
indicating that control rods must be removed to produce power.
6363

64-
- If `temperature * neutrons_produced_per_second` are within plus or minus 10% of the `threshold`
65-
the reactor is in _criticality_ and the status code of 'NORMAL' should be output, indicating that the
66-
reactor is in optimum condition and control rods are in an ideal position.
64+
- If the value `temperature * neutrons_produced_per_second` is within 10% of the `threshold` (so either 0-10% less than the threshold, at the threshold, or 0-10% greater than the threshold), the reactor is in _criticality_ and the status code of 'NORMAL' should be output, indicating that the reactor is in optimum condition and control rods are in an ideal position.
6765

6866
- If `temperature * neutrons_produced_per_second` is not in the above-stated ranges, the reactor is
6967
going into meltdown and a status code of 'DANGER' must be passed to immediately shut down the reactor.

0 commit comments

Comments
 (0)