X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fcompiler.sgml;h=e66bca33ba61da9496f6b864c1ebb1bb980d3414;hb=a09b213e5812edd1ef3e88c18bde6bd1294da547;hp=18c797a990245240cde9175c0e8763135568632f;hpb=e167549e2b05a51b1a4c3ca7a4fafe1a0482cba3;p=sbcl.git

diff --git a/doc/compiler.sgml b/doc/compiler.sgml
index 18c797a..e66bca3 100644
--- a/doc/compiler.sgml
+++ b/doc/compiler.sgml
@@ -721,7 +721,7 @@ interpretation, and setting <parameter>safety</> less than
 compiler's decision whether to inline operations, which tend to
 increase the size of programs. Use the value <literal>0</> with
 caution, since it can cause the compiler to inline operations so
-promiscuously that the net effect is to slow the program by causing
+indiscriminately that the net effect is to slow the program by causing
 cache misses or swapping.</para>
 
 <!-- FIXME: old CMU CL compiler policy, should perhaps be adapted
@@ -790,7 +790,7 @@ _
 _\item[\code{space}] \cindex{space optimization quality}How much space
 _  the compiled code should take up.  Inline expansion is mostly
 _  inhibited when \code{space} is greater than \code{speed}.  A value
-_  of \code{0} enables promiscuous inline expansion.  Wide use of a
+_  of \code{0} enables indiscriminate inline expansion.  Wide use of a
 _  \code{0} value is not recommended, as it may waste so much space
 _  that run time is slowed.  \xlref{inline-expansion} for a discussion
 _  of inline expansion.