From 2d59f92d69b86d5af3d2cb8fa7d56937d3bc14c1 Mon Sep 17 00:00:00 2001
From: Oren <oren_segal@student.uml.edu>
Date: Mon, 2 Mar 2015 04:49:07 +0000
Subject: [PATCH] Update binary flow doc

---
 docs/AparapiUcoresBinaryFlow.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/AparapiUcoresBinaryFlow.txt b/docs/AparapiUcoresBinaryFlow.txt
index b6a921ab..f40b79c3 100644
--- a/docs/AparapiUcoresBinaryFlow.txt
+++ b/docs/AparapiUcoresBinaryFlow.txt
@@ -4,7 +4,9 @@ Aparapi Ucores Binary Flow
 This is currently used only for FPGAs but we plan to expand it for general manual optimization/compilation of OpenCL source code.
 
 A Binary flow is one where the Aparapi framework generates an OpenCL file while running and then tries to read and execute the binary compilation of that source file.
+
 Sequence of events
+------------------
 
 1. Aparapi Application is executed. Aparapi automatically generates an OpencL source file describing the kernel(file name is the full java kernel class name.cl)
 
@@ -29,6 +31,4 @@ Example:
 
 	3. Copy the binary output file (ClassXXXName.aocx) to folder where the .cl file resides.
 
-4. Run application again in ACC/GPU mode. This time Aparapi will detect the ClassXXXName.aocx and use the FPGA as the acclerator.
-
-
+4. Run application again in ACC/GPU mode. This time Aparapi will detect the ClassXXXName.aocx and use the FPGA as the acclerator.
\ No newline at end of file
-- 
GitLab