Fix use of test-case

1 files changed, 1 insertions, 1 deletions

diff --git a/method.tex b/method.tex
index a06b2a0..4cc52be 100644
--- a/method.tex
+++ b/method.tex
@@ -194,7 +194,7 @@ To ensure that our testing scales to a large number of large programs, we enforc
 %In cases where simulation takes longer, we do not consider them as failures or crashes and we record them. 
 % When testing Intel HLS, we place three time-outs since its execution is generally slower than other HLS tools: a \ref{XX}-minute time-out for C compilation, a \ref{XX}-hour time out for HLS compilation and a \ref{XX}-hour time-out for co-simulation. 
 
-%  And the number of timeouts placed has increased to 4. The first timeout sets when compiling the C++ program to CPU and returning an executable once finished. The second timeout is placed when running the executable to get the C++ result. The third timeout, which been given the most extended period, is at synthesizing the design and generating the co-simulation executable. Finally, running the co-simulation executable requires the fourth timeout. The test case can be dumped at any timeout period if the task is not finished within the limited time.
+%  And the number of timeouts placed has increased to 4. The first timeout sets when compiling the C++ program to CPU and returning an executable once finished. The second timeout is placed when running the executable to get the C++ result. The third timeout, which been given the most extended period, is at synthesizing the design and generating the co-simulation executable. Finally, running the co-simulation executable requires the fourth timeout. The test-case can be dumped at any timeout period if the task is not finished within the limited time.
 
 \subsection{Reducing buggy programs}\label{sec:method:reduce}