seoz pushed a commit to branch master.

commit 3b9f8e48471179da7f751bf696f9f27b39a720df
Author: Daniel Juyung Seo <[email protected]>
Date:   Tue Apr 2 16:25:51 2013 +0900

    Ecore.h: fixed ecore documentation.
---
 src/lib/ecore/Ecore.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/lib/ecore/Ecore.h b/src/lib/ecore/Ecore.h
index 6a5e3e3..78cfd3d 100644
--- a/src/lib/ecore/Ecore.h
+++ b/src/lib/ecore/Ecore.h
@@ -2221,7 +2221,7 @@ typedef void (*Ecore_Thread_Notify_Cb)(void *data, 
Ecore_Thread *thread, void *m
  * so here it's safe to use anything from the EFL freely.
  *
  * The thread can also be cancelled before its completion calling
- *ecore_thread_cancel(), either from the main thread or @p func_blocking.
+ * ecore_thread_cancel(), either from the main thread or @p func_blocking.
  * In this case, @p func_cancel will be called, also from the main thread
  * to inform of this happening. If the thread could not be created, this
  * function will be called and it's @c thread parameter will be NULL. It's
@@ -2268,7 +2268,7 @@ EAPI Ecore_Thread *ecore_thread_run(Ecore_Thread_Cb 
func_blocking, Ecore_Thread_
  * be called from the main thread for every message sent from @p func_heavy
  * with ecore_thread_feedback().
  *
- * Like with ecore_thread_run(), a new thread will be launched to run
+ * Like ecore_thread_run(), a new thread will be launched to run
  * @p func_heavy unless the maximum number of simultaneous threads has been
  * reached, in which case the function will be scheduled to run whenever a
  * running task ends and a thread becomes free. But if @p try_no_queue is

-- 

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2

Reply via email to