summaryrefslogtreecommitdiffstats
path: root/lib/libm/common_source/exp.3
diff options
context:
space:
mode:
Diffstat (limited to 'lib/libm/common_source/exp.3')
-rw-r--r--lib/libm/common_source/exp.38
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/libm/common_source/exp.3 b/lib/libm/common_source/exp.3
index 3c8a5aa..ae54b7f 100644
--- a/lib/libm/common_source/exp.3
+++ b/lib/libm/common_source/exp.3
@@ -96,7 +96,7 @@ of
to the exponent
.Ar y .
.Sh ERROR (due to Roundoff etc.)
-exp(x), log(x), expm1(x) and log1p(x) are accurate to within
+exp(x), log(x), expm1(x) and log1p(x) are accurate to within
an
.Em up ,
and log10(x) to within about 2
@@ -231,10 +231,10 @@ infinite or \*(Na) before computing x**0 cannot care
whether 0**0 = 1 or not.
Any program that depends
upon 0**0 to be invalid is dubious anyway since that
-expression's meaning and, if invalid, its consequences
+expression's meaning and, if invalid, its consequences
vary from one computer system to another.
.It
-Some Algebra texts (e.g. Sigler's) define x**0 = 1 for
+Some Algebra texts (e.g. Sigler's) define x**0 = 1 for
all x, including x = 0.
This is compatible with the convention that accepts a[0]
as the value of polynomial
@@ -252,7 +252,7 @@ The reason for setting 0**0 = 1 anyway is this:
If x(z) and y(z) are
.Em any
functions analytic (expandable
-in power series) in z around z = 0, and if there
+in power series) in z around z = 0, and if there
x(0) = y(0) = 0, then x(z)**y(z) \(-> 1 as z \(-> 0.
.Ed
.It
OpenPOWER on IntegriCloud