1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 2fa4d2c..5a2d641 100644
--- a/README.md
+++ b/README.md
@@ -22,10 +22,12 @@ They are designed with the following principles in mind:
 These scripts were tested using Python 2.7.2. They have not been tested using Python 3. The [Matplotlib][matplotlib] Python library is needed for plotting.
 The `run_exps.py` script should almost always be run using a LITMUS^RT kernel. In addition to the kernel, the following LITMUS-related repos must be in the user's `PATH`:
 1. [liblitmus][liblitmus]: for real-time executable simulation and task set release
 2. [feather-trace-tools][feather-trace-tools]: for recording and parsing overheads and scheduling events
 Additional features will be enabled if these repos are present in the `PATH`:
 1. [rt-kernelshark][rt-kernelshark]: to record ftrace events for kernelshark visualization
 2. sched_trace ([UNC internal][rtunc]) to output a file containing scheduling events as strings

diff --git a/README.md b/README.md index 2fa4d2c..5a2d641 100644 --- a/README.md +++ b/README.md
@@ -22,10 +22,12 @@ They are designed with the following principles in mind:
22	These scripts were tested using Python 2.7.2. They have not been tested using Python 3. The [Matplotlib][matplotlib] Python library is needed for plotting.	22	These scripts were tested using Python 2.7.2. They have not been tested using Python 3. The [Matplotlib][matplotlib] Python library is needed for plotting.
23		23
24	The `run_exps.py` script should almost always be run using a LITMUS^RT kernel. In addition to the kernel, the following LITMUS-related repos must be in the user's `PATH`:	24	The `run_exps.py` script should almost always be run using a LITMUS^RT kernel. In addition to the kernel, the following LITMUS-related repos must be in the user's `PATH`:
		25
25	1. [liblitmus][liblitmus]: for real-time executable simulation and task set release	26	1. [liblitmus][liblitmus]: for real-time executable simulation and task set release
26	2. [feather-trace-tools][feather-trace-tools]: for recording and parsing overheads and scheduling events	27	2. [feather-trace-tools][feather-trace-tools]: for recording and parsing overheads and scheduling events
27		28
28	Additional features will be enabled if these repos are present in the `PATH`:	29	Additional features will be enabled if these repos are present in the `PATH`:
		30
29	1. [rt-kernelshark][rt-kernelshark]: to record ftrace events for kernelshark visualization	31	1. [rt-kernelshark][rt-kernelshark]: to record ftrace events for kernelshark visualization
30	2. sched_trace ([UNC internal][rtunc]) to output a file containing scheduling events as strings	32	2. sched_trace ([UNC internal][rtunc]) to output a file containing scheduling events as strings
31		33