test: uninit: typo

[model-checker.git] / README.md

diff --git a/README.md b/README.md
index 23492ebfc671a0873dd58fe4091e11526adf9161..ea3b2423753bf3698ca3d280187ce63c3bea8261 100644 (file)
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ eliminate redundant executions to significantly shrink the state space.
 The model checking algorithm is described in more detail in this paper
 (currently under review):
 
-  [http://demsky.eecs.uci.edu/publications/c11modelcheck.pdf](http://demsky.eecs.uci.edu/publications/c11modelcheck.pdf)
+  <http://demsky.eecs.uci.edu/publications/c11modelcheck.pdf>
 
 It is designed to support unit tests on concurrent data structure written using
 C11/C++11 atomics.
@@ -40,7 +40,7 @@ flavors. We have not attempted to port to Windows.
 
 Other references can be found at the main project page:
 
-  [http://demsky.eecs.uci.edu/c11modelchecker.php](http://demsky.eecs.uci.edu/c11modelchecker.php)
+  <http://demsky.eecs.uci.edu/c11modelchecker.php>
 
 Basic build and run
 -------------------
@@ -104,18 +104,18 @@ SC
 
 
 Note that we also provide a series of benchmarks (distributed separately),
-which can be placed under the benchmarks/ directory. After building CDSChecker,
+which can be placed under the `benchmarks/` directory. After building CDSChecker,
 you can build and run the benchmarks as follows:
 
         cd benchmarks
         make
         ./run.sh barrier/barrier -y -m 2     # runs barrier test with fairness/memory liveness
-        ./bench.sh                           # run all benchmarks twice, with timing results
+        ./bench.sh                           # run all benchmarks and provide timing results
 
 Running your own code
 ---------------------
 
-We provide several test and sample programs under the test/ directory, which
+We provide several test and sample programs under the `test/` directory, which
 should compile and run with no trouble. Of course, you likely want to test your
 own code. To do so, you need to perform a few steps.