diff options
Diffstat (limited to 'src/tools/lcc/doc/install.html')
| -rw-r--r-- | src/tools/lcc/doc/install.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/tools/lcc/doc/install.html b/src/tools/lcc/doc/install.html index 3cc59a8f..3410e8f1 100644 --- a/src/tools/lcc/doc/install.html +++ b/src/tools/lcc/doc/install.html @@ -722,7 +722,7 @@ C:\dist\lcc\4.1>copy %BUILDDIR%\bprint.exe \bin <h2><a NAME="bugs">Reporting Bugs</a></h2> <p>lcc is a large, complex program. We find and repair errors routinely. If you think that -you've found a error, follow the steps below, which are adapted from the instructions in +you've found an error, follow the steps below, which are adapted from the instructions in Chapter 1 of <cite>A Retargetable C Compiler: Design and Implementation</cite>. <ol> @@ -751,7 +751,7 @@ Chapter 1 of <cite>A Retargetable C Compiler: Design and Implementation</cite>. HREF="ftp://ftp.cs.princeton.edu/pub/lcc"><code>pub/lcc</code></a>. A <a HREF="ftp://ftp.cs.princeton.edu/pub/lcc/README"><code>README</code></a> file there gives acquistion details, and the <a HREF="../LOG"><code>LOG</code></a> file reports what errors - were fixed and when they were fixed. If you report a error that's been fixed, you might + were fixed and when they were fixed. If you report an error that's been fixed, you might get a canned reply.</li> <li>Send your program by electronic mail to <code>lcc-bugs@cs.princeton.edu</code>. Please send only valid C programs; put all remarks in C comments so that we can process reports |