aboutsummaryrefslogtreecommitdiff
path: root/reproduce
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-01-11 15:26:12 +0000
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-01-11 15:26:12 +0000
commitf92bef4546eebe068363b5afb82a6fffe07565eb (patch)
tree592c3d54a6e030dd5bcd14502091f2e2df60933a /reproduce
parent7cc80b3b9a2eebf5286a983df3ebaf3952ea6fca (diff)
Corrected markdown code notations in one README.md
In markdown, to specify that part of the text should be shown as code we need to put it between two `. But in `reproduce/software/make/README.md', the code parts started with ` and finished in ' (like the file name above). With this commit, this has been corrected and it will display properly on web browsers.
Diffstat (limited to 'reproduce')
-rw-r--r--reproduce/software/make/README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/reproduce/software/make/README.md b/reproduce/software/make/README.md
index 4eaefce..fc04dfb 100644
--- a/reproduce/software/make/README.md
+++ b/reproduce/software/make/README.md
@@ -2,12 +2,12 @@ Software building instructions
==============================
This directory contains Makefiles that are called by the high-level
-`reproduce/software/bash/configure.sh' script. The main target for the
+`reproduce/software/bash/configure.sh` script. The main target for the
installation of each software is a simple plain text file that contains the
name of the software and its version (which is put in the paper in the
end). Once built, these plain-text files are all put in the proper
-sub-directory under `$(BDIR)/software/installed/version-info' (where
-`$(BDIR)' is the top-level build-directory specified by the user).
+sub-directory under `$(BDIR)/software/installed/version-info` (where
+`$(BDIR)` is the top-level build-directory specified by the user).
Besides being directly used in the paper, these simple plain text files
also act as prerequisites for higher-level software that depend on
@@ -16,7 +16,7 @@ lower-level ones.
Note on prerequisites
---------------------
-Tarballs are order-only prerequsites (after a `|') because we already
+Tarballs are order-only prerequsites (after a `|`) because we already
check their contents with the checksums, so their date is irrelevant: a
tarball with a different content must have a new/different name, thus it
will not exist, so it will be created, even when its order-only.q