commit 48c11bb4f05a0e4af8ad4a0715340358d2a2e221
parent b2c3a8efa895ffd34886922b0de6c5e41a8a909e
Author: Christophe Coustet <christophe.coustet@meso-star.com>
Date: Fri, 16 Feb 2018 12:15:07 +0100
Fix some typos.
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kspectrum.html.in b/kspectrum.html.in
@@ -117,7 +117,7 @@ the obsessions of:</p>
<li>being able to resume interrupted runs: whether your PC crashes or Kspectrum
reaches the maximum computation time allowed by the cluster's queue, it will
- be possible to resume a interrupted computation instead of starting over from
+ be possible to resume an interrupted computation instead of starting over from
scratch: as in a video game, Kspectrum performs frequent backups of the
current run.</li>
</ul>
@@ -134,7 +134,7 @@ details.</p>
<p>You will have to download both the <code>.tgz</code> file and the
installation script, and place both files in the same directory. Then run the
installation script. This will uncompress the archive, compile and run a small
-program that will generate a example composition file (for Venus' atmosphere).
+program that will generate an example composition file (for Venus' atmosphere).
The installation script will also try to link Line-by-Line spectroscopic
databases to your new installation of Kspectrum, but will most probably fail if
you are not a frequent Kspectrum user, and you will have to read the
@@ -160,6 +160,6 @@ of failure can be fixed by editing the "Makefile" file in order to check
compilation options (and more specifically options related to the target
architecture and optimisations). Whenever you modify a source file, you can
re-compile using the <code>make all</code> command. But in the case you have to
-modify a include file, you will have to erase all existing object files first
+modify an include file, you will have to erase all existing object files first
using the <code>make clean</code> command, before recompiling from scratch
using the <code>make all</code> command again.</p>
