From 4750828c26192edcf08fc13fe01834fa667f5165 Mon Sep 17 00:00:00 2001 From: Bob Burger Date: Fri, 13 May 2016 08:49:00 -0400 Subject: [PATCH] fixed misspellings in comments original commit: 44370695fbfe86fbf1cd5dd115a2289626604796 --- c/number.c | 2 +- s/print.ss | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/c/number.c b/c/number.c index 5c9d043163..22a00640ca 100644 --- a/c/number.c +++ b/c/number.c @@ -1163,7 +1163,7 @@ static double floatify_normalize(p, e, sign, sticky) bigit *p; iptr e; IBOOL sig if (round) { mlow += 1; if (e == 0 && mlow == hidden_bit) { - e = 1; /* squeeking into lowest normalized spot */ + e = 1; /* squeaking into lowest normalized spot */ } else if (mlow == hidden_bit * 2) { /* don't bother with mlow = mlow >> 1 since hidden bit and up are ignored after this */ e += 1; diff --git a/s/print.ss b/s/print.ss index edaa5a7e19..2c1ae350a4 100644 --- a/s/print.ss +++ b/s/print.ss @@ -510,7 +510,7 @@ floating point returns with (1 0 -1 ...). ; words, a digit is insignificant if incrementing the preceding ; digit does not cause the number to fall outside the rounding ; range of v." For 1e23, which falls exactly midway between two - ; fp numbers and reads as the next one down due to "unbiasd rounding", + ; fp numbers and reads as the next one down due to "unbiased rounding", ; if we add even a single 1 digit way down, we're pushed to the next ; higher (when read). For example: ; 100000000000000000000000.000000000000000000000000000000000000001