Skip to content

Commit f3accee

Browse files
committed
Minor typos/wording in float-next-up-down.
1 parent f787513 commit f3accee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/0000-float-next-up-down.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Answering this question has multiple uses:
2929
range, you need to be able to enumerate them. One might also want to check if
3030
and how your function fails just outside its supported range.
3131

32-
- Exlusive ranges. If you want to ensure a variable lies within an exclusive
32+
- Exclusive ranges. If you want to ensure a variable lies within an exclusive
3333
range, these functions can help. E.g. to ensure that `x` lies within [0, 1)
3434
one can write `x.clamp(0.0, 1.0.next_down())`.
3535

@@ -178,7 +178,7 @@ pub const fn next_down(self) -> Self {
178178
[drawbacks]: #drawbacks
179179

180180
Two more functions get added to `f32` and `f64`, which may be considered
181-
cluttered by some.
181+
already cluttered by some.
182182

183183
Additionally, there is a minor pitfall regarding signed zero. Repeatedly calling
184184
`next_up` on a negative number will iterate over all values above it, with the

0 commit comments

Comments
 (0)