fix internal links in 2004/vik1/index.html
Fix indentation of code blocks. Ran `bin/readme2index.sh -v 1 2004/vik1` to perform the above.
This commit is contained in:
1 parent
caf859b823
commit
10cffba634
2 files changed
+16
-16
No files matched your search
+8
-8
@@ -87,20 +87,20 @@ order as described below.
|
|||||||
|
|
||||||
a - Advanced racing in a winter landscape
|
a - Advanced racing in a winter landscape
|
||||||
d - Racing in at night in the dark
|
d - Racing in at night in the dark
|
||||||
# - Race track selection 1-3 are valid numbers
|
# - Race track selection 1-3 are valid numbers
|
||||||
```
|
```
|
||||||
|
|
||||||
Here are a few examples:
|
Here are a few examples:
|
||||||
|
|
||||||
```
|
```
|
||||||
Command line: Description:
|
Command line: Description:
|
||||||
|
|
||||||
$ ./vik1 Run track 1 at daytime in the summer
|
./vik1 Run track 1 at daytime in the summer
|
||||||
$ ./vik1 a Run track 1 at daytime in the winter
|
./vik1 a Run track 1 at daytime in the winter
|
||||||
$ ./vik1 d Run track 1 at night in the summer
|
./vik1 d Run track 1 at night in the summer
|
||||||
$ ./vik1 3 Run track 3 at daytime in the summer
|
./vik1 3 Run track 3 at daytime in the summer
|
||||||
$ ./vik1 d3 Run track 3 at night in the summer
|
./vik1 d3 Run track 3 at night in the summer
|
||||||
$ ./vik1 ad2 Run track 2 at night in the winter
|
./vik1 ad2 Run track 2 at night in the winter
|
||||||
```
|
```
|
||||||
|
|
||||||
Note that the order in which the argument characters are entered is
|
Note that the order in which the argument characters are entered is
|
||||||
|
|||||||
@@ -200,16 +200,16 @@ order as described below.</p>
|
|||||||
|
|
||||||
a - Advanced racing in a winter landscape
|
a - Advanced racing in a winter landscape
|
||||||
d - Racing in at night in the dark
|
d - Racing in at night in the dark
|
||||||
# - Race track selection 1-3 are valid numbers</code></pre>
|
# - Race track selection 1-3 are valid numbers</code></pre>
|
||||||
<p>Here are a few examples:</p>
|
<p>Here are a few examples:</p>
|
||||||
<pre><code> Command line: Description:
|
<pre><code> Command line: Description:
|
||||||
|
|
||||||
$ ./vik1 Run track 1 at daytime in the summer
|
./vik1 Run track 1 at daytime in the summer
|
||||||
$ ./vik1 a Run track 1 at daytime in the winter
|
./vik1 a Run track 1 at daytime in the winter
|
||||||
$ ./vik1 d Run track 1 at night in the summer
|
./vik1 d Run track 1 at night in the summer
|
||||||
$ ./vik1 3 Run track 3 at daytime in the summer
|
./vik1 3 Run track 3 at daytime in the summer
|
||||||
$ ./vik1 d3 Run track 3 at night in the summer
|
./vik1 d3 Run track 3 at night in the summer
|
||||||
$ ./vik1 ad2 Run track 2 at night in the winter</code></pre>
|
./vik1 ad2 Run track 2 at night in the winter</code></pre>
|
||||||
<p>Note that the order in which the argument characters are entered is
|
<p>Note that the order in which the argument characters are entered is
|
||||||
important. It is for example not possible to type <code>./vik1 da</code>. (Well it is
|
important. It is for example not possible to type <code>./vik1 da</code>. (Well it is
|
||||||
possible, but the result will not be as expected.)</p>
|
possible, but the result will not be as expected.)</p>
|
||||||
|
|||||||
Reference in new issue
Block a user