aboutsummaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-06-13 00:23:52 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-06-13 00:29:01 +0100
commitbedfe761bb6bb8f1fc0976b069593b45bdf2a25a (patch)
tree7d2825f4949e6cff5209de425861ad8a5c7ee53c /paper.tex
parent7009163a8bc55df553de8c4764b4b7aee43ffa0b (diff)
Two small edits in demo listing and paragraph after it
Recently, by default, Maneage will not take the title directly in the PDF, the title should be given in the 'metdata.conf' file and it is passed onto LaTeX as a variable. So the comment to "add project title" in the listing could be confusing. To avoid confusing, I edited it to "Set your name as author". The comments above the '\title' part is very complete and users will clearly be able to modify the title if they want. Also, we had an extra ')' in the line just under it which is now corrected.
Diffstat (limited to 'paper.tex')
-rw-r--r--paper.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/paper.tex b/paper.tex
index e788b06..e4347fd 100644
--- a/paper.tex
+++ b/paper.tex
@@ -383,12 +383,12 @@ $ ./project configure # Build software environment.
$ ./project make # Do analysis, build PDF paper.
# Start editing, test-building and committing
-$ emacs paper.tex # e.g., add project title.
+$ emacs paper.tex # Set your name as author.
$ ./project make # Re-build to see effect.
-$ git add -u && git commit # Commit changes
+$ git add -u && git commit # Commit changes.
\end{lstlisting}
-The branch-based design of Figure \ref{fig:branching}) allows projects to re-import Maneage at a later time (technically: \emph{merge}), thus improving its low-level infrastructure:
+The branch-based design of Figure \ref{fig:branching} allows projects to re-import Maneage at a later time (technically: \emph{merge}), thus improving its low-level infrastructure:
in (a) authors do the merge during an ongoing project;
in (b) readers do it after publication, e.g., the project remains reproducible but the infrastructure is outdated, or a bug is fixed in Maneage.
Low-level improvements in Maneage can thus propagate to all projects, greatly reducing the cost of curation and maintenance of each individual project, before \emph{and} after publication.